markwal / OctoPrint-GPX

An OctoPrint plug-in to use GPX as the protocol layer underneath rather than replacing g-code to talk to s3g/x3g machines, for example, a FlashForge.
GNU Affero General Public License v3.0
104 stars 25 forks source link

Sometimes the OctoPrint-GPX loses its settings on OctoPrint upgrade #37

Closed markwal closed 7 years ago

markwal commented 7 years ago

From foosel/OctoPrint/issues/1659, @jackpine63 says:

Based on what you have above, problem solved. I didn't even think to check GPX settings. Apparently, the upgrade from 1.2.18 to 1.3.0 reset the GPX settings to default (?) I went in to my 1.2.18 backup and found:

$ ls -l total 16 -rw-r--r-- 1 pi pi 171 Nov 11 17:37 gpx.ini -rw-r--r-- 1 pi pi 171 May 27 2016 gpx.ini.bkp

Both files are identical. However, in the upgraded image, I found the two files were different. gpx.ini.bkp matches the two files in the 1.2.18 backup:

[machine] actual_filament_diameter=1.75 [printer] build_progress=0 ditto_printing=0 gcode_flavor=makerbot machine_type=fcp nominal_filament_diameter=1.75 recalculate_5d=0

However, the active gpx.ini in the 1.3.0 system is different:

[machine] actual_filament_diameter=1.75 [printer] build_progress=1 ditto_printing=0 gcode_flavor=reprap machine_type=r1d nominal_filament_diameter=1.75 recalculate_5d=0

Note the different values for gcode_flavor and machine_type. I guess I could have updated in Octoprint, but I just copied gpx.ini.bkp to gpx.ini and rebooted. Things are back to working correctly now.

I didn't go back and try to repeat the upgrade to verify I can duplicate the problem (out of spare SD cards), but appears after the upgrade one has to go into GPX settings and reset everything, or restore the file on the file system as I did.

Thanks