esanya/fes-battery-control

Battery Controller for FES

fes-battery-control

Battery Controller for FES

Environment Setup

Install

• VirtualBox: https://www.virtualbox.org/wiki/Downloads
• LinuxMint: https://www.linuxmint.com/download.php

Clone Git Repo

• git clone https://github.com/esanya/fes-battery-control.git

Setup Python VEenv

• python3 -mvenv fes-battery-control (the same folder as the checked out repository)

Install Dependencies

• ./bin/pip3 install crccheck
• ./bin/pip3 install telemetrix
• ./bin/pip3 install paho-mqtt

Learning Python

• https://www.freecodecamp.org/news/python-code-examples-simple-python-program-example/
• https://realpython.com/python3-object-oriented-programming/

PCB

• https://www.circuito.io/app?components=9442,11021,417986,442979,942700,942700,2345678,2345678,2345678,2345678

Decoding the Protocol

The messages are defined as Kaitai Struct (https://kaitai.io/) in the protocol_fes.ksy file. Most of the messages are text. The LCD1 messages is binary.

Start the SW without HW

• socat -d -d pty,raw,echo=0 tcp-listen:8083
• ./bin/python3 ./dummybattery.py -p 8083 -lo=25
• socat -d -d pty,raw,echo=0 tcp-listen:8084
• ./bin/python3 ./dummybattery.py -p 8084 -lo=25
• mkfifo /tmp/bttrymngr_ctrl.fifo
• ./bin/python3 ./battery_ctrl.py -mt True -bu1 /dev/pts/X -bu2 /dev/pts/Y (/dev/pts/X,Y from the socat command output)

Read the logs

• tail -f /tmp/bttrymngr_report.log

Controll the SW

• echo "bat=all target_soc=70" > /tmp/bttrymngr_ctrl.fifo
• echo "bat=all charge" > /tmp/bttrymngr_ctrl.fifo
• echo "bat=all shutdown" > /tmp/bttrymngr_ctrl.fifo
• echo "bat=all target_soc=60" > /tmp/bttrymngr_ctrl.fifo
• echo "bat=all discharge" > /tmp/bttrymngr_ctrl.fifo
• echo "bat=all shutdown" > /tmp/bttrymngr_ctrl.fifo

fes-battery-control's Issues

Decode the complete LCD1 message

Decode the LCD1 message. Currently only the SOC is decoded from it, but there should be other valuable data in it...

This could be done/tried by:

• start the Windows management SW in a VM
• send emulated battery messages to the VM changing different bytes in LCD1
• check the management SW for changes

Autodetect USB devices

USB devices like:

• FES battery 1
• FES battery 2
• arduino

should be detected automatically somewhere in

fes-battery-control/battery_ctrl.py

Line 46 in 21c9b2a

This could be done by checking the output for the command dmesg | grep "attached now"

As the USB devices are attached they produce some specific output in dmesg....

Move LCD calls to separate thread

Create fifo within the BatteryManager

FIFO is created manually.

Should be created in the constructor:

fes-battery-control/batterymanager.py

Line 24 in 21c9b2a

Add buttons / potenciometer to manually interact with the device

The buttons and other input devices can be configured at:

fes-battery-control/batterymanager.py

Line 52 in efe1450

in a new method with lines similar like in method:

fes-battery-control/batterycontrol.py

Line 48 in efe1450

def initPin(self):

but the pins have to configured like AnalogInput or DigitalInput, for more docs: https://github.com/MrYsLab/telemetrix/

https://htmlpreview.github.io/?https://github.com/MrYsLab/telemetrix/blob/master/html/telemetrix/index.html#telemetrix.telemetrix.Telemetrix.set_pin_mode_analog_input

Examples:

https://github.com/MrYsLab/telemetrix/blob/master/examples/analog_input.py
https://github.com/MrYsLab/telemetrix/blob/master/examples/digital_input.py

Add to LCD some infos about charging / discharging status

Currently only target SOC and current SOC is displayed on the LCD.

fes-battery-control/batterymanager.py

Line 102 in 21c9b2a

def printCurrentStateToLcd(self):

Some info about the state of relays (charging/ discharging) should be added...

Integrate MQTT client

The SW should

• provide status / notifications via MQTT (publish to a topic).
• be controlled via MQTT (subscribe to a topic).