robincornelius
object kays not supported are grayed out, still visible
Consider 1018, identity, It is misleasing that access type is rw and memory type is ROM. This apparent contradition is simply resolved: the access type is not active.
It would be nicer if there were nothing visible at all.
This comes back to the fact that ROM/RAM/EEPROM are not part of CanOpen but part of the specific implementation.
With the current can open implementation. "ROM" objects are really variables in ram that are initialised from ROM at power up. So technically they can be written to, the value is volatile but there is a defined initialisation state so will be reset every power up/reboot.
If you consider the example EEPROM code its even worse. The "ROM" values are copied from EEPROM into ram at eeprom initialisation. It is also possible to perform a "save" function on the these variables and update their initialisation states, By using indexes 0x1010 and 0x1011 to force the save.
Any variables declared as "EEPROM" in canopennode will be written to eeprom as soon as their value changes.
I am reluctant to change things here as its nothing specificly to do with CanOpen and only the CanOpenNode implementation and also the fact that ROM is not really ROM in all cases.
