ERROR CODE 0280 not conntected

[speedo]

At the track, or I would of searched this more but I need it now. My V2 was working and now I can't connect to the car.

The V2 does power up but when I try to scan or data log I can't get in and I get the code.

I just uninstalled and reinstalled software and firmware everything and updated the V2. I am LOST on this one. Could it be something with the cars computer?

The only thing that was funny the last pass when it saved what I thought was my data log but it was a save trace file????

How can I check the OB2 port to make sure its reading??

[speedo]

Has to be a setting in the V2 just did my old autotap software scan tool and it got the vin and trouble codes.

I think I am missing a setting or something with that code I saved.

[Blacky]

Error $0280: Unsupported protocol (i.e. no vehicle detected)

Cause:
FlashScan or AutoCal could not detect a valid OBD protocol.

Action:
Check all cables and connections.
Make sure ignition is turned on to the run position.
Make sure the vehicle is supported by EFILive.

Some more things to try:
Turn ignition on first, wait 10 seconds, then connect FlashScan.
Press Ctrl+OK 2 or 3 times per second until you see the VPW-XX or CAN-XX in the lower right corner of the FlashScan display. (Where XX is the number of detected controllers).

Try FlashScan in a different vehicle. If it still fails then maybe there is a problem with the OBDII cable or with FlashScan itself.

Regards
Paul

[Blacky]

I meant to also say that the error codes are described in the file:\Program Files\EFILive\V8\Documents\EFILive Error Codes.pdf

Regards
Paul

[speedo]

Is there anyway I can mess up that V2 from reading the car...??

I reinstalled the firmware and it updated the V2, but still doesn't connect to my car.

My old autotap scanner software does work.

Just trying to determine if its the V2 or the car CPU.

[Blacky]

What sort of vehicle are you trying to connect to?

Although this is not the recommended way to connect...
Try connecting FlashScan to the vehicle first, then turn on the ignition. does the orange LED second from the right flash randomly? If so then FlashScan is detecting the CAN and/or VPW data on the vehicle's OBDII connector. If not, then FlashScan is not detecting any data and is possibly faulty.

If you do see the orange LED flashing then do this:
With the ignition still on, disconnect FlashScan from the vehicle so that FlashScan is powered off. Reconnect FlashScan to the vehicle, wait for about 10 seconds, then press the Ctrl+OK button three times.
(To press Ctrl+OK, hold down the Ctrl button and while holding it down, press and release the Ok button).

Then select Scan Tool->Scan Options->Save Trace File.

Disconnect FlashScan from the vehicle, connect FlashScan to your PC.
Run the EFILive Explorer software and copy the saved trace file from the [Scan] tab page to your PC. Send me the saved trace file to paul@efilive.com

Regards
Paul

[speedo]

Thanks for all the info, I got to looking at the V2 after trying everything I found the problem this morning, one of the wires in the T5? connector was bent down for some reason, so it wasn't connecting.

Is there warranty on something like this? Not sure how this one wire was bent when the ones around it are fine since it was in the middle.

[joecar]

Do you have a photo...?

[Ira]

I'll be the one fixing it. It sounds maybe like one of the little wires in the ethernet connector is bent. I've sent you contact information privately to see about getting it fixed.

Ira

[TBMSport]

Soooooo...I now have this problem. If the cables are ok, the boot/firmware reinstall don't work...is my V2 fried?

[joecar]

Try this:


Error $0280: Unsupported protocol (i.e. no vehicle detected)

Cause:
FlashScan or AutoCal could not detect a valid OBD protocol.

Action:
Check all cables and connections.
Make sure ignition is turned on to the run position.
Make sure the vehicle is supported by EFILive.

Some more things to try:
Turn ignition on first, wait 10 seconds, then connect FlashScan.
Press Ctrl+OK 2 or 3 times per second until you see the VPW-XX or CAN-XX in the lower right corner of the FlashScan display. (Where XX is the number of detected controllers).

Try FlashScan in a different vehicle. If it still fails then maybe there is a problem with the OBDII cable or with FlashScan itself.

Regards
Paul

[TBMSport]

Paul. Thanks, but I tried in vehicle and on bench ECM. Using CTRL +OK did nothing (holding CTRL, then hitting OK nor pressing both together 2,3,4,5 times). It just stays on main screen. I used two different OBDII cables.

[joecar]

So it does not work on other vehicles either...?

Have you tried another USB cable...?
Is the OBD cable ok/undamaged...?

Sounds like it's fried (do you know what may have led to this)...?

Where are you located...?

[TBMSport]

So it does not work on other vehicles either...?

Have you tried another USB cable...?
Is the OBD cable ok/undamaged...?

Sounds like it's fried (do you know what may have led to this)...?

Where are you located...?

I was trying to benchtop program a T43 module and discovered that the power cord I had was a 1.25 Amp, rather than 2.5A so I now suspect that the power draw on it and possible disconnect or power down of the benchtop harness may have caused a kick back or spike in power. :wallbash:

[Blacky]

Paul. Thanks, but I tried in vehicle and on bench ECM. Using CTRL +OK did nothing (holding CTRL, then hitting OK nor pressing both together 2,3,4,5 times). It just stays on main screen. I used two different OBDII cables.

Can you communicate with the device from the EFILive V8 software via the USB connection? I.e. can you select the F7 Licensing option and does the license information from the FlashScan device show up?

If so we can check if the FlashScan device communicate with a controller via the OBDII connection After connecting FlashScan with the ignition on and pressing Ctrl+Ok a few times, can you save a trace file (F1 Scan -> F3 Scan Options -> F1 Save Trace), then create a support ticket (as described here: http://support.efilive.com/kb_article.php?ref=7778-QEKN-0400 ) and submit the trace file with a description of the problem.

If not, try saving the trace file while the FlashScan device is using an SD Card, then transfer the trace file by reading from the SD Card directly from a PC card reader on your PC/laptop.

Regards
Paul

[TBMSport]

Hey Paul,

I can communicate via V8 and was able to pull up the licensing info. However, whenever I hit the CTRL+OK all I get is a yellow light flash (on the 2nd from the right light). No screen change. F1->F3->F1 saves the trace, but I'm not sure it's actually communicating with the ECM. It's as if every thing up to the serial port going to the ECM is fine, but no functional communication AT the port and further down the line. I know the OBDII cord is ok because the AutoCal can powers up with the ECM and reads DTC's.

[Blacky]

Hey Paul,

I can communicate via V8 and was able to pull up the licensing info. However, whenever I hit the CTRL+OK all I get is a yellow light flash (on the 2nd from the right light). No screen change. F1->F3->F1 saves the trace, but I'm not sure it's actually communicating with the ECM. It's as if every thing up to the serial port going to the ECM is fine, but no functional communication AT the port and further down the line. I know the OBDII cord is ok because the AutoCal can powers up with the ECM and reads DTC's.

That's why I'd like to see the trace file. The Orange LED just tells us that there is data on the OBDII cable, but not which direction the data is traveling. It is possible that the LED is only flashing to indicate that FlashScan is sending an OBDII query to the ECM and that the ECM is not responding or that the message is not even getting out the RJ45 connector on FlashScan. The trace file will show me the data direction and the protocol info I need to determine what (if any) data is coming back from the ECM. Although from what you have described it sounds like the CAN transceiver chip on the V2 may be damaged.

Do you have access to a VPW based vehicle? (i.e. LS1, LB7, LLY style controller). If so it would be nice to see if FlashScan can communicate with that type of vehicle. If it can then it is almost certain that the CAN transceiver is damaged.
If that is the case, it can be repaired by replacing that chip. SoCal Diesel can do that repair (https://www.efilive.com/distributors).

Regards
Paul

[TBMSport]

Gotcha. Thanks...let me figure out how to save this and make a ticket.

[JCA]

Hi my v2 is doing the same thing it worked on Saturday on a ls1 I was tuning but went to do a e38 2 day and no love tried every thing its doing exactly the same as yours tbm sport I used swaped the v2 for a spare autocal I have using same cables laptop etc and worked no probs its been a few months since ive done a e38 so it might be that the can receiver like paul said I will try reading a ls1 2morrow - DAM IT

[Black6spdZ]

Hi my v2 is doing the same thing it worked on Saturday on a ls1 I was tuning but went to do a e38 2 day and no love tried every thing its doing exactly the same as yours tbm sport I used swaped the v2 for a spare autocal I have using same cables laptop etc and worked no probs its been a few months since ive done a e38 so it might be that the can receiver like paul said I will try reading a ls1 2morrow - DAM IT

Is this a common occurrence and failure with the V2s? I have just bought a used V2 with the same problem, $0280 no vehicle detected and my firends V2 works no problem with the same cable.

So I just did a full format and made sure it was updated with latest firmware. Uploaded E35A scan and tune files to it and nothing else. Get the same $0280 when attempting to scan valid E35A PID list. Next I tried to read tune and injector data and get $0281 error. So is this box fried? What does it cost to fix?

Update, passthrough does not detect ecm either.

[joecar]

Is this a common occurrence and failure with the V2s? I have just bought a used V2 with the same problem, $0280 no vehicle detected and my firends V2 works no problem with the same cable.

So I just did a full format and made sure it was updated with latest firmware. Uploaded E35A scan and tune files to it and nothing else. Get the same $0280 when attempting to scan valid E35A PID list. Next I tried to read tune and injector data and get $0281 error. So is this box fried? What does it cost to fix?

Update, passthrough does not detect ecm either.Does V8 Scan&Tune see your V2...?

[Black6spdZ]

yes, every part of it operates normal connected to USB, its only when I try to connect it to the ECM that it has this problem. I've been using a friends FS v2 for years with no problem.. nothing new to me. I'm pretty sure its a hardware problem.. possibly the CAN transceiver like mentioned earlier in this thread. I've talked to SoCal and mailed it off yesterday to repair.

[TBMSport]

Ok...mine started acting up again and giving me the same error when I attempt to plug into my E67's (in vehicle or benchtop). However there is no issue when plugging into my LS1 PCM in my '99 Silverado (as advised by Lorenzo at SoCal). Additionally, I notice that when I unplug the OBD/ECM port-side of the cable from the V2 (keeping the USB side plugged in), the V2 reboots. I also have the latest firmware and software updates.

It seems there is a problem with the OBD port side, but apparently only with E67. Is this a software or hardware problem that requires me to send it to SoCal?

[Blacky]

Ok...mine started acting up again and giving me the same error when I attempt to plug into my E67's (in vehicle or benchtop). However there is no issue when plugging into my LS1 PCM in my '99 Silverado (as advised by Lorenzo at SoCal). Additionally, I notice that when I unplug the OBD/ECM port-side of the cable from the V2 (keeping the USB side plugged in), the V2 reboots. I also have the latest firmware and software updates.

It seems there is a problem with the OBD port side, but apparently only with E67. Is this a software or hardware problem that requires me to send it to SoCal?

THe V2 device will always reboot when the OBDII plug is disconnected while the USB cable remains connected, that is normal.

THe LS1 controller communicates with FlashScan using the VPW protocol. The E67 controller communicates with FlashScan using the CAN protocol. Both of thos protocols are routed through different hardware circuits on FlashScan. It is quite likely that the CAN circuit has a failed transceiver chip, while the VPW circuit continues to operate normally. If that is the case, then it needs to be sent back to SoCal for repair. Before you do, (to rule out the possibility that your E67 is not faulty) make sure you've tried to connect to at least two different CAN based vehicles. Most 2005+ model years are CAN based.

Regards
Paul

[bobxr50]

I had the same problem.

Mine would work on my LB7 (VPW). But anytime I would hook up to a CAN (Cummins) circuit it would give me the same code.

When I would store my V2 I kept all the cords connected and wrapped them around the V2. Well 7+ years of doing that made the two pins inside the V2 bend down and not touch the connector were the CAN communicate. I believe the left ones.

Look on the bottom of the V2 were the Ethernet end connects too and make sure all the pins are at the same height.

I took a super small screw driver and bent them up and I have not had any troubles since.

I don't have any pics on my phone but can help you out of you have any ?s.

I would like to get the word out that when you store your V2 Disconnect ALL cables. Do not keep them connected. Our V2 are getting older and we will continue to see more and more of this.

[joecar]

Good advice.

[Blacky]

I would like to get the word out that when you store your V2 Disconnect ALL cables. Do not keep them connected. Our V2 are getting older and we will continue to see more and more of this.

Agreed, its in the quick start guide on the CD that ships with each FlashScan device.
18367

In other news, FlashScan V3 (no release date yet) does not use RJ12 or RJ45 style connectors. It uses more robust connectors for OBDII, Serial and CAN connections.

Regards
Paul