R-net
Error Code List with Remedies
Error
ID
Error Name
0001
0200
0203
Memory Error
PM Memory Error
Calibration Error
0204
Memory Error
0208
0500
0600
0601
0602
0603
0703
0704
0707
0808
080A
Memory Error
Reference Hold Error
Error Converting 0V Mux 0 Connection
Error Converting 0V Mux 1 Connection
Error Converting 0V Mux 2 Connection
Error Converting 0V Mux 3 Connection
Joystick Supply Failure
12V Supply Failure
Regulator Supply Failure
Joystick Error
Mid Reference Error
Joystick Error
Mid Reference Comparison Error
Mid Reference Comparison Startup
Joystick Error
Error
SID Detached
OMNI Input Device Disconnected
Gone To Sleep
EEPROM
Write Error
EEPROM
Not Busy Fault
EEPROM
Write Timeout
EEPROM
Address Out Of Range
Joystick Error
Joystick Error Right
Joystick Error
Joystick Error Forward
Joystick Error
Dual Path Comparison Right Error
Joystick Error
Dual Path Comparison Forward Error
Current Limit
Reference Fault
Current Limit
Failed To Operate When Positive Inpu
Current Limit
Left Sense Trip
Current Limit
Right Sense Trip
Current Limit
Startup Fault
Current Limit
Sense Trip
Motors Cross Coupled
Solenoid Brake
Driver Fault
Solenoid Brake
Interlock Fault
M1 Solenoid Brake Fault
M2 Solenoid Brake Fault
High Battery Voltage
High Battery Voltage
Overvoltage Comparator Tripped
Relay On In Standby
Relay Off In Drive
Relay Interlock Fault
Relay Driver Fault
Relay Stuck Closed
Watchdog Failed To Trip
Right Forward Current Null Bad
Right Reverse Current Null Bad
080B
0905
0A00
0B00
0B01
0B02
0B08
0E00
0E02
1200
1202
1302
1304
1308
1309
130A
1310
1404
1503
1504
1505
1506
1600
1601
1700
1701
1703
1704
1705
1801
1B01
1B02
Revision
1
Extended Description
Fault Type
Text displayed on
JSM or OMNI
Remedy
#
Running Ram Check Error
EEPROM Check Error
EEPROM Calibration Data Check Error
EEPROM Programming Data Check
Error
EEPROM Persistent Data Check Error
System fault
System fault
System fault
Memory Error
PM Memory Error
Cal Error
1
2
3
System fault
Memory Error
1
System fault
Control fault
Control fault
Control fault
Control fault
Control fault
Control fault
Control fault
Control fault
System fault
System fault
Memory Error
Joystick Error
Joystick Error
1
TBD
3
3
3
3
TBD
3
3
4
4
System fault
Joystick Error
4
System fault
System fault
Control fault
Control fault
Control fault
Control fault
System fault
System fault
System fault
System fault
Control fault
Control fault
Control fault
Control fault
Control fault
Control fault
Control fault
Control fault
Control fault
System fault
System fault
System fault
System fault
Control fault
Control fault
Control fault
Control fault
Control fault
Control fault
Control fault
Control fault
SID Disconnected
Gone to Sleep
5
6
TBD
TBD
TBD
TBD
4
4
4
4
TBD
TBD
3
3
3
3
3
3, 7, 8
3, 7, 8
7
8
9
9
TBD
TBD
3, 10
TBD
3, 10
3, 10
3
3
Revision effective from:
2009-06-01
Joystick Error
Joystick Error
Joystick Error
Joystick Error
M1 Brake Error
M2 Brake Error
High Battery
High Battery
Page:
1/ 9
R-net
Error
ID
1B10
1C01
1C02
1C10
1D00
1D03
1E03
1E07
1E20
1E21
1E22
1E23
1E24
1E25
1E26
1E27
1E28
1E29
1E2A
1E2B
1E2C
1E2D
1E2E
1E2F
1E30
1E31
1E32
1E33
1E34
1E35
1E36
1E37
1E38
1E39
1E3A
1E3B
1E3C
1E3D
1E3E
1E3F
2A00
2A01
2B00
2B01
2C00
2C01
2C02
2F01
3100
Error Name
Error Code List with Remedies
Extended Description
Positive Current Feedback Null Bad
Left Forward Current Null Bad
Left Reverse Current Null Bad
Negative Current Feedback Null Bad
Front End Fault
Switch Input
Pullup Circuit Failure
Inhibit Active
Charger Connected
User Switch Detached
Inhibit Active
Inhibit Active
Inhibit Active
Inhibit Active
Inhibit Active
Inhibit Active
Inhibit Active
Inhibit Active
Inhibit Active
Inhibit Active
Inhibit Active
Inhibit Active
Inhibit Active
Inhibit Active
Inhibit Active
Inhibit Active
Inhibit Active
Inhibit Active
Inhibit Active
Inhibit Active
Inhibit Active
Inhibit Active
Inhibit Active
Inhibit Active
Inhibit Active
Inhibit Active
Inhibit Active
Inhibit Active
Inhibit Active
Inhibit Active
Inhibit Active
Inhibit Active
Feedback Voltage Fault Right
Right Voltage Null Bad
Feedback Voltage Fault Left
Left Voltage Null Bad
Low Battery Voltage
Low Battery Voltage
Very Low Battery Voltage (<16v)
Low Battery Voltage
Low Battery Lockout (<16v)
Center Joystick
Low Bridge Voltage
Revision
1
Revision effective from:
2009-06-01
Fault Type
Control fault
Control fault
Control fault
Control fault
Control fault
Control fault
System fault
System fault
System fault
System fault
System fault
System fault
System fault
System fault
System fault
System fault
System fault
System fault
System fault
System fault
System fault
System fault
System fault
System fault
System fault
System fault
System fault
System fault
System fault
System fault
System fault
System fault
System fault
System fault
System fault
System fault
System fault
System fault
System fault
System fault
Control fault
Control fault
Control fault
Control fault
System fault
System fault
System fault
System fault
Control fault
Text displayed on
JSM or OMNI
Charging
Switch Detached
Inhibit Active
Inhibit Active
Inhibit Active
Inhibit Active
Inhibit Active
Inhibit Active
Inhibit Active
Inhibit Active
Inhibit Active
Inhibit Active
Inhibit Active
Inhibit Active
Inhibit Active
Inhibit Active
Inhibit Active
Inhibit Active
Inhibit Active
Inhibit Active
Inhibit Active
Inhibit Active
Inhibit Active
Inhibit Active
Inhibit Active
Inhibit Active
Inhibit Active
Inhibit Active
Inhibit Active
Inhibit Active
Inhibit Active
Inhibit Active
Inhibit Active
Inhibit Active
Low Battery
Low Battery
Low Battery
Center Joystick
Page:
2/ 9
Remedy
#
3
3
3
3
TBD
TBD
11
12
13
13
13
13
13
13
13
13
13
13
13
13
13
13
13
13
13
13
13
13
13
13
13
13
13
13
13
13
13
13
13
13
3
3
3
3
14
14
14
4
3, 10
R-net
Error
ID
3101
3203
3211
3215
3611
3A00
3A05
3B00
3C00
3D00
3D01
3E00
3E01
6401
7902
7A08
7A09
7A0A
7A0B
7A0C
7A0D
7A0E
7A12
7A13
7A22
7A23
7A32
7A33
7A42
7A43
7A52
7A53
7A62
7A63
7A90
7A91
7C00
7E00
7E01
7E02
7E03
7E04
7E05
7E06
7E07
Error Name
Error Code List with Remedies
Extended Description
Bridge To Battery Short
Port 2 Verification Error
Bad Settings
Parameter Range Error
ADC Storage Error
Failed To Arm Trip Latch
Bad Settings
System Power Cycle Required
M1 Motor Open Circuit
M2 Motor Open Circuit
M1 Motor Shorted High
M1 Motor Shorted Low
M2 Motor Shorted High
M2 Motor Shorted Low
Latched Drive Timeout
Latched drive timeout expired
High Temperature
Overtemperature
Actuator Driver Over Temperature
(Actuators)
Actuator Driver Error
Enabled In Standby
Actuator Driver Error
Disabled In Drive
Actuator Driver Failure
Over-current Actuator
Channel Current Exceeded
Channel Current Amplifier Failure
Over-current Actuator
Actuator Current Sensor Temperature
Channel
Actuator 1 Shorted High
Actuator 1 Shorted Low
Actuator 2 Shorted High
Actuator 2 Shorted Low
Actuator 3 Shorted High
Actuator 3 Shorted Low
Actuator 4 Shorted High
Actuator 4 Shorted Low
Actuator 5 Shorted High
Actuator 5 Shorted Low
Actuator 6 Shorted High
Actuator 6 Shorted Low
Over-current Actuator
Common Current Exceeded
Channel
Total Current Amplifier Failure
Thermistor Fault
Thermistor measurement is out of range
PM Memory Error
Running Repository Error
PM Memory Error
Unable to Open PM Req File
Memory Error
Unable to synchronise with Repository
Memory Error
Failed to cancel queued message
Memory Error
Repository aborted transfer
Memory Error
Repository timeout during transfer
Invalid Repository node number
Memory Error
detected
Memory Error
Incompatible file format
Revision
1
Revision effective from:
2009-06-01
Fault Type
Control fault
Control fault
System fault
Control fault
Control fault
System fault
System fault
System fault
System fault
System fault
System fault
System fault
System fault
System fault
Control fault
System fault
Control fault
Control fault
Control fault
System fault
Control fault
System fault
Text displayed on
JSM or OMNI
Bad Settings
Bad Settings
Cycle Power
M1 Motor Error
M2 Motor Error
M1 Motor Error
M1 Motor Error
M2 Motor Error
M2 Motor Error
Latched TO
Overtemp. (Acts)
Over-current
Over-current
Control fault
Control fault
Control fault
Control fault
Control fault
Control fault
Control fault
Control fault
Control fault
Control fault
Control fault
Control fault
System fault
Remedy
#
3
TBD
15
TBD
3
15
16
17
18
19
20
21
22
23
24
25
25
25
25
25
25
25
25
25
25
25
25
25
25
25
25
25
25
25
Over-current
25
Control fault
Control fault
System fault
System fault
System fault
System fault
System fault
System fault
PM Memory Error
PM Memory Error
Memory Error
Memory Error
Memory Error
Memory Error
25
3
2
2
1
1
1
1
System fault
Memory Error
1
System fault
Memory Error
1
Page:
3/ 9
R-net
Error
ID
Error Name
7E08
7E09
Memory Error
Memory Error
7E0A
Memory Error
7E0B
7E0C
7E0D
7E0E
Memory Error
Memory Error
Memory Error
Memory Error
7E0F
Memory Error
7E10
Memory Error
7E11
Memory Error
7E12
Memory Error
7E13
Memory Error
7E14
Memory Error
7E15
Memory Error
7E20
7E21
7E22
7E23
7E24
7E25
7E26
7E27
7E28
7E29
7E2A
7E2B
7E2C
7E2E
7E2F
7E30
7E34
7E35
7E36
7E37
7E38
7E39
7E3A
7F00
8100
8101
8102
8103
8104
Memory Error
Memory Error
Memory Error
Memory Error
Memory Error
Memory Error
Memory Error
Memory Error
Memory Error
Memory Error
Memory Error
Memory Error
Memory Error
Memory Error
Memory Error
Memory Error
Memory Error
Memory Error
Memory Error
Memory Error
Memory Error
Memory Error
Memory Error
Bad Cable
System Error
Bus Off
CAN Receiver Overrun
Memory Error
System Error
Revision
1
Error Code List with Remedies
Extended Description
Fault Type
Text displayed on
JSM or OMNI
Remedy
#
Bad data in Repository file
Bad descriptor in Repository file
Old file format in Repository cannot
restore corrupt file
File Slot CRC does not match
Special File sequence error
Incompatible Special File format
Unable to repair corrupt Special File
Invalid Special File version in
Repository
Invalid Special File variant
Upgrade would mix Special File
variants
Unable to repair corrupt Special File set
Failed to delete Special File in order to
repair set
Repository aborted tranfer – Special
File
Repository timeout during tranfer Special File
Get Repository Timeout
Release Repository Timeout
Check Repository Timeout
Repository Taken
Repository Not Released
Set Values Get File Slot Error
Set Values Set Slot Location Error
Slot Write Error
Set Values Slot Data Error
Set Values Get File Slot Error
Get Values Get File Slot Error
Get Values Set Slot Location Error
Get Values Slot Data Error
Get Size Get File Slot Error
Get Slot Size Error
Get Operating Time Error
Get Eventlog Event Error
Get Org Number Error
Get Attributes Get File Slot Error
Get Slot Check Error
Set Slot Verify Error
Get File Attributes Error
Repository Data Corrupt
CAN Transceiver in fault tolerent mode
CAN Device Off-line
System fault
System fault
Memory Error
Memory Error
1
1
System fault
Memory Error
1
System fault
System fault
System fault
System fault
Memory Error
Memory Error
Memory Error
Memory Error
1
1
1
1
System fault
Memory Error
1
System fault
Memory Error
1
System fault
Memory Error
1
System fault
Memory Error
1
System fault
Memory Error
1
System fault
Memory Error
1
System fault
Memory Error
1
System fault
System fault
System fault
System fault
System fault
System fault
System fault
System fault
System fault
System fault
System fault
System fault
System fault
System fault
System fault
System fault
System fault
System fault
System fault
System fault
System fault
System fault
System fault
System fault
System fault
Control fault
Control fault
System fault
System fault
Memory Error
Memory Error
Memory Error
Memory Error
Memory Error
Memory Error
Memory Error
Memory Error
Memory Error
Memory Error
Memory Error
Memory Error
Memory Error
Memory Error
Memory Error
Memory Error
Memory Error
Memory Error
Memory Error
Memory Error
Memory Error
Memory Error
Memory Error
Bad Cable
System Error
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
26
27
TBD
TBD
1
27
Rebus Tx Queue Full
Rx DLC Not As Expected
Revision effective from:
2009-06-01
Memory Error
System Error
Page:
4/ 9
R-net
Error
ID
Error Name
8105
8106
8107
8108
8109
810A
810B
DIME Error
System Error
System Error
System Error
System Error
PM Memory Error
PM Memory Error
Error Code List with Remedies
Extended Description
8180
8181
8182
8183
8184
Config Failure
Rebus Event Queue Overflow
Config Data Access Error
Pre-Op Failure
SCF File Read Failure
DCF File Read Failure
Failed to Init DCF Tables by Pre-Op
System Error
End
System Error
Config Failure - No Repository Node
Config Failure - Too Many Repository
System Error
Nodes
SCID Received by Waking Node
Memory Error
Tx Confirm Timeout
System Error
Config Failure - No PG Input Device
Config Failure - Invalid PG Input
System Error
Devices Param System fault
Config Failure - Unexpected Non PG
System Error
Input Device System fault
Bad Settings
Unable to Select Profile
Memory Error
Invalid AIM Indicated
Memory Error
Invalid Mode or Profile Message
Bad Settings
No Modes Available
Focus Mask Access Error
8800
Overtemperature (Lamps)
8811
8812
8819
881D
881E
882C
883C
8E00
8E01
Left Lamp Short Circuit
Right Lamp Short Circuit
Brake Lamp Short Circuit
Left Indicators Short Circuit
Right Indicators Short Circuit
Indicators Open Circuit
Indicators Open Circuit
Indicators Single Bulb Failure
Statemachine Queue Overflow
Event Queue Overflow
Module reporting Error may need
Module Error
repair.
810C
810D
810E
8110
8140
8141
8142
8143
FFFF
Revision
1
Lighting Driver Over Temperature
Revision effective from:
2009-06-01
Fault Type
Text displayed on
JSM or OMNI
Remedy
#
System fault
System fault
System fault
System fault
System fault
System fault
System fault
DIME Error
System Error
System Error
System Error
System Error
PM Memory Error
PM Memory Error
28
27
27
27
27
2
2
System fault
System Error
27
System fault
System Error
27
System fault
System Error
27
Control fault
System fault
System fault
Memory Error
System Error
1
TBD
System Error
27
System Error
27
System fault
System fault
System fault
System fault
Control fault
System fault
System fault
System fault
System fault
System fault
System fault
System fault
System fault
Control fault
Control fault
System fault
Bad Settings
Memory Error
Memory Error
Bad Settings
Overtemp.
(Lamps)
Left Lamp Short
Right Lamp Short
Brake Lamp Short
L Ind Lamp Short
R Ind Lamp Short
Ind Lamp Failed
Ind Lamp Failed
Module Error
Page:
5/ 9
15
1
1
15
TBD
25
25
25
25
25
25
2
25
TBD
TBD
1, 29
R-net
Error Code List with Remedies
The remedy numbers shown in the right column of the Error Code List refer to the Suggested Actions below. Go to
the remedy number shown in the Error Code list and perform the actions to attempt to remedy the issue. If these
actions do not resolve the issue, contact Permobil Technical Support for further assistance.
Remedy
1
2
3
4
5
6
7
8
9
10
Suggested Actions
This memory error could be caused by any of the modules within the R-net system.
 Check all cables and connections.
 Turn the wheelchair off and back on using the power button on the JSM or other input device.
If the trip is still present and the system contains non-PGDT Modules (i.e. ESP, ICS Master Module, Co-Pilot, etc):
 Disconnect all the non-PGDT modules and turn the wheelchair off and back on using the power button.
If this has cleared the error:
 Connect each non-PGDT Module in turn, cycling the power each time.
 If the trip reappears after one of the power cycles then the last module added to the system must be causing the error.
This memory error is specific to the R-net Power Module.
 Check all cables and connections.
 Using the R-net PC Programmer, re-write the wheelchair’s program file to the control system.
The most current program file for the specific wheelchair model should be used, contact Permobil for assistance.
Perform the following steps:
 Check the condition and charge level of the batteries.
 Ensure the connections between the batteries and power module are tight and the cables are not damaged.
 Ensure the connections between the motors and power module are tight and the cables are not damaged.
 Remove and Restore power to the Drive System by turning the Circuit Breaker off/on or by disconnecting the Main
Fuse from the batteries and reconnecting it.
The most common cause of this error is if the joystick is deflected away from center before and during the time the control
system is switched on. The joystick displaced screen will be displayed for 5 seconds, if the joystick is not released within that
time then a error is registered.
 Ensure that the joystick is centered and power-up the control system.
The Omni has detected that the Specialty Input Device (SID) has become disconnected.
 Check all cables and connectors between the Omni and the SID.
If the error persists:
 Check that the setting of the Omni parameter, 9-Way Detect, is appropriate for the SID that is being used. For
example, if the SID has no detect-link (connection between pins 5 & 8), then this parameter should be set to Off.
This occurs when the control system has been left inactive for a time greater than the parameter Sleep Timer. An entry is made
in the system log each time this occurs.
This error occurs when the control system detects a problem in the solenoid brake connected to the M1 port of the Power
Module or the connections to the brake itself.
 The brake connected to M1 varies by configuration, follow cabling to ensure you are checking the correct one.
 Check the solenoid brake, cables and connections to the power module.
This error occurs when the control system detects a problem in the solenoid brake connected to the M2 port of the Power
Module or the connections to the brake itself.
 The brake connected to M2 varies by configuration, follow cabling to ensure you are checking the correct one.
 Check the solenoid brake, cables and connections to the power module.
This occurs when the control system detects that the battery voltage has risen above 35V. The most common reasons for this
are overcharging of the battery or bad connections between the control system and the batteries.
 Check the charge level and condition of the batteries.
 Ensure the connections between the batteries and the control system are tight and not damaged.
 Ensure the connection between the batteries and circuit breaker/main fuse are tight and not damaged.
This error is sometimes caused by low battery voltage or a worn or defective battery.
 Check the charge level and condition of the batteries.
 Ensure the connections between the batteries and the control system are tight and not damaged.
 Ensure the connection between the batteries and circuit breaker/main fuse are tight and not damaged.
Revision
1
Revision effective from:
2009-06-01
Page:
6/ 9
R-net
Remedy
11
12
13
14
15
16
17
18
19
Error Code List with Remedies
Suggested Actions
This occurs when the control system detects that a charger is connected to the front of the JSM/OMNI or the chassis mounted
charger connector. The Battery charging screen (climbing bars) will be displayed during charger connection.
 An entry is made in the system log each time this occurs. Disconnect the charger from the Wheelchair.
If the trip is still present after the charger has been disconnected, the Joystick Module may be defective, contact Permobil.
The Omni has detected that the User Switch has become disconnected from the U1 or U2 port of the Omni.
 Check all cables and connectors between the Omni ports and the User Switch.
If the trip is still present after the above checks have been made, then the User Switch may be defective. Try replacing it with a
known good switch.
If it is required to use the Omni without a User Switch being connected, then the parameter Switch Detect should be set to Off.
If a User Switch is not used the responsibility for that decision lies with the healthcare professional.
This occurs when any of the Inhibit inputs are active and in a latched state. The actual inhibit that is active is indicated by the
last 2 digits of the Error Code. The code is in Hex. For example:
1E20 - For Inhibit 2
1E21 - For Inhibit 3
1E22 - For Inhibit 4
1E23 - For Inhibit 5
 Turn the wheelchair off and on, this will drop the inhibit out of its latched state, that might clear the trip.
 Check all wiring and switches connected to the indicated Inhibits.
This error occurs when the controller detects that the battery voltage has fallen below 16V.
 Check the charge level and condition of the batteries.
 Ensure the connections between the batteries and the control system are tight and not damaged.
 Ensure the connection between the batteries and circuit breaker/main fuse are tight and not damaged.
This error occurs when the control system detects incorrect or invalid program settings.
 Make a note of the current parameter settings by reading them from the controller and saving or printing them.
 Check that all parameter settings appear correct. Re-program the control system using the R-net PC Programmer.
If the error persists:
 Reset the control system to factory default settings using the Return to Defaults command.
 Using the previously saved or printed parameter settings, re-program the required settings in small groups, cycling
the power after each group to see if the trip occurs again.
This message is displayed when the R-net system encounters a change in the system or program settings, and must power
down and back up again for the adjustments to be held. It is not a trip condition, but an indication that the Cycle Power
function has been activated.
 Turn the wheelchair off and back on using the power button on the JSM or other input device.
This error occurs when the control system detects that the motor connected to the M1 port of the Power Module has become
disconnected.
 The motor connected to M1 varies by configuration, follow cabling to ensure you are checking the correct one.
 Check the motor cables and connections between the motor and control system, ensure there is no damage.
 Check the motor for proper operation using a voltmeter and/or external power source.
This error occurs when the control system detects that the motor connected to the M2 port of the Power Module has become
disconnected.
 The motor connected to M2 varies by configuration, follow cabling to ensure you are checking the correct one.
 Check the motor cables and connections between the motor and control system, ensure there is no damage.
 Check the motor for proper operation using a voltmeter and/or external power source.
This occurs when the control system detects that the motor connected to M1 on the Power Module has "short-circuited" to a
battery positive connection.
 The motor connected to M1 varies by configuration, follow cabling to ensure you are checking the correct one.
 Check the motor cables and connections between the motor and control system, ensure there is no damage.
 Check for voltage between the M1 motor connections and the positive battery terminals when the wheelchair is on,
but not driving the motors.
 Check the motor for proper operation using a voltmeter and/or external power source.
Revision
1
Revision effective from:
2009-06-01
Page:
7/ 9
R-net
Remedy
20
21
22
23
24
25
26
27
Error Code List with Remedies
Suggested Actions
This occurs when the control system detects that the motor connected to M1 on the Power Module has "short-circuited" to a
battery negative connection.
 The motor connected to M1 varies by configuration, follow cabling to ensure you are checking the correct one.
 Check the motor cables and connections between the motor and control system, ensure there is no damage.
 Check for voltage between the M1 motor connections and the negative battery terminals when the wheelchair is on,
but not driving the motors.
 Check the motor for proper operation using a voltmeter and/or external power source.
This occurs when the control system detects that the motor connected to M2 on the Power Module has "short-circuited" to a
battery positive connection.
 The motor connected to M2 varies by configuration, follow cabling to ensure you are checking the correct one.
 Check the motor cables and connections between the motor and control system, ensure there is no damage.
 Check for voltage between the M2 motor connections and the positive battery terminals when the wheelchair is on,
but not driving the motors.
 Check the motor for proper operation using a voltmeter and/or external power source.
This occurs when the control system detects that the motor connected to M2 on the Power Module has "short-circuited" to a
battery negative connection.
 The motor connected to M2 varies by configuration, follow cabling to ensure you are checking the correct one.
 Check the motor cables and connections between the motor and control system, ensure there is no damage.
 Check for voltage between the M2 motor connections and the negative battery terminals when the wheelchair is on,
but not driving the motors.
 Check the motor for proper operation using a voltmeter and/or external power source.
This message is displayed when the Latched Drive Timeout period is exceeded. It is not a trip condition, but an indication that
the Timeout period has been exceeded.
 If the Latched Drive Timeout period is not long enough, adjust the Latched Timeout parameter.
This error occurs when the control system reaches its Temperature Threshold and thus becomes too hot. The controller goes
out of drive into standby to allow the controller to cool down. An entry is made in the system log each time the controller gets
too hot and goes out of drive.
This error refers to a problem with the PGDT Seating Module (SM) or Intelligent Seating Module (ISM).
Permobil Wheelchairs do not utilize these modules, therefore this error code should not be seen on Permobil products.
This error is displayed when the control system detects a fault in the wiring in the R-net bus cables between any of the
modules.
 Confirm that all cables are securely connected to their mating connectors (no yellow showing.)
 Check all cables and connections for continuity from one end of the cable to the other, using an ohmmeter.
 If there is any visible damage to any cable, replace it.
 Disconnect one cable from the system at a time cycling the power after each disconnection. When the error is no
longer displayed, that cable or the module it connects to is at fault.
This occurs when the system detects a trip that cannot be attributed to a specific module.
 Check all cables and connections.
 Turn the wheelchair off and back on using the power button on the JSM or other input device.
If the trip is still present and the system contains non-PGDT Modules (i.e. ESP, ICS Master Module, Co-Pilot, etc):
 Disconnect all the non-PGDT modules and turn the wheelchair off and back on using the power button.
If this has cleared the trip:
 Connect each non-PGDT Module in turn, cycling the power each time.
If the error reappears after one of the power cycles then the last module added to the system must be causing the error.
Revision
1
Revision effective from:
2009-06-01
Page:
8/ 9
R-net
Remedy
28
29
Error Code List with Remedies
Suggested Actions
This error occurs when the control system detects an identification conflict between two modules in the system.
If a new module has been introduced:
 Disconnect the new module and cycle the power.
 If no trip is present connect the new module to the system and cycle the power.
 If the trip reappears then the new module must be the cause of the problem.
If there have been no additions:
 Disconnect one module at a time.
 Cycle power as each module is removed using the power button on the JSM or other input device.
 When the error is no longer displayed, reconnect the modules in reverse order to help identify the conflicting devices.
If the error is still present after the above checks have been made, contact Permobil for further assistance.
This error refers to an unknown problem with the module that is reporting the error.
 Access the System Fault Log using the On-Board Programming (OBP) or the R-net PC Programmer. Find the module
name/ID that has an FFFF error in its error log.
 The module with FFFF in its error log needs to be investigated and may need to be repaired or replaced.
Revision
1
Revision effective from:
2009-06-01
Page:
9/ 9