Raymond EASI REACH:
Code 28

I have a unit that code 28 comes up intermittantly. Once the truck is shut down and restarted everything works ok. Does anyone know what this code refers to?
  • Posted 23 Jun 2009 13:03
  • Discussion started by Jenn
  • Alberta, Canada
Showing items 1 - 11 of 11 results.
How do you perform the test for the encoder? Do you need a laptop or is it an on-board test? Thanks!
  • Posted 12 Sep 2019 02:26
  • Reply by Otterwork
  • Manitoba, Canada
for code 28, verify the encoder pully is tight on shaft and does'nt spin. also, make sure the encoder is free to swivel. do not tighten the mounting screws as the belt may jump the teeth. play in the encoder is ok. If your connections are all ok, and you tried another known good encoder, the system card or VFC may need replacement.
Code 29 is also no encoder counts while drive is commanded. You need to go into INPUT tests I16 and manually turn encoder to verify it counts from 255 to zero as you turn it. Again, make sure gear is not spinning on shaft and belt is free to spring back. possible other cause are System card, VFC.
  • Posted 2 Aug 2011 01:04
  • Reply by EasiTek
  • Ontario, Canada
Did you ever resolve the original code 28 issue? I have the same code but my belt/gears are good and swapped the encoder with a known good one and still the problem presist. Anyone have any other ideas?
  • Posted 21 Jul 2011 04:45
  • Reply by BenH
  • California, United States
hi I got code 29 same truck, please any help wellcome.
  • Posted 6 Jul 2011 05:23
  • Reply by VerticalVicDude
  • California, United States
Thanks for your help
  • Posted 12 May 2010 12:23
  • Reply by Jenn
  • Alberta, Canada
The other way to diagnose is to open up before turning on the key, remove the encoder belt, and then turn on. If the 84 does not come on then you have brake issues allowing the truck to travel as noted above. This is the issue 99% of the time. I would also add that the barkes may need to be bled.. cheaper and faster than replacing the brakes
  • Posted 11 May 2010 23:59
  • Reply by JonG
  • United States
code 84, if the truck is jumping upon start up, your brakes are slipping, check the pads or the adjustments to see that they are opening evenly, the top pads tend to wear faster than the bottoms
  • Posted 11 May 2010 10:47
  • Modified 11 May 2010 10:49 by poster
  • Reply by blaine
  • Rhode Island, United States
Hi son t, I thank you for your help with code 28 this same unit is now got a code 84 do you know what this is?
  • Posted 5 May 2010 05:19
  • Reply by Jenn
  • Alberta, Canada
Hi son t, I thank you for your help with code 28 this same unit is now got a code 84 do you know what this is?
  • Posted 5 May 2010 05:19
  • Reply by Jenn
  • Alberta, Canada
Hi Jenn,
Some reasons could make code 28, anyhow you may need to check the drive belt and pulley of encoder first, they may be loose or bad. Good luck
  • Posted 5 Jul 2009 23:46
  • Reply by son_t
  • Vietnam, Vietnam
Hi Jenn,
Some reasons could make code 28, anyhow you may need to check the drive belt and pulley of encoder first, they may be loose or bad. Good luck
  • Posted 5 Jul 2009 23:43
  • Reply by son_t
  • Vietnam, Vietnam

Post your Reply

Forkliftaction.com accepts no responsibility for forum content and requires forum participants to adhere to the rules. Click here for more information.

Having trouble using the Discussion Forums? Contact us for help.

Fact of the week
Bluetooth is named after the 10th-century Viking king, Harald Bluetooth, who united warring tribes in Denmark and Norway. In 1997, Jim Kardach from Intel gave the name to the technology because of its ability to unite different communication protocols, just as Harald united various tribes.
Movers & Shakers
Pete Stanislawczyk Pete Stanislawczyk
Chief executive officer, East Penn Manufacturing
President, East Penn Manufacturing
APAC vice president, Jungheinrich
Senior VP direct sales and marketing, Daifuku Intralogistics America
Latest job alerts …
Ottumwa, IA, United States
Harrisburg, SD, United States
Wentzville, MO, United States
Fact of the week
Bluetooth is named after the 10th-century Viking king, Harald Bluetooth, who united warring tribes in Denmark and Norway. In 1997, Jim Kardach from Intel gave the name to the technology because of its ability to unite different communication protocols, just as Harald united various tribes.