It sounds horrible but if you follow the instructions here: https://www.eggtimerrocketry.com/page29.php
It's not too bad. WinAVR is available here: https://sourceforge.net/projects/winavr/files/WinAVR/20100110/
If your connected unit is not on COM 2 it's a piece of cake to edit the file to your given com port. I've messed with it
many times in the past and have never wrecked any of my units. If the cable is connected wrong, it just doesn't flash.
There's a little knack in getting it started but if the connections are good you'll get the button pushing timing right.
Now when you say quit working what do you mean? I'm waiting for Cris to send me a new LCD as my unit in the yellow case will work for awhile and then all of a sudden the screen goes blank. The data keeps coming across the Bluetooth link. I took it out of the case and the same behavior was seen. Sometimes the thing has to run 2 hours and then the LCD goes blank. Switch off/on and then it comes back. Sometimes goes blank in 5 minutes....
I'm hoping it's not the mainboard in mine but is this the behavior your unit is doing? Might not be the firmware then.
Kurt Savegnago
It's not too bad. WinAVR is available here: https://sourceforge.net/projects/winavr/files/WinAVR/20100110/
If your connected unit is not on COM 2 it's a piece of cake to edit the file to your given com port. I've messed with it
many times in the past and have never wrecked any of my units. If the cable is connected wrong, it just doesn't flash.
There's a little knack in getting it started but if the connections are good you'll get the button pushing timing right.
Now when you say quit working what do you mean? I'm waiting for Cris to send me a new LCD as my unit in the yellow case will work for awhile and then all of a sudden the screen goes blank. The data keeps coming across the Bluetooth link. I took it out of the case and the same behavior was seen. Sometimes the thing has to run 2 hours and then the LCD goes blank. Switch off/on and then it comes back. Sometimes goes blank in 5 minutes....
I'm hoping it's not the mainboard in mine but is this the behavior your unit is doing? Might not be the firmware then.
Kurt Savegnago