Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | |||
| can:higher_layer_protocols:duplicate_mac_id [2013/04/05 15:10] – heinz | can:higher_layer_protocols:duplicate_mac_id [2026/08/14 15:09] (current) – removed - external edit (Unknown date) 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ==== DeviceNet Duplicate MAC ID Protocol Summary ==== | ||
| - | |||
| - | In the following explanation "Dup MAC Request/ | ||
| - | MAC ID Request/ | ||
| - | |||
| - | === Power-up === | ||
| - | * Transmit Dup MAC request message | ||
| - | * Wait 1 second (listening for replies - see ((During two 1-second timeout periods above)) below) | ||
| - | * Transmit Dup MAC request message | ||
| - | * Wait 1 second (listening for replies - see !1 below) | ||
| - | * Transition to Online State | ||
| - | |||
| - | |||
| - | 1a) If a Dup MAC request or response is received transition to the Communication Fault state | ||
| - | |||
| - | !2 - While in the Online state | ||
| - | 2a) If a Dup MAC Request message is received, send Dup MAC Response | ||
| - | 2b) If a Dup MAC Response message is received, transition to the Communication | ||
| - | (this situation seems unlikely, but can occur if two network segments are powered up and then connected together) | ||
| - | |||
| - | |||
| - | There are two ways to leave the Communication Fault state: | ||
| - | |||
| - | - Manual Intervention (power cycle, device reset or other manual intervention) | ||
| - | - MAC ID is changed (possibly to the same value) via the offline connection set which causes the device to re-start the media access state machine. This option is only available if the device supports the offline connection set. | ||
| - | |||
| - | Generally speaking, if a duplicate MAC ID fault occurs, you must identify the node(s) with the incorrect MAC ID, make corrections, | ||
| - | |||
| - | If the affected devices support the offline connection set it is possible to change the MAC ID's and reset faulted devices from a configuration tool without cycling network power or disconnecting devices. | ||
| - | |||
| - | This email is intended to be a general explanation, | ||
| - | |||
| - | Nick Jones, Oct 15. 2002 | ||
| - | |||
| - | |||
| - | http:// | ||
| - | |||
| - | |||
| - | |||