Good morning all, I am hoping someone might be able to help me out here a bit. I have a Celestron C5, thus no commercially available auto focuser. I am working on assembling the Myfocuserpro2 system and have the main Arduino connected to my astroberry via USB. Tests on the Arduino with my windows laptop and the control software indicate that the controller board is working and responding to commands. The remainder of the electronics are not connected yet, but I wanted to ensure it could connect to the astroberry before I went to crazy. Mosquito and blackfly season are right around the corner here, so remote control is a real interest to me...
When I set it up in INDI, this is what I am seeing:
INFO 35.123348 sec : Session log file /home/astroberry/.indi/logs/2021-04-20/indi_myfocuserpro2_focus/indi_myfocuserpro2_focus_13:05:51.log
ERROR 45.259544 sec : Handshake Attempt 1, updatePosition response error: Timeout error.
ERROR 49.260228 sec : Handshake Attempt 2, updatePosition response error: Timeout error.
ERROR 53.263551 sec : Handshake Attempt 3, updatePosition response error: Timeout error.
INFO 53.263693 sec : Handshake failed after 3 attempts
INFO 53.263754 sec : Error retrieving data from MyFocuserPro2, please ensure MyFocuserPro2 controller is powered and the port is correct.
Has anybody run into this issue before?
Cheers!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I would like you to test out your focus controller using the Windows application. Please just humor me on this.
I want to know if it is a focus controller problem or an INDI problem, and getting you to use the Windows application is a good way to identify issues.
I hope that you are running the latest firmware because the INDI driver requires updated firmware to work.
If you run it under Windows and everything appears fine, the +500 and -500 work, halt works then it would tell me the controller appears ok and that it could be an INDI issue
What I can tell u is that v307 of the firmware is soon to be released and has a few changes which makes it more compatible with the INDI driver. That release is about a week away.
Please let me know the results of your testing with Windows
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Sure thing! So I did exactly that. It does communicate with the native
application just fine. To take it one step further, I downloaded the trial
version of sequence generator pro and let that have a crack at it with
windows based ASCOM and it wont connect to it either. Just for kicks, I
also installed the firmware on an arduino uno (genuine) just because my
nano is a knockoff, and still no connection. The firmware I have loaded is
the 176 version that is currently available on the SF site that I just
downloaded a few days ago.
But, and perhaps this is behind the issue, I have not really done any
specific setup for my system yet. I simply loaded the firmware in an
attempt to test the connection. I am waiting for some parts to arrive this
saturday to begin setting up the prototyping so no hardware is really
connected yet, therefore, no real configuration has been done. Is there a
possibility this could be a part of the issue?
I would like you to test out your focus controller using the Windows
application. Please just humor me on this.
I want to know if it is a focus controller problem or an INDI problem, and
getting you to use the Windows application is a good way to identify issues.
I hope that you are running the latest firmware because the INDI driver
requires updated firmware to work.
If you run it under Windows and everything appears fine, the +500 and -500
work, halt works then it would tell me the controller appears ok and that
it could be an INDI issue
What I can tell u is that v307 of the firmware is soon to be released and
has a few changes which makes it more compatible with the INDI driver. That
release is about a week away.
Please let me know the results of your testing with Windows
You programmed the controller with
myFocuserPro v1xx firmware
You then attempted to use a myFocuserPro2 ASCOM driver with it. That will fail,
try using a myFocuserPro ASCOM driver
myFocuserPro and myFocuserPro2 are two completely different products.
Note:
myFocuserPro refers to v1xx of the myFocuserPro products. This was the first design and works with the Moonlite drivers, so can be supported on the Mac (tested on MacBook with TheSky and Moonlite drivers) and Linux systems (tested with the INDI Moonlite driver under Ubuntu and Ekos)
myFP2 refers to v2xx of the myFocuserPro2 products. This design is v2 and is NOT compatible with Mac and Linux systems. Version 2 controllers do have a number of additional features that are not available on the v1 design and use a different protocol. You cannot use v2xx ASCOM or Windows software with a v1xx programmed controller or vice-versa.
Both systems are supported by either a V1 or V2 Windows application and ASCOM drivers.
If you have built a v1xx controller, and want to upgrade to v2xx ASCOM drivers and Windows application, this is easy. Simply load the equivalent v2xx firmware into the controller and use the supplied v2 ASCOM drivers and v2 Windows application.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I knew it had to be something simple... I re flashed the controller with the 305 firmware and all is communicating now. ** I'm sure I am not the first to say, but you have done a really great job with this project.** Thank you for all your efforts and to any who have contributed! A donation will be coming your way shortly!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Good morning all, I am hoping someone might be able to help me out here a bit. I have a Celestron C5, thus no commercially available auto focuser. I am working on assembling the Myfocuserpro2 system and have the main Arduino connected to my astroberry via USB. Tests on the Arduino with my windows laptop and the control software indicate that the controller board is working and responding to commands. The remainder of the electronics are not connected yet, but I wanted to ensure it could connect to the astroberry before I went to crazy. Mosquito and blackfly season are right around the corner here, so remote control is a real interest to me...
When I set it up in INDI, this is what I am seeing:
INFO 35.123348 sec : Session log file /home/astroberry/.indi/logs/2021-04-20/indi_myfocuserpro2_focus/indi_myfocuserpro2_focus_13:05:51.log
ERROR 45.259544 sec : Handshake Attempt 1, updatePosition response error: Timeout error.
ERROR 49.260228 sec : Handshake Attempt 2, updatePosition response error: Timeout error.
ERROR 53.263551 sec : Handshake Attempt 3, updatePosition response error: Timeout error.
INFO 53.263693 sec : Handshake failed after 3 attempts
INFO 53.263754 sec : Error retrieving data from MyFocuserPro2, please ensure MyFocuserPro2 controller is powered and the port is correct.
Has anybody run into this issue before?
Cheers!
I would like you to test out your focus controller using the Windows application. Please just humor me on this.
I want to know if it is a focus controller problem or an INDI problem, and getting you to use the Windows application is a good way to identify issues.
I hope that you are running the latest firmware because the INDI driver requires updated firmware to work.
If you run it under Windows and everything appears fine, the +500 and -500 work, halt works then it would tell me the controller appears ok and that it could be an INDI issue
What I can tell u is that v307 of the firmware is soon to be released and has a few changes which makes it more compatible with the INDI driver. That release is about a week away.
Please let me know the results of your testing with Windows
Sure thing! So I did exactly that. It does communicate with the native
application just fine. To take it one step further, I downloaded the trial
version of sequence generator pro and let that have a crack at it with
windows based ASCOM and it wont connect to it either. Just for kicks, I
also installed the firmware on an arduino uno (genuine) just because my
nano is a knockoff, and still no connection. The firmware I have loaded is
the 176 version that is currently available on the SF site that I just
downloaded a few days ago.
But, and perhaps this is behind the issue, I have not really done any
specific setup for my system yet. I simply loaded the firmware in an
attempt to test the connection. I am waiting for some parts to arrive this
saturday to begin setting up the prototyping so no hardware is really
connected yet, therefore, no real configuration has been done. Is there a
possibility this could be a part of the issue?
Best Regards!
GP
On Wed, Apr 21, 2021 at 7:27 AM brownrb brownrb@users.sourceforge.net
wrote:
HI, here is the results from the testing with the windows Pro focuser software. All was working well with it.
4/21/2021 10:25:25 AM: Disconnect START=================================================
4/21/2021 10:25:25 AM: Disconnect: Disconnecting
4/21/2021 10:25:25 AM: DisableAll START=================================================
4/21/2021 10:25:25 AM: DisableAll END===================================================
4/21/2021 10:25:25 AM: Disconnect END===================================================
4/21/2021 10:25:26 AM: Connect START=================================================
4/21/2021 10:25:26 AM: Connect: Setting readtimeout to 5000
4/21/2021 10:25:26 AM: Connect: START TIME NOW
4/21/2021 10:25:26 AM: Connect: Attempt to open serial port
4/21/2021 10:25:26 AM: Connect: Check if serial port opened
4/21/2021 10:25:26 AM: Connect: Comport=isOpen
4/21/2021 10:25:26 AM: Connect: Comport Opened, wait 3s
4/21/2021 10:25:26 AM: Connect: Opened Serial port COM3
4/21/2021 10:25:26 AM: Connect: Delay on Connect = 2
4/21/2021 10:25:28 AM: Connect: Get FirmwareVersion
4/21/2021 10:25:28 AM: Connect: sendcmd GF# to get version
4/21/2021 10:25:28 AM: Connect: response = myFP-A4998HW203
176#
4/21/2021 10:25:28 AM: Connect: Firmware = myFP-A4998HW203
176
4/21/2021 10:25:28 AM: Connect: Comport=connected
4/21/2021 10:25:28 AM: Connect: Send command = :GM#
4/21/2021 10:25:28 AM: Connect: response = 2710#
4/21/2021 10:25:28 AM: Connect: maxsteps = 10000
4/21/2021 10:25:28 AM: Connect: Send command = :GP#
4/21/2021 10:25:28 AM: Connect: response = 123C#
4/21/2021 10:25:28 AM: Connect: Position = 4668
4/21/2021 10:25:28 AM: Connect: Send command = :GY#
4/21/2021 10:25:28 AM: Connect: response = 2710#
4/21/2021 10:25:28 AM: Connect: maxIncrements = 10000
4/21/2021 10:25:28 AM: Connect: Send command = :GO#
4/21/2021 10:25:28 AM: Connect: response = 1#
4/21/2021 10:25:28 AM: Connect: CoilPower = 1
4/21/2021 10:25:28 AM: Connect: Send command = :GR#
4/21/2021 10:25:28 AM: Connect: response = 0#
4/21/2021 10:25:28 AM: Connect: Reverse Direction = 0
4/21/2021 10:25:28 AM: Connect: Send command = :GS#
4/21/2021 10:25:28 AM: Connect: response = 01#
4/21/2021 10:25:28 AM: Connect: Stepmode = 1
4/21/2021 10:25:28 AM: Connect: Send command = :FM#
4/21/2021 10:25:28 AM: Connect: response = 1#
4/21/2021 10:25:28 AM: Connect: Send command = :MS0#
4/21/2021 10:25:28 AM: Connect: Send command = :GX#
4/21/2021 10:25:29 AM: Connect: response = 09C4#
4/21/2021 10:25:29 AM: Connect: GX:2500
4/21/2021 10:25:29 AM: Connect: Send command = :MU#
4/21/2021 10:25:29 AM: Connect: response = 200#
4/21/2021 10:25:29 AM: Connect: MotorSpeedChangeValue = 200
4/21/2021 10:25:29 AM: Connect: Send command = :MW#
4/21/2021 10:25:29 AM: Connect: response = 0#
4/21/2021 10:25:29 AM: Connect: Motorspeedchange status : 0
4/21/2021 10:25:29 AM: Connect: Send command = :PQ#
4/21/2021 10:25:29 AM: Connect: response = 0#
4/21/2021 10:25:29 AM: Connect: Stepsize status : 0
4/21/2021 10:25:29 AM: Connect: Send command = :PG#
4/21/2021 10:25:29 AM: Connect: response = 10#
4/21/2021 10:25:29 AM: Connect: Temperature precision = 10
4/21/2021 10:25:29 AM: Connect: Send command = :PM0#
4/21/2021 10:25:29 AM: GetTemp: Send command : :GZ#
4/21/2021 10:25:29 AM: GetTemp: response = 20.000#
4/21/2021 10:25:29 AM: GetTemp: Temperature (adj) = 20
4/21/2021 10:25:29 AM: Connect: FINISH TIME NOW
4/21/2021 10:25:29 AM: EnableAll START=================================================
4/21/2021 10:25:29 AM: EnableAll END===================================================
4/21/2021 10:25:29 AM: Connect END===================================================
4/21/2021 10:26:02 AM: plus500: Start
4/21/2021 10:26:02 AM: movefocusercmd: =START=========================================================
4/21/2021 10:26:02 AM: movefocusercmd: Serial Port is Open
4/21/2021 10:26:02 AM: movefocusercmd: ConnectedState is true
4/21/2021 10:26:02 AM: movefocusercmd: Check if focuser is moving
4/21/2021 10:26:02 AM: movefocusercmd: response = 00#
4/21/2021 10:26:02 AM: movefocusercmd: ismoving is false, now Get Position
4/21/2021 10:26:02 AM: movefocusercmd: response = 123C#
4/21/2021 10:26:02 AM: movefocusercmd: Moving to = 5168
4/21/2021 10:26:02 AM: movefocusercmd: Check if focuser is moving
4/21/2021 10:26:02 AM: movefocusercmd: response = 01#
4/21/2021 10:26:02 AM: movefocusercmd: Focuser is moving
4/21/2021 10:26:03 AM: movefocusercmd: Re-Check if focuser is still moving
4/21/2021 10:26:04 AM: movefocusercmd: response = 01#
4/21/2021 10:26:04 AM: movefocusercmd: Focuser is moving
4/21/2021 10:26:05 AM: movefocusercmd: Re-Check if focuser is still moving
4/21/2021 10:26:05 AM: movefocusercmd: response = 01#
4/21/2021 10:26:05 AM: movefocusercmd: Focuser is moving
4/21/2021 10:26:06 AM: movefocusercmd: Re-Check if focuser is still moving
4/21/2021 10:26:06 AM: movefocusercmd: response = 01#
4/21/2021 10:26:06 AM: movefocusercmd: Focuser is moving
4/21/2021 10:26:07 AM: movefocusercmd: Re-Check if focuser is still moving
4/21/2021 10:26:07 AM: movefocusercmd: response = 01#
4/21/2021 10:26:07 AM: movefocusercmd: Focuser is moving
4/21/2021 10:26:08 AM: movefocusercmd: Re-Check if focuser is still moving
4/21/2021 10:26:08 AM: movefocusercmd: response = 01#
4/21/2021 10:26:08 AM: movefocusercmd: Focuser is moving
4/21/2021 10:26:09 AM: movefocusercmd: Re-Check if focuser is still moving
4/21/2021 10:26:09 AM: movefocusercmd: response = 01#
4/21/2021 10:26:09 AM: movefocusercmd: Focuser is moving
4/21/2021 10:26:10 AM: movefocusercmd: Re-Check if focuser is still moving
4/21/2021 10:26:10 AM: movefocusercmd: response = 00#
4/21/2021 10:26:10 AM: movefocusercmd: Focuser has stopped
4/21/2021 10:26:10 AM: movefocusercmd: Get Position
4/21/2021 10:26:10 AM: movefocusercmd: response = 1430#
4/21/2021 10:26:11 AM: movefocusercmd: Move completed
4/21/2021 10:26:11 AM: movefocusercmd: =END===========================================================
4/21/2021 10:26:11 AM: plus500: Stop
4/21/2021 10:26:29 AM: minus500: Start
4/21/2021 10:26:29 AM: movefocusercmd: =START=========================================================
4/21/2021 10:26:29 AM: movefocusercmd: Serial Port is Open
4/21/2021 10:26:29 AM: movefocusercmd: ConnectedState is true
4/21/2021 10:26:29 AM: movefocusercmd: Check if focuser is moving
4/21/2021 10:26:29 AM: movefocusercmd: response = 00#
4/21/2021 10:26:29 AM: movefocusercmd: ismoving is false, now Get Position
4/21/2021 10:26:29 AM: movefocusercmd: response = 1430#
4/21/2021 10:26:29 AM: movefocusercmd: Moving to = 4668
4/21/2021 10:26:29 AM: movefocusercmd: Check if focuser is moving
4/21/2021 10:26:29 AM: movefocusercmd: response = 01#
4/21/2021 10:26:29 AM: movefocusercmd: Focuser is moving
4/21/2021 10:26:30 AM: movefocusercmd: Re-Check if focuser is still moving
4/21/2021 10:26:30 AM: movefocusercmd: response = 01#
4/21/2021 10:26:30 AM: movefocusercmd: Focuser is moving
4/21/2021 10:26:31 AM: movefocusercmd: Re-Check if focuser is still moving
4/21/2021 10:26:31 AM: movefocusercmd: response = 01#
4/21/2021 10:26:31 AM: movefocusercmd: Focuser is moving
4/21/2021 10:26:32 AM: movefocusercmd: Re-Check if focuser is still moving
4/21/2021 10:26:32 AM: movefocusercmd: response = 01#
4/21/2021 10:26:32 AM: movefocusercmd: Focuser is moving
4/21/2021 10:26:33 AM: movefocusercmd: Re-Check if focuser is still moving
4/21/2021 10:26:33 AM: movefocusercmd: response = 01#
4/21/2021 10:26:33 AM: movefocusercmd: Focuser is moving
4/21/2021 10:26:34 AM: movefocusercmd: Re-Check if focuser is still moving
4/21/2021 10:26:35 AM: movefocusercmd: response = 01#
4/21/2021 10:26:35 AM: movefocusercmd: Focuser is moving
4/21/2021 10:26:36 AM: movefocusercmd: Re-Check if focuser is still moving
4/21/2021 10:26:36 AM: movefocusercmd: response = 01#
4/21/2021 10:26:36 AM: movefocusercmd: Focuser is moving
4/21/2021 10:26:37 AM: movefocusercmd: Re-Check if focuser is still moving
4/21/2021 10:26:37 AM: movefocusercmd: response = 00#
4/21/2021 10:26:37 AM: movefocusercmd: Focuser has stopped
4/21/2021 10:26:37 AM: movefocusercmd: Get Position
4/21/2021 10:26:37 AM: movefocusercmd: response = 123C#
4/21/2021 10:26:37 AM: movefocusercmd: Move completed
4/21/2021 10:26:37 AM: movefocusercmd: =END===========================================================
4/21/2021 10:26:37 AM: minus500: Stop
4/21/2021 10:27:07 AM: SetPosition: =START=========================================================
4/21/2021 10:27:07 AM: SetPosition: Serial Port is Open
4/21/2021 10:27:07 AM: SetPosition: Focuser position = 4668
4/21/2021 10:27:07 AM: SetPosition: =END===========================================================
4/21/2021 10:27:10 AM: gotofocuspos: =START=========================================================
4/21/2021 10:27:10 AM: gotofocuspos: Serial Port is Open
4/21/2021 10:27:10 AM: gotofocuspos: ConnectedState is true
4/21/2021 10:27:10 AM: gotofocuspos: Check if focuser is moving
4/21/2021 10:27:10 AM: gotofocuspos: response = 00#
4/21/2021 10:27:10 AM: gotofocuspos: Focuser is NOT moving
4/21/2021 10:27:10 AM: gotofocuspos: Moving to position = 4668
4/21/2021 10:27:10 AM: gotofocuspos: Check if focuser is moving
4/21/2021 10:27:10 AM: gotofocuspos: response = 00#
4/21/2021 10:27:10 AM: gotofocuspos: focuser has stopped
4/21/2021 10:27:10 AM: gotofocuspos: Get Position
4/21/2021 10:27:10 AM: gotofocuspos: response = 123C#
4/21/2021 10:27:10 AM: gotofocuspos: Move completed
4/21/2021 10:27:10 AM: gotofocuspos: =END===========================================================
This is what I recieve when I use sequence generator pro to attempt a connection:
[04/21/21 10:34:11.549][DEBUG][Main Thread][NONE] Disconnecting ASCOM Focuser: ASCOM.myFocuser2ASCOM1.Focuser
[04/21/21 10:35:16.448][DEBUG][Main Thread][NONE] PopulateDataModel: Transferring view to the data model...
[04/21/21 10:35:16.455][DEBUG][MF Update Thread][NONE] Performing serialize...
[04/21/21 10:37:21.142][DEBUG][Main Thread][NONE] Connecting ASCOM focuser...
[04/21/21 10:37:28.244][DEBUG][Main Thread][NONE] Failed to connect to focuser. : Cannot connect to controller (ASCOM.DriverException: Serial port Exception ---> System.Runtime.InteropServices.COMException: Timed out waiting for received data
at ASCOM.Utilities.Serial.ReceiveTerminated(String Terminator) in C:\ASCOM Build\Export\ASCOM.Utilities\ASCOM.Utilities\Serial.vb:line 1204
at ASCOM.myFocuser2ASCOM1.Focuser.CommandString(String command, Boolean raw)
--- End of inner exception stack trace ---
at ASCOM.myFocuser2ASCOM1.Focuser.CommandString(String command, Boolean raw)
at ASCOM.myFocuser2ASCOM1.Focuser.set_Connected(Boolean value))
at ASCOM.myFocuser2ASCOM1.Focuser.set_Connected(Boolean value)
at ASCOM.myFocuser2ASCOM1.Focuser.set_Link(Boolean value)
at s9.set_Link(Boolean value)
at s2.io()
[04/21/21 10:37:28.245][DEBUG][Main Thread][NONE] Disconnecting ASCOM Focuser: ASCOM.myFocuser2ASCOM1.Focuser
[04/21/21 10:37:53.745][DEBUG][Main Thread][NONE] Connecting ASCOM focuser...
[04/21/21 10:37:55.657][DEBUG][Main Thread][NONE] PopulateDataModel: Transferring view to the data model...
[04/21/21 10:37:55.663][DEBUG][MF Update Thread][NONE] Performing serialize...
[04/21/21 10:38:00.821][DEBUG][Main Thread][NONE] Failed to connect to focuser. : Cannot connect to controller (ASCOM.DriverException: Serial port Exception ---> System.Runtime.InteropServices.COMException: Timed out waiting for received data
at ASCOM.Utilities.Serial.ReceiveTerminated(String Terminator) in C:\ASCOM Build\Export\ASCOM.Utilities\ASCOM.Utilities\Serial.vb:line 1204
at ASCOM.myFocuser2ASCOM1.Focuser.CommandString(String command, Boolean raw)
--- End of inner exception stack trace ---
at ASCOM.myFocuser2ASCOM1.Focuser.CommandString(String command, Boolean raw)
at ASCOM.myFocuser2ASCOM1.Focuser.set_Connected(Boolean value))
at ASCOM.myFocuser2ASCOM1.Focuser.set_Connected(Boolean value)
at ASCOM.myFocuser2ASCOM1.Focuser.set_Link(Boolean value)
at s9.set_Link(Boolean value)
at s2.io()
[04/21/21 10:38:00.821][DEBUG][Main Thread][NONE] Disconnecting ASCOM Focuser: ASCOM.myFocuser2ASCOM1.Focuser
Cheers!
GP
I am a bit confused because this site is for myFocuserPro2
Last edit: brownrb 2021-04-22
You programmed the controller with
myFocuserPro v1xx firmware
You then attempted to use a myFocuserPro2 ASCOM driver with it. That will fail,
try using a myFocuserPro ASCOM driver
myFocuserPro and myFocuserPro2 are two completely different products.
Note:
myFocuserPro refers to v1xx of the myFocuserPro products. This was the first design and works with the Moonlite drivers, so can be supported on the Mac (tested on MacBook with TheSky and Moonlite drivers) and Linux systems (tested with the INDI Moonlite driver under Ubuntu and Ekos)
myFP2 refers to v2xx of the myFocuserPro2 products. This design is v2 and is NOT compatible with Mac and Linux systems. Version 2 controllers do have a number of additional features that are not available on the v1 design and use a different protocol. You cannot use v2xx ASCOM or Windows software with a v1xx programmed controller or vice-versa.
Both systems are supported by either a V1 or V2 Windows application and ASCOM drivers.
If you have built a v1xx controller, and want to upgrade to v2xx ASCOM drivers and Windows application, this is easy. Simply load the equivalent v2xx firmware into the controller and use the supplied v2 ASCOM drivers and v2 Windows application.
I knew it had to be something simple... I re flashed the controller with the 305 firmware and all is communicating now. ** I'm sure I am not the first to say, but you have done a really great job with this project.** Thank you for all your efforts and to any who have contributed! A donation will be coming your way shortly!