Closed timsainb closed 2 years ago
I think what you are describing are two different issues, so I'll try to answer them separately.
Writing this I realize that the software should definitely check the Trigger Mode configuration of all cameras at the start of a recording, I'll add that to the TODO list for the next release.
As always, thanks for all the detailed bug reports and please let me know if this helps in resolving those two issues.
Ok, for the capture not starting, I think you are right, it is an arduino issue. All I had to do was unplug and replug and then reinitialize the trigger in the GUI and things work fine again.
For posterity and anyone in the future having this issue, here is a sample of the readout I get when this is happening:
[Acquisition is running w/o trigger]
T: 371
FL: 478
FR: 523
T: 355
FR: 309
FL: 383
T: 457
FR: 303
FL: 514
T: 356
FR: 400
T: 382
[press pause]
Trying to stop Acquisition
FL: 1700
stopped Worker
FL: 415
FR: 827
FL: 414
FR: 748
FR: 339
FL: 376
FR: 375
FL: 398
FR: 389
FL: 376
FR: 1007
FR: 394
FL: 773
FR: 456
FL: 418
FR: 460
FL: 477
FR: 513
FL: 541
FR: 563
FL: 434
FR: 465
FL: 399
FR: 315
FL: 507
FR: 443
FL: 534
FR: 542
FL: 643
FR: 1894
FR: 417
FL: 552
FR: 416
FL: 555
Trying to stop Acquisition
FR: 411
stopped Worker
FL: 599
FL: 534
FL: 770
FL: 392
FL: 657
FL: 358
FL: 386
FL: 333
FL: 359
FL: 388
FL: 526
FL: 519
FL: 368
FL: 384
Trying to stop Acquisition
stopped Worker
[Switch to arduino trigger]
VALUE: FrameBurstStart
VALUE: Off
VALUE: On
VALUE: Line3
VALUE: ReadOut
VALUE: Off
VALUE: On
VALUE: Line3
VALUE: ReadOut
VALUE: On
VALUE: Off
VALUE: Line3
VALUE: ReadOut
VALUE: Off
VALUE: On
VALUE: Line3
VALUE: ReadOut
VALUE: Off
VALUE: On
VALUE: Line3
VALUE: ReadOut
VALUE: Off
ttyACM0
VALUE: Default
VALUE: On
VALUE: FrameStart
VALUE: Line3
VALUE: Off
VALUE: BayerRG8
VALUE: Off
VALUE: Off
VALUE: Default
VALUE: On
VALUE: FrameStart
VALUE: Line3
VALUE: Off
VALUE: BayerRG8
VALUE: Off
VALUE: Off
VALUE: Default
VALUE: On
VALUE: FrameStart
VALUE: Line3
VALUE: Off
VALUE: BayerRG8
VALUE: Off
VALUE: Off
VALUE: Default
VALUE: On
VALUE: FrameStart
VALUE: Line3
VALUE: Off
VALUE: BayerRG8
VALUE: Off
VALUE: Off
VALUE: Default
VALUE: On
VALUE: FrameStart
VALUE: Line3
VALUE: Off
VALUE: BayerRG8
VALUE: Off
VALUE: Off
2
acquisitionSpecs2
[Try playing and pausing a few times]
Trying to stop Acquisition
stopped Worker
Trying to stop Acquisition
stopped Worker
Trying to stop Acquisition
stopped Worker
Trying to stop Acquisition
stopped Worker
Trying to stop Acquisition
stopped Worker
The not stopping issue hasn't happened to me again but I'll try to dig deeper next time it does.
I haven't reproduced this issue in a while so I'll close this.
It's a bit hard to describe this bug because I don't know exactly what's going on.
Sometimes when starting AcquisitionTool up, I am unable to get the arduino acquisition working. Terminal says it is starting acquisition, but no frames are captured. When I switch over to non-arduino acquisition, the cameras work fine. To fix the problem, I unplug all of the USBs as well as the arduino, reboot the computer, and re-create the camera settings defaults. I haven't been able to localize the problem to any one component so I just reinitialize them all.
I also have had trouble with the cameras continuing to acquire after pressing pause or stop, which freezes the GUI. Maybe these two are related, and the arduino gets stuck in a loop and needs to be rebooted to communicate with the GUI again.