Janez

You probably like to create SDO client to communicate with SDO server devices. It is used here in more advanced way (follow CO_GTWA_ST_WRITE): https://github.com/CANopenNode/CANopenNode/blob/c10043a11044f0c107b486dfbf01759e1ca9b6f5/309/CO_gateway_ascii.c#L1621 Take a look into CO_SDOclient.h. In...

SDO server is already part of every device made from CANopenNode. Here is some more information: https://canopennode.github.io/index.html

I really don't understand the question. How CANopenNode is used in your case?

Finally, example is there: https://github.com/CANopenNode/CANopenNode/blob/master/301/CO_SDOclient.h Should work, but, didn't test it. It should be valid for v2 and v4.

RTR bit is there only for completeness, but it is not used.

CO_SDOserver_initCallbackPre() may be used for wakeup in some operating systems. Please see https://github.com/CANopenNode/CANopenDemo/blob/master/demo/domainDemo.c for example. Actually, in the core (new object dictionary principle), each Object dictionary entry is accessed by...

Yes, this have to be solved, see #312

I think, up to 8 logical devices is best solution for your case. PDOs are not the problem. There are 4 TPDO and RPDOs, which just have pre-defined COB-IDs. You...

I think, this can be a good approach. PDOs will be automatically configured on startup. User could re-configure them in run-time, if he like so. If you will use eeprom...

Another, most flexible and elegant option for automatic (more than four) default PDOs when using logical devices may be extending `preDefinedCanId` argument in CANopen.c file: ``` uint16_t preDefinedCanId = i...