U1094

Code

Other U — Network/User

SCP (J1850) Invalid or Missing Data for Experimental #2

Brand: Other

Type: U — Network/User

Views: UK: 30 EN: 57 RU: 23

AI status

Completed

ready

Completed 100%

Page language: EN

Related system or features dependent on Experimental #2 data may be inoperative or behave erratically
One or more network-related warning lights or communication-related DTCs present
Intermittent operation of functions controlled by modules that read the Experimental #2 message
No obvious mechanical fault — issues are primarily electronic/communication

Scan vehicle for additional U-codes and module presence; note which modules are not responding
Verify battery voltage and charging system health (low voltage can cause communication faults)
Visually inspect J1850 (SCP) network harness, connectors, and grounds for damage or corrosion
Check for loose or aftermarket modules or connectors that may be interfering with the bus
Check for TSBs or software updates for modules associated with Experimental #2
Use a lab scope or CAN/J1850 breaker tool to view the bus waveform and message timing

Presence and frequency of the Experimental #2 message ID on the J1850/SCP bus
Expected data length and payload bytes for Experimental #2 (compare to factory spec)
Message timing/interval (periodicity) and any missing frames
Bus physical-layer voltages and waveform integrity (dominant/recessive levels, noise)
Bus error frames or collisions reported by modules
Module power and ground voltages while attempting communication

Retrieve freeze frame and all stored codes from all modules. Note which modules report as missing or not responding.
Confirm battery voltage >= manufacturer minimum and good charging system. Recharge or connect a stable power supply if needed.
Inspect connectors, pins, and wiring on modules that transmit or receive Experimental #2 data. Repair any corrosion, bent pins, or damaged wires.
Check for software/calibration updates or known bulletins for the vehicle that reference Experimental messages or U1094.
Perform a module presence check with a scan tool: identify the module that should send Experimental #2. If the module is not present, test its power and ground circuits.
Use a lab scope or a dedicated network analyzer to monitor the J1850/SCP bus during fault occurrence. Look for missing message IDs, malformed frames, excessive noise, or bus contention.
Wiggle-test harnesses and connectors while monitoring the bus and code status to locate intermittent wiring faults.
If a specific module is determined to be transmitting invalid data, attempt reprogramming or reflash per manufacturer procedures after confirming root cause. Replace module only after verifying hardware fault.
After repairs, clear codes and perform a road test or use diagnostic routines to ensure the Experimental #2 message is present and stable. Re-scan to confirm U1094 does not return.
If intermittent or unresolved, escalate to manufacturer technical support with captured waveform/logs and list of performed checks.

Open/short/intermittent harness or connector on the J1850 network related to the transmitting module
Transmitting module not powered, asleep, or not present (module failed or replaced without programming)
Corrupted message because of electrical noise or multiple nodes driving the bus
Module software/calibration incompatibility preventing proper message formation