loic/ina260-zmq-publisher
1
0
Fork 0
mirror of https://gitlab.com/manzerbredes/ina260-zmq-publisher.git synced 2025-04-08 14:29:10 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Minor changes

Browse source
This commit is contained in:
Loic Guegan 2023-07-18 13:06:53 +02:00
parent 7f87211b01
commit d489fa8d6d
2 changed files with 7 additions and 9 deletions

3
README.md
View file

@ -2,8 +2,7 @@
A ZeroMQ-based power monitoring publisher for the ina260 chip.\
This repository provides:
- `logger`: that collects power measurements from the ina260 using the dedicated driver
- `publisher`: that continuously publish the logger's data using the ZeroMQ pub/sub communication pattern
- `publisher`: that collects power measurements from the ina260 using the dedicated driver with a thread that continuously publish the power measurements data using the ZeroMQ pub/sub communication pattern
- `subscriber`: a program that collects the measurements published by the publishers (used to create a broker, frontend etc...)
*Note: Nothing is stored locally! Everything that is published by the publishers is either received by the subscriber or lost.*

13
config.mk
View file

@ -1,4 +1,4 @@
##### ZeroMQ
##### Network Communications
# ZMQ_PORT is the port used for all communications
ZMQ_PORT=5556
# SUBSCRIBER_ADDR is used by the publishers
@ -12,21 +12,20 @@ ZMQ_TOKEN=ina260-zmq-publisher
# Units is bytes
ZMQ_MSG_SIZE=5242880
##### Loggers/Publisher
##### Publishers/Subscriber
# LOG_DELAY defines the delay between 2 consecutive
# ina260 power read performed by the logger
# Unit is milliseconds
LOG_DELAY=1000
LOG_DELAY=0
# SUBSCRIBER_DIR will contain all the measurments
# received from the publishers
SUBSCRIBER_DIR=./data
# LOG_INTERVAL determined the duration
# of a logging period. At the end of a logging period,
# a file with all the power measurements is generated by the loggers in LOGGERS_DIR
# This file, is then transmitted by the publishers to the subscriber
# all the measurements are send by a publisher thread
# Unit is seconds
LOG_INTERVAL=20
# KEY is attached to all the messages published by the node
# It allows you to filter the messages received on the client
# KEY is attached to all the messages published to the subscriber
# It allows you to filter the messages on the publisher
# if you are using multiple monitoring nodes (multiple publishers)
KEY=node1