After update to the latest firmware i notice chilipper workshop wouldn’t save the configure onto my tinyG v8 properly. Any thoughts on whats going ?
Never mind, I think there is something wrong with my chrome browser, I switch to firefox the problem is fix 
FWIW some keys in my config dont seem to be saving either . I am on a DUE so it is TinygG2.
so here is what i notice, if i update configuration, on my serial i usually get this
“{“x”:{“am”:1,“sn”:1,“vm”:16008,“sx”:2,“fr”:16008,“sv”:2997,“tm”:599.999,“lv”:102,“tn”:0,“lb”:19.99,“jd”:0.0102,“zb”:2.997,“jm”:5004,“jh”:10008}}”
then it would stop, my guess would be the chilipepper start update all the motor and axis. My tinyG will stop responding after this occur.
I think the problem is having to do with the json server not sending the information to the tinyG properly. After many attempting with restarting serial port json server, i manage to update my configuration again. werid.
What fw version are you running on tinyG? 440.16 is most recent, and a bug has been introduced complicating parameter setting, see https://github.com/synthetos/TinyG/issues/138.
But, seeing your parameters such as “vm”:16008, you have an additional issue that your parameter values are bad.
Difficult to work this issue here, please start a thread at https://groups.google.com/forum/#!forum/chilipeppr and report your OS, tinyG fw version, SPJS version for starters.
@Anthony_Webb What G2 fw build are you running on DUE? You are aware that DUE implementation has no persistence for parameters (no EEPROM), correct? The parameter set must be reloaded after every power cycle.
@cmcgrath5035 I am running the latest code in the master branch. One key in particular is $xJM, it defaults to 20, and will not change to anything else. But if I manually do something like $xJM=5000 it will stick just fine.
I have not played with my DUE in a few weeks, so may be rusty. I think you are saying that on powerup, $xjm=20. By Manually, you mean $xjm=5000 in the serial console?
How else did you try(and fail) to change it? For example, did you open the configuretinyG widget and it displayed 20 and would not let you change?
Or are you saying you changed with $xjm=5000 in SP Console, then power cycled (or reset) and $xjm was 50 again? The DUE has no persistence, meaning no place to put the new value except RAM, which is lost on power cycle and reloaded from flash factory defaults on boot-up.
I booted up, opened up the config widget, it showed 20, I changed to 5000, hit save. Re-opened up the widget and it was still at 20. Repeated, several more times, no nice. Then at the serial console I did $xjm=5000, then opened up the widget and the change had stuck, the widget reflected 5000 I had entered at the serial console. No power cycles of the DUE were involved in my tests.
@cmcgrath5035 Hello Carl, I have posted a very detail description to my problem to the link you provided
https://groups.google.com/forum/#!forum/chilipeppr
To keep things sort, jog no longer works on any of my machine with I use chilipeppr, Y motor command would freezes chilipeppr or tinyG (which i need to restart the json server , tinyG or chilipeppr), configuration wouldn’t update properly.
I have posted version of the code that updated the configuration properly vs one that failed.
I appreciate your time looking into this for me. I wrestle with these problems for 9 hour yesterday and finally throw my white towel at the machine at mid night.