GE MM300 Manual page 143
Motor management system/low voltage motor protection and control
Hide thumbs
Also See for MM300:
- Instruction manual (198 pages) ,
- Quick start manual (77 pages) ,
- Installation recommendations (21 pages)
Table of Contents
Advertisement
CHAPTER 4: FIELDBUS INTERFACE
MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE
Table 4-22: Motor Data Object, Class Code A0h, Attributes:
ATTRIBUTE
NAME/DESCRIPTION
ACCESS
01H
Get
Revision of Motor Data Object
Table 4-23: Motor Data Object, Class Code A0h, Instance 01h, Attributes, Get Access:
NAME/DESCRIPTION
ATTRIBUTE
01H
Motor Data
02H
Digital Data
03H
Summary of Motor Data
04H
Reserved
05H
Motor status
06H
Motor load (%)
07H
Cause of last trip
08H
Thermal capacity used (%)
09H
Current metering
0AH
Average Line Voltage (V)
0BH
Power metering
0CH
Contact Input Status
0DH
Contact Output Status
0EH
RTD metering
DATA FORMAT, SUMMARY OF MOTOR DATA
ITEM DESCRIPTION
Motor status
Motor load (%)
Cause of last trip
Thermal capacity used (%)
DATA FORMAT, MOTOR DATA
ITEM DESCRIPTION
Motor status
Motor load (%)
Cause of last trip
Thermal capacity used (%)
Average phase current (A)
Ground current (A)
Average Line Voltage (V)
Real power (kW)
Power factor
Contact Input Status
Contact Output Status
Local hottest RTD number
Local hottest RTD temperature
DEVICENET PROTOCOL
DATA
TYPE
UINT
SIZE IN
BYTES
38
9
7
NA
1
2
2
2
8
2
6
8
4
3
SIZE IN BYTES
FORMAT
1
FC129 (low byte only)
2
F1
2
FC134
2
F1
SIZE IN BYTES
FORMAT
1
FC129 (low byte only)
2
F1
2
FC134
2
F1
4
F10
4
F10
2
F1
4
F13
2
F21
8
BIT per input
4
BIT per output
1
Unsigned 8 bit integer
2
F4
VALUE
1
FORMAT
See below
See below
See below
NA
FC129 (low byte
only)
F1
FC134
F1
See below
F1
See below
BIT per input
BIT per output
See below
4–65
Hide quick links:
Advertisement
Table of Contents
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