Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
configuring-smoothie [2019/02/05 16:55]
arthur
configuring-smoothie [2020/02/29 22:21] (current)
arthur
Line 64: Line 64:
 Smoothie will not work without a valid configuration file on the SD card. Smoothie will not work without a valid configuration file on the SD card.
  
-The filename must be <kbd>​config</​kbd> or <kbd>​config.txt</​kbd>+The filename must be <code>​config</​code> or <code>​config.txt</​code>
  
  
Line 70: Line 70:
 It is not recommended you allow the sdcard to [[https://​technet.microsoft.com/​en-us/​library/​cc753703(v=ws.11).aspx|auto mount]], and it is highly recommended that the sdcard be unmounted at all times except when files need to be copied or the config file needs to be edited. It is not recommended you allow the sdcard to [[https://​technet.microsoft.com/​en-us/​library/​cc753703(v=ws.11).aspx|auto mount]], and it is highly recommended that the sdcard be unmounted at all times except when files need to be copied or the config file needs to be edited.
  
-"​Unmounting"​ does not refer to a phyisical ​action, do not confuse it with "​removing"​ the card from the board. "​unmounting"​ just means "​telling your computer to stop accessing the card", which is usually done by clicking menus with your mouse ( on windows this is usually called "​safely eject" ).+"​Unmounting"​ does not refer to a physical ​action, do not confuse it with "​removing"​ the card from the board. "​unmounting"​ just means "​telling your computer to stop accessing the card", which is usually done by clicking menus with your mouse ( on windows this is usually called "​safely eject" ).
  
 Concurrent access to the sdcard via the host and the smoothie is not supported. The sdcard must be safely removed or unmounted then smoothie reset after copying or editing files from the host mount point. Concurrent access to the sdcard via the host and the smoothie is not supported. The sdcard must be safely removed or unmounted then smoothie reset after copying or editing files from the host mount point.
Line 130: Line 130:
 <callout type="​danger"​ icon="​true"​ title="​ Notepad++">​ <callout type="​danger"​ icon="​true"​ title="​ Notepad++">​
  
-Do not use Notepad++ to edit the configuration file, it thinks it'​s ​smarter than everybody and modifies ​the file in invisible ways that can make it unreadable or confusing ​to Smoothie.+If you use Notepad++ to edit the configuration file, make sure you switch the file encoding to "​ANSI"​ (done with 2 clicks) - click "​Encoding"​ on the Menu bar then click "​ANSI"​. It'​s ​easy.  Otherwise, Notepad++ will change ​the encoding ​to UTF8 by default.
  
-Looking for a good simple text editor that runs under Windows and will edit Smoothie config files with no problems? Try https://​wiki.gnome.org/​Apps/​Gedit +Another ​good simple text editor that runs under Windows and will edit Smoothie config files with no problems ​is: https://​wiki.gnome.org/​Apps/​Gedit
- +
-In more detail : Notepad++ will change the encoding to UTF8 by default but you can force it to use ANSI and it will be fine.+
  
 ANSI and UTF8 are equivalent for a subset of characters but sometimes quotes and such can be replaced with Unicode variants. ANSI and UTF8 are equivalent for a subset of characters but sometimes quotes and such can be replaced with Unicode variants.
Line 170: Line 168:
 As these settings can be temporarily overridden with Mxxx commands there is a way to save these settings. Once saved they are reloaded on reset or boot overriding the settings in the config file. If you then edit the config file, make sure the setting you are editing is not being overridden by the override file (<​kbd>​M503</​kbd>​ will tell you if there is an active override file). This can sometimes explain why editing the config file appears to have no effect. As these settings can be temporarily overridden with Mxxx commands there is a way to save these settings. Once saved they are reloaded on reset or boot overriding the settings in the config file. If you then edit the config file, make sure the setting you are editing is not being overridden by the override file (<​kbd>​M503</​kbd>​ will tell you if there is an active override file). This can sometimes explain why editing the config file appears to have no effect.
  
-||~ M-code ​||~ Description ​||~ Example ​|+M-code ​Description ​Example | 
-|| <​kbd>​M500</​kbd> ​|| Save settings to an override file  ​|| || +| <​kbd>​M500</​kbd>​ | Save settings to an override file  | || 
-|| <​kbd>​M501</​kbd> ​|| load config-override file optionally specifying the extension ​|| <​kbd>​M501</​kbd>​ - loads <​kbd>​config-override</​kbd>,​ <​kbd>​M501 test1</​kbd>​ - loads <​kbd>​config-override.test1</​kbd> ​|+| <​kbd>​M501</​kbd>​ | load config-override file optionally specifying the extension | <​kbd>​M501</​kbd>​ - loads <​kbd>​config-override</​kbd>,​ <​kbd>​M501 test1</​kbd>​ - loads <​kbd>​config-override.test1</​kbd>​ | 
-|| <​kbd>​M502</​kbd> ​|| Delete the override file, reverting to config settings at next reset  ​||  ​|+| <​kbd>​M502</​kbd>​ | Delete the override file, reverting to config settings at next reset  |  | 
-|| <​kbd>​M503</​kbd> ​|| Display overridden settings if any ||  ​|+| <​kbd>​M503</​kbd>​ | Display overridden settings if any |  | 
-|| <​kbd>​M504</​kbd> ​|| Save the settings to an override file with specified extension ​|| <​kbd>​M504</​kbd>​ blue-pla ​||+| <​kbd>​M504</​kbd>​ | Save the settings to an override file with specified extension | <​kbd>​M504</​kbd>​ blue-pla |
  
 <callout type="​danger"​ icon="​true"​ title="​Crashing">​ <callout type="​danger"​ icon="​true"​ title="​Crashing">​