Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mainboard blew up #32

Closed
walterinho opened this issue Jul 4, 2018 · 9 comments
Closed

Mainboard blew up #32

walterinho opened this issue Jul 4, 2018 · 9 comments

Comments

@walterinho
Copy link

Hi there,

I did flash your code to my board successfully, but it blew up once I connected it.

image

I don't know what was the problem, do you think I could replace those components?

@rene-dev
Copy link
Contributor

rene-dev commented Jul 4, 2018

you probably flashed unsupported hardware. post a pic of the rest of the board.

@walterinho
Copy link
Author

walterinho commented Jul 4, 2018

This is the mainboard.

image

I do have another board (see below), but the st-link tool says there's no target connected:

image
Is there a way to use the second mainboard?

@walterinho
Copy link
Author

@rene-dev , How can I know if the hardware is supported?

I have this new mainboard, and I don't want to screw it up again.

image

@LeoDJ
Copy link
Collaborator

LeoDJ commented Jul 12, 2018

The best way to test it is to use a different power supply than the battery, that is current limited. Something like a lab bench power supply or if you feel adventurous and skilled enough the supplied hoverboard charger. But I highly recommend a lab bench power supply.
If the firmware on the mainboard tries to pull too much current, it will be limited by the supply instead of blowing components up with the high current from the battery.

@HITMAnsOFT
Copy link

HITMAnsOFT commented Jul 14, 2018

Is that the buzzer control transistor? It shouldn't be fatal to the operation of the board if that's the only visible damage. You can still try to run it with a current-limited power supply.

@johnsokol
Copy link

johnsokol commented Jul 19, 2018 via email

@walterinho
Copy link
Author

Thank you very much for your help guys, please bear with me, I'm a noob at some topics in Electronics.

@LeoDJ, thanks! I followed your instructions with the new board and it works perfectly, I tested it with a maximum of 1.5A. Now my problem is that I need to use the hoverboard's battery, do you think that after doing these test it is safe to use it to the original battery with this board? or what options could I have?

@HITMAnsOFT yes, it is the buzzer control transistor and I thought the same but it doesn't work at all, I tried to test what is going on by connecting the oscilloscope to each motor phase and GND (I don't know if this is correct haha) and I realized that one of the phases of each motor doesn't change it's width (duty cycle) when I send a different speed and steer command. Is there a better way of checking what is wrong?

@johnsokol thanks for your help, the problem is that I live in London, =(, but I really appreciate that you are interested in helping me, maybe you have any advice about how to check what is wrong with the board.

@btsimonh
Copy link
Contributor

@walterinho I have the same YST board, and all is working well.

@SafeMantella
Copy link

The best way to test it is to use a different power supply than the battery, that is current limited. Something like a lab bench power supply or if you feel adventurous and skilled enough the supplied hoverboard charger. But I highly recommend a lab bench power supply.
If the firmware on the mainboard tries to pull too much current, it will be limited by the supply instead of blowing components up with the high current from the battery.

What's the ideal voltage and current to test the board? I tried 36V 2.2A and nothing happened

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants