5,838
edits
Updating MX to new version: Difference between revisions
m
→Upgrading on a Raspberry Pi computer by commands from a Microsoft Windows computer: new section
| Line 40: | Line 40: | ||
For simplicity, in guidance below, MX is stopped before any files are replaced. | For simplicity, in guidance below, MX is stopped before any files are replaced. | ||
==Upgrading on a Raspberry Pi (RPi) computer by commands from a Microsoft Windows computer (PC)== | |||
I recommend you download WinSCP (this and PuTTy share some settings). This will allow you to connect your PC to your rPi and copy files back and forth. You can use it to copy the MX distribution, you download and unzip on your PC, onto the RPi. You can also use it to take a back-up of your RPI files onto your PC, and to pick certain files off your RPi. e.g. copy log files from [[MXdiags folder]] to your PC to read diagnostics etc. | |||
You can download PuTTy (shares some settings with WinSCP) to enable you to open a terminal session and send commands to your RPi computer. | |||
If you have Cumulus MX setup to run as a service then you will need to do one of these, should you wish to add debugging when the upgraded MX begins... | |||
1. Edit the CumulusMX service file (see [[MX_on_Linux#Running_as_a_service]]) to add the -debug parameter (do this if always want debugging on, not usually needed) | |||
2. Just set it from Program Settings | Logging Options (easiest for turning debug on when you need it and off when you don't need it) | |||
3. Edit the Cumulus.ini file and enable it in there (no longer recommended) | |||
==Upgrading if you run MX as a service== | ==Upgrading if you run MX as a service== | ||