Troubleshooting the MegaJolt Lite Jr.

Configuration software compatibility

If you see an error message while attempting to communicate with the MJLJ, such as 'Could not open port' or 'Timeout reading runtime data' you can use a terminal program to directly test the MJLJ unit.

Here are the instructions for this testing procedure, using the common 'Hyperterminal' software.

Troubleshooting with Hyperterminal

Open up Hyperterminal. create a connection, and configure it to connect directly to the COM port you are using for the MJLJ.

When it asks for the communication settings, use the following:

Bits Per Second: 4800
Data Bits: 8
Parity: None
Stop Bits: 1
Flow Control: none

When you get to the main screen, send a capital 'C' to the controller. you won't see what you type echoed on the screen, but the controller should 'reply' with what looks like a sequence of random data. This simulates the Configuration software requesting the controller's current configuration

Pressing 'S' returns the current runtime status; You will see only a few characters displayed.

If the above does not work, or if Hyperterminal indicates a COM port or communications error:

1. Use a different serial cable. The cable you're using might not be compatible serial cable, or may have a broken internal connection.
2. Are you using the same serial port with other applications? Programs like synchronization software for hand-held devices like the Palm are known for keeping the serial port open, preventing other applications from accessing it.
3. As a debugging step, try a different computer. This will at least let you know the MJLJ and software can communicate, and will help narrow down the source of the problem.
4. If you're using a USB-serial adapter, make sure the latest drivers are installed, the driver shows no errors, and you know which COM port it was installed on. Often the USB-Serial adapter will install on a high COM port number, like COM6. You can verify this by accessing 'Device Manager' in Windows and viewing the properties of the USB-Serial adapter under 'Ports'.

If you can get the expected response from the MJLJ, then there is a configuration problem with the MJLJ software. Verify you have the correct COM port set under 'Options'. If the trouble persists, check for a newer version of the software, or inquire on the forums[1] for additional help.

Hardware Troubleshooting

If you built the MJLJ from a kit and your controller does not communicate or otherwise doesn't seem to be 'alive', perform the following checks;

Check Power

• Verify you have an adequate power supply, correctly connected to the MJLJ unit. See the Vehicle installation guide
• With the unit powered up, check to make sure the correct voltage (+5v) is present at all of the power input pins of the integrated circuits and oscillator.

Ensure sure the components are installed correctly

• Diodes and capacitors installed with the correct polarity (capacitors marked with a '+' or '-' sign)
• Integrated circuits, oscillator and transistors with the correct polarity (orient the notch on the chip with the notch shown on the circuit board)

Check for good solder joints

• Carefully inspect the pins to make sure the solder connections are bright and flow completely around the pins and onto the pad.
• Ensure that you haven't accidentally lifted the pad away from the board and broken a solder trace.
• Check for solder 'bridges' where you might have solder across two pads, resulting in a short circuit.

MJLJ communicates with Configuration software; No RPM signal

If you can communicate with the MJLJ software but cannot get an RPM signal from the EDIS module-

1. Check the connection between the EDIS module and the MJLJ. Ensure the PIP signal from the EDIS module is connected to the correct pin on the Molex connector. Review the MJLJ connection diagram for your version of MJLJ hardware.
2. Perform the Hardware check in the Hardware Troubleshooting section.
3. If you have access to an oscilloscope, you can verify the PIP signal on Pin 4 of the processor.
4. You can also check the PIP signal using the AC setting of a multimeter. with the engine running you should see an AC reading that goes away when the engine is not running.
5. Feel free to inquire on the Forums

MJLJ Communicates with PC; Does not control advance

If you can communicate with the MJLJ, but cannot get the MJLJ to control the EDIS module (i.e. you have connected a timing light and cannot observe the ignition advance changing), verify the following:

1. Verify the MJLJ sees the PIP signal emitted from the EDIS module. The best way to verify this is to observe the realtime display, watching for RPM changes.
2. If the configuration software shows an RPM reading, check the connections for the SAW signal, verifying that it is connected correctly. If you have an oscilloscope, watch for the SAW pulse coming from the MJLJ module; otherwise, watch for an AC signal using a volt meter.
3. Check your wiring. Ensure you are connecting to the correct pins on the MJLJ molex connector and the EDIS module.
4. Finally, inquire on the Forums.

Problems with USB-Serial Adapter

Communication stops when engine is running

If the Configuration Software stops communicating with the MJLJ when the engine is started, try to physically distance the USB-Serial adpater from the MJLJ by inserting a serial extension cable. This may be especially bad for USB-Serial adapters that can plug straight into the MJLJ.

The current theory is the unshielded electronics of the USB-Serial adapter is affected by electrical interference, presumably ignition noise. Some adapters are more sensitive than others; so far this has been reported on adapters based on the Prolific chipset.