Frequently Asked Question

200 Series — Serial Data Displays

Last Updated 19 hours ago

200 Series Serial Data Displays — Troubleshooting & Setup Guide

Models: D0200, D0220, D0230, D0240, D0260, D0265, A0220, A0230, A0240, A0260, A0265


Product Manual: 200 Series Computer-Controlled Display Manual

Download and keep this manual handy — it contains wiring diagrams, spec sheets, programming options, and protocol details referenced throughout this article.


1. Power Supply and Input Voltage

1.1 AC vs. DC Power Input

Symptom: Uncertainty about which power source to use, or display not powering on after connecting DC supply.

Cause: The 200 Series supports both AC and DC input, but DC has important grounding requirements.

Solution:

  • AC input: 16–28 VAC (preferred). The included 24 VAC transformer provides ground loop isolation for input signals.
  • DC input: 18–30 VDC. The DC ground must be electrically isolated from your signal ground. The display contains an internal diode bridge that introduces a ~0.7V offset between power input and signal ground. Connecting DC ground to signal ground will cause problems.
  • Both polarities are accepted on the DC terminals — the internal diode bridge handles polarity automatically.
  • Replacement 24 VAC adapter (with 20 ft wire): 9100-0101 Power Adapter

1.2 Running Multiple Displays from One Power Supply

Symptom: Considering powering multiple displays from a single transformer.

Cause/Concern: Each display draws up to approximately 0.7 A @ 24 VAC. The standard included transformer is rated ~0.83 A — sufficient for one display only.

Solution:

  • If daisy-chaining power to multiple displays, use a transformer rated for the combined load.
  • Running multiple displays off one small transformer is not recommended and may cause ground loop issues between signal ground and power supply.
  • Note: D0265 displays ship with a 110 VAC power cord rather than a low-voltage transformer.

2. RS232 Communication

2.1 RS232 Signal Voltage Requirements

Symptom: Display does not respond to serial data from a microcontroller or single-board computer (e.g., Raspberry Pi).

Cause: Many microcontrollers output TTL (3.3V or 5V) logic levels, which are not compatible with RS232. The RS232 standard requires ±5V minimum (typically ±12V).

Solution:

  • Use an RS232 level shifter / converter between your microcontroller and the display.
  • ⚠️ Warning: The TX terminal on the display outputs true RS232 voltage (swinging from −9V to +9V). Connecting this directly to GPIO pins will damage most microcontrollers.

2.2 RS232 Cable Length Limitations

Symptom: Display works at short distances but becomes unreliable over longer cable runs.

Cause: RS232 is reliable up to approximately 50 feet (15 m) at 9600 baud.

Solution:

  • For runs exceeding 50 ft, reduce baud rate (e.g., to 2400 baud) or switch to RS485 or 20 mA digital current loop if your signal source supports it.
  • A DB9-to-3-wire adapter (20 ft) is available for RS232 connections.

2.3 TX1 and TX2 Output Pins — Daisy-Chaining Displays

Symptom: Need to display the same data on multiple displays driven from a single data source.

Solution:

  • The RS232 connector includes two transmit outputs:

- TX1 – Software rebroadcast of received data

- TX2 – Hardware rebroadcast of received data

  • Connect TX1 or TX2 from the first display to the RX input of the next display to pass data downstream.

3. RS485 Communication

3.1 RS485 Not Available on D0220

Symptom: Customer wants RS485 input on a D0220 display.

Cause: The D0220 uses a smaller circuit board that supports RS232 only.

Solution:

  • Use a D0230, D0240, or D0260 for RS485 support.

3.2 Erratic Display Behavior on RS485 Bus

Symptom: Multiple displays on an RS485 communications bus show flickering, incorrect data, or erratic behavior.

Cause: Common causes include:

  • Shorted RS485 conductor in the cable
  • Incorrect protocol setting or display address
  • Hardware fault (e.g., missing pull-up resistor on Select button)

Solution:

  1. Inspect the RS485 cable for shorts between conductors.
  2. Verify each display is configured with the correct address and protocol.
  3. Disconnect the data input (change the input switch) and observe whether the displays flicker or show 8s.
  4. Press the Select button to cycle through 8s / Count / Revcode modes. Confirm firmware revision displays correctly (current firmware: Rev 1.9, dated 6/1/2022).
  5. Replace damaged cable segments as needed.

4. 20 mA Current Loop Input

4.1 Understanding the 20 mA Port

Symptom: Uncertainty about how the 20 mA port on a D0230 or similar display works.

Cause: The 20 mA port is a digital protocol current loop — not a 4–20 mA analog current loop. This is an older protocol that few modern devices still use.

Solution:

  • Confirm your signal source outputs a digital 20 mA current loop signal (not 4–20 mA analog).
  • For current loop displays, a 24 VDC power source is typically wired in series with the loop to drive the current.
  • See the current loop display manual for wiring details.
  • ⚠️ Note: 200 Series displays do not support 4–20 mA analog current loops.

4.2 Diagnosing a Damaged 4–20 mA Module (D0240)

Symptom: D0240 display with 4–20 mA module has been repaired repeatedly; suspected recurring damage.

Solution:

  1. Disconnect power and signal from the display.
  2. Measure resistance across the blue resistor on the current loop module.
  3. Expected value: ~200 ohms. A higher resistance indicates the module is damaged and needs replacement.
  4. Identify and correct the root cause of overcurrent/overvoltage before reinstalling.

5. Scale Protocol Configuration

5.1 Display Shows Incorrect Weight, Wrong Format, or All Zeros

Symptom: Display powers on and receives data, but shows wrong values, all zeros, or unexpected formatting (e.g., half weight with a pound sign).

Cause: The display protocol/mode setting does not match the scale's output format.

Solution:

Access the programming menu and set the appropriate mode. Common mode settings:

Setting Mode Description
91 ASCII mode
92 General Scale mode (also disables unwanted alpha characters)
93 + A0 Mettler Toledo protocol
93 + A1 Rice Lake protocol
  • To save changes: Press and hold the Mode button for approximately 3 seconds until the display exits programming mode.
  • For truck scale programming, see page 14 of the product manual.

5.2 Disabling Alpha Characters on the Display

Symptom: Display is showing unwanted alphabetic characters.

Solution:

  1. Enter Programming Mode by pressing the Mode button.
  2. Press Mode repeatedly until the left (tens) digit shows 9 (Area 9).
  3. Use the Select button to set the value to 2 (General Scale mode).
  4. Press Mode to navigate to Area 1.
  5. Set the value to 0 to disable alpha characters.

5.3 Verifying the Display Is Receiving Data

Symptom: Display shows zeros and is unresponsive; unclear whether the problem is the cable, scale, or display.

Solution:

  1. Confirm the power/status LED is illuminated and blinking.
  2. Disconnect the communication wire and observe the LED blink rate.
  3. Reconnect the communication wire — if the blink rate changes (typically faster), the display is receiving data.
  4. If there is no change in LED behavior with/without the cable connected, the issue is likely:

- A broken or shorted communication cable

- The scale is not outputting data (check scale settings/enable RS232 output on scale head)

  1. Using a multimeter, verify RS232 signal voltage: should read approximately −9 VDC at rest between GND and RX, briefly spiking to +9 VDC during transmission.

6. Wiring and Installation

6.1 Correct RS232 Wiring from Scale to Display

Symptom: Display shows 00 and is unresponsive after installation; issue recurs after short time.

Cause: Incorrect wiring — connecting the scale's RX line to the display may create a feedback path that can damage hardware over time.

Solution:

  • Connect only TX → RX and GND → GND from scale to display.
  • Do not connect the scale's RX terminal to the display's TX terminal unless bidirectional communication is explicitly required.

6.2 RS485 Wiring for Multiple Displays

Symptom: Displays wired for RS485 chaining are not communicating.

Solution:

  • Verify that RS485 A/B (or +/−) terminals are connected correctly and consistently across all displays in the chain.
  • Confirm each display has a unique address if using addressed commands.
  • Check for shorted conductors in the cable run.

6.3 Pushbutton / Foot Pedal Input Wiring

Symptom: Display increments erratically or continuously without intentional input.

Cause: Input 1 circuit is being held closed continuously by a mis-wired or defective foot pedal.

Solution:

  1. Verify the foot pedal wiring matches the expected momentary contact configuration (normally open, closes briefly on press).
  2. Check that the pedal is not wired to decrement instead of increment.
  3. Test with a standard pushbutton to isolate whether the pedal itself is defective.
  4. Replace or rewire the foot pedal as needed.

7. Serial Data Commands and Display Formatting (D0260/D0265)

7.1 Display Layout and Character Limits

The D0260/D0265 supports up to 6 numeric digits. Colons and decimals occupy dedicated hardware positions and do not count as digit characters.

Hardware layout reference:


- 1 . 2 . : 3 . 4 . : 5 . 6

Key rules:

  • Decimals appear between digit positions: 1.2.3.4.5.6
  • Colons are in fixed positions: 12:34:56
  • Minus sign can be displayed as a digit or in a dedicated far-left position (6-digit displays)
  • Numbers scroll in from the right: 123 1234123456
  • Sending only \r (carriage return) blanks the display
  • There is no decimal position after the last (rightmost) digit

7.2 Command Format Examples

Command Sent Display Shows
:00:2959\r 00:29:59
.00.2959\r 00.2959
0:029:59\r 00:29:59
0.029.59\r 0.029.59
456:\r 4:56
3:456\r 34:56
12:34.56\r 12:34.56 (mixed colons/decimals supported)
\r (blank)
  • Colons are always in fixed positions — the display will always show at least 2 digits before each colon.
  • Mixing colons and decimals in the same command is supported.

7.3 Data Overflow — Left Digit Cut Off

Symptom: Display shows correct data but is missing the leftmost digit (e.g., 800.123 instead of 7800.123).

Cause: Sending more characters than the display can show causes the leftmost character to scroll off screen.

Solution:

  • Limit data strings to 6 numeric characters.
  • Verify your software is not padding or sending extra leading digits.

7.4 Display Addressing (Enabling/Disabling Specific Displays)

Symptom: Need to enable or disable a specific display on a shared communications bus.

Solution:

  • Use the enable command with the display's address to turn it on.
  • Use the corresponding disable command — for example, 720100 — to turn it off.
  • Refer to the manual for the full addressed command protocol.

7.5 Modbus Not Supported

Symptom: Attempting to communicate with 200 Series displays using Modbus protocol.

Cause: 200 Series displays do not implement the Modbus protocol.

Solution:

  • Use the native ASCII serial protocol documented in the product manual.
  • For simple applications, sending ASCII digits followed by a carriage return (e.g., 123\r) is sufficient.
  • For applications requiring network/Ethernet connectivity, consider the D484A display with REST API support.

8. 20 mA Current Loop Wiring (Active vs. Passive Receiver)

Symptom: D0265 showing all zeros when connected to a scale with 20 mA digital output.

Cause: Incorrect header jumper position (active vs. passive receiver mode).

Solution — Passive receiver (scale provides current):

  • Wire: Signal+ → 20mA+, Signal− → 20mA−
  • Set the 20 mA current source header to the horizontal position

Solution — Active receiver (display provides current):

  • Wire: Signal+ → 20mA−, Signal− → GND
  • Set the 20 mA current source header to the vertical position

Test both configurations if uncertain — verify by measuring voltage across the signal wires. If passive mode shows 0V across terminals, try active mode.


9. When to Contact Support

Contact Microframe support directly if:

  • The display powers on but is completely unresponsive to button presses or serial data after verifying wiring and settings
  • The display was damaged (e.g., by incorrect wiring, overvoltage, or repeated component failure) and needs RMA repair
  • You need help configuring a display for an unlisted or unusual scale protocol
  • You are planning a multi-display RS485 installation and need addressing or topology guidance
  • You require custom hardware (e.g., 110 VAC input, outdoor enclosure, custom firmware, or non-standard digit count)
  • Your display is showing symptoms consistent with a hardware fault (e.g., random button firing, corrupted display output not resolved by rewiring)

For RMA requests or repairs, contact Microframe through the support ticket system or visit microframecorp.com.

Help Topics
  • Technical Support

Please Wait!

Please wait... it will take a second!