CHAPTER 4: FIELDBUS INTERFACE
Message Router (Class Code 02H)
DeviceNet Object (Class Code 03H)
DeviceNet Connection Object (Class Code 05H)
MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE
Table 4-13: Identity Object, Class Code 01h, Attributes:
ATTRIBUTE
ACCESS
01h
Get
Table 4-14: Identity Object, Class Code 01h, Instance 01h, Attributes:
ATTRIBUTE
ACCESS
NAME/DESCRIPTION
01h
Get
Vendor ID
02h
Get
Device Type
03h
Get
Product Code
04h
Get
Revision (Major, Minor)
The message router (class code 2) object provides a messaging connection point through
which a client may address a service to any object or instance residing in the physical
device. There is no external visible interface to the message router object.
Table 4-15: Identity Object, Class Code 03h, Services:
CODE
0x0E
0x10
Table 4-16: Identity Object, Class Code 03h, Attributes:
ATTRIBUTE
ACCESS
01h
Get
Table 4-17: Identity Object, Class Code 03h, Instance 01h, Attributes:
ATTRIBUTE
ACCESS
DESCRIPTION
01h
Get
02h
Get
05h
Get
Table 4-18: Connection Object, Class Code 05h, Services:
CODE
0x05
0x0E
0x10
NAME/DESCRIPTION
Revision of Identity Object
DATA TYPE
UINT
UINT
UINT
USINT
SERVICES AVAILABLE TO THIS OBJECT
NAME
DESCRIPTION
Get_Attribute_Single Returns the contents of the given attribute
Set_Attribute_Single Sets the contents of the given attribute
NAME/DESCRIPTION
Revision of DeviceNet Object UINT
NAME/
DATA TYPE
MAC ID
USINT
Baud Rate
USINT
Allocation Choice
BYTE
Master's MAC ID
USINT
SERVICES AVAILABLE TO THIS OBJECT
NAME
DESCRIPTION
Reset
Reset the device to power up configuration
Get_Attribute_Single Returns the contents of the given attribute
Set_Attribute_Single Sets the contents of the given attribute
DEVICENET PROTOCOL
DATA TYPE
VALUE
UINT
1
VALUE
928
12
0x4D42
1.1
DATA TYPE
VALUE
1
VALUE
0 to 63
0 = 125 kbps
1 = 250 kbps
2 = 500 kbps
Bit 0: Explicit Messaging
Bit 1: polled I/O
Bit 6: acknowledge suppression
0 to 63: address; 255 = unallocated
4–63
Need help?
Do you have a question about the MM300 and is the answer not in the manual?
Questions and answers
we have a problem with device MM300. it says that the device is invalid through the software and does not read the device. the communication is through RS 485. is it possible to give us an advice or send us some reccomendations or instructions?
For a GE MM300 device that is not recognized by software and communicates via RS485, follow these troubleshooting steps:
1. Ensure correct RS485 wiring:
- Use two-wire RS485 in a daisy chain configuration.
- Install a 120 Ohm resistor in series with a 1 nF ceramic capacitor at each end of the link.
- Use shielded wire and ground the shield at only one location.
2. Check device addressing and termination:
- Confirm proper device address and ensure no address conflicts.
- Verify that termination networks are correctly installed at both ends.
3. Confirm half-duplex communication:
- Ensure that the system supports half-duplex communication and not sending and receiving data simultaneously.
4. If using USB for setup (e.g., USB-to-RS485 converter) and the device is not recognized:
- Repeat the connection procedure 2–3 times.
- If still not recognized, uninstall the USB driver from Device Manager under modems.
- Disconnect the USB cable, wait at least 10 seconds, then reconnect.
- When prompted by the Hardware Wizard, select "No, not this time," then "Install the software automatically," and press "Continue Anyway."
- Finish the installation and check if the USB device appears in the setup software.
These steps help ensure proper hardware connection and correct software recognition of the MM300 device.
This answer is automatically generated