https://github.com/vemonitor/vedirect_m8
Victron Serial VeDirect Reader and simulator. Fork from karioja/vedirect
https://github.com/vemonitor/vedirect_m8
python3 reader serial-communication simulator vedirect victronenergy
Last synced: 3 months ago
JSON representation
Victron Serial VeDirect Reader and simulator. Fork from karioja/vedirect
- Host: GitHub
- URL: https://github.com/vemonitor/vedirect_m8
- Owner: vemonitor
- License: mit
- Created: 2022-05-26T18:30:58.000Z (over 3 years ago)
- Default Branch: main
- Last Pushed: 2024-08-30T04:08:46.000Z (over 1 year ago)
- Last Synced: 2025-09-25T15:24:23.142Z (4 months ago)
- Topics: python3, reader, serial-communication, simulator, vedirect, victronenergy
- Language: Python
- Homepage:
- Size: 1.27 MB
- Stars: 9
- Watchers: 2
- Forks: 4
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- Funding: .github/FUNDING.yml
- License: LICENSE
- Code of conduct: CODE_OF_CONDUCT.md
Awesome Lists containing this project
README
# VeDirect M8
[](https://pypi.org/project/vedirect_m8/)
[](https://snyk.io/test/github/mano8/vedirect_m8)
[](https://codecov.io/gh/vemonitor/vedirect_m8)
[](https://www.codacy.com/gh/mano8/vedirect_m8/dashboard?utm_source=github.com&utm_medium=referral&utm_content=mano8/vedirect_m8&utm_campaign=Badge_Grade)
[](https://pepy.tech/project/vedirect_m8)
## Description
This is a Python library for decoding the Victron Energy VE.Direct text protocol
used in their range of MPPT solar charge controllers and battery monitors.
This is a forked version of a package originally created by Janne Kario
[VeDirect](https://github.com/karioja/vedirect).
This version was originally developed for the [vemonitor_m8](https://github.com/vemonitor/vemonitor_m8) package.
## Installation
To install directly from GitHub:
``python3 -m pip install "git+https://github.com/mano8/vedirect_m8"``
To install from PypI :
``python3 -m pip install vedirect_m8``
## Test on virtual serial port
The sim_data directory contains a set of live recordings of the serial port data
sent by the 3 devices that I own.
* SmartSolar MPPT 100/20 running firmware version 1.39
* BlueSolar MPPT 75/15 running firmware version 1.23
* BVM 702 battery monitor running firmware version 3.08
On unix systems, these recordings can be fed to the Vedirect decoder
using a pair of virtual serial ports.
First you need install socat on your machine.
On debian systems type on your terminal :
```bash
sudo apt-get install socat
```
Next install the vedirect_m8 package ``see above``.
Now, to create a pair of virtual serial ports issue the following command:
```bash
socat -d -d PTY,raw,echo=0,link=/${HOME}/vmodem0 PTY,raw,echo=0,link=/${HOME}/vmodem1
```
This will create 2 virtual serials ports connected to each other.
Anything sent to ```/${HOME}/vmodem0``` will be echoed to ```/${HOME}/vmodem1``` and vice versa.
In other terminal, run the vedirectsim script with your desired device:
```bash
python examples/vedirectsim.py --port /${HOME}/vmodem0 --device bmv702
```
Or if you need to see the inputs sent on serial port :
```bash
python examples/vedirectsim.py --port /${HOME}/vmodem0 --device bmv702 --debug
```
Device option must be ``bmv702, bluesolar_1.23, or smartsolar_1.39``.
Then, in other terminal, attach the decoder to /${HOME}/vmodem1:
```bash
python examples/vedirect_print.py --port /${HOME}/vmodem1
```
All the inputs from the selected device file, are encoded to the vmodem0 serial port,
then echoed to the vmodem1 by socat, and finally decoded by the vedirect module.
## The Vedirect Controller
This script extends from Vedirect,
and add ability to automate connection to serial port.
Useful if you don't know the serial port,
or if you disconnect VeDirect USB cables and don't reconnect on sames USB ports.
To do so, we need a serialTest extra configuration settings.
Warning, all the test must successful for validate the serial port.
### Available serialTest
Two test types, can be used to validate a serial port.
#### 1. Value Tests
This type of test evaluates whether the key value from the decoded data
is equal to the provided value.
The configuration must contain the following parameters :
* typeTest: must be equal to ```value``` here.
* key: the key of the value to tested from decoded data
* value: the value to test must be equal of the value of the key from decoded data
Must be used only on static keys values egg ```PID```, ```SER#``` or , ```FW```.
Example for the bmv702 device from sim_data directory:
```python
'serialTest':{
'PID_test': {
"typeTest": "value",
"key": "PID",
"value": "0x203" # the value to test
},
'FW_test': {
"typeTest": "value",
"key": "FW",
"value": "308" # the value to test
}
}
```
In this example, we search a serial port, sending vedirect encoded data
containing at least,
the keys ```PID``` and ```FW```, whose values are respectively
```0x203``` and ```308```.
#### 2. Column keys Tests
This type of test evaluates whether the all the keys provided exists
in the decoded data.
The configuration must contain the following parameters :
* typeTest: must be equal to ```value``` here.
* keys: the keys that must be present in the decoded data
Example for the bmv702 device from sim_data directory:
```json
"serialTest": {
"KeysTest": {
"typeTest": "value",
"keys": ["V", "I", "P", "CE", "SOC", "H18"]
}
}
```
In this example, we search a serial port, sending vedirect encoded data
containing at least,
the keys ```[ "V", "I", "P", "CE", "SOC", "H18" ]```
### Complete configuration example
Example with Complete configuration :
```python
from vedirect_m8.ve_controller import VedirectController
def print_data_callback(packet):
print(packet)
if __name__ == '__main__':
conf = {
'serialPort': "/${HOME}/vmodem1",
'timeout': 0,
'serialTest':{
'PID_test': {
"typeTest": "value",
"key": "PID",
"value": "0x203"
},
'FW_test': {
"typeTest": "value",
"key": "FW",
"value": "308"
},
"KeysTest": {
"typeTest": "columns",
"keys": [ "V", "I", "P", "CE", "SOC", "H18" ]
}
}
}
ve = VedirectController(**conf)
ve.read_data_callback(print_data_callback)
```
In this example, we search a serial port,
sending vedirect encoded data containing at least:
* the keys ```[ "V", "I", "P", "CE", "SOC", "H18" ]```
* and the keys ```PID``` and ```FW```,
whose values are respectively ```0x203``` and ```308```.
When the script is initialized, it first tries to connect to the
```/${HOME}/vmodem1``` serial port.
If the connection fails, it waits for an available serial port
that matches all the tests above.
Then, when a valid serial port is found, it will start
to decode VeDirect data from that serial port normally.
Later, if you disconnect the serial USB cable
and reconnect it to another USB port, the serial port
will change and the connection will fail.
This will restart the same process, it is waiting for an available serial port
that matches all the tests above. Then, when a valid serial port is found,
it resumes decoding VeDirect data from that serial port normally.