Open klausz opened 1 year ago
@klausz Just wanted to give an update.
I've not been able to replicate this behavior but I have an intuition of where it's coming from. (Likely the lib we're using to have a file-select window for loading OD files).
That said, OreSat does have some other priorities at the moment in preparation for OreSat0.5, so I do apologize if this takes a bit before I can find and solve the problem.
Declaration of Node + EDS As a side question (prio low as there are other priorities):
network.connect (bustype = 'socketcan', channel='vcan0')
node0x3 = CANopen.Remote_Node(3, 'e35.eds')
network.add_node(0x3)
Best would be when i can test this incrementally with Jupyter Notebooks. Maybe there is an already existing test script where the information can be taken from. (Or a Video seeing how it works).
I encountered this same bug. I was able t figure out it came from putting a comment before an object definition
...
;comment
[1000]
...
@ryanpdx, I tried to test again but without success (as i had no 'comment' entries). Nevertheless you had it working. It would be good to have a very 'narrow' application working. There we need an .eds (or .dcf) and a .log file. Any idea from you or others? When this minimum solution is working each one can start to increase the data input and nail down the errors.
Describe the bug Cannot load the .eds files
To Reproduce Steps to reproduce the behavior: Having two different *.eds files in
../.cache/canopen_monitor
when starting the program:canon-monitor -I vcan0
an error message comes up:Expected behavior There should be no error. (On another PC there is no error message but eds parsing is not working
Environment (please complete the following information): Ubuntu 22.04
Additional context As side issue: Unfortunately on two different Ubuntu Linux PCs I never has the eds funktionality CANopen Data with Parsed EDS Data working)