Using a Nano with TMC2209 and 1.8° stepper motor.
(1) I can't connect via myFP2W 2.5.1.3 using 9600 or 57600 baud speed (two files attached).
The "strange" things is that I can connect via ASCOM and Sharpcap.
I can request a positive move and the motor turn well (via Sharpcap).
(2) But when I request a negative move, the motor doesn't turn and the position return to Zero.
First, may you please point me to an idea/solution about the myFP2W 2.5.1.3 connection problem (1)?
I guess I need to start to set it up before using through Sharpcap (2).
Thanks.
In "serialcomms.h", I have done this ugly modification :
case 62: // Get update of position on lcd when moving (0=disable, 1=enable)
// SendPacket('L', myfocuser.display_updateonmove);
SendPacket('L', 0L);
break;
Now I can connect, and probably no link, but Sharpcap work as it should....
I am alone in this case?
Edit : The problem with Sharpcap was coming from me, on my breed board I forgot to remove the Diag pin,... So it was connected to enable pin... Stupid...
Did my code trick is dangerous ? I didn't use any screen...
Latest Windows app works with latest firmware.
Using older firmware with latest app will mean some things will hang
This is because new features get added and old features get replaced
So a new winds app is lookin for those new things and it cannot find them so it times out.
New firmware should not be used with Old windows app. Again, the old app will look for something that may have been changed or deleted in the new firmware and again, timeouts and failure to connect is the most obvious result.
Regards
Robert
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
Using a Nano with TMC2209 and 1.8° stepper motor.
(1) I can't connect via myFP2W 2.5.1.3 using 9600 or 57600 baud speed (two files attached).
The "strange" things is that I can connect via ASCOM and Sharpcap.
I can request a positive move and the motor turn well (via Sharpcap).
(2) But when I request a negative move, the motor doesn't turn and the position return to Zero.
First, may you please point me to an idea/solution about the myFP2W 2.5.1.3 connection problem (1)?
I guess I need to start to set it up before using through Sharpcap (2).
Thanks.
Last edit: Antoine Cesbron 2024-09-08
Hi,
In "serialcomms.h", I have done this ugly modification :
case 62: // Get update of position on lcd when moving (0=disable, 1=enable)
// SendPacket('L', myfocuser.display_updateonmove);
SendPacket('L', 0L);
break;
Now I can connect, and probably no link, but Sharpcap work as it should....
I am alone in this case?
Edit : The problem with Sharpcap was coming from me, on my breed board I forgot to remove the Diag pin,... So it was connected to enable pin... Stupid...
Did my code trick is dangerous ? I didn't use any screen...
Last edit: Antoine Cesbron 2024-09-08
There is a rule, perhaps unwritten, and it is
Latest Windows app works with latest firmware.
Using older firmware with latest app will mean some things will hang
This is because new features get added and old features get replaced
So a new winds app is lookin for those new things and it cannot find them so it times out.
New firmware should not be used with Old windows app. Again, the old app will look for something that may have been changed or deleted in the new firmware and again, timeouts and failure to connect is the most obvious result.
Regards
Robert