- This topic has 2 replies, 2 voices, and was last updated 3 years, 10 months ago by
.
-
OK, it sounds like you are back in operation.
It also sounds like you are developing one or more control programs.I assume you are aware of a special condition that exists in tinyG due to a hardware bug in the Microcontroller.
Writes to EEPROM, the non-volitile memory used on the controller, take a relative long time. To work around the bug, tinyG stops listening to the serial interface until the EEPROM signals that the write cycle is complete.
TinyG then issues a status response if you have your program watching the return stream.The issues does not appear if you manually key in parameter changes one at a time from a console like Coolterm. but dumping a string of commands all at once will likely result in some commands being missed or worse, causing partial writes or incorrect values to be written to EEPROM. There are also instances where the EEPROM refuses additional writes.
If you seek to automate parameter updates, the proper way is to send a parameter value the pause sending, waiting for a confirmation that the EEPROM has completed before sending the next parameter.Read this old, closed issue for hints https://github.com/synthetos/TinyG/issues/123
A useful way to look for EEPROM corruption is to Send $$ an observe parameter values. If you observe unrealistic or impossible values, or values tou would not have set, it is an indicator of possible EEPROM corruption.
Sending the $defa command will reset the EEPROM to the default values that are in the FW download(compiled in)
- You must be logged in to reply to this topic.
