Visualize CANopen Data with retrieved *.eds decription - use: oresat / CANopen-monitor
Budget: $10 – $30 USD
Whats needed:
Having CANopen data from CANdump and also *.eds files there is a need to make this data readable.
It seems the best suited python opensource tool that can be used withe Linux is oresat / CANopen-monitor (on github). Unfortunately it seems there are errors in the program.
https://github.com/oresat/CANopen-monitor/issues/86
Therefore - based on the available source code - this should be fixed so that its possible to have the CANopen data described based on the eds files given per node.
If there is another solution/program it should be brought up. This will be adressed in a different milestone
---------
More formal:
Requirement:
Need for a Linux-/Python based program to decode a min 2 node CANopen Network signals with the corresponding *.eds files. It should also work for other *.eds files and CANopen Daten which is not published.
Use Program:
CANopen monitor from Oresat https://github.com/oresat/CANopen-monitor seems to fit best.
But there seem to be error(s).
Use:
OS: Ubuntu Linux 22.04 (20.04 should also work).
Setup:
Installation (if needed use sudo):
sudo pip install canopen-monitor
start programm
sudo canopen-monitor -i vcan0
Declare two nodes with the eds files (its unclear how tis is done; code needed):
Node 0x1a
BreadcrumbsCANopen-monitor/canopen_monitor/assets/eds/GPS_OD.eds
https://github.com/oresat/CANopen-monitor/blob/master/canopen_monitor/assets/eds/GPS_OD.eds
Node 0x32
CANopen-monitor/canopen_monitor/assets/eds/CFC_OD.eds
https://github.com/oresat/CANopen-monitor/blob/master/canopen_monitor/assets/eds/CFC_OD.eds
Communicate:
cansend vcan0 100#111111111138 (should deliver 04/22/2023 07:32:11.15300)
PDO:
TPDO1
cansend vcan0 19a#0000 -> There should be eds data (no error message) in the Miscellaneous Part of screen
RPDO1
cansend vcan0 21a#0000 -> There should be eds data (no error message) in the Miscellaneous Part of screen
TPDO2
cansend vcan0 2b2#0000 -> There should be eds data (no error message) in the Miscellaneous Part of screen
RPDO2
cansend vcan0 332#0000 -> There should be eds data (no error message) in the Miscellaneous Part of screen
TSDO TX
cansend vcan0 59a#0721010000000000 -> Show 'cycles per second' from eds SDO + Value Node 1
cansend vcan0 5b2#3021030000000000 -> Show 'Epoch time offset ms' from eds SDO + Value Node 2
TSDO RX
cansend vcan0 61a#0721010000000000 -> Show 'cycles per second' from eds SDO + Value Node 1
cansend vcan0 632#3021030000000000 -> Show 'Epoch time offset ms' from eds SDO + Value Node 2
NMT/Heartbeat:
cansend vcan0 71a#00 -> Status Alive Boot up
cansend vcan0 71a#05 -> Alive Operational
cansend vcan0 732#00 -> Status Alive Boot up
cansend vcan0 732#05 -> Alive Operational
The error is also described here:
https://github.com/oresat/CANopen-monitor/issues/86
xxxxxxxxxxxxx
I think it makes sense to have different milestones:
#1 Show the output when the program is working. This can be a video with whatever data (from the working CANopen-monitr application) or a video/some screenshots after you have investigated to make it working.
#2 Explain how to make it working on my Ubuntu Linux machine, with the CANopen data give and sent through the cansend command
#3 Having it working with ovn CANopen CANdump data and own *.eds files. Data is confidential and will not be given away.
Alternatively
#9 Suggest another opensource program that can ce used instead of CANopen-monitor.
Add-on
#11 Show how this can be done with Jupyter Notebooks (better for iterative incremental software development)
Having CANopen data from CANdump and also *.eds files there is a need to make this data readable.
It seems the best suited python opensource tool that can be used withe Linux is oresat / CANopen-monitor (on github). Unfortunately it seems there are errors in the program.
https://github.com/oresat/CANopen-monitor/issues/86
Therefore - based on the available source code - this should be fixed so that its possible to have the CANopen data described based on the eds files given per node.
If there is another solution/program it should be brought up. This will be adressed in a different milestone
---------
More formal:
Requirement:
Need for a Linux-/Python based program to decode a min 2 node CANopen Network signals with the corresponding *.eds files. It should also work for other *.eds files and CANopen Daten which is not published.
Use Program:
CANopen monitor from Oresat https://github.com/oresat/CANopen-monitor seems to fit best.
But there seem to be error(s).
Use:
OS: Ubuntu Linux 22.04 (20.04 should also work).
Setup:
Installation (if needed use sudo):
sudo pip install canopen-monitor
start programm
sudo canopen-monitor -i vcan0
Declare two nodes with the eds files (its unclear how tis is done; code needed):
Node 0x1a
BreadcrumbsCANopen-monitor/canopen_monitor/assets/eds/GPS_OD.eds
https://github.com/oresat/CANopen-monitor/blob/master/canopen_monitor/assets/eds/GPS_OD.eds
Node 0x32
CANopen-monitor/canopen_monitor/assets/eds/CFC_OD.eds
https://github.com/oresat/CANopen-monitor/blob/master/canopen_monitor/assets/eds/CFC_OD.eds
Communicate:
cansend vcan0 100#111111111138 (should deliver 04/22/2023 07:32:11.15300)
PDO:
TPDO1
cansend vcan0 19a#0000 -> There should be eds data (no error message) in the Miscellaneous Part of screen
RPDO1
cansend vcan0 21a#0000 -> There should be eds data (no error message) in the Miscellaneous Part of screen
TPDO2
cansend vcan0 2b2#0000 -> There should be eds data (no error message) in the Miscellaneous Part of screen
RPDO2
cansend vcan0 332#0000 -> There should be eds data (no error message) in the Miscellaneous Part of screen
TSDO TX
cansend vcan0 59a#0721010000000000 -> Show 'cycles per second' from eds SDO + Value Node 1
cansend vcan0 5b2#3021030000000000 -> Show 'Epoch time offset ms' from eds SDO + Value Node 2
TSDO RX
cansend vcan0 61a#0721010000000000 -> Show 'cycles per second' from eds SDO + Value Node 1
cansend vcan0 632#3021030000000000 -> Show 'Epoch time offset ms' from eds SDO + Value Node 2
NMT/Heartbeat:
cansend vcan0 71a#00 -> Status Alive Boot up
cansend vcan0 71a#05 -> Alive Operational
cansend vcan0 732#00 -> Status Alive Boot up
cansend vcan0 732#05 -> Alive Operational
The error is also described here:
https://github.com/oresat/CANopen-monitor/issues/86
xxxxxxxxxxxxx
I think it makes sense to have different milestones:
#1 Show the output when the program is working. This can be a video with whatever data (from the working CANopen-monitr application) or a video/some screenshots after you have investigated to make it working.
#2 Explain how to make it working on my Ubuntu Linux machine, with the CANopen data give and sent through the cansend command
#3 Having it working with ovn CANopen CANdump data and own *.eds files. Data is confidential and will not be given away.
Alternatively
#9 Suggest another opensource program that can ce used instead of CANopen-monitor.
Add-on
#11 Show how this can be done with Jupyter Notebooks (better for iterative incremental software development)