J1939 Safety is an extension of J1939 which is described in the specification SAE J1939-76. The safety communication can be done in parallel to a normal J1939 transmission in the same network.
Author: Torsten Gedenk
CANopen Bootup Message
The CANopen Bootup Message is sent by a CANopen device when it starts. This is done to indicate to all other devices in the network that it is ready to communicate by other CANopen services. Although it may sound simple, there are preconditions that need to be met before a bootup message can be sent. The CAN-ID of the bootup messages depends on the CANopen node-ID of the device. That is why the device must have a valid node-ID between 1 and 127 in order to transmit a bootup message. Therefore, devices without a defined node-ID or without any switches to set the node-ID must use a dynamic Node-ID configuration by Layer Setting Services (LSS).
CAN-ID and CAN data
Anyway, we only discuss the case with a valid node-ID for now.
The CAN-ID of a bootup message is 0x700 + node-ID. That means that the CAN-IDs are located in the range between 0x701 and 0x77f. Each CANopen bootup message has a length of 1 byte. The value of this one byte is always 0x00. The same CAN-ID but different data are used by CANopen Heartbeat or Node Guarding messages.
Continue reading “CANopen Bootup Message”
(Deutsch) CANopen Netzwerkmanagement – NMT
Sorry, this entry is only available in Deutsch.
Real-time event 34 in GDB | SIG34
If the outputs regarding Real-time event 34 (SIG34) disturb with debugging on Linux using gdb or ddd, one may configure the GDB to ignore these events:
handle SIG34 pass handle SIG34 noprint
BAM: J1939 Broadcast Announce Message
Summary
- Transmission of 9 up to 1785 bytes
- Broadcast(0xff) to all ECUs in the network
- no flow control/no hand shake
- at least 50ms gaps between the CAN messages
- PGN of BAM Connection Message: 0xEC00 / 60416
- PGN of BAM Data Message: 0xEB00 / 60160
The German article provides more detailed information about it.