Having some issue getting the motor to move. I have installed all the software, the ascom platform, the windows application. I've uploaded the firmware to the arduino.
The windows app and ascom drivers connect to my arduino board fine.
However the motor does not respond to move commands. The leds on the driver board only get 2 lit up. (there are 4). I'm assuming that the appropriate signals are not getting to the input pins on the ULN2003 chip.
my wiring and board is fine as if I upload some other basic stepper motor coder (accelstepper or even the basic arduino stepper.h library) the motor works just fine.
Can anyone shed some light on why this isn't working? I'm not sure what screenshots etc you will require to help solve the issue, so if you need some specific information let me know and ill do my best to get some screenshots.
Thank you in advance.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi
you do not mention of you are using a pcb or your own layout.
You do say it appears to work with other code.
What firmware file are you using?
I would suspect the following
1. Your pin connections for the nano to the uln2003 driver board do not match the firmware
2. You have selected the wrong board type
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
So at the moment its not on a pcb but just wired up on a breadboard.
I'm using firmware - myFP2M - ULN2003-292 on the arduino.
using myFocuserPRo2_2_4_4_2 - for the windows app.
Ascom driver was version 2.7.0.0
all downloaded from the sourceforge page.
my pinout for the uln2003 is IN1 -4 is to Pins 4-7 on the arduino. I checked the myboards.h file and this is the correct pinout no?
if i use the jog command in the windows app, the TX and RX lights on the arduino uno flash. but the stepper does nothing. so the pc is definately communicating with the arduino. Just nothing to the stepper.
I have also bought a new stepper and driver board today and tried it out tonight to only get the same result.
I have tried the test program you supply with the arduino firmware and can confirm it works with my wiring.
Let me know if you have any other ideas that may help solve the issue?
Last edit: Aaron Jasperson 2019-12-10
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
No. Again, you are using the wrong zip file. The myFP2M is NOT recommended for any controller expect those that are purchased direct from me. The file you should be using is
That different code file has worked. My apologies. I missed the fact their were 2 different versions. its a subtle difference in the name. myFP2 vs myFP2M which I never picked up on in your previous post.
Can report all seems to work as intended.
Thanks again.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi guys,
Having some issue getting the motor to move. I have installed all the software, the ascom platform, the windows application. I've uploaded the firmware to the arduino.
The windows app and ascom drivers connect to my arduino board fine.
However the motor does not respond to move commands. The leds on the driver board only get 2 lit up. (there are 4). I'm assuming that the appropriate signals are not getting to the input pins on the ULN2003 chip.
my wiring and board is fine as if I upload some other basic stepper motor coder (accelstepper or even the basic arduino stepper.h library) the motor works just fine.
Can anyone shed some light on why this isn't working? I'm not sure what screenshots etc you will require to help solve the issue, so if you need some specific information let me know and ill do my best to get some screenshots.
Thank you in advance.
Hi
you do not mention of you are using a pcb or your own layout.
You do say it appears to work with other code.
What firmware file are you using?
I would suspect the following
1. Your pin connections for the nano to the uln2003 driver board do not match the firmware
2. You have selected the wrong board type
So at the moment its not on a pcb but just wired up on a breadboard.
I'm using firmware - myFP2M - ULN2003-292 on the arduino.
using myFocuserPRo2_2_4_4_2 - for the windows app.
Ascom driver was version 2.7.0.0
all downloaded from the sourceforge page.
my pinout for the uln2003 is IN1 -4 is to Pins 4-7 on the arduino. I checked the myboards.h file and this is the correct pinout no?
if i use the jog command in the windows app, the TX and RX lights on the arduino uno flash. but the stepper does nothing. so the pc is definately communicating with the arduino. Just nothing to the stepper.
I have also bought a new stepper and driver board today and tried it out tonight to only get the same result.
I have tried the test program you supply with the arduino firmware and can confirm it works with my wiring.
Let me know if you have any other ideas that may help solve the issue?
Last edit: Aaron Jasperson 2019-12-10
Is there a difference between using an Uno and a Nano for the project? I wouldn't of thought that would cause a problem but maybe?
I currently use an Uno.
I am using the 292.zip. When you go to the ULN2003 folder the actual ino file is called myFP2M-ULN2003-292.
No. Again, you are using the wrong zip file. The myFP2M is NOT recommended for any controller expect those that are purchased direct from me. The file you should be using is
https://sourceforge.net/projects/arduinoascomfocuserpro2diy/files/ARDUINO%20FIRMWARE/
If you unzip the zip file from the link, it creates a folder called
myFP2_ULN2003_292
Do not use the myFP2M firmware.
Thank you Rob.
That different code file has worked. My apologies. I missed the fact their were 2 different versions. its a subtle difference in the name. myFP2 vs myFP2M which I never picked up on in your previous post.
Can report all seems to work as intended.
Thanks again.
Hi Aaron
there are actually a number of variations
myfp2
myfp2m - ready built for purchase
myfp2n - uses nextion touch display
myfp2esp - a wifi version based on esp8266 or esp32 wifi chip
Each has its own unique firmware. I probably made the error of putting all those variations in one location
Anyhows, glad you got it sorted
Cheers
Robert