search

flyandi / BitsyLED

A simple LED driver for Remote Control Cars, Planes, Multicopters and everything in between
http://flyandi.net/code/bitsyled
33 stars 4 forks source link

Connection from Configurator to Arduino not possible #2

Closed DerElch87 closed 5 years ago

DerElch87 commented 5 years ago

To start with, I'm feeling really bad to annoy you two times a day with problems or wishes :)

I and also a collegue from a german FPV forum are experiencing problems with the connection between the configurator and the arduino.

Configurator: 0.6.2 Firmware: 1.0.3 Arduino Nano (with old bootloader)

I changed the config.h accordingly and flashed the software.

There seems to be no connection possible, it simply outputs "connecting..." and nothing changes.

The collegue experienced the same after updating to 0.6.2 - before it worked with 0.6.0 But for him a downgrade also didn't helped.

So either there is some kind of incompadibility with one of the recent windows 10 updates or something else strange is going on.

Thanks and greetings

flyandi commented 5 years ago

Let me dig into it. You using just a simple Nano board, right?

DerElch87 commented 5 years ago

Yes, should be identically to a ProMini, only with a FTDI / CH340. ATMega 328P AU 1529 16MHz Thanks

flyandi commented 5 years ago

OK cool - let me play around with it.

VolkerFi commented 5 years ago

Hello, Flyandy,

I am the user who wrote to you on the hackaday website. I meant the user DerElch87 with the same problem. I was able to repeat the same behaviour today with an Arduino uno.

The tested Arduino nano all have an "old" bootloader. All 4 copies show the same behaviour (config.h -> arduino):

Thank you very much for your effort. VolkerFi

Translated with www.DeepL.com/Translator

flyandi commented 5 years ago

So I was playing around with and seems the EEPROM becomes corrupt and does not properly send back the data - for some reason the data itself stays correct in the EEPROM. I will fix this and make the protocol more stable - may have to rethink the protocol header with a more solid checksum

DerElch87 commented 5 years ago

Great that you found the issue. Looking forward for a fix :) Thanks and BR

VolkerFi commented 5 years ago

That sounds good for the future.

Thanks, VolkerFi

flyandi commented 5 years ago

I was out for a while but will be publishing some fixes shortly here.

net-worker commented 5 years ago

Can you publish the fix or is this Project Dead? Thanks 4 information and BR

flyandi commented 5 years ago

Alright everyone. I finally had some time to catch up on this tonight and did some stability improvement with the EEPROM. Looks like the issue is that the serial buffer was too little and too fast which caused the EEPROM not properly to store the data and also the serial buffer to choke eventually.

Firmware 1.04 and Configurator 0.6.5 are up now. Hope this will fix some stuff - it did for me on the 1.2.1 boards with the ATT84.