Identity Object (Class Code 01H) - GE MM300 Manual

Motor management system/low voltage motor protection and control
Hide thumbs Also See for MM300:
Table of Contents

Advertisement

DEVICENET PROTOCOL

Identity Object (Class Code 01H)

4–62
VALUE
Dec
Hex
71
0x47
72
0x48
73
0x49
74
0x4A
75
0x4B
80
0x50
81
0x51
82
0x52
Commands are actioned on a change in Output data.
The example diagram below shows the MM300 polled I/O data read/written using a
DeviceNet master simulator. In this example, the "Start A" command has been sent via
Output data. In reading the Input data and interpreting the first byte value (98h) based on
the data format for that byte (FC129) the following is true:
Auto control is enabled
Contactor A is energized
Drive Available is true
In the event that there is a communication fault, and a pre-fault polled output command
caused the MM300 to start a motor, the motor will continue to run even after the
communication fault. To prevent this situation from occurring when remote
communication is used with the device the user must ensure that the 'Comm Failure Trip'
feature is configured. Refer to the MM300 Instruction manual, page 90 - Communications
Setpoints, under the Home > Setpnts > Cfg > Comms HMI page, for more information.
Figure 4-11: DeviceNet polled I/O data
Table 4-12: Identity Object, Class Code 01h, Services:
CODE
0x05
0x0E
DESCRIPTION
Clear Maintenance Timer
Clear RTD Maximums
Reset Motor Information
Auto Mode
Manual Mode
Trigger Waveform Capture
Start Datalog
Stop Datalog
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
MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE
CHAPTER 4: FIELDBUS INTERFACE

Hide quick links:

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the MM300 and is the answer not in the manual?

Questions and answers

Kristiyan
March 31, 2025

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?

1 comments:
Mr. Anderson
March 31, 2025

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

Table of Contents

Save PDF