Troubleshooting the MegaJolt Lite Jr. - Revision history

Brentp: /* Troubleshooting with Hyperterminal */ oriented toward MJLJ V4

2009-01-11T04:34:45Z

Troubleshooting with Hyperterminal: oriented toward MJLJ V4

← Older revision		Revision as of 04:34, 11 January 2009
Line 11:		Line 11:
	When it asks for the communication settings, use the following:		When it asks for the communication settings, use the following:

	Bits Per Second: ~~4800~~ - for V3 MJLJ hardware ; or ~~38400~~- for V4 hardware		Bits Per Second: 38400- for MJLJ V4 hardware, or 4800 - for V3 MJLJ hardware
	Data Bits: 8		Data Bits: 8
	Parity: None		Parity: None

Brentp: /* Communication stops when engine is running */ added page on usb-serial adapters

2008-11-22T18:43:51Z

Communication stops when engine is running: added page on usb-serial adapters

← Older revision		Revision as of 18:43, 22 November 2008
Line 66:		Line 66:
	==Problems with USB-Serial Adapters==		==Problems with USB-Serial Adapters==
	===Communication stops when engine is running===		===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.~~		See our [[USB-serial_adapters\|USB-Serial adapter information page]] for extended information on USB-Serial adapters.

	~~This problem typically manifests itself as the software reading rpm/advance/load data after the motor is started, then freezing in a matter of seconds.~~

	~~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~~.

Brentp: /* Troubleshooting with Hyperterminal */

2008-11-09T19:32:08Z

Troubleshooting with Hyperterminal

← Older revision		Revision as of 19:32, 9 November 2008
Line 11:		Line 11:
	When it asks for the communication settings, use the following:		When it asks for the communication settings, use the following:

	Bits Per Second: 4800		Bits Per Second: 4800 - for V3 MJLJ hardware ; or 38400- for V4 hardware
	Data Bits: 8		Data Bits: 8
	Parity: None		Parity: None
Line 19:		Line 19:
	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		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.		Pressing 'S' returns the current runtime status; You will see only a few random characters displayed.

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

Alexander: /* Communication stops when engine is running */

2008-02-24T22:24:23Z

Communication stops when engine is running

← Older revision		Revision as of 22:24, 24 February 2008
Line 67:		Line 67:
	===Communication stops when engine is running===		===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.		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.

			This problem typically manifests itself as the software reading rpm/advance/load data after the motor is started, then freezing in a matter of seconds.

	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.		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.

Alexander: /* MJLJ communicates with Configuration software; No RPM signal */

2008-02-24T22:17:28Z

MJLJ communicates with Configuration software; No RPM signal

← Older revision		Revision as of 22:17, 24 February 2008
Line 50:		Line 50:

	#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.		#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.
			#Check the Molex connector itself, specifically that the pins in the connector are properly seated. If they are not pushed far enough into the plug, they can fail to make an internal connection at all, or intermittently.
	#Perform the Hardware check in the Hardware Troubleshooting section.		#Perform the Hardware check in the Hardware Troubleshooting section.
	#If you have access to an oscilloscope, you can verify the PIP signal on Pin 4 of the processor.		#If you have access to an oscilloscope, you can verify the PIP signal on Pin 4 of the processor.

Brentp: /* Problems with USB-Serial Adapter */

2007-09-19T05:51:18Z

Problems with USB-Serial Adapter

← Older revision		Revision as of 05:51, 19 September 2007
Line 63:		Line 63:
	#Finally, inquire on the [http://www.autosportlabs.org Forums].		#Finally, inquire on the [http://www.autosportlabs.org Forums].

	==Problems with USB-Serial ~~Adapter~~==		==Problems with USB-Serial Adapters==
	===Communication stops when engine is running===		===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.		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.		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.

Brentp: added section on halted communication with running engine

2007-09-19T05:50:58Z

added section on halted communication with running engine

← Older revision		Revision as of 05:50, 19 September 2007
Line 62:		Line 62:
	#Check your wiring. Ensure you are connecting to the correct pins on the MJLJ molex connector and the EDIS module.		#Check your wiring. Ensure you are connecting to the correct pins on the MJLJ molex connector and the EDIS module.
	#Finally, inquire on the [http://www.autosportlabs.org Forums].		#Finally, inquire on the [http://www.autosportlabs.org 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.

Brentp: /* MJLJ Communicates with PC; Does not control advance */ fixed link

2007-09-02T19:00:37Z

MJLJ Communicates with PC; Does not control advance: fixed link

← Older revision		Revision as of 19:00, 2 September 2007
Line 61:		Line 61:
	#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.		#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.
	#Check your wiring. Ensure you are connecting to the correct pins on the MJLJ molex connector and the EDIS module.		#Check your wiring. Ensure you are connecting to the correct pins on the MJLJ molex connector and the EDIS module.
	#Finally, inquire on the ~~Forums.~~[http://www.autosportlabs.org]		#Finally, inquire on the [http://www.autosportlabs.org Forums].

Brentp: /* MJLJ communicates with Configuration software; No RPM signal */ fixed link

2007-09-02T19:00:15Z

MJLJ communicates with Configuration software; No RPM signal: fixed link

← Older revision		Revision as of 19:00, 2 September 2007
Line 53:		Line 53:
	#If you have access to an oscilloscope, you can verify the PIP signal on Pin 4 of the processor.		#If you have access to an oscilloscope, you can verify the PIP signal on Pin 4 of the processor.
	#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.		#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.
	#Feel free to inquire on the [~~Forums~~ http://www.autosportlabs.org]		#Feel free to inquire on the [http://www.autosportlabs.org Forums]

	==MJLJ Communicates with PC; Does not control advance==		==MJLJ Communicates with PC; Does not control advance==

Brentp: /* MJLJ communicates with Configuration software; No RPM signal */ fixed link, added line

2007-09-02T18:59:24Z

MJLJ communicates with Configuration software; No RPM signal: fixed link, added line

← Older revision		Revision as of 18:59, 2 September 2007
Line 52:		Line 52:
	#Perform the Hardware check in the Hardware Troubleshooting section.		#Perform the Hardware check in the Hardware Troubleshooting section.
	#If you have access to an oscilloscope, you can verify the PIP signal on Pin 4 of the processor.		#If you have access to an oscilloscope, you can verify the PIP signal on Pin 4 of the processor.
	#Feel free to inquire on the Forums![http://www.autosportlabs.org]		#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.
			#Feel free to inquire on the [Forums http://www.autosportlabs.org]

	==MJLJ Communicates with PC; Does not control advance==		==MJLJ Communicates with PC; Does not control advance==