-
Notifications
You must be signed in to change notification settings - Fork 139
Device Info Tab
The device info tab is mostly informational and is not that relevant to CanOpenNode exporting. It is there for completeness and so that correct EDS files can be created and other EDS files imported and viewed/edited. Some fields are used for the reports and concrete node ID is also required for reports. The tool is also designed to not only create the CanOpenNode CO_OD.c and h but also generate the EDS files to ship to customers.
Device info follows the EDS specification CiA DSP-306
- Product name - The name of the product (max 243 characters)
- Product number - The vendor number of the product (Unsigned 32)
- vendor name - The name of the manufacture as registered with CiA (max 244 characters)
- vendor number - The number assigned to the vendor by CiA (Unsigned 32)
The product number and vendor number should also be the same as the identity object at 0x1008 sub 1 for vendor number and sub 2 product number
TODO - There is currently no link between these fields and the 0x1008 Identity object, also we do not currently support product revision (sub3). Also OrderCode is another field we are not currently supporting. Any editing of these fields should update the identity object and also warn if the loaded EDS has any mismatch.
The EDS contains information about itself. This is useful for version control management. This information is stored in the section [FileInfo] with in the EDS.
- File version - (Unsigned 8)
- File revision - (Unsigned 8)
- EDS version - Current version id 4.0
- Description - Max 243 characters
- Creation Date/Time - Creation time/date of the file
- Created By - Max 245 characters
- Modification Date Time - Last modified time (auto updates with each save)
- Modified By - Max 244 characters
The actual date and time fields are stored as independent date and time fields and are in the format Time (characters in format „hh:mm(AM|PM)“) Date (characters in format „mm-dd-yyyy“)
The character limits are imposed by the EDS specification. This tool will warn if it loads an eds out of spec and will only export as per the EDS specs. However internally and in the xml format there are no limits for length of these fields.
- No RX PDOS - How many RX PDOs are supported
- No Tx PDOS - How many TX PDOs are supported
These fields are auto generated by editing the PDOs within the tool. Adding/removing will update these numbers
This represents the various baudrate flags found within the EDS that state what rates the product supports. When exporting to CanOpenNode these have no effect but should reflect what your product supports.
These are various other settings that the EDS can state the device supports
- Simple bootup slave
- Simple bootup master
- Dynamic Channels Supported
- Compact PDO
- Group Messaging
- LSS Supported
- Granularity
None of these are used in the tool or by CanOpenNode they are provided only for EDS viewing and editing and there meanings are outside the scope of the tool. Please consult CiA DSP-306 and other CanOpen specs for more details.
This is an extra field used for reporting. When building a network of nodes it is possible to set the desired node address at this point. The reporting tool will then look for any $NODEID fields and replace these with the ID provided here. This allows the real device to still dynamically change its PDOS with node ID eg 0x180+$NODEID but the reporting tool can make sense of the real desire network.