Two Camera simultaneous usage - Issues and Questions

[s3igell]

This past weekend, I had another chance to setup and test the Two BYE Camera Support - at a Dark Site where I could actually expect my Guiders to find Guide Stars and I had 3 nights to "tweak the setup".

 

BYE is making some real progress in this challenging configuration.

1) Multiple Camera Instances could Connect and Control separate Cameras

2) All Image Capture and Download functions work

 

But, I was still unable to connect BYEOS to separate PHD2 Guider instances.  Both BYE instances communicated to the same (first) PHD2 instance. This is to be expected as the default - even for the Camera2 instance - is to connect to "localhost".  I still (see this older posting - howto-setup-backyardeos-to-use-two-2-cameras) couldn't get BYE to recognize "localhost:4301" or any other attempted variant to connect to "any" PHD2 Server Instance.  But then, I couldn't confirm if this was a BYE or PHD2 issue, as despite OpenPHDGuiding team assurances, I couldn't get the 2nd instance of PHD2 to start without a "server failed" message - (I'm posting that issue to their site).

 

What IS the proper BYE Setting entry to specify the 2nd PHD2 Server Instance ??

 

 

 

[s3igell]

Update:

After the above tests, BYE failed with a "Program has stopped working" popup from Win7.

 

 

After restarting the BYE Session, and retesting...  Success for "localhost"; Success for "localhost:4300"; AND...  

 

Success for "localhost:4301" when running a 2nd PHD2 Instance ("phd2.exe -i 2")!!  

I even got it to perform a Dither (at least the PHD Graph marked a Dither on the Simulator of the 2nd PHD2 Instance)!!

 

Now, if only it had done that successfully during my 3 Dark Dark Nights at the All-Arizona Star Party!!  I'd have been ecstatic!!

(Instead, I settled for mere "Quite Pleased" that I was able to run 2 DSLRs and 2 Guiders on separate Mounts with 1 Dithered and the other not...)

[admin]

This past weekend, I had another chance to setup and test the Two BYE Camera Support - at a Dark Site where I could actually expect my Guiders to find Guide Stars and I had 3 nights to "tweak the setup".

 

BYE is making some real progress in this challenging configuration.

1) Multiple Camera Instances could Connect and Control separate Cameras

2) All Image Capture and Download functions work

 

But, I was still unable to connect BYEOS to separate PHD2 Guider instances.  Both BYE instances communicated to the same (first) PHD2 instance. This is to be expected as the default - even for the Camera2 instance - is to connect to "localhost".  I still (see this older posting - howto-setup-backyardeos-to-use-two-2-cameras) couldn't get BYE to recognize "localhost:4301" or any other attempted variant to connect to "any" PHD2 Server Instance.  But then, I couldn't confirm if this was a BYE or PHD2 issue, as despite OpenPHDGuiding team assurances, I couldn't get the 2nd instance of PHD2 to start without a "server failed" message - (I'm posting that issue to their site).

 

What IS the proper BYE Setting entry to specify the 2nd PHD2 Server Instance ??

 

 

 

Is there a place in PHD to choose a port it listen to?  If yes make sure each BYE instance have to correct port.

 

Regards,

[s3igell]

PHD2 sets up a Port to listen for each Instance - starting at 4300 for 1st Instance, 4301 for 2nd, 4302 for 3rd, etc.  (At least it is supposed to, but I can't figure how to specify the Port value in the BYE Settings.)

 

As a test, I use the settings "PHD Guider 'Test'" button while having one instance of PHD2 v2.3.1 running with "Enable Server":

If I use "localhost" as the "Host IP", I get "Success".

If I use "localhost:4300" as the "Host IP", I get "Error" (after the same amount of time expired as the first test).

If I use "localhost::4300" as the "Host IP", I get "Error" (after the same amount of time expired as the first test).

If I use "localhost:4400" as the "Host IP" (PHD's base port for their newer JSON protocol), I get "Error" (after the same amount of time expired as the first test).

 

What is the proper way to stipulate a Port Number in this BYE Setting entry ??

Back upon the initial posting of v3.1.0 RC01 on 7/7/14, you had an acknowledged issue with parsing of "localhost:4300" even though that was the then default for that just released RC), but you never responded (it was rather hectic times for you) with what would be the proper way to specify a Port number within that BYE setting.

 

 

[admin]

PHD2 sets up a Port to listen for each Instance - starting at 4300 for 1st Instance, 4301 for 2nd, 4302 for 3rd, etc.  (At least it is supposed to, but I can't figure how to specify the Port value in the BYE Settings.)

 

As a test, I use the settings "PHD Guider 'Test'" button while having one instance of PHD2 v2.3.1 running with "Enable Server":

If I use "localhost" as the "Host IP", I get "Success".

If I use "localhost:4300" as the "Host IP", I get "Error" (after the same amount of time expired as the first test).

If I use "localhost::4300" as the "Host IP", I get "Error" (after the same amount of time expired as the first test).

If I use "localhost:4400" as the "Host IP" (PHD's base port for their newer JSON protocol), I get "Error" (after the same amount of time expired as the first test).

 

What is the proper way to stipulate a Port Number in this BYE Setting entry ??

Back upon the initial posting of v3.1.0 RC01 on 7/7/14, you had an acknowledged issue with parsing of "localhost:4300" even though that was the then default for that just released RC), but you never responded (it was rather hectic times for you) with what would be the proper way to specify a Port number within that BYE setting.

 

 

Are you using 3.1?

 

Regards,

[admin]

In 3.1 "localhost:4300" should work.

 

Regards,

[s3igell]

Tested using v3.1.0-rc5...

 

"localhost:4300" fails the Test, while "localhost" results in "Success".

As well, on the PHD2 v2.3.1 side, the status bar shows "New Connection" for the latter, but no change for the former...

[admin]

I just tried "localhost:4300" with PHD 2 and it worked.

 

Send me the log files.