Missing J16/J17 in "ESP32-DRV8825-Layout-TopView.jpg" and IN/OUT LED misfunction
ASCOM-INDI ESP32 Wifi focuser
Brought to you by:
brownrb
Menu
▾
▴
Hi,
first of all, thanks for this really useful project, as my telescope also wobbles like a cow's tail on an HEQ5-Pro when trying to find the focus.
After strange behavior of the circuit on a breadboard (when I came with the hand over the cables of the pushbuttons, the stepper moved), I have installed "pull-down" resistors.
But they are missing in the schematic "ESP32-DRV8825-Layout-TopView.jpg" and "myFP2-ESP32-DRV8825-08_schem.jpg".
In the source code these resistors (10k) for the pushbuttons are also mentioned.
Another problem are the "In/Out-LED", which light up when I activate them in the management server, but go out when I move the stepper and don't turn on again (pins D18/D19).
Here I have also independently inserted resistors, even if they are not mentioned in the circuit diagram.
But the function is not fulfilled.
Thanks in advance
Hi Lutz
Thank you for yout post, I will try to provide you with some information etc. I have placed portions of your post in italics, with my responses in normal text font.
But they are missing in the schematic "ESP32-DRV8825-Layout-TopView.jpg" and "myFP2-ESP32-DRV8825-08schem.jpg".
I don;t think so.. see attached
pg33 of pdf
J16 AND J17 PB ENABLE JUMPERS
PCB revisions (ESP32-DRV8825-Rev6 and ESP32-ULN2003-Rev4) have two special jumpers J16-PBOEN and J17-PBIEN which must be closed (using a motherboard shunt jumper) to enable the push button switches.
make sure the jumpers mentioned above are shorted
In general, the push buttons can be enabled/disabled using the management webserver. There is no longer a firmware setting for push buttons. I mention this just as clarification. Same for LED's
Next
Another problem is the "In/Out-LED", which light up when I activate them in the management server, but go out when I move the stepper and don't turn on again (pins D18/D19).
Just a query here. When you enable them in the management server you indicate they turn on immediately, is that correct? And stay on? And then when a move motor occurs they go out?
I need some clarification on what is occuring.
Just as with the pushbuttons, they are not defined in firmware, and can be enabled/disabled in the management server. I mention this just as clarification.
The LEDs do not and should not be used with any resistors (unless you are not using pre-wired leds, you should not be pulling one wire to ground or to vcc via a resistor.
You do not mention what version of the firmware you are using, so it is a little hard for me to say more at this time. There were some issues in earlier versions.
You can view the state of this via the management server pg 41 of manual. Admin page 2.
1. Can the LEDs be enabled or disabled: the state is shown in the sqaure brackets following the word State. When you click the button does the state change?
View the controller configuration using a web browser - see pg 136 of PDF,
USING THE MANAGEMENT SERVER: SHOW CONTROLLER CONFIG
Appending the filename to the Management server URL (URL:6060) will display the contents of the specified file. In the following example, the URL 192.168.4.1:6060/data_per.jsn specifies the SPIFFS file /data_per.jsn identified from the previous list example.
You should see "leds":0 when disabled and "leds":1 when enabled.
attachment data_per
Next view the board config file. PDF, pg 136.
USING THE MANAGEMENT SERVER: SHOW BOARD CONFIG
You can display the contents of the Driver board configuration file by adding /board_config.jsn to the Management server URL
You should see as per
attatchment board_config
You indicate that when you enable the leds, and then issue a move etc the led's do not light up.
You did not say how you were moving the stepper, it would help to know if this was the buttons, the web app, the ascom remote service etc. More info=better answer.
So if you did a move after the LEDS were enabled, and they did not light up, you need again, after the move, to view that data_per and board_config files to verify that nothing is changed.
If they are still they same, please post or email me the following
1. What firmware version you are using.
2. The actual sequence of steps you did - this is so I can then a) recreate your setup, b) follow each step 1 by 1 in the order your did it s=and thus see if I can replicate the issue you have found
3. the files of data_per and board_config - BEFORE you did the test sequence, and AFTER the test sequence was fininshed.
regards
Robert
I did forget 1 thing.
The led's are powered for the duration of the step only. This means that the LED is pulsed, and when the pulses are short (depends on a number of things including step mode) the leds are in fact working, but because the pulse is so short they can reach full brightness.
Try this:
make sure the leds are enabled
set motor speed to fast
turn off all the lights (if indoors testing)
move the motor 1000 steps
you should be able to see the dim glow of the LED's