Comments (13)
Hi,
In the latest standard (2019) there is still:
7.3.5 Device commissioning
There shall be an additional section in DCF with the entryDeviceComissioning
...
I think, this is intended, keyword in the standard can't just change.
from canopeneditor.
Thank you very much. I can confirm that this fixes the behavior.
PS: I have got an email from microsoft that your email was put into quarantine. Seems like it flagged the binaries inside the archive.
from canopeneditor.
Unfortunately, the standard (DSP306) defines the section with "DeviceComissioning". Clearly a typo, but unfortunately defined exactly like this.
This is why the file is written in conformity with the standard. A tool that evaluates this should therefore at least accept this way of writing.
from canopeneditor.
Oh, that is a weird thing. Thanks for the fast reply. I will try to fix it in the Python module then.
from canopeneditor.
DSP306 Version 1.1 Date: 29.06.2001 stated
5.3 Device Commissioning
There is an additional section in the DCF named DeviceComissioning:
(...)
Example:
[DeviceComissioning]
I do not have access to never versions of DSP306, maybe some one can take a look and report any changes.
from canopeneditor.
I just checked the version 1.3.0 from 2005. The typo with DeviceComissioning is still there, but I think I found a smaller thing which is on the CANopenEditor side.
There shall be an additional section in the DCF named DeviceComissioning:
NodeID shall indicate the device’s address (Unsigned8)
NodeName shall indicate the node name (max 246 characters)
Baudrate shall indicate the device’s baudrate (Unsigned16)
NetNumber shall indicate the number of the network (Unsigned32)
NetworkName shall indicate the name of the network (max 243 characters)
In a generated DCF with CANopenEditor I got
[DeviceComissioning]
NodeId=1
NodeName=
BaudRate=500
NetNumber=0
NetworkName=
So, NodeID and Baudrate seem to be a little off with the capitalization.
from canopeneditor.
Should be fixed in 76baf61 bugfix branch.
Please test and give feedback.
from canopeneditor.
Thank you for the fast fix, but where do I find the binaries? Is there a pipeline where I can download the artifacts?
from canopeneditor.
Thank you for the fast fix, but where do I find the binaries? Is there a pipeline where I can download the artifacts?
I release the binaries at irregular intervals, though I have been able to do at least a minimal test cycle.
You have received an email with the binaries
from canopeneditor.
Hm, can't find any email with an archive or a download link in my mailbox. Only the notifications with your replies.
from canopeneditor.
from canopeneditor.
I also just noticed that according to the standard the keys are not case sensitive. So strictly speaking this change wasn't even necessary. Sorry for the noise.
from canopeneditor.
It's okay, it can be good that others don't fit the standard. It doesn't hurt and I still had some life time left. :-)
from canopeneditor.
Related Issues (20)
- refactor CanopenEditor HOT 3
- Remove CanOpenNodeXML (inc bridge)
- Move import & export part of eds away from eds.cs
- Can't add item into OD HOT 6
- CanopenEditor: Exporting to XDD v1.0 format sets wrong type on "Highest sub-index supported" HOT 2
- System.ArgumentException with grid columns HOT 2
- Question: are the generated C files subject to (L)GPL? HOT 5
- Build and run instructions? HOT 2
- LSS Master/Slave parameters does not export to OD.c/h HOT 5
- Concrete Node Id does not propagate to proper value of $NODEID HOT 1
- Impossible to import .eds file from Weidmueller UR20-FBC-CAN HOT 5
- Column span out of the range of valid values (INT32) HOT 2
- Layout of PDO tab oversize out of window. HOT 3
- "not specified" type for Domain objects HOT 14
- Hello, about using CANopenEditor configuration SRDO problem HOT 4
- An error occurred while I was editing PDO obiect dictionary, such that I lose my modification. HOT 2
- Unsigned32 Variable in TPDO doesn't have proper data length in bits HOT 7
- EDS file seems to generate wrong access type for PLC TPDO and RPDO HOT 3
- PDO Mapping 'Invalid' not work while 'Export CanOpenNode' HOT 2
- TPDO and RPDO Assigned COB IDs HOT 4
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from canopeneditor.