FORUM
Hi,
I have been using the solo board as a means of testing whether my motors have been shorted out or not. With the two boards I bought, they worked for a while and then the E2 light would stop flashing. I was under the impression that the over_current protection would be able to help. Any ideas on how to fix this issue? The power LED remains on.
Hi @ethpaige,
- May I know what version of SOLO UNO you are using? ( V1 or V2 )
- Can I have your Firmware version?
- Does E1 LED blink or stay on while E2 is off?
- what happens after you recycle the power of SOLO when the E2 stays off? does it start to blink back?
Regards
Milad
If you found the answers helpful and you could solve your problems, please kindly verify here to help others in the future.
Hi @milad ,
I am using a SOLO UNO V2.
I'm not sure on the firmware version, I can't connect up to the computer to check it.
E1 has remained off this entire time
When I power cycle, only the Green power led turns on. E1 and E2 stay off.
This is the case for the two boards I am using.
Thank you,
Ethan
Hi @ethpaige,
ok, it seems there is a chance that the boards are damaged, however before saying it definitively:
1-
I have been using the solo board as a means of testing whether my motors have been shorted out or not
Can you explain how this test is performed? so the motors were under speed or torque control? ( what types of motors)
2- Can you check if at the output of the +5V pin ( from the small Green Pheonix connector) if you see the +5V with respect to the GND on the same connector?
Milad
If you found the answers helpful and you could solve your problems, please kindly verify here to help others in the future.
1. I am testing a BLDC with Hall-Sensors. I run the test in torque mode. I set a reference torque of 0.5A and verify the motor spins at the correct speed. This test was working very well for several days, and then all of a sudden, my board disconnected from my PC and the E2 light remained off. I then started using the second board, and the same thing happened, it worked very well and then the E2 led remained off.
2. I do see +5V on both boards.
I have connected the boards via USB and am using Solopy for the programming.
Ethan
it seems the boards are damaged, especially the input voltage regulation which creates the +5V, that part can tolerate up to 63V and if for any reason some voltages above that come to the board, it can damage that component, and subsequently, if there is no +5V on the boards, the rest of the components can not work.
- do you see any visible sign of damage to the boards?
milad
If you found the answers helpful and you could solve your problems, please kindly verify here to help others in the future.
Ok, sorry I misunderstood that.
Ok then, let's do one more test:
- Turn Off SOLO
- put Pin Number 3 of SOLO in the Down Position ( we are putting SOLO in DFU mode which is used only for firmware upgrading purposes, so with this step we are by passing the firmware on SOLO)
- Turn ON SOLO
- do you see E1 and E2 turning ON or do they stay off?
if they stay off it means most probably the DSP on board is damaged, that can usually happen if you apply external signals with higher voltage ratings than allowed
I'll remain available.
Milad
If you found the answers helpful and you could solve your problems, please kindly verify here to help others in the future.
After doing the test, the two LEDs stayed off. My power supply is set two 28 V, so what do you think caused this?
Hi @ethpaige,
After doing the test, the two LEDs stayed off. My power supply is set two 28 V, so what do you think caused this?
it seems the DSP is damaged, this can usually happen if you apply higher voltages than what is allowed on the inputs like S/T, P/F or digital lines, so may I know what is the final wiring of your system? what are the modules/wirings connected to SOLO except the motor?
Regards
Milad
If you found the answers helpful and you could solve your problems, please kindly verify here to help others in the future.
At the time, I had only the micro-usb connected to the motor driver and I was controlling it using Solopy. I was connected to a sensored BLDC, but nothing was connected to any digital inputs like S/T, P/F or the digital lines. Eventually I will be connecting a raspberry pi to the SOLO, but only when I know that it will work the way I expect it to.
Ok @ethpaige, please get in touch with support[at]solomotorcontrollers.com to proceed further with the warranty, they will go into details on how to help you and how to avoid future failures like this, to me, it seems, from your first post that you are somehow testing your motors with SOLO to see if they are having short in their wirings ( correct me if I'm wrong), however, SOLO UNO V2 is better to be used with motors that are electrically stable, so if you test motors that are shorted or creating sparks during their operation (even internally) that makes it very hard to claim that no issue will happen for SOLO, btw, let's see with the support team and how we can proceed on this. 😉
Regards
Milad
If you found the answers helpful and you could solve your problems, please kindly verify here to help others in the future.