What it means
A08755 is an alarm from the CANopen interface of the drive. It appears when a CANopen object that has been entered in the mapping of a Process Data Object (PDO) is not provided for the PDO mapping: the drive accepts only objects from a fixed list of mappable objects in a Receive Process Data Object (RPDO) or Transmit Process Data Object (TPDO), and the entry that raised the alarm lies outside this list. Depending on the manual, the alarm is shown as «CAN: Obj cannot be mapped» or as «CAN: Object cannot be mapped».
Why it appears
- A CANopen object that is not provided for the Process Data Object (PDO) mapping has been entered in the PDO mapping.
What to check
- Open the PDO mapping in which the object was entered and check the object number in the affected mapping slot.
- Replace the object with a CANopen object that is provided for the PDO mapping, or enter 0. The manual permits, among other objects, for the RPDO the objects 6040 hex, 6060 hex and 6071 hex as well as the object areas starting at 5800 hex and at 5820 hex (this area up to 5827 hex), and for the TPDO the objects 6041 hex, 6061 hex, 6063 hex, 6069 hex and 6074 hex as well as the object areas starting at 5810 hex and at 5830 hex (this area up to 5837 hex); the manual's list contains further objects for both the RPDO and the TPDO.
- Enter the mapping with sub-index 0, because only sub-index 0 of the specified objects can be mapped.
Acknowledging and restarting
The alarm requires no acknowledgement: it remains present as long as the inadmissible object sits in the PDO mapping and goes away once the entry is corrected. The manual notes: As long as A08755 is present, the COB-ID cannot be set to valid.
Only after the PDO mapping has been corrected can the COB-ID of the affected PDO be set to valid.
What differs between the drive families
Straight from the manuals' own fields — A08755 is not described identically everywhere.
| Drive family | Reaction | Acknowledge | Message class | Component | Manual |
|---|---|---|---|---|---|
| S120, S150 | NONE | NONE | Error in the parameterization / configuration / commissioning procedure (18) | None | SINAMICS S120, S150 List Manual · p. 2928 |
| G130, G150 | NONE | NONE | Error in the parameterization / configuration / commissioning procedure (18) | None | SINAMICS G130, G150 List Manual · p. 1642 |
| G120 | NONE | NONE | Error in the parameterization / configuration / commissioning procedure (18) | — | SINAMICS G120 · p. 901 |
The drives this code lives on
A08755 is described for G120, G130, G150, S120, S150. These are the converters of those families in our catalogue — price on request.
Questions technicians ask
What does alarm A08755 mean on a SINAMICS drive?
A CANopen object entered in the PDO mapping is not provided for the PDO mapping. The drive keeps the alarm raised until the entry is replaced by a mappable object or by 0.
Which CANopen objects may be mapped into the RPDO?
Among others 6040 hex, 6060 hex and 6071 hex and the object areas starting at 5800 hex and at 5820 hex (up to 5827 hex); the manual's list contains further objects. Only sub-index 0 of these objects may be mapped.
How is A08755 cleared?
The alarm needs no acknowledgement. Remove the inadmissible object from the PDO mapping — enter a mappable object or 0 — and the alarm goes.
Why can the COB-ID not be set to valid?
As long as A08755 is present, the COB-ID cannot be set to valid. Only when the PDO mapping has been corrected does the drive accept a valid COB-ID.
Codes next to this one
Source
Written from Siemens' own List Manuals and operating instructions; every number, designation and parameter on this page is checked against them before publication.
All SINAMICS codes: fault and alarm codes · the A08xxx group · SINAMICS manuals · Siemens manuals