well the focuser code i got to upload to the ESP32. I am using the 8825 driver on a PCB i ordered.
I can get on the Wifi network with my laptop. Then use the windows application to connect to:
192.168.4.1:2020
The OLED screen never displays anything. The buttons do no light up the LEDs when pushed. The stepper motro does not turn. The on/off switch does not switch. :)
I am supplying 12volt in and the ESP32 power on. The IC7878 gets warm to hot (i have not attached a heat sink yet).
I tried several test application and i am not sure what to look for. The only one i got to work was the OLED i uploaded and the OLED showed:
Uknown
224
<c> R Brown 2020</c>
So that made me feel good that the OLED displayed some thing. I was not sure what i was suppose to do with the LED test code/switch test code. I compiled and uploaded and turn on the serial monitor and pushed buttons, but nothing changed. The on/off switch and on led does nothing.
Make sure it is the latest firmware
release 230-1
and do not forget to upload the data sketch files after uploading the firmware
The myFP2-ESP firmware is not the same as for myFP2 or other projects
At an early stage in development, the decision was made to have the focuser configuration handled differently. So a lot of the usual #define statements for enabling options did not appear or were not used.
Instead, a lot of these were moved into a web server interface, with the intent that the options could be enabled, disabled, started and stopped from the management interface - AND - the most important part - NOT reqquire re-programming the controller because some
hardware just got added.
So you could program the controller, and not having a push button - decide to add some push buttons in a month from now - and just flick the software stick (ie use the management server to enable them) and it would work - without a reprogram being necessary.
So one has to be in a different mind set for the myFP2ESP controller
In times like that (being stuck) the pdf - read the manual - sheds the light upon your plight
Most things are "disabled" by default
Most things are enabled using the management web server interface
try using the web interface
pdf - pg 32
DISPLAY MANAGEMENT
The Management server (page1) has options for controlling the display. The options are
pdf - pg 128
Many options are only available via the Management Server interface, such as enabling and disabling of
• Temperature probe
• OLED display
• In-Out LED’s
• Push buttons
• Web-Server
• ASCOM Remote Server
• Backlash and backlash settings
• and managing board configuration
pdf - pg 33
PUSH BUTTON MANAGEMENT
Enabling or disabling the push buttons is done on MANAGEMENT Server, page 3.
pg131
in out leds
etc
Regards
Robert
Last edit: brownrb 2021-09-17
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Make sure it is the latest firmware
release 230-1
and do not forget to upload the data sketch files after uploading the
firmware
In times like that the pdf - read the manual - sheds the light upon your
plight
Most things are "disabled" by default
Most things are enabled using the management web server interface
try using the web interface
pdf - pg 32
DISPLAY MANAGEMENT
The Management server (page1) has options for controlling the display. The
options are
pdf - pg 128
Many options are only available via the Management Server interface, such
as enabling and disabling of
• Temperature probe
• OLED display
• In-Out LED’s
• Push buttons
• Web-Server
• ASCOM Remote Server
• Backlash and backlash settings
• and managing board configuration
pdf - pg 33
PUSH BUTTON MANAGEMENT
Enabling or disabling the push buttons is done on MANAGEMENT Server, page
3.
OK i got it running! Thanks again! My buttons work! OLED works!
Power switch and power LED still not working. The diode is with the "ring"
towards the driver. Or going down if you read the type on the PCB.
I did attach regular LEDs. I just read that I should have included
resistors. So maybe I damaged my ESP32.
The in/out LED are the blinking type just because i had them on hand. They
do blink when i enable the feature. They do no blink when i push the
in/out buttons or command the motor to move in/out with the website. I
assume that is their purpose to light up when the motor is turning in/out.
All in all a great project! I just have a few more bugs to work out.
AH! I bet this is what messed me up. I did not do the ESP32 Sketch data
upload.... I got all excited and stopped reading the PDF and hit "upload".
THis my first arduino project that this is a step to perform.
Hopefully this will fix the management website. I never could connect to
192.168.4.1:6060 website.
YA! I got the management website... i will start poking some more.
Thanks for the help!!!
Chad
On Fri, Sep 17, 2021 at 4:42 AM brownrb brownrb@users.sourceforge.net
wrote:
Make sure it is the latest firmware
release 230-1
and do not forget to upload the data sketch files after uploading the
firmware
In times like that the pdf - read the manual - sheds the light upon your
plight
Most things are "disabled" by default
Most things are enabled using the management web server interface
try using the web interface
pdf - pg 32
DISPLAY MANAGEMENT
The Management server (page1) has options for controlling the display. The
options are
pdf - pg 128
Many options are only available via the Management Server interface, such
as enabling and disabling of
• Temperature probe
• OLED display
• In-Out LED’s
• Push buttons
• Web-Server
• ASCOM Remote Server
• Backlash and backlash settings
• and managing board configuration
pdf - pg 33
PUSH BUTTON MANAGEMENT
Enabling or disabling the push buttons is done on MANAGEMENT Server, page
3.
OK i got it running! Thanks again! My buttons work! OLED works!
Power switch and power LED still not working. The diode is with the "ring"
towards the driver. Or going down if you read the type on the PCB.
I did attach regular LEDs. I just read that I should have included
resistors. So maybe I damaged my ESP32.
The in/out LED are the blinking type just because i had them on hand. They
do blink when i enable the feature. They do no blink when i push the
in/out buttons or command the motor to move in/out with the website. I
assume that is their purpose to light up when the motor is turning in/out.
All in all a great project! I just have a few more bugs to work out.
Thanks!
Chad
On Fri, Sep 17, 2021 at 9:19 AM Chad Gray archer60x@users.sourceforge.net
wrote:
AH! I bet this is what messed me up. I did not do the ESP32 Sketch data
upload.... I got all excited and stopped reading the PDF and hit "upload".
THis my first arduino project that this is a step to perform.
Hopefully this will fix the management website. I never could connect to
192.168.4.1:6060 website.
YA! I got the management website... i will start poking some more.
Thanks for the help!!!
Chad
On Fri, Sep 17, 2021 at 4:42 AM brownrb brownrb@users.sourceforge.net
wrote:
Make sure it is the latest firmware
release 230-1
and do not forget to upload the data sketch files after uploading the
firmware
In times like that the pdf - read the manual - sheds the light upon your
plight
Most things are "disabled" by default
Most things are enabled using the management web server interface
try using the web interface
pdf - pg 32
DISPLAY MANAGEMENT
The Management server (page1) has options for controlling the display. The
options are
pdf - pg 128
Many options are only available via the Management Server interface, such
as enabling and disabling of
• Temperature probe
• OLED display
• In-Out LED’s
• Push buttons
• Web-Server
• ASCOM Remote Server
• Backlash and backlash settings
• and managing board configuration
pdf - pg 33
PUSH BUTTON MANAGEMENT
Enabling or disabling the push buttons is done on MANAGEMENT Server, page
3.
I did attach regular LEDs. I just read that I should have included
resistors. So maybe I damaged my ESP32.
The in/out LED are the blinking type just because i had them on hand. They
do blink when i enable the feature. They do no blink when i push the
in/out buttons or command the motor to move in/out with the website. I
assume that is their purpose to light up when the motor is turning in/out.
The ESP32 can provide up to 40mA per pin, but easuly damaged if one exceeds that.
All LED's should have a limiting resistor in series to ensure the current drawn from the pin is kept low enough so as not to damage the pin,
Different color LED's require differene resistor values.
I prefer the pre-wired LED's to make things simple
There are many web sites which provide on line calculators for determining the resistor values based on voltage and current for a particular colored LED.
The blinking type are no good. Doubtful if they would work.
The leds for in/out are pulsed for the same duration when the motor is pulsed. This is around 3us. a very short pulse.
What that means is that if moving 50+ more steps then the led's do glow bright enough
This is due to the residual light effect (they still glow a bit when the pulse driving them ends - similar to a light bulb. The downside is they hardly glow at all for a short number of steps.
It is not worth the effort to use some form of latch or comparator to handle the leds. One gets used to seeing what one sees and most of time users use it in a remote observatory - so leds are not that important in these scenarios.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The OLED screen never displays anything.
1: check you have tjhe SDA and SCL lines correct
2. Check that you have 3.3V on the VCC line
3. Make sure OLED is defined as OLED_TEXT in configuration file
4. Use management server to enable the display
5.The header J8 goes SDA, SCL, 3V3, GND (so sda goes to sda, scl to scl etc)
The buttons do no light up the LEDs when pushed.
1. Enable the push buttons using the management server -
2. Enable the IN-OUT leds using the management server -
The stepper motor does not turn.
Check you have 12V power ON - it will not work without 12V -
On the drv8825 chip measure voltage with multimeter -
red lead to VMOT
black lead to next pin down - GND
Should read 12V
the pins that control movement are
DIR
EN
STEP
make sure they are not touching other pins on the underside of the board
Remove the drv8825 (of using the recommended header risers)
Measure from D14 to Enable pin - should be 0 ohms - and no other pin
Measure from D33 to Step pin - should be 0 ohms - and no other pin
Measure from D32 to Dir pin - should be 0 ohms - and no other pin
Then check DRV8825 to stepper motor
2B -pin1 rs232 - black
2A -pin2 rs232 - green
1A - pin 3 rs232 - red
1B - pin 4 rs232 - blue
The on/off switch does not switch.
Attches to J2 header
Did you fit a fuse across J3?
If not then 12V cannot get to the drv8825 or other parts of the focuser
Did you fit the Diode in place - and the correct way round?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello,
well the focuser code i got to upload to the ESP32. I am using the 8825 driver on a PCB i ordered.
I can get on the Wifi network with my laptop. Then use the windows application to connect to:
192.168.4.1:2020
The OLED screen never displays anything. The buttons do no light up the LEDs when pushed. The stepper motro does not turn. The on/off switch does not switch. :)
I am supplying 12volt in and the ESP32 power on. The IC7878 gets warm to hot (i have not attached a heat sink yet).
I tried several test application and i am not sure what to look for. The only one i got to work was the OLED i uploaded and the OLED showed:
Uknown
224
<c> R Brown 2020</c>
So that made me feel good that the OLED displayed some thing. I was not sure what i was suppose to do with the LED test code/switch test code. I compiled and uploaded and turn on the serial monitor and pushed buttons, but nothing changed. The on/off switch and on led does nothing.
The only part i do not have hooked up is the C5, IR stuff and home switch.
Make sure it is the latest firmware
release 230-1
and do not forget to upload the data sketch files after uploading the firmware
The myFP2-ESP firmware is not the same as for myFP2 or other projects
At an early stage in development, the decision was made to have the focuser configuration handled differently. So a lot of the usual #define statements for enabling options did not appear or were not used.
Instead, a lot of these were moved into a web server interface, with the intent that the options could be enabled, disabled, started and stopped from the management interface - AND - the most important part - NOT reqquire re-programming the controller because some
hardware just got added.
So you could program the controller, and not having a push button - decide to add some push buttons in a month from now - and just flick the software stick (ie use the management server to enable them) and it would work - without a reprogram being necessary.
So one has to be in a different mind set for the myFP2ESP controller
In times like that (being stuck) the pdf - read the manual - sheds the light upon your plight
Most things are "disabled" by default
Most things are enabled using the management web server interface
try using the web interface
pdf - pg 32
DISPLAY MANAGEMENT
The Management server (page1) has options for controlling the display. The options are
pdf - pg 128
Many options are only available via the Management Server interface, such as enabling and disabling of
• Temperature probe
• OLED display
• In-Out LED’s
• Push buttons
• Web-Server
• ASCOM Remote Server
• Backlash and backlash settings
• and managing board configuration
pdf - pg 33
PUSH BUTTON MANAGEMENT
Enabling or disabling the push buttons is done on MANAGEMENT Server, page 3.
pg131
in out leds
etc
Regards
Robert
Last edit: brownrb 2021-09-17
AH! I bet this is what messed me up. I did not do the ESP32 Sketch data
upload.... I got all excited and stopped reading the PDF and hit "upload".
THis my first arduino project that this is a step to perform.
Hopefully this will fix the management website. I never could connect to
192.168.4.1:6060 website.
YA! I got the management website... i will start poking some more.
Thanks for the help!!!
Chad
On Fri, Sep 17, 2021 at 4:42 AM brownrb brownrb@users.sourceforge.net
wrote:
OK i got it running! Thanks again! My buttons work! OLED works!
Power switch and power LED still not working. The diode is with the "ring"
towards the driver. Or going down if you read the type on the PCB.
I did attach regular LEDs. I just read that I should have included
resistors. So maybe I damaged my ESP32.
The in/out LED are the blinking type just because i had them on hand. They
do blink when i enable the feature. They do no blink when i push the
in/out buttons or command the motor to move in/out with the website. I
assume that is their purpose to light up when the motor is turning in/out.
All in all a great project! I just have a few more bugs to work out.
Thanks!
Chad
On Fri, Sep 17, 2021 at 9:19 AM Chad Gray archer60x@users.sourceforge.net
wrote:
Hmm the fuse i just use a jumper for now. I pulled the jumper and
everything is still running.
On Fri, Sep 17, 2021 at 10:09 AM Chad Gray archer60x@users.sourceforge.net
wrote:
The ESP32 can provide up to 40mA per pin, but easuly damaged if one exceeds that.
All LED's should have a limiting resistor in series to ensure the current drawn from the pin is kept low enough so as not to damage the pin,
Different color LED's require differene resistor values.
I prefer the pre-wired LED's to make things simple
There are many web sites which provide on line calculators for determining the resistor values based on voltage and current for a particular colored LED.
The blinking type are no good. Doubtful if they would work.
The leds for in/out are pulsed for the same duration when the motor is pulsed. This is around 3us. a very short pulse.
What that means is that if moving 50+ more steps then the led's do glow bright enough
This is due to the residual light effect (they still glow a bit when the pulse driving them ends - similar to a light bulb. The downside is they hardly glow at all for a short number of steps.
It is not worth the effort to use some form of latch or comparator to handle the leds. One gets used to seeing what one sees and most of time users use it in a remote observatory - so leds are not that important in these scenarios.
The OLED screen never displays anything.
1: check you have tjhe SDA and SCL lines correct
2. Check that you have 3.3V on the VCC line
3. Make sure OLED is defined as OLED_TEXT in configuration file
4. Use management server to enable the display
5.The header J8 goes SDA, SCL, 3V3, GND (so sda goes to sda, scl to scl etc)
The buttons do no light up the LEDs when pushed.
1. Enable the push buttons using the management server -
2. Enable the IN-OUT leds using the management server -
The stepper motor does not turn.
Check you have 12V power ON - it will not work without 12V -
On the drv8825 chip measure voltage with multimeter -
red lead to VMOT
black lead to next pin down - GND
Should read 12V
the pins that control movement are
DIR
EN
STEP
make sure they are not touching other pins on the underside of the board
Remove the drv8825 (of using the recommended header risers)
Measure from D14 to Enable pin - should be 0 ohms - and no other pin
Measure from D33 to Step pin - should be 0 ohms - and no other pin
Measure from D32 to Dir pin - should be 0 ohms - and no other pin
Then check DRV8825 to stepper motor
2B -pin1 rs232 - black
2A -pin2 rs232 - green
1A - pin 3 rs232 - red
1B - pin 4 rs232 - blue
The on/off switch does not switch.
Attches to J2 header