<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent posts to Discussion</title><link href="https://sourceforge.net/p/canopennode/discussion/" rel="alternate"/><link href="https://sourceforge.net/p/canopennode/discussion/feed.atom" rel="self"/><id>https://sourceforge.net/p/canopennode/discussion/</id><updated>2026-05-26T12:15:04.448000Z</updated><subtitle>Recent posts to Discussion</subtitle><entry><title>Automatic recovery after Error</title><link href="https://sourceforge.net/p/canopennode/discussion/387151/thread/fbde4243ef/?limit=100#2262" rel="alternate"/><published>2026-05-26T12:15:04.448000Z</published><updated>2026-05-26T12:15:04.448000Z</updated><author><name>TrojanObelix</name><uri>https://sourceforge.net/u/trojanobelix/</uri></author><id>https://sourceforge.netbe455dc96f6e6656b28e395b86bb6b16c84b77ed</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Hi Janez,&lt;/p&gt;
&lt;p&gt;I’m currently working on 100% compatible successors to our existing IO nodes, using an STM32G491 and the latest stack. &lt;/p&gt;
&lt;p&gt;My problem is that, following an error, the NMT master in the field attempts to reactivate the node exclusively via the NMT command “Start Node”. However, as the error register 0x1001 is still not equal to 0, the transition from PreOperational to Operational is not carried out.&lt;/p&gt;
&lt;p&gt;Only when I first reset it using the NMT command ‘Reset Communication’ – as can be seen at the end of the log – is the error register cleared, and the node can be returned to Operational mode via the NMT command ‘Start Node’.&lt;/p&gt;
&lt;p&gt;As the new IO nodes must also work on older systems (i.e. older NMT masters), I need an AutoRecovery function (as you once called it). Is this already available in the current stack? If not, can you give me a tip on where and how this would be best implemented? &lt;/p&gt;
&lt;p&gt;Best regards from Germany! &lt;br/&gt;
Dirk&lt;/p&gt;
&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;No&lt;/th&gt;
&lt;th&gt;Time (abs)&lt;/th&gt;
&lt;th&gt;ID (hex)&lt;/th&gt;
&lt;th&gt;Data (hex)&lt;/th&gt;
&lt;th&gt;Node-ID (dec)&lt;/th&gt;
&lt;th&gt;Object Type&lt;/th&gt;
&lt;th&gt;Message&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;85.750&lt;/td&gt;
&lt;td&gt;01:07:23.280.422.3&lt;/td&gt;
&lt;td&gt;70B&lt;/td&gt;
&lt;td&gt;FF&lt;/td&gt;
&lt;td&gt;11&lt;/td&gt;
&lt;td&gt;Monitoring&lt;/td&gt;
&lt;td&gt;PreOperational    *&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;85.768&lt;/td&gt;
&lt;td&gt;01:07:24.278.784.2&lt;/td&gt;
&lt;td&gt;70B&lt;/td&gt;
&lt;td&gt;RTR (DLC=1)&lt;/td&gt;
&lt;td&gt;11&lt;/td&gt;
&lt;td&gt;Node guarding&lt;/td&gt;
&lt;td&gt;request&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;85.773&lt;/td&gt;
&lt;td&gt;01:07:24.280.710.8&lt;/td&gt;
&lt;td&gt;70B&lt;/td&gt;
&lt;td&gt;7F&lt;/td&gt;
&lt;td&gt;11&lt;/td&gt;
&lt;td&gt;Monitoring&lt;/td&gt;
&lt;td&gt;PreOperational&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;85.778&lt;/td&gt;
&lt;td&gt;01:07:24.713.608.3&lt;/td&gt;
&lt;td&gt;0&lt;/td&gt;
&lt;td&gt;01 0B&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;NMT&lt;/td&gt;
&lt;td&gt;Node-ID 11  start remote node&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;85.785&lt;/td&gt;
&lt;td&gt;01:07:25.019.632.7&lt;/td&gt;
&lt;td&gt;60B&lt;/td&gt;
&lt;td&gt;40 01 10 00 00 00 00 00&lt;/td&gt;
&lt;td&gt;11&lt;/td&gt;
&lt;td&gt;SSDOreq #1&lt;/td&gt;
&lt;td&gt;Read  1001.00  Init Sequence  'ErrorRegister'&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;85.787&lt;/td&gt;
&lt;td&gt;01:07:25.020.898.2&lt;/td&gt;
&lt;td&gt;58B&lt;/td&gt;
&lt;td&gt;4F 01 10 00 10 00 00 00&lt;/td&gt;
&lt;td&gt;11&lt;/td&gt;
&lt;td&gt;SSDOresp #1&lt;/td&gt;
&lt;td&gt;Read  1001.00  'ErrorRegister' = 16&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;85.792&lt;/td&gt;
&lt;td&gt;01:07:25.278.364.9&lt;/td&gt;
&lt;td&gt;70B&lt;/td&gt;
&lt;td&gt;RTR (DLC=1)&lt;/td&gt;
&lt;td&gt;11&lt;/td&gt;
&lt;td&gt;Node guarding&lt;/td&gt;
&lt;td&gt;request&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;85.796&lt;/td&gt;
&lt;td&gt;01:07:25.280.599.4&lt;/td&gt;
&lt;td&gt;70B&lt;/td&gt;
&lt;td&gt;FF&lt;/td&gt;
&lt;td&gt;11&lt;/td&gt;
&lt;td&gt;Monitoring&lt;/td&gt;
&lt;td&gt;PreOperational    *&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;85.812&lt;/td&gt;
&lt;td&gt;01:07:26.277.954.3&lt;/td&gt;
&lt;td&gt;70B&lt;/td&gt;
&lt;td&gt;RTR (DLC=1)&lt;/td&gt;
&lt;td&gt;11&lt;/td&gt;
&lt;td&gt;Node guarding&lt;/td&gt;
&lt;td&gt;request&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;85.816&lt;/td&gt;
&lt;td&gt;01:07:26.280.270.1&lt;/td&gt;
&lt;td&gt;70B&lt;/td&gt;
&lt;td&gt;7F&lt;/td&gt;
&lt;td&gt;11&lt;/td&gt;
&lt;td&gt;Monitoring&lt;/td&gt;
&lt;td&gt;PreOperational&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;85.828&lt;/td&gt;
&lt;td&gt;01:07:26.992.687.0&lt;/td&gt;
&lt;td&gt;0&lt;/td&gt;
&lt;td&gt;01 0B&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;NMT&lt;/td&gt;
&lt;td&gt;Node-ID 11  start remote node&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;85.833&lt;/td&gt;
&lt;td&gt;01:07:27.277.572.3&lt;/td&gt;
&lt;td&gt;70B&lt;/td&gt;
&lt;td&gt;RTR (DLC=1)&lt;/td&gt;
&lt;td&gt;11&lt;/td&gt;
&lt;td&gt;Node guarding&lt;/td&gt;
&lt;td&gt;request&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;85.837&lt;/td&gt;
&lt;td&gt;01:07:27.279.784.1&lt;/td&gt;
&lt;td&gt;70B&lt;/td&gt;
&lt;td&gt;FF&lt;/td&gt;
&lt;td&gt;11&lt;/td&gt;
&lt;td&gt;Monitoring&lt;/td&gt;
&lt;td&gt;PreOperational    *&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;85.853&lt;/td&gt;
&lt;td&gt;01:07:28.141.570.0&lt;/td&gt;
&lt;td&gt;0&lt;/td&gt;
&lt;td&gt;82 0B&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;NMT&lt;/td&gt;
&lt;td&gt;Node-ID 11  reset communication&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;85.854&lt;/td&gt;
&lt;td&gt;01:07:28.277.149.7&lt;/td&gt;
&lt;td&gt;70B&lt;/td&gt;
&lt;td&gt;RTR (DLC=1)&lt;/td&gt;
&lt;td&gt;11&lt;/td&gt;
&lt;td&gt;Node guarding&lt;/td&gt;
&lt;td&gt;request&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;85.858&lt;/td&gt;
&lt;td&gt;01:07:28.304.313.8&lt;/td&gt;
&lt;td&gt;70B&lt;/td&gt;
&lt;td&gt;00&lt;/td&gt;
&lt;td&gt;11&lt;/td&gt;
&lt;td&gt;Bootup&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;85.859&lt;/td&gt;
&lt;td&gt;01:07:28.327.334.8&lt;/td&gt;
&lt;td&gt;60B&lt;/td&gt;
&lt;td&gt;40 00 10 00 00 00 00 00&lt;/td&gt;
&lt;td&gt;11&lt;/td&gt;
&lt;td&gt;SSDOreq #1&lt;/td&gt;
&lt;td&gt;Read  1000.00  Init Sequence  'Device Type'&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;85.860&lt;/td&gt;
&lt;td&gt;01:07:28.328.570.3&lt;/td&gt;
&lt;td&gt;58B&lt;/td&gt;
&lt;td&gt;43 00 10 00 91 01 8F 00&lt;/td&gt;
&lt;td&gt;11&lt;/td&gt;
&lt;td&gt;SSDOresp #1&lt;/td&gt;
&lt;td&gt;Read  1000.00  'Device Type' = 008F0191h&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;85.861&lt;/td&gt;
&lt;td&gt;01:07:28.357.279.1&lt;/td&gt;
&lt;td&gt;60B&lt;/td&gt;
&lt;td&gt;40 18 10 00 00 00 00 00&lt;/td&gt;
&lt;td&gt;11&lt;/td&gt;
&lt;td&gt;SSDOreq #1&lt;/td&gt;
&lt;td&gt;Read  1018.00  Init Sequence  'Highest sub-index supported'&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;85.862&lt;/td&gt;
&lt;td&gt;01:07:28.358.506.6&lt;/td&gt;
&lt;td&gt;58B&lt;/td&gt;
&lt;td&gt;4F 18 10 00 04 00 00 00&lt;/td&gt;
&lt;td&gt;11&lt;/td&gt;
&lt;td&gt;SSDOresp #1&lt;/td&gt;
&lt;td&gt;Read  1018.00  'Highest sub-index supported' = 4&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;85.863&lt;/td&gt;
&lt;td&gt;01:07:28.387.285.4&lt;/td&gt;
&lt;td&gt;60B&lt;/td&gt;
&lt;td&gt;40 18 10 01 00 00 00 00&lt;/td&gt;
&lt;td&gt;11&lt;/td&gt;
&lt;td&gt;SSDOreq #1&lt;/td&gt;
&lt;td&gt;Read  1018.01  Init Sequence  'Vendor-ID'&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;85.864&lt;/td&gt;
&lt;td&gt;01:07:28.389.233.3&lt;/td&gt;
&lt;td&gt;58B&lt;/td&gt;
&lt;td&gt;43 18 10 01 0C 01 00 00&lt;/td&gt;
&lt;td&gt;11&lt;/td&gt;
&lt;td&gt;SSDOresp #1&lt;/td&gt;
&lt;td&gt;Read  1018.01  'Vendor-ID' = 0000010Ch&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;85.865&lt;/td&gt;
&lt;td&gt;01:07:28.417.253.6&lt;/td&gt;
&lt;td&gt;60B&lt;/td&gt;
&lt;td&gt;40 18 10 02 00 00 00 00&lt;/td&gt;
&lt;td&gt;11&lt;/td&gt;
&lt;td&gt;SSDOreq #1&lt;/td&gt;
&lt;td&gt;Read  1018.02  Init Sequence  'Product code'&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;85.866&lt;/td&gt;
&lt;td&gt;01:07:28.418.517.8&lt;/td&gt;
&lt;td&gt;58B&lt;/td&gt;
&lt;td&gt;43 18 10 02 CD 00 00 00&lt;/td&gt;
&lt;td&gt;11&lt;/td&gt;
&lt;td&gt;SSDOresp #1&lt;/td&gt;
&lt;td&gt;Read  1018.02  'Product code' = 000000CDh&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;85.867&lt;/td&gt;
&lt;td&gt;01:07:28.447.269.9&lt;/td&gt;
&lt;td&gt;60B&lt;/td&gt;
&lt;td&gt;40 18 10 03 00 00 00 00&lt;/td&gt;
&lt;td&gt;11&lt;/td&gt;
&lt;td&gt;SSDOreq #1&lt;/td&gt;
&lt;td&gt;Read  1018.03  Init Sequence  'Revision number'&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;85.868&lt;/td&gt;
&lt;td&gt;01:07:28.448.528.1&lt;/td&gt;
&lt;td&gt;58B&lt;/td&gt;
&lt;td&gt;43 18 10 03 02 00 00 00&lt;/td&gt;
&lt;td&gt;11&lt;/td&gt;
&lt;td&gt;SSDOresp #1&lt;/td&gt;
&lt;td&gt;Read  1018.03  'Revision number' = 00000002h&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;85.869&lt;/td&gt;
&lt;td&gt;01:07:28.477.238.2&lt;/td&gt;
&lt;td&gt;60B&lt;/td&gt;
&lt;td&gt;40 18 10 04 00 00 00 00&lt;/td&gt;
&lt;td&gt;11&lt;/td&gt;
&lt;td&gt;SSDOreq #1&lt;/td&gt;
&lt;td&gt;Read  1018.04  Init Sequence  'Serial number'&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;85.870&lt;/td&gt;
&lt;td&gt;01:07:28.478.460.4&lt;/td&gt;
&lt;td&gt;58B&lt;/td&gt;
&lt;td&gt;43 18 10 04 00 00 00 00&lt;/td&gt;
&lt;td&gt;11&lt;/td&gt;
&lt;td&gt;SSDOresp #1&lt;/td&gt;
&lt;td&gt;Read  1018.04  'Serial number' = 00000000h&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;85.886&lt;/td&gt;
&lt;td&gt;01:07:29.271.769.7&lt;/td&gt;
&lt;td&gt;0&lt;/td&gt;
&lt;td&gt;01 0B&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;NMT&lt;/td&gt;
&lt;td&gt;Node-ID 11  start remote node&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;85.892&lt;/td&gt;
&lt;td&gt;01:07:29.276.753.1&lt;/td&gt;
&lt;td&gt;70B&lt;/td&gt;
&lt;td&gt;RTR (DLC=1)&lt;/td&gt;
&lt;td&gt;11&lt;/td&gt;
&lt;td&gt;Node guarding&lt;/td&gt;
&lt;td&gt;request&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;85.893&lt;/td&gt;
&lt;td&gt;01:07:29.276.995.0&lt;/td&gt;
&lt;td&gt;70B&lt;/td&gt;
&lt;td&gt;05&lt;/td&gt;
&lt;td&gt;11&lt;/td&gt;
&lt;td&gt;Monitoring&lt;/td&gt;
&lt;td&gt;Operational&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;85.908&lt;/td&gt;
&lt;td&gt;01:07:29.849.632.6&lt;/td&gt;
&lt;td&gt;60B&lt;/td&gt;
&lt;td&gt;40 01 10 00 00 00 00 00&lt;/td&gt;
&lt;td&gt;11&lt;/td&gt;
&lt;td&gt;SSDOreq #1&lt;/td&gt;
&lt;td&gt;Read  1001.00  Init Sequence  'ErrorRegister'&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;85.909&lt;/td&gt;
&lt;td&gt;01:07:29.850.138.4&lt;/td&gt;
&lt;td&gt;58B&lt;/td&gt;
&lt;td&gt;4F 01 10 00 00 00 00 00&lt;/td&gt;
&lt;td&gt;11&lt;/td&gt;
&lt;td&gt;SSDOresp #1&lt;/td&gt;
&lt;td&gt;Read  1001.00  'ErrorRegister' = 0&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;85.922&lt;/td&gt;
&lt;td&gt;01:07:30.276.362.5&lt;/td&gt;
&lt;td&gt;70B&lt;/td&gt;
&lt;td&gt;RTR (DLC=1)&lt;/td&gt;
&lt;td&gt;11&lt;/td&gt;
&lt;td&gt;Node guarding&lt;/td&gt;
&lt;td&gt;request&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;85.923&lt;/td&gt;
&lt;td&gt;01:07:30.276.783.0&lt;/td&gt;
&lt;td&gt;70B&lt;/td&gt;
&lt;td&gt;85&lt;/td&gt;
&lt;td&gt;11&lt;/td&gt;
&lt;td&gt;Monitoring&lt;/td&gt;
&lt;td&gt;Operational       *&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;85.950&lt;/td&gt;
&lt;td&gt;01:07:31.275.945.2&lt;/td&gt;
&lt;td&gt;70B&lt;/td&gt;
&lt;td&gt;RTR (DLC=1)&lt;/td&gt;
&lt;td&gt;11&lt;/td&gt;
&lt;td&gt;Node guarding&lt;/td&gt;
&lt;td&gt;request&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;85.951&lt;/td&gt;
&lt;td&gt;01:07:31.276.155.1&lt;/td&gt;
&lt;td&gt;70B&lt;/td&gt;
&lt;td&gt;05&lt;/td&gt;
&lt;td&gt;11&lt;/td&gt;
&lt;td&gt;Monitoring&lt;/td&gt;
&lt;td&gt;Operational&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;85.978&lt;/td&gt;
&lt;td&gt;01:07:32.275.547.9&lt;/td&gt;
&lt;td&gt;70B&lt;/td&gt;
&lt;td&gt;RTR (DLC=1)&lt;/td&gt;
&lt;td&gt;11&lt;/td&gt;
&lt;td&gt;Node guarding&lt;/td&gt;
&lt;td&gt;request&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;85.979&lt;/td&gt;
&lt;td&gt;01:07:32.275.937.8&lt;/td&gt;
&lt;td&gt;70B&lt;/td&gt;
&lt;td&gt;85&lt;/td&gt;
&lt;td&gt;11&lt;/td&gt;
&lt;td&gt;Monitoring&lt;/td&gt;
&lt;td&gt;Operational       *&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;</summary></entry><entry><title>CAN Open Node stack on dual port</title><link href="https://sourceforge.net/p/canopennode/discussion/387151/thread/95190e7426/?limit=25#ea66" rel="alternate"/><published>2026-02-25T15:09:13.468000Z</published><updated>2026-02-25T15:09:13.468000Z</updated><author><name>Alexis Hou</name><uri>https://sourceforge.net/u/alexis34/</uri></author><id>https://sourceforge.net3c419e158287017063b8dcc283f7bc9e8226ead4</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Well I succeeded to make it for multiple port application using 2 object dictionnaries using CO_MULTIPLE_OD flag. Just a pain to have to rename a lot of variable from each OD. &lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>CAN Open Node stack on dual port</title><link href="https://sourceforge.net/p/canopennode/discussion/387151/thread/95190e7426/?limit=25#cb67" rel="alternate"/><published>2026-02-24T13:52:02.132000Z</published><updated>2026-02-24T13:52:02.132000Z</updated><author><name>Alexis Hou</name><uri>https://sourceforge.net/u/alexis34/</uri></author><id>https://sourceforge.net9a2394df1ec331b9d7c361d834fa736df8dfc93b</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Hello everyone,&lt;/p&gt;
&lt;p&gt;Is it possible to use the canopen node stack for multiple port application.&lt;/p&gt;
&lt;p&gt;Like I want my MCU (STM32) to be master on the nodes on port CAN1, and slaves on port CAN2.&lt;/p&gt;
&lt;p&gt;If it's possible what would have need to do ?&lt;/p&gt;
&lt;p&gt;I was planning to remove all global variable from co_app_stm32.c by a structure like : "typedef struct CO_AppInstance {&lt;br/&gt;
    CO_t&lt;em&gt; CO;&lt;br/&gt;
    CANopenNodeSTM32&lt;/em&gt; hw;&lt;br/&gt;
    uint32_t time_old;&lt;br/&gt;
    CO_ReturnError_t err;&lt;br/&gt;
} CO_AppInstance;"&lt;/p&gt;
&lt;p&gt;And change the functions within to take the instance in parameter.&lt;br/&gt;
But I would also need to have two object dictionnaries.&lt;/p&gt;
&lt;p&gt;I don't know how I will manage that exactly, so any advice will be nice.&lt;/p&gt;
&lt;p&gt;BR,&lt;/p&gt;
&lt;p&gt;Alexis&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>How can I interface with external structs and the stack ODs?</title><link href="https://sourceforge.net/p/canopennode/discussion/387151/thread/260c37a30b/?limit=25#e51d" rel="alternate"/><published>2026-01-19T13:54:26.362000Z</published><updated>2026-01-19T13:54:26.362000Z</updated><author><name>Nicola</name><uri>https://sourceforge.net/u/nic0896/</uri></author><id>https://sourceforge.netebd80a9408026d9da00375ddd4115c77c847b5ee</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Hi, I have a problem using a stack on an STM32.&lt;br/&gt;
I need to exchange data from a stack (motor speed, temperature, status, etc.) via CANopen, and I am using CANopenNode.&lt;/p&gt;
&lt;p&gt;The problem is that I can’t find anything about how to exchange variables with the rest of the firmware.&lt;br/&gt;
Additionally, there doesn’t seem to be a way to associate Object Dictionary entries with functions (e.g. 0x2001 → start motor).&lt;br/&gt;
I cant find any examples of this ...&lt;br/&gt;
Thank you for your time.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Feasibility of Connecting one OD's RPDO/TPDO to another OD's unique OD Entry(Multiple OD Topic)</title><link href="https://sourceforge.net/p/canopennode/discussion/387151/thread/7f250f7462/?limit=25#3605" rel="alternate"/><published>2025-10-09T20:07:09.993000Z</published><updated>2025-10-09T20:07:09.993000Z</updated><author><name>Janez</name><uri>https://sourceforge.net/u/jani22/</uri></author><id>https://sourceforge.neta149cf557adaed8826816cd4fd3f3b3be2d57e1f</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Yes, application can define and and initialize it to add additional functionality or override default read/write callbacks.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Feasibility of Connecting one OD's RPDO/TPDO to another OD's unique OD Entry(Multiple OD Topic)</title><link href="https://sourceforge.net/p/canopennode/discussion/387151/thread/7f250f7462/?limit=25#b601" rel="alternate"/><published>2025-10-08T20:21:36.667000Z</published><updated>2025-10-08T20:21:36.667000Z</updated><author><name>Marcus Iqbal</name><uri>https://sourceforge.net/u/marcusiqbal/</uri></author><id>https://sourceforge.net3ff41fc123846b89924660068b78a90b32b85216</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;The custom callback functions that you mention above for any OD entry, are you refering  to the OD_extension_t that is a part of each OD_entry_t?&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Feasibility of Connecting one OD's RPDO/TPDO to another OD's unique OD Entry(Multiple OD Topic)</title><link href="https://sourceforge.net/p/canopennode/discussion/387151/thread/7f250f7462/?limit=25#97fc" rel="alternate"/><published>2025-10-02T17:30:12.425000Z</published><updated>2025-10-02T17:30:12.425000Z</updated><author><name>Janez</name><uri>https://sourceforge.net/u/jani22/</uri></author><id>https://sourceforge.netae206e4b79015f255b074b62436dc36355b33b02</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;In CANopenNode V4 (latest on github) you could specify a custom callback function for reading and for writing any OD entry. SDOs and PDOs use those callbacks. That way you can access any external library, own way. You would then probably use CANopenNode for all CANopen communication.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Feasibility of Connecting one OD's RPDO/TPDO to another OD's unique OD Entry(Multiple OD Topic)</title><link href="https://sourceforge.net/p/canopennode/discussion/387151/thread/7f250f7462/?limit=25#9b8a" rel="alternate"/><published>2025-10-01T19:39:57.156000Z</published><updated>2025-10-01T19:39:57.156000Z</updated><author><name>Marcus Iqbal</name><uri>https://sourceforge.net/u/marcusiqbal/</uri></author><id>https://sourceforge.net8bce285a0e955ecda92f0c9fe2ff77c8e6fcc6ac</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Hello,&lt;br/&gt;
I am working on a device that has an internal library with its own OD to handle SDO comm's and most of the internal OD entries for my project. As I expand the scope of my project I am realizing a blocker to an idea I had. I was planning to make a front facing OD that contains the RPDO, TPDO and several required OD entries while the internal library had it's own OD that handled some backend battery/speed/rpm entries. I did want the PDO's to be able to map to the internal OD's entries but working with the EDSEditor it became apparent that the PDO's seem to be limited to being mapped strictly with entries contained within its own OD. &lt;/p&gt;
&lt;p&gt;My question to the community is: has there been any mapping done between multiple OD's? Specifically mapping of one OD's entries to another OD's PDO's?&lt;/p&gt;
&lt;p&gt;I've attached the text output of the EDSEditor that made me realize I my planned out structure could be impractical.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Getting non-volatile memory working with CANopen</title><link href="https://sourceforge.net/p/canopennode/discussion/387151/thread/bc63a189ea/?limit=25#67b4" rel="alternate"/><published>2025-07-17T01:14:30.673000Z</published><updated>2025-07-17T01:14:30.673000Z</updated><author><name>Christopher Theriault</name><uri>https://sourceforge.net/u/eqqman/</uri></author><id>https://sourceforge.netee0e36fa6402c8a7eefb5f5ce349c4c73e89e17a</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Hello-&lt;br/&gt;
CAN (and by extension, CANopen) is a completely new environment for me.  My setup is a Windows PC with a Kvaser Leaf 3 wired to a Nucleo-STM32G0B1RE.  The CANopen stack comes from Zephyr.&lt;br/&gt;
Basic communications are going just fine.  I can use the libedssharp editing tool to create new object dictionary entries and read &amp;amp; write to them.  The problem I'm having is doing anything with storage in flash.  From what I'm told CiA specification 301 defines object dictionary entries 0x1010 and 0x1011 are to be used to "store/restore" default parameters- i.e., read and write to flash.  So I have several gaps in my understanding of this:&lt;br/&gt;
1) By adding subindices to 0x1010 and 0x1011 you can specify up to 126 subcategories of parameters for flash placement (https://canopennode.github.io/CANopenNode/group__CO__storage.html).  However, I have no idea how to flag any user-defined OD entry as being one of these subcategories.  The libedssharp editor allows for defining storage groups such as "RAM", "ROM", and "EEPROM", but these labels are essentially meaningless.  The CANopenNode link referenced above says "When object dictionary is generated (OD.h and OD.c files), OD variables are grouped into structures according to 'Storage group' parameter", so it makes sense that the names defined by the editing tool don't amount to anything.  But the editing tool isn't presenting any options that allow me to set a value that will be relevant to 0x1010 and 0x1011, and nothing in these files ever gets flagged as &lt;code&gt;const&lt;/code&gt;, so all storage groups end up in RAM no matter what category I pick for them.&lt;br/&gt;
2) Usage of 0x1010 and 0x1011 almost implies that there are two copies of certain object dictionary entries in the system, the "live" version and the "default" version.  Is this correct?  If so this could be an issue as we require file uploads to take place and there won't be enough space in the RAM to store the file before writing it to flash.&lt;br/&gt;
3)  If I had points 1) and 2) resolved, then the final question would be what to do to make sure that the flash storage location is exactly where we need it to be in the flash.&lt;br/&gt;
If anyone can clear up my misunderstandings on these points or explain a good reference that  does, it would be appreciated.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>CANopenNode as "master"</title><link href="https://sourceforge.net/p/canopennode/discussion/387151/thread/5184aed70e/?limit=25#7a8f" rel="alternate"/><published>2025-01-22T13:37:51.410000Z</published><updated>2025-01-22T13:37:51.410000Z</updated><author><name>Søren  Bendtsen</name><uri>https://sourceforge.net/u/bigbendk/</uri></author><id>https://sourceforge.net32cdc4978ca0fb55d8e28851f0b1adf25c0d130e</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Hi,&lt;br/&gt;
I have project where an STM32 MCU with Zephyr RTOS, that acts as a master, to control one or more CANopen devices on the bus. &lt;/p&gt;
&lt;p&gt;I have not been able to find a sample that initializes CANopenNode and communicates as a master - is this available somewhere? &lt;br/&gt;
The project is using simple heartbeat and PDO/SDO exchange.&lt;/p&gt;&lt;/div&gt;</summary></entry></feed>