supported_hardware:pigpio
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | |||
| supported_hardware:pigpio [2023/02/13 14:52] – external edit 127.0.0.1 | supported_hardware:pigpio [2023/04/10 12:57] (current) – removed raw HTML as that is no longer supported James Sentman | ||
|---|---|---|---|
| Line 36: | Line 36: | ||
| No units are created automatically by this plugin since there are so many pins it would be frustrating to have it create so many potentially unneeded units. Instead create a new Unit on your PIGPIO interface and set the Address of the unit to the pin number that you would like to control. XTension will ignore the pins that you do not have units configured for so they may be used by other processes without interference. | No units are created automatically by this plugin since there are so many pins it would be frustrating to have it create so many potentially unneeded units. Instead create a new Unit on your PIGPIO interface and set the Address of the unit to the pin number that you would like to control. XTension will ignore the pins that you do not have units configured for so they may be used by other processes without interference. | ||
| - | < | + | ----- |
| ===Digital Input:=== | ===Digital Input:=== | ||
| Line 54: | Line 54: | ||
| If you’re connecting the pin to a switch or a button you will need to set a debounce period. Any physical switch will have a few milliseconds during the transition where the actual read value will be switching wildly back and forth between on and off before it settles down. This value is the amount of time the reading must be stable in MICROseconds (not milliseconds) before the change will be reported. Without this you’re likely to get dozens or even hundreds of updates back and forth during the first fraction of a second after you press the button. A value of 10,000 is the default and seems good for most devices I’ve used it with. The value must be stable for 10 milliseconds before the change is reported. Value values are from 0 to 300,000. | If you’re connecting the pin to a switch or a button you will need to set a debounce period. Any physical switch will have a few milliseconds during the transition where the actual read value will be switching wildly back and forth between on and off before it settles down. This value is the amount of time the reading must be stable in MICROseconds (not milliseconds) before the change will be reported. Without this you’re likely to get dozens or even hundreds of updates back and forth during the first fraction of a second after you press the button. A value of 10,000 is the default and seems good for most devices I’ve used it with. The value must be stable for 10 milliseconds before the change is reported. Value values are from 0 to 300,000. | ||
| - | < | + | ----- |
| Line 61: | Line 61: | ||
| Digital output pins have no other options to setup. They will be connected to ground when the Unit in XTension is off and to the positive voltage of the Pi when turned on. (unless you set them to reverse logic in XTension) Please read the documentation on the Pi to learn how much current you can pull from these pins, (it’s not very much at all) before you will burn them out. You can connect a single LED to a pin with the proper resistor, but not one to every pin without some other external hardware to take the load off the Pi itself. | Digital output pins have no other options to setup. They will be connected to ground when the Unit in XTension is off and to the positive voltage of the Pi when turned on. (unless you set them to reverse logic in XTension) Please read the documentation on the Pi to learn how much current you can pull from these pins, (it’s not very much at all) before you will burn them out. You can connect a single LED to a pin with the proper resistor, but not one to every pin without some other external hardware to take the load off the Pi itself. | ||
| - | < | + | ----- |
| ===Servo Control:=== | ===Servo Control:=== | ||
| Line 70: | Line 70: | ||
| The Servo pin Unit also supports the “rate” parameter of the [[dictionary: | The Servo pin Unit also supports the “rate” parameter of the [[dictionary: | ||
| - | < | + | ----- |
| ===PWM=== | ===PWM=== | ||
| Line 79: | Line 79: | ||
| The PWM unit type lets you choose the PWM frequency of the output. Slower rates may produce visible and annoying flicker in any led’s attached, but very high frequencies may cause ballasted lamps to overheat and either burn out or become a fire hazard. In my testing a value of 800hz was more than enough to make the flickering invisible to my eye. | The PWM unit type lets you choose the PWM frequency of the output. Slower rates may produce visible and annoying flicker in any led’s attached, but very high frequencies may cause ballasted lamps to overheat and either burn out or become a fire hazard. In my testing a value of 800hz was more than enough to make the flickering invisible to my eye. | ||
| - | < | + | ----- |
| ===Hardware Serial Port=== | ===Hardware Serial Port=== | ||
| Line 92: | Line 92: | ||
| **IMPORTANT: | **IMPORTANT: | ||
| - | < | + | ----- |
| ===Software Serial Port=== | ===Software Serial Port=== | ||
| Line 105: | Line 105: | ||
| **IMPORTANT: | **IMPORTANT: | ||
| - | < | + | ----- |
| ===More Info=== | ===More Info=== | ||
| The pigpiod server has many more abilities than just the few pin types that I have supported in this first version. If you need 1-wire support or support for the various i2c or other devices that can be connected through it please let me know and I will move that up my to do list. | The pigpiod server has many more abilities than just the few pin types that I have supported in this first version. If you need 1-wire support or support for the various i2c or other devices that can be connected through it please let me know and I will move that up my to do list. | ||
supported_hardware/pigpio.1676299926.txt.gz · Last modified: 2023/02/13 14:52 by 127.0.0.1