m-pod FAQs

Support ‣ m-pod ‣ Troubleshooting

1. The output (▲) LED does not light up and there is no output.

2. The output (▲) and/or link (∎) LEDs flash periodically and m-pod stops responding.

3. What is the signal drive capability of m-pod?

___________________________________________

1. The output (▲) LED does not light up and there is no output.

A likely cause is that the cable is not pushed all the way in on. This could be on the m-pod side or the “host” side, e.g. Riponda or StimTracker.
With m-pod, you can map any input signal to any output line – or not. If the output LED is not lighting up, it is possible that the signal you need is not assigned to an output line. Use Xidon to view or reconfigure your m-pod pin assignments.

2. The output (▲) and/or link (∎) LEDs flash periodically and m-pod stops responding.

m-pod includes memory integrity features that allow it to self-recover in case of data loss. m-pod indicates a data loss by flashing one or both LEDs and it can restore its data using an internal backup after it restarts. To restart it, turn off and back on the device that m-pod is connected to, i.e. StimTracker or Riponda response pad.

Here are the error codes:

Both LEDs flashing rapidly, 3 times/second.
Cause: bad data. Restart m-pod.
Link LED (∎) alone, flashing briefly once every 2 seconds.
Cause: bad data. Restart m-pod.
Output LED (▲) alone, flashing briefly once every 2 seconds.
Cause: an attempt was made by the computer software to perform a locked function. Restart m-pod.
Output LED alone, flashes rapidly (100ms on, 100ms off).
m-pod model is not set, likely because the firmware was updated. Set the model using our free Xidon software.
Link LED alone, flashes rapidly.
Cause: bad data. Restart m-pod.
Link LED flashing 1 second on, 1 second off.
m-pod is in firmware update mode. If Xidon cannot detect m-pod, contact us for assistance in completing the firmware update.