You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Instead of a Maestro for lights we're going to use a GPIO.
Steps:
Remove the existing Light class and and tests from the project.
Create a Light interface in the devices package. The flash method should do the same thing as the existing light class; just change between on/off at the same frequency.
Implement the interface using a pi4j gpio object. Place this in the io.rpi package. Some name like RaspberryGpioLight
Add the light channel to the config.
Add the light to the Rov ctor and manage.
SpeedValue no longer really works; the value is a boolean not a float range. For now you can just map the speedvalue to a boolean, until you recreate the lights value fully.
eventPublisher.valuesOfType(LightASpeedValue.class)
.startWith(newLightASpeedValue())
.map(SpeedValue::getSpeed)
.map(v -> v > 0.5)
The text was updated successfully, but these errors were encountered:
Instead of a Maestro for lights we're going to use a GPIO.
Steps:
Light
class and and tests from the project.Light
interface in thedevices
package. The flash method should do the same thing as the existing light class; just change between on/off at the same frequency.pi4j
gpio object. Place this in theio.rpi
package. Some name likeRaspberryGpioLight
Rov
ctor and manage.SpeedValue no longer really works; the value is a boolean not a float range. For now you can just map the speedvalue to a boolean, until you recreate the lights value fully.
The text was updated successfully, but these errors were encountered: