instantiations / pigpio-vast

Pigpio binding library for VA Smalltalk

Pigpio wrapper for VAST Platform (VA Smalltalk)

This is a Smalltalk wrapper of the C library pigpio to manage the GPIO pins of a Raspberry Pi
Explore the docs »

Report a defect | Request feature

This project is designed for anyone wanting to access GPIOs of a Raspberry Pi and starting with IoT. The library provides not just pulling up and down pins but also many of the most important protocols such as 1-Wire, I2C, SPI, etc.

License

• The code is licensed under MIT.
• The documentation is licensed under CC BY-SA 4.0.

Installation

1. Install VA Smalltalk 11.0.1 or newer.
2. Install Tonel support in your development image following this guide.
3. Clone this repository.
4. The easiest and recommended approach is to install it via a script:

| loader path |
path := (CfsPath named: '<insert path to root pigpio-vast local repo here>').
loader := TonelLoader readFromPath: path.
loader
	beUnattended; "do not prompt and use all defaults"
	useGitVersion.
loader loadAllMapsWithRequiredMaps.

Or you can load the Configuration Map RaspberryHardwareInterfaceCore from the context menu of the Configuration Maps Browser: "Import" -> "Load Configuration Maps from Tonel repository..." -> select path to root pigpio-vast local repo. This will open a dialog and will use convenient defaults for the load. Refer to its documentation for more details.

5. Optionally run the SUnit tests included in the map RaspberryHardwareInterfaceTest to ensure correct installation. One easy way is to right-click on the RaspberryHardwareInterfaceTest map name in the Name pane (as opposed to version pane ) and then select Test Loaded Applications.

Quick Start

• Download the latest ECAP from Instantiations
• Read some related blog posts

Acknowledgments

• vast-pigpio started as a clone of RaspberryHardwareInterface which was was a port done by Louis LaBrunda from Squeak's implementation done by Tim Rowledge.
• Norbert Schlemmer
• Gerardo Richarte
• Anton Petrov and HRWorks for their work on the MFRC522 wrapper
• Joan, pigpio author
• Github repository layout was generated with Ba-St Github-setup project.

Contributing

Check the Contribution Guidelines

pigpio-vast's Issues

Add shortcuts methods to pull up and down all pins in I2CDeviceGPIOMCP23017

Something like pullUpAllPins and pullDownAllPins that do output: 0 or output: 16rFFFF

Rename all Gpio to Pigpio

In many places of the RaspberryHardware core refers to the word GPIO instead of Pigpiod. Examples is the classes RaspberryGpioDaemonInterface and RaspberryGpioInterface. In that case the "Gpio" is not really GPIO as the phisical pin (hardware) but the LIBRARY. Therefore, that must be Pigpio.

There are probably other places than these 2 class names where it calls "Gpio" instead of "Pigpiod". We should try to rename as much as we can see.

Apply Instantiations coding standards to the library

At least some basic things like formatting on all the apps...

The test map should set SUnit as required map

Make GPIOPortMCP23017 more general and support native GPIOs

Right now, GPIOPortMCP23017 works with a device. The API of that device is basically a subset of I2CDeviceGPIOMCP23017. I believe that subset of functionality / API should eventually be moved up in the hierarchy (to I2cDevice or GpioBusDevice). That way, GPIOPortMCP23017 could be renamed to GPIOPort and depending on which device you pass, it would use either the GPIOs of MCP23017 or the native ones.

At this point, it would also be interesting to think if those GpioBusDevice and similar GPIO* classes should be renamed to Pigpio*.

Better document that we cannot use RaspberryGpioInterface but RaspberryGpioDaemonInterface

We should explain better that in VAST, we can only use RaspberryGpioDaemonInterface so far and that RaspberryGpioInterface crashes the VM. We should put that as class comments or even rename RaspberryGpioInterface to RaspberryGpioInterfaceBROKEN or move it to a separate subclass or something. In addition, we can implement RaspberryGpioInterface class >> raspberryGpioStart doing a self error: 'not supported... use daemon instead....

OneWireDS18B20ThermometerDevice>temperature problem

OneWireDS18B20ThermometerDevice>temperature fails to close the file after reading it. See new code below.

temperature
"Answer the current temperature value of this device. It is possible the device may not have reported a correct list
of data, so return 999 as a placeholder"
| file data pos tStr |

file := CfsReadFileStream open: devFilePath.
file isCfsError ifFalse: [
	data := file contents.
            file close.                                    "This is the new line."
	((data indexOfSubCollection: 'YES') > 0) ifTrue: [
		pos := data indexOfSubCollection: 't='.
		(pos > 0) ifTrue: [
			tStr := data copyFrom: pos + 2 to: data size.
			^tStr asNumber / 1000.0.
		].
	].
].
^999.

Bring Carrillon I2CDeviceGPIOMCP23017, GPIOPort etc to the base library

The Carrillon project has a nice I2CDeviceGPIOMCP23017 as well as reifieed the GPIOPort.
We should move all that from Carrillon to this repo.