Dual Camera Mode doesn't run Camera 2's plan

[XCalRocketMan]

I've attached two Canon cameras, a 50D and a 70D. Both use USB cables to connect.  I have two instances of BYE 3.1.11 running; the master (50D) and the provided slave (Camera 2, 70D).  Both cameras connect and both operate from their respective BYE instances.  I set Dual Camera on the master instance to connect to localhost:1502 and verify that the Camera 2 instance is, in fact, on 1502.  Each camera has a different plan. When I press 'Start Capture' on the master instance the cameras start to image fine, but, the 70D does not follow its plan, but appears to be using the master's plan settings. Number of images, ISO setting and Shutter Speed are mirrored on the slave.

[admin]

would the slave instance camera have mirror lock enabled by any chance?

[XCalRocketMan]

Nope.  Checked that.  And I also noticed that the f/stop ISN'T changed, just the shutter speed and the ISO value.  The f/stop isn't even the one specified in the plan, but appears to be the one last used on the camera.

 

Edited July 4, 2017 by XCalRocketMan

[admin]

ummm... Can you try with 3.1.9 and see if it makes a difference.  If yes I think I might know the cause.

[XCalRocketMan]

No luck - still the same.

[admin]

send me the log files for both instances.

[XCalRocketMan]

Here are the two logs of the same plans run with 3.1.9  and 3.1.11.

The 50D (master) was to take 2 images at 1/1000 f2.8 Iso1600 followed by 1 at 1/500 f3.5 Iso800.

The 70D (slave) was to take 1 image at 1/200 f4.0 Iso1000 followed by 2 images at 1/100 f8.0 Iso1250

 

logfile-[20170704-10h45m24s609]-[2036]-2017-07-04.txt

logfile-[20170704-18h22m50s986]-[8696]-2017-07-04.txt

[admin]

Both these logfiles are for the 50D and the master instance.  I need the slave and the master instance where you try the dual camera feature.

Regards,

[XCalRocketMan]

Sorry bout that.  here are the 70D files 

logfile-[20170704-10h47m26s681]-[10436]-2017-07-04.txt

logfile-[20170704-18h23m08s961]-[12796]-2017-07-04.txt

[admin]

Thanks for the log file... however... it seems to work and the slave instance *does* follow the master plan.

 

MASTER -> 2017-07-04 18:24:16,522 [MoveFile(Normal)] INFO  - moved to C:\BackyardEOS_Images\50D\LIGHT_Tv11000s_1600iso_f2-8_+22c_20170704-18h24m10s225ms.CR2
SLAVE  -> 2017-07-04 18:24:13,732 [MoveFile(Normal)] INFO  - moved to C:\BackyardEOS_Images\70D\LIGHT_Tv11000s_1600iso_f5-0_+22c_20170704-18h24m07s333ms.CR2

MASTER -> 2017-07-04 18:24:27,935 [MoveFile(Normal)] INFO  - moved to C:\BackyardEOS_Images\50D\LIGHT_Tv11000s_1600iso_f2-8_+21c_20170704-18h24m22s062ms.CR2
SLAVE -> 2017-07-04 18:24:25,397 [MoveFile(Normal)] INFO  - moved to C:\BackyardEOS_Images\70D\LIGHT_Tv11000s_1600iso_f5-0_+22c_20170704-18h24m19s225ms.CR2

 

Can you elaborate what you meant in your original post... " 'Start Capture' on the master instance the cameras start to image fine, but, the 70D does not follow its plan, but appears to be using the master's plan settings. Number of images, ISO setting and Shutter Speed are mirrored on the slave."

The entire idea to master / slave is exactly that, for the slave to take it's exposure setting, including settings such as ISO and duration to be driven by the master plan.  The slave plan in ignored; this is by design.

Regards,

[XCalRocketMan]

Argh.  OK, my bad. I totally missed the bubble on this one!!  I get it now. No issues.  Sorry to have wasted your time on this

But, I am purchasing the software as it seems very powerful and easy to use.

[astroman133]

Sorry to jump in late here.

If I understand you are running two instances of BYE with 2 different capture plans. In this case there is no benefit from synchronization so you should not set up the Master/Slave relationship. Simply start each capture plan at the appropriate time.

The Master/Slave relationship is for the case where you want to synchronize the imaging plans for 2 or more cameras on the same mount so that you can dither between exposures. This is only possible if both instances of BYE are running the same capture plan (as defined in the Master instance of BYE) at the same time (are synchronized). That way when both cameras are finished with the exposure dithering can occur and then the capture of the next exposure can be started.

[Szumi]

Would it be possible to put in a wait command so the master will run the plan until it hits a wait # instruction while the slave does its own plan using different exposures continuing until it hits the same  wait# command.  When both cameras are waiting on the same wait number, do a dither then continue.

[admin]

55 minutes ago, Szumi said:

Would it be possible to put in a wait command so the master will run the plan until it hits a wait # instruction while the slave does its own plan using different exposures continuing until it hits the same  wait# command.  When both cameras are waiting on the same wait number, do a dither then continue.

Please start a new thread... you are replying to a 3 year old thread and your suggestion is not related to the original reported issue.

I don't understand your request... the slave is already waiting for a command from the master.  If your master does the dithering then it won't send the command to the slave until dither is complete on the master instance.