Configuring Isel 4820 Wireless MPG Input Interfaces

The wireless pendant presents one dry contact per axis, step, or button selection, but the HMC/MM2000 I/O interface expects binary-coded states. Connecting those contacts directly, adding a plain DB37 breakout, or routing encoder pulses into a connector marked 4 does not resolve that electrical and logical mismatch.

Common fixes that fail

A passive DB37 breakout only exposes conductors. It cannot reproduce the factory interposer board’s diode logic, so one-of-N contacts remain one-of-N contacts rather than the required three axis bits, two step-size bits, and three button bits.

Adding pull-down resistors without identifying the I/O input circuit can also fail. A pull-down is useful only when the card’s active polarity, internal impedance, input thresholds, leakage current, and field voltage make it the correct off-state bias. The wrong resistance can prevent an input from reaching its on threshold or continuously dissipate excessive power. This is heat, not logic.

An ESP32 does not automatically make the interface more reliable. It can debounce selectors, reject illegal combinations, and control transitions between codes, but it also introduces a power supply, startup state, firmware, output-interface circuitry, and failure modes that a diode matrix does not have. Use a controller only when temporal filtering or invalid-code rejection is required.

Finally, a cabinet label is not proof that a DB37 line is electrically unused. The conductor may still reach an output driver, feedback input, reserved card channel, or configured axis. Two active sources connected to the same line can damage either interface.

Electrical quantities that decide compatibility

The number that matters is the current and voltage seen at each receiver contact, diode, pull resistor, and card input in both logical states. Obtain the receiver output specification and the HMC card input specification before choosing components.

For each pull-down, check both boundaries. It must be low enough to hold the input below its off threshold despite leakage, yet high enough that the active source can raise the input above its on threshold. Confirm resistor power for every code having multiple asserted bits; several illuminated input LEDs mean several simultaneous current paths.

Binary selection mechanism

The factory arrangement used a diode matrix to translate mechanical selections into binary-weighted I/O states. The documented allocation is three bits for axis selection, two bits for step size, and three bits for buttons. The manual’s LED test uses binary weights in 1-2-4-8 order; build the actual truth table from the documented position-to-LED mapping rather than assigning codes by position number.

Each selector contact forms a matrix row. Diodes connect that row only to the bit columns that must be active for the selected code. Their orientation blocks current from feeding backward into another row. Pull resistors establish a defined state when no selection is active.

A passive matrix has no memory and cannot distinguish an intended code from the bitwise combination of two simultaneous contacts. Selector overlap, contact bounce, or two pressed buttons can therefore produce a different valid binary number. Record every simultaneous-contact result and determine whether MM2000 ignores it, interprets it as another function, or requires interlocking. An MCU becomes justified when the interface must wait for a stable selection, reject multiple active rows, or force a neutral code during transitions.

De-energized channel identification

1. Obtain the HMC connector pinout, I/O assignment, and axis configuration. Separate the selection-bit wiring to the I/O card from the differential A/B pulse wiring to the motion card.
2. Remove machine power and verify the relevant control supplies are de-energized. Disconnect both ends of the candidate DB37 cable so resistance and continuity tests cannot back-feed a card.
3. Map every proposed pin end to end. Check for continuity to protective earth, signal common, other pins, limit circuits, encoder conductors, and any installed driver or receiver.
4. Review the MM2000 configuration and card-channel assignments for axis 4. A channel is available only when the connector pins, hardware channel, and software assignment are all unoccupied.
5. Reconnect the existing machine without the wireless receiver. Observe the candidate channel through the card LEDs or available diagnostics while operating the machine through its normal modes. Unexpected state changes disqualify the line.
6. Where documentation cannot identify whether a pin is an input or output, stop before applying a signal. Have Isel or a qualified control technician identify the card and connector circuit.

A breakout installed inline can also create a signal stub. Keep each differential pair together through the breakout, avoid separating its conductors into long terminal leads, and retain the documented shield and common arrangement.

Diode-matrix construction and checkout

1. Write a truth table containing every axis, increment, and button position and the corresponding binary-weighted LEDs. Include neutral, selector-transition, and simultaneous-button states.
2. Characterize one card input with a current-limited test source matching the documented field supply. Measure on-state voltage, current, and off-state leakage before calculating pull resistors.
3. Build the proposed matrix using the approximately 18 1N4148 diodes only after confirming their polarity and electrical ratings against the measured circuit. Label rows and bit columns rather than relying on wire color.
4. Bench-test the matrix independently from the machine. Activate one dry contact at a time and compare every output with the truth table; then test all credible overlapping selections.
5. Connect only the selection matrix to the I/O card, with motion inhibited. Confirm that the LEDs follow the manual’s weighted order and that released controls return to the defined neutral pattern.
6. Cycle receiver power and machine control power separately. No encoded function may become active during receiver startup, loss of wireless communication, or reconnection.

Reverse-biased or missing diodes usually appear as extra bits, coupled selections, or a code that changes when another control is pressed. An unsuitable pull resistance appears as dim or unstable LEDs, failure at the lowest supply voltage, or a bit that remains active after release.

Differential encoder commissioning and verification

The handwheel’s differential A/B output is a separate interface from the dry-contact matrix. Identify the receiver’s positive and negative conductor for each phase and the motion card’s corresponding differential inputs. Match driver type, accepted voltage range, common-mode range, and any required termination from the two manuals; connector shape alone establishes none of these properties.

1. With the receiver disconnected from the card, use an oscilloscope with a suitable differential measurement method to confirm complementary signals within each pair and quadrature between A and B.
2. Turn the wheel slowly in each direction and verify that phase order reverses with direction. Check for pulses while the wheel is stationary, while selectors move, and while receiver power cycles.
3. Connect the verified pairs to the confirmed unused channel. Initially inhibit axis motion and observe pulse counting or channel diagnostics.
4. Command a low-risk test with the selected axis clear of travel limits. Confirm selected axis, increment selection, direction, and counts over repeated equal handwheel movements.
5. Test neutral selection, communication loss, selector transitions, and power restoration. None should create motion or retain a previous command unexpectedly.

Noise faults point toward pair separation, an incorrect reference or shield arrangement, excessive breakout stubs, incompatible termination, or receiver/card level mismatch. Incorrect direction with clean counts points toward phase assignment; intermittent extra counts require waveform inspection before software compensation.

FAQ