TinyG keeps some parameters while “forgetting” others

Home › Forums › TinyG › TinyG Support › TinyG keeps some parameters while “forgetting” others

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • June 1, 2022 at 2:11 pm #12141
    bluemetal09
    Participant

    I have used my TinyG board for months without any issues, but it has recently started to behave erratically clearly screwing up an ellipsis profile for good gcode (consistently adding deviations that did not exist in the g-code). In trying to pinpoint the issue, I tried to connect it with the latest Universal G-Code Sender (UGCS 2.0.11) using both a Windows machine and a Mac without success while still able to connect with GRBL-GRU – to see if the sender was the problem. A factory default reset ($defa=1) solved that connection problem but as soon as any board parameter was changed no new connection could be established. Firmware was re-flashed (same as previously 0.97-440.20) without any change in behavior.
    Additionally, certain parameters would be permanently recorded like $3tr=8 while others like $ex=1 or $jv=5 were forgotten the moment sender was close. This was likely been from the start of the issues but I only saw when re-programming it. It still connects every time with GBRL-GRU and that is how I see the “memory loss” but only after a factory default reset with UGCS. That gives me hope that the board is not yet lost.
    Has anyone experienced something similar and/or has any suggestions?

    June 1, 2022 at 6:09 pm #12142
    cmcgrath5035
    Moderator

    I have no experience with GRBL-GRU and very limited with UGCS. Most of my work has been with Chilipeppr or CoolTerm, and occasionally via a Linux putty terminal. I have over time had folks attempt variou bulk loading schemes for setting parameters that resulted in erratic behavior. defa=1 was a recovery mechanism. The root of the issue in those cases is a hardware bug in the tinyG micro controller-EEPROM interface, which is patched by shutting down the serial reader interface while an EEPROM write is being performed. Manually entering parameters one at a time via a CLI is OK, bulk loading needs to be properly implemented to ensure all data is properly written.

    In Chilipeppr, code in the SPJS properly handles this.

    In this item https://github.com/synthetos/TinyG/wiki/scripting-settings
    a 40ms delay is suggested. I have seen delays as much as 100ms. Up to you

    June 1, 2022 at 8:35 pm #12143
    bluemetal09
    Participant

    Thank you for the prompt reply. I should have stated that I am entering parameters by hand, one at a time. I can see the board Ok the input and I can immediately check it is there. Closing the sender and opening it again, without resetting or turning the power to the board off and those values ($ex and $jv for instance) are back at defaults while others remain with the new values. Really puzzling.

    June 2, 2022 at 5:36 pm #12144
    cmcgrath5035
    Moderator

    It has been a long time since I played with parameter setup and do not have a current hookup to refresh on.

    I do recall a situation where a parameter default change in value needed to be followed by an immediate tinyG hard reset.

    Are your trying to use $ex=1?
    I did in the beginning (6 years ago) but it fell into disfavor – due to poor device driver implementations of the protocol.$ex=2 is the preferred if you are not using a system such as Chilipeppr which manages flow based on buffer fill.

  • Author
    Posts
Viewing 4 posts - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.