On controller from Accelerated Systems Inc. it is possible to set parameters via…
- User
On controller from Accelerated Systems Inc. it is possible to set parameters via 'SDO-Expedited Write' messages. What message do I need to send to save it permanently to flash? ('Save to Flash'-Feature)
- Assistant
Excellent question. This is a standard and critical function when working with CANopen devices like those from Accelerated Systems Inc. (ASI).
To save all configurable parameters to the controller's non-volatile memory (flash), you need to send an SDO write message to a specific object in the CANopen Object Dictionary. This is standardized by the CiA 301 specification, which ASI controllers follow.
The Short Answer
You need to write the ASCII value for "save" (
0x65766173) to the Object Dictionary Index1010h, Sub-index01h.- Object Index:
1010h(Store Parameters) - Sub-index:
01h(Save all parameters) - Data (4 bytes):
0x65766173which is'e' 'v' 'a' 's'in little-endian byte order, corresponding to the string "save".
The Detailed CAN Message
Here is the exact SDO-Expedited Write message you need to send. Remember that CANopen SDO messages have a specific structure.
1. Determine the COB-ID (CAN ID)
The COB-ID for sending an SDO message to the controller is calculated as:
COB-ID = 600h + Node-ID600his the base ID for SDO Tx from the client (your device).Node-IDis the unique address of your ASI controller on the CAN bus. This is often1,2, or another value you have configured.
Example: If your controller's Node-ID is
1, the COB-ID to send the message on is601h.2. Construct the 8-Byte Data Payload
The payload for an SDO-Expedited Write message is structured as follows:
Byte 0 Bytes 1-2 Byte 3 Bytes 4-7 Command Index (Little-Endian) Sub-index Data (Little-Endian) 23h10 1001h73 61 76 65Breakdown:
- Byte 0:
23h(Command Specifier)- This byte tells the controller that this is a 4-byte expedited write request.
- Bytes 1 & 2:
10 10(Index)- This is the Object Index
1010hin little-endian format (LSB first).
- This is the Object Index
- Byte 3:
01h(Sub-index)- This selects the "Save all parameters" function.
- Bytes 4-7:
73 61 76 65(Data)- This is the required signature to trigger the save action. It is the ASCII string "save" sent in little-endian format:
's'=73h'a'=61h'v'=76h'e'=65h
- This is the required signature to trigger the save action. It is the ASCII string "save" sent in little-endian format:
Complete CAN Message Example
Assuming your controller's Node-ID is 1:
- CAN-ID:
601h - DLC (Data Length Code):
8 - Data Payload:
23 10 10 01 73 61 76 65
Your CAN tool would send this single frame:
ID: 601h, Data: 23 10 10 01 73 61 76 65What to Expect in Response
After sending the command, you should monitor for a response from the controller. The controller will respond on its SDO Tx COB-ID, which is
580h + Node-ID.- For a Node-ID of 1, the response ID is
581h.
Successful Response: The controller will confirm the write was successful with this message:
ID: 581h, Data: 60 10 10 01 00 00 00 0060hin the first byte indicates a successful write response.- The following bytes echo back the Index and Sub-index that were written to.
Error Response (Abort): If something went wrong, you would receive an SDO Abort message:
ID: 581h, Data: 80 10 10 01 [Abort Code]80hindicates an abort.- The last 4 bytes contain a specific abort code explaining the error (e.g., object doesn't exist, value out of range, etc.).
Important Considerations
- Wait After Saving: Writing to flash memory can take some time (from milliseconds to a second). Do not power cycle the controller immediately after sending the save command. It's good practice to wait at least 1-2 seconds to ensure the write operation is complete.
- Know Your Node-ID: The most common mistake is using the wrong Node-ID, which results in the controller never receiving the message.
- Check Documentation: While
1010his the standard, always refer to the specific EDS (Electronic Data Sheet) file or manual for your ASI controller model to be 100% certain. Manufacturers can sometimes add proprietary objects or deviate slightly.
- Object Index:
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.