Saturday, May 11, 2019

Brick Interface

The Brick interface consists of three parts.

  1. Motor Control
  2. LED Control
  3. Input Control
Motor Control
The Motor Control is similar to the motor control in the original Brick Controller.  There are connectors for up to four motors.  In the original Brick Controller the motor control was either on or off, that is it was full speed or off.  In this version, I have implemented Pulse Width Modulation (PWM) control, thus allowing for independent speed control of each motor. I suspect that the first version of firmware and app software will not have this implemented yet, but will be an upgrade.

LED Control
There are controls for 10 LED sources.  LED 1- 9 are controlled by the LP5569 LED controller.  LED 10 is controlled by the PIC32 and is connected to a PWM generator in the PIC32, so it will have some lighting effects.  The LP5569 provides a wealth of capability.  I suspect like the motor controller it will be implemented in stages as the firmware and software coalesce into a working application.  If you want to see what the capabilities are, search the blog for LP5569.  There were 9 entries in the spring of 2018 where I was working on this as a standalone LED controller.

Input Control
While this was implemented in the original version, it was not very clear how to use it.  This time I put some more thought into it.  It is still very basic and it may still evolve.  Mostly I will need to verify that there is sufficient electrical protection on each input.  What I would like to see is a two fold interface.  First is an ON/OFF type input.  The user will connect the input to ground, provided in the connector, which will casue the running script to do something.  Second is to provide a variable voltage, 0 to 3.3VDC again this in the connector, to an input.  As the voltage changes, the running script will do something. The first option was implemented in the in the original version.  The second will take some thought as to how it will be implemented and thus will probably be an upgrade in the future.


No comments:

Post a Comment