-
Notifications
You must be signed in to change notification settings - Fork 4
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
Issue encountered trying to revive a photon #3
Comments
Did you connect both GND connections? |
Yes I did |
Did this ever get resolved? I have the exact issue with my Photon at the moment. |
Unfortunately not. I just used the extra photon I had bought. |
you could try getting hold of a programmer shield and reprogramming the photon from scratch. Do you know what caused the photon to become unresponsive? if it's hardware failure then this tool won't be able to help fix it. |
It had a battery with a power shield and solar panel and 1 servo connected. The battery died a couple times and required the whole "key doctor" thing. The last time the battery died, the main led went out on the Photon and the d7 light is the only thing that comes on when it's plugged in. I tried the "Norwegian Blue" process and it gets far enough to tell me to check the wiring and the LED on the programming Photon goes from solid blue to solid yellow and stays there. I have to unplug it and plug it back in to get back to the solid blue led on the good photon. |
So I was trying to revive one of my inresponsive photons. Here is the link to my post in the community forums detailing what is wring with it. (https://community.particle.io/t/unable-to-change-mode-on-photon/21561/18.
When I connect to my programmer photon through putty I get this error after the " Do you have a dead device and wish to continue ?" message.
Unknown ACK(5) received. Please Double check the wiring then try again.
And yeah I did double check the wiring.
PS: I am using a 12K resistor instead of 10K since I do not have one on
me right now
Any help would be aprreciated. Thanks
The text was updated successfully, but these errors were encountered: