Electronique de commande smoothieboard

| Nov 6, 2019 | Electronique de commande

I ) SD Micro card

We can separate the smoothieboard controler in

Software part :
Firmware —-> can be update
config file —-> setting of smoothieboard
Gcode files —> machining path

Hardware électronic board with :
32-bit Cortex-M3 LPC1769 processor
with 512kB flash and 64kB RAM
Ethernet and USB connections
Various inputs and outputs for extensibility

 

Without Sd-card the smoothieboard can’t works

If the smoothieboard can’t read the two file more important
config and Firmware.cur, the smoothieboard don’t start.

If have problem with sd-card or firmware inside sd-card.
Can see with color of led.

 

Don’t mix smoothieboard firmware and config with gcode file.
Create special folder ‘gcode” for exemple to put machining file inside.
If you don’t can do mistake and delete sometimes important file.

Can have two more file, depend of options you choice.

  • config-override : – Created when the g-code M500 is played.
  • on_boot.gcode : – Played on startup of smoothieboard. Can be used to initialize the smoothie driven device.
It’s important save firmware and config file in other place of sd card for exemple computer, if you change something and whant return back, can find original file.

Overway is to copy sd-card to other sd-card (like copy sd-card for raspberry pi)

All is normal

 The Led 2 and 3 blink at this speed
 The Les 4 and 1 stay on

Sd-Card problem

 

The Led 4 stay off

Firmware crash

All green led stay on or Led 3 and 2 stay off

For overcome problem see Troubleshooting section of smoothieboard documentation http://smoothieware.org/troubleshooting#troubleshooting-a-problem-with-your-smoothieboard

Many settings in smoothie can be set immediately with M commands, these settings are lost on reset, however they can be saved to a non-volatile storage (similar to EEPROM on other systems).

The values in the configuration file will be overridden for those configuration options.

There is a set of M-codes (M50x) documented below that allow you to save all the current settings that have Mxxx commands to set them. This is particularly convenient for parameters that require tuning, as you can use a command to modify them without having to open the file and reset the board.

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 (M503 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
M500 Save settings to an override file
M501 load config-override file optionally specifying the extension M501 – loads config+override, M501 test1 – loads config+override.test1
M502 Delete the override file, reverting to config settings at next reset
M503 Display overridden settings if any
M504 Save the settings to an override file with specified extension M504 blue-pla

Crashing

Do not issue M500 or M504 when gcode is read by machine, or the machine could crash or the SD card become corrupted.

Do not

Edit the config-override file yourself, only use the commands to edit the values.

 

0条评论