TrojanObelix

Maybe it is because the used XXAT CANopen Client is not able to handle normal SDO-transfer? :-( Damn.

Transmit CAN data of SDOserver: In switch (SDO->state) 1. State CO_SDO_ST_UPLOAD_INITIATE_RSP (...) SDO->state = CO_SDO_ST_UPLOAD_SEGMENT_REQ; // set next state (...) (void)CO_CANsend(SDO->CANdevTx, SDO->CANtxBuff); // (Buffer =(0x41 0x08, 0x10, 0x00, 0x07, 0x00, 0x00, 0x00) Expected! Okay break; 2. State CO_SDO_ST_UPLOAD_SEGMENT_REQ #if ((CO_CONFIG_SDO_SRV)&CO_CONFIG_SDO_SRV_BLOCK) == 0 (...) // millions states break; // go here till timeout!

Hi Janez, I have a problem with sdo transfer. Something messed up my stack. I use the CANopenNode_STM32 on different own boards. CANopenNode is the V4 master (tried older commits as well) Everything was tested fine weeks ago. But now I tired it again and none of the boards work anymore. The expedited transfer seems to work, but if the objekt is lager the normal (segmented transfer) fails with a timeout Example: Device Type 0x1000 works fine Device Name ("TIOM205") 0x1008 timed out I do not see any...

Feature request: unselect/selext all exclusions

Okay, found "delete" it under contect menu. Nice. But might be worth to enhanced and link it under "edit" Menu

File operation on file context and via edit menue

Okay, I got it: The XC16 compiler V2.00 is buggy. Runs like clockwork with V2.10.

I use the Master V1.3 on a PIC24 If I define a node as HB consumer (Obj 1016h), with a consumer time of 5 s, nothing happens at first (standard conform). According to the standard, monitoring starts with the first heartbeat. However, when the first heartbeat is sent by the monitored node, I receive an emergency and a bootup from the monitoring node when the consumer time expires. At least near the time, does not seem to be exactly this time. What's going wrong? Is thee a known bug in the V1.3 master...