colefuerth / bfg-research Goto Github PK

Current implementation of all I2C devices uses their raw addresses, they need to be reworked to use ports on the multiplexer.

The multiplexer will take TwoWire instances.

A map also needs to be created on which devices are on which ports.

Callable attributes should just be a description of each individual key, and then a separate table can match devices to their callable keys.

Packets appear to be sending correctly, but only blank responses have been recorded in python.

The arduino serial has been tested, and is confirmed to be working. JSON packets can be unpacked, evaluated, and repacked, then sent. The problem is in python

• make a table in the readme of all of the addresses

Arduino source folder can be confusing to read, should have documentation added

INA219 is a current sensor, and needs implementation.

• Implement on Arduino
• Add to Python device list
• Add to README database

The arduino has a series of messages for debugging and errors. The Pi, therefore, needs a system to differentiate between JSON packages, and debug messages/errors

So far, the only devices implemented and documented are the BFG devices, themselves. The remainder of the devices must be added to the documentation, with appropriate references.

Each payload response needs to be timestamped and logged

• Unpack payload into list
• Title the list
• Date stamp the list
• Log the unpackaged payload in the appropriate CSV file

arduino-cli libraries do not seem to work consistently across all machines.

My solution to this is, all libraries not native to the Arduino IDE, will be cloned from their source into the arduino/lib working directory.

The makefile build will still be exclusive to arduino-cli, but the libraries install command must only be git clones, for portability.

Device protected member _channel cannot be unsigned if the default channel is -1!

Devices with completed implementation on ARDUINO:

• LC709203F BFG
• LTC2941 BFG
• MAX17043 BFG
• TCA9548A I2C Multiplexer
• SHTC3 Temp and Humidity Sensor
• MAX31855 Thermocouple Amplifier
• INA260 Current/Voltage/Power sensor

it should definitely be loaded via arduino library rather than repository

All devices should have serial comms initialized in an begin() function, NOT in the constructor. This is just bad practice, and prevents effective debugging

The refresh time of readings must be determined, and implemented to be variable.

• Periodic calls to arduino for data packets
• Need to differentiate between monitoring devices, and BFGs
• Need to keep track of file size and available disk space
• Each packet sent should get a response before sending another one

Unlike its peers, the MAX31855 Thermocouple Amplifier uses a Serial Peripheral Interface.

This poses the problem, do we integrate the serial over pi, or over arduino?

Multiple devices call Wire.begin(). This breaks preexising wire connections, but most of the libraries will accept an exising TwoWire instance.

It is probably best to create one TwoWire instance in setup(), and pass it to all I2C initializations.

When serial payloads come back to the PC quickly, sometimes they get mashed together.

A solution for this will be, newline characters will be used as delimiters on the stream between serial packets.