Starting with version 1.0.4 the linux versions of Repetier-Server can access GPIO pins directly from the interface. This allows it to change a output pin to trigger a relay for example. But you can also check a input for a signal change and trigger some actions. This would be required to add a server controlled filament sonsor or to have some extra buttons that trigger quick functions like an emergency button.
If you think this is something for you, make sure your electronic knowledge is good enough for the task. You will be connecting and configuring new electronics and errors can lead to physical damage of your computer. You do this on your own risk, so don’t tell me I did not warn you.
Now for the brave, the page to control these pins is in Global Settings->GPIO Pins. At the beginning the list is empty and you can add new entries with a dialog box at the bottom. You select one of the five types and give it a name. If you want to use it also in g-code the name should NOT contain whitespaces! The name for the menu can be selected later on. Once added the editor opens. The contents differs and will be described in the next sections.
A fully configured setup might look like this test setup.
In the image above you see the table with all entries. Name is the official name you would also use for @gpio server command. Function describes what it does. GPIO Pin is the pin number. Raspberry PI users should watch out with the numbering scheme. There are several numberings in use in the available tutorials. Often they use wiringPi numbering, but we use the numbers as assigned by linux which is in tutorial normally called BCM numbering based on the chipset used. For pwm outputs it is the pwm channel and not a pin number!
Set output on/off
This is the most basic output function. It allows you to control a pins output either by @gpio server command or by toggling it in the menu. Most important thing when using a output pin is, to not draw more current then the pin can deliver. That is normally not much. If you draw more the best that can happen is that just that output dies. Add a 330 Ohm resistor after the output and you are normally safe. Still enough for a simple led. For a relais you need more electronic, so I leave that to the experts.
So lets look at the editor:
Description is for your internal use. Make notes so you know what you wanted or what to do to recreate it.
Display Name is the name that you will see in the menu for the function.
Next you have Icon On and Icon Off. Both are optional and should be svg graphics indicating device is on or off. If omitted you get a defazlt switch icon from us.
Printer Association controls in which menu the function will be put. It is either Global Function or one of your 3d printer names. The Show in Menu checkbox controls, if you will see it in a menu at all. If not it can only be called as server command.
Next you see the correct server command to enable, disable or toggle the pins output.
GPIO Pin is the physical pin with numbering linux uses. For raspberry pi users this means the BCM numbering scheme.
Last checkbox Activate on Init can be set, if you want the signal to be on when server starts. Otherwise it will be off at startup.
Set PWM Output
This is a bit more complex. A pwm output does change the output signal very quickly. The percentage between on and off can be defined to allow e.g. a dimmed light. The main problem is that you can not simply say which pin to use. Instead you assign it to a channel. Which channel maps to which pin depends on your linux configuration. For raspberry pi you even have to enable this feature. Normally pwm is used for audio output. For raspberry pi you edit /boot/config.txt to enable pwm for pins and also to configure which channel maps to which pin. E.g. adding
From the overlay description:
Info: Configures both PWM channels
Legal pin,function combinations for each channel:
PWM0: 12,4(Alt0) 18,2(Alt5) 40,4(Alt0) 52,5(Alt1)
PWM1: 13,4(Alt0) 19,2(Alt5) 41,4(Alt0) 45,4(Alt0) 53,5(Alt1)
1) Pin 18 is the only one available on all platforms, and
it is the one used by the I2S audio interface.
Pins 12 and 13 might be better choices on an A+, B+ or Pi2.
2) The onboard analogue audio output uses both PWM channels.
3) So be careful mixing audio and PWM.
4) Currently the clock must have been enabled and configured
by other means.
Params: pin Output pin (default 18) – see table
pin2 Output pin for other channel (default 19)
func Pin function (default 2 = Alt5) – see above
func2 Function for pin2 (default 2 = Alt5)
clock PWM clock frequency (informational)
The dialog for pwm looks like this:
The main difference is that you need to set the PWM Channel and PWM Chip instead of a pin. Chip is normally 0. Frequency is the PWM frequency while duty cycle defines how much on it is. Value is in percent. With invert polarity you can make 0 map to 100% on and vice versa.
In the menu you get a knob to select power when selected. In the server command you can still use on and off for 100 and 0% but also enter the percentage directly.
Run G-Code on change
The last 3 selections are very similar. They only differ in the action taken on signal change. Here we take a GPIO pin as input signal and execute an action on a switch from low to high or high to low. The dialog looks like this:
GPIO Pin is the input signal pin. Also some chips can define a pull-up or pull-down resistor internally, we can not do this. So it is best to a physical resistor to pull signal explicitly if required. Normally a resistor between 1k and 10k should make no problems.
Edge defines when to trigger and can be Falling (High to Low), Rising (Low to High) or Both.
Debounce time tells how long the signal must be stable to trigger. Especially important on cheap buttons that change signal at the beginning.
Last is the G-Code to execute on the selected printer. In this case we assume an external filament sensor that the server monitors. We make a info dialog pop up informing what the problem is and then pause the printer. Make sure the pause script moves away from the print.
Run web action on change
Same as previous input handling. The only difference is that you select from a dropdown list the web action that should be executed. Of course it must be defined previously in the Web Action tab.
Run external command on change
Same as the last 2 inputs. Here you select one the defined external action defined in extcommands.xml.
From those using the GPIO pins I guess 99% will be using one of the Raspberry PI models available. All later models share the same 40 pin GPIO header that is explicitly meant to extend the board. Apart from some 5V, 3.3V and ground pins, all can be used for input and output operations. If you can, spare those that can also be used as special functions like I2C or serial communication. If you want to use those, make sure no driver or software is using them.
Also already stated here I repeat that online tutorials use 2 different naming schemes. wiringPi and BCM. Here you need the BCM scheme as shown in the image below:
When you login via ssh you can check the pins and their configuration:
You can also use gpio to configure and change pins. Note that when you refer a pin you need -g option to tell gpio to use BCM numbering.