What order should we boot hardware - open MyFocuser program, connect USB?

[PaulW]

I finally finished the project today, when it works, it works awesome, I
love it, but I'm having a very difficult time connecting hardware to the
MyFP2W software on my computer. I have tried plugging in the USB first, then
opening the program, reverse, I think every possible combo, it takes about
15 tries before it finally connects, then it doesn't load the options
properly, it starts out at 0-10000 for position etc. and I have to go into
settings and restore my last saved setup file.

I must be doing something fundamentally wrong. It's a current Lenovo laptop
running WIN10 Pro, and firmware 337a, which as mentioned when it finally
connects, works perfectly.

Any guidance would be greatly appreciated.

Thank you.

[PaulW]

Here is my log file, it looks like it is connecting, transferring data but then fails near the end.

OK I can confirm data is moving between the program and the focuser. I can change the position with the RE then try connecting again, it reads the data and updates in the "focuser" tab, the new position, but it won't stay connected.

Maybe this video will help.

https://www.icloud.com/photos/#/icloudlinks/0b6wRn-dZY9HtnDniJWWr9Ocw/0/

[PaulW]

I can't get the above link to work but if you copy and paste it to browser it works.

https://www.icloud.com/photos/#/icloudlinks/0b6wRn-dZY9HtnDniJWWr9Ocw/0/

PS and now I can't get it to connect at all, before it was just intermittent.

[brownrb]

what is firmware 337a?

The focuser I see from the log that it is DRV8825HW203_FRE
So the firmware foldername in the firmware zip file would be
myFP2_DRV8825HW203_338

I found v338 zip file on the sourceforge site,
https://sourceforge.net/projects/arduinoascomfocuserpro2diy/files/ARDUINO%20FIRMWARE/myFP2_Firmware_338.zip/download

So first thing to do is use firmware 338.

I see from the windows log you are using ver 2513 Windows app
from the log
2024-10-25 9:33:18 AM: Read_position START
2024-10-25 9:33:18 AM: SendString Sending=:00#
2024-10-25 9:33:18 AM: SendString Sending=OK
2024-10-25 9:33:18 AM: SendString END
2024-10-25 9:33:18 AM: ReceiveResponse START
2024-10-25 9:33:18 AM: ReceiveResponse client is connected
2024-10-25 9:33:23 AM: ReceiveResponse Error No response
2024-10-25 9:33:23 AM: ReceiveResponse Error message: System.TimeoutException: The operation has timed out

9:33:18 aent. 2:44:23 a 5s timeout because controller did not send a reply.

You also said that sometimes it connects and sometimes it does not, which stronhly points to a connection issue. If there was an error occuring at the exact same time in the connection sequence then that would definately point to either a firmware issue or a windows app issue.
But from your message that does not seem to be the case?

Before I go much further, did you leave anything out? I am making the assumption that the controller is connected to the PC using a usb cable connection only, One end of the cable into the PC, the other end of the cable into the controller. How long is the cable?

Regards
Robert

[PaulW]

"what is firmware 337a?"

https://sourceforge.net/p/arduinoascomfocuserpro2diy/discussion/general/thread/938f877697/#3880

I am reluctant to update the firmware as it was working perfectly, all functions working as they should.

Yesterday I tried connecting to NINA and it works 100%, so I thought I would try connecting to MyFP2W again.......AND IT CONNECTED! Yeah, no idea why all of a sudden. I just tried it now, and it connects, mmmm. Whatever was causing the issue has resolved itself. And it still connects with NINA and works as it should.

Yes USB connected to the laptop, about 3' cable and separate 12vdc for the motor.

Here are a few pictures.

Thanks for everything Robert. Now we just need some clear skies...rain forecast all week.

https://share.icloud.com/photos/054po4r36NXAhKSc5vGb8fyYg

[brownrb]

Link is blocked?

[PaulW]

Something to do with source forge, I modified the link, it should work now, if not just copy and paste it.

So the connection problem came back yesterday so I tried the one thing I hadn't yet, I cleared the EEPROM first then reloaded the firmware, also updated to 338, and evrything works again.

Thank you.