If your using a real bench top power supply(and it sounds like you are) you shouldn't have to worry.Sounds like you have an adjustable voltage supply with a maximum current limiter as a safe guard not the limit of the supply. If that's the case you should be fine at 1.7 amps since it'll be able to maintain the necessary voltage with out any issues but it may be a bit on the conservative side IMO.

It's the rating on transformers that's the issue, most of the cheap ones are listing peak currant with at a fixed voltage. The PCM will only draw around 700mA while flashing and the spike when it erases the flash chip is only around 1.2 amps and is VERY brief but as electronics age...especially capacitors they can begin to pull more current so its better to have a safe over head. While I have never tested an OBDLink to see what it's draw is while running in block mode...based on the BT protocol they use and the processor I'd suspect it's pulling around 150-200mA at most and could even be under 100ma on the newer ones. So adding that on top of the PCM you want something that can do a solid 1 amp for an extended period of time and can surge for at least say 1.5 amps.

 

Hi all,

A couple of options for power supplies would be WiFi Routers and Satellite Set-Top Boxes.
I have two PSUs from Dish that are 12v @ 3a, and one from an AT&T Uverse that is 12v @ 4a
Have 3 from routers that are 12v @ 2a.

Mike

 

Any of those should be fine. Amperage is not something that's forced like voltage. Current that's simply what it's able to supply if the load requires it.

 

I am having trouble even getting a read using lsdroid and lx obdii. Every time I try it gives me " invalid hexadecimal number " The pcm is still in car as I do not have a bench system and over here, just getting a harness to modify for bench use costs a couple of hundred bucks so trying to avoid that if possible. I have tried the recommendation of pulling fuses to eliminate crossover but it has made no difference. For info this is an Australia in a WL caprice with a p59 pcm running 12592433 os. I want to flash this to 12587603 as the 2433 has only limited tuning scope on tuner pro due to a lack of info on the xdf for that os. Any advice would be appreciated. Thanks.

 

I suspect you could do it for less by building from parts rather than starting with an existing harness...

The OBD2 part is easy, here's a couple options:
https://www.amazon.com.au/iKKEGOL-Co...773879&sr=8-38
https://www.amazon.com.au/Car-Connec...774681&sr=8-18
The one I'm using is basically identical to that 2nd one.

And this is the PCM connector, however I couldn't find one on the down-under Amazon:
https://smile.amazon.com/gp/product/...?ie=UTF8&psc=1

Maybe they could ship you one from the US? Or if shipping is painfully expensive, grab the part number from the Amazon page and see if you can find it from a local supplier.

I hope this helps.

 

That's a great idea NSFW. Thanks very much for that info.Hopefully that will solve my problem. Even if it doesn't, at least I will have a bench harness lol! Cheers mate!

 

Now that is not an issue any I have had any one run into in a very long time. It is very unlikely it has anything to do with it being in the vehicle but it's possible . However as a word of warning.....once you do get this sorted out and go to flash the OS......flashing an OS in a stock vehicle(as in was equipped with a P01 or P59 factory) is not something I would suggest. There are a number of reasons why but a lot of it comes down to the Obdlinks inability to properly detect all messages present on the data bus.

Now back to your IS issue. What type of Android device are you using and what version of Android is it running? How "old" is your OBDLink, if your not sure what firmware the device has you can use the Obdlink app to update the device to the current firmware and in a lot of cases where there is odd behavior that takes care of the issue.

What version of Ls Droid are you using, BetaV0.2,0 I'm guessing?

When does it flag the invalid hexadecimal error? Is it when you ID the PCM I'm guessing? If it's not when you ID the PCM there will be a couple of .txt file saved in the base storage area on your device as well as an error log file. If you can post all of those it would be extremely helpful sorting out whats going on. The error log files will be saved regardless of when when the error occurs and it can create a couple of different kinds of error files depending on what type of error has been detected so just post anything that is LsDroid error or read related.

Take a look and see if there is any bin file that may have been saved as well......it may not be a complete file but it could have saved at least part of the data. If so being able to compare what was read with what it was saved as might point a direction as to whats going on.

 

Hi PeteS160. I am using a Huawei Nova 3E running android 9. My OBD link is new and according to the app is running 5.5 firmware. I am using BETAV0.2.0 as you said. It gives the fault usually a few percent into a full read but not at a specific point. I have attached the txt files I found but there was no .bin file I could see. I have a spare pcm for this vehicle so was happy to try out a full flash and see what happened. Thanks for having a look.

 

Ok just tried an update of firmware on lx and it went from 4.5 to 4.6 so obviously I was looking at the wrong details. Tried another read though and got the same result unfortunately.

 

In the logs you posted, the very last block shows whats going on. I've taken a pic of the log so I could highlight the point of interest where the problem occurs.




<DATAERROR means that either the frame was not fully received by the ODBLink from the PCM, there was a data collision on the bus and the Obdlink closed the port due to the collision. If it was a collision it would have been from another module on the bus trying to send out a broad cast message while the PCM was in the middle of transmitting data. Side tracking a bit.....this is a great example of why in vehicle flashing a new OS is NOT recommended. When the ODBLink runs into an issue it just reports errors and closes the port with no reason as to what caused it or why. Had you been flashing an OS this would have become a very unpleasant situation. Anyways moving on here.....the part about this log that is really strange is that after it reports DATAERROR it goes on to request the block again....as it should and the block does appear to be returned in it's entirety on the second try. What strikes me as very odd is that there is no \r\n after the <DATAERROR and there should be. With out the new line or carriage return it breaks all kinds of things with in the app....the cause of the error your getting is because it's attempting to convert the word <DATAERROR into a hexadecimal format and that's not possible. With out the \r\n there is nothing that's separating the <dataerror line from the rest of the block so it assumes that is part of the block and tries to convert it when verifying the block sum.

I have never seen behavior like this before on any of the OBDLink devices and it's very odd that it's only affecting the reply <DATAERROR and not every line. There is a setting in the Obdlink device to turn on/off carriage returns and new line settings but it's the type of thing that it affects every setting in the device including device status/system reply messages. If either of these was set incorrectly you would never make it past the initial connection screen where it configured the OBDLink device initially.

What OBDLink device specifically are you using, I'm not sure if you covered that or not? Is this an Mx+ by any chance?

Before I start pointing fingers.....I'd like to try and rule a couple of things out that should be rather simple
1) Do you have another vehicle you can test this on?
2)Do you have another phone/tablet you can test this with on your vehicle? If not do you have a friend you can convince to install the app and use it with their phone?

The fact the device is reporting the data error means something happened in the device or on the data bus......the fact it's not sending the \r\n or perhaps the obdlink is sending them and they are just not being received by your phone at the exact time it reports the error seems awfully strange.

I am by no means saying it isn't possible I can figure out a way to deal with the lack of the \r\n on the error or that there isn't something else going on that's related to the app itself but looking at that log makes me think this is going to be something that's not app related. Being able to recreate your current issue with another phone on or on another vehicle would then only leaves 2 things in question. The OBDLink or my App. If we can get it narrowed down to just those two it'll make things easier to sort out. Of course if another vehicle or phone fixes the issue....we have another place to look then.

 

Alrighty then. The one I am using is obdlink lx. I have just tried using on a p01 ecu in car and it will id the os but will time out and not even start a read. Have tried this with the original phone and now a nokia 3.1 running android 9. I also tried this new phone on the original p59 I started with and it has the same problem of the invalid hexadecimal number. So to sum up, I have tried 2 different ecu and get 2 different issues, I have tried 2 different phones and get the same results with both phones on both vehicles. The only common thing is using the same obdlink lx on both vehicles and android 9 on both phones . Hope that is enough info so far. Sorry to give you a headache lol.

 

Try downloading an App like Torq and using it with the LX for a while, I'd say a good 15-20 mins. See if the app ever seems to hang or lag out....or one of the gauges just goes crazy in the app for no reason. Torq won't break from the dataerror thing but it will make what ever pid it's reporting data for freeze or get a crazy reading back that you would be able to see. It's not a great or real scientific way to go about things but it's something that's easy to do and won't require you manually entering data into a serial terminal....and since it seems the last good serial terminal app has been removed from the Playstore I can't even point you at the App to use for that method at the moment lol.

If you have a laptop with Bluetooth you could also try the PCM Hammer and see if that runs into the same issue in your vehicle. That would at least completely rule out the phone or my App as being part of the issue. If you just purchased this LX I'd check to see what the warranty/return period was from the vendor. I know OBDLink has a great warranty if you need to deal with them directly but it won't be as easy if it's something you bought locally. Just figured I'd bring this up since a defective device does look like it's possible here and you may still be with in your return/replacement window if it's a new purchase.

 

Will definitely try these new tests and get back to you. Might be a couple of days as I am working at the moment and don't have much free time. Thanks PeteS160.

 

I'm a little late to the party, but there is a open source bin editing platform for OBD2 GM V6's

http://www.theblattners.com/Projects...r/default.html

the real problem is that there is no datalogger, most of us V6 guys were using it in conjunction with a DHP Powertunr. you could very easily read the PCM, edit the file, and re-flash it to the PCM using LS-droid if you have specific changes you needed to make. FYI, it appears as though the 2002 L67 file appears to have the most tuneable parameters, and you can edit any of the V6 files for a manual by changing a single flag. I had a thread on 60degreeV6 about it, but the site is down, and might not be coming back... if you use tiny tuner, make sure you download the database, and select "use database" to view the full potential of the program.

I also made this thread which may be helpful for V6 guys doing engine swaps. the pinouts are sourced from Alldata.

http://www.gearhead-efi.com/Fuel-Inj...V6-PCM-pinouts

 

I had completely forgotten about tiny tuner. It's been years since I've seen that. Thanks for bring that up. I'll include some info on that when I do a release on the version of Ls Droid that has the V6 write enabled. It's been slow going finding people that are willing to risk a PCM to test something out.....and that have the necessary tools to externally log the flash..... so if something did go wrong there is an outside log of the entire process that lead up to the point it went south. Most of the V6 guys are a rather odd bunch that I've run into and the whole concept of flashing/tuning seemed like it was just way over their heads. Like that's not something the average person does....that's what the guy with a dyno is for.... they just take him the car and he does all that stuff.

 

the Fiero community does a bit of their own tuning, depending on which engine and trans, but most of the guys who have built truly badass V6's have used OBD1 stuff like the 7730 which is a pretty awesome ECM for what it is. I was playing with OBD2 quite a bit before I decided to swap to MS3. the V6 PCM's had too many limitations compared to the MS3 which is virtually limitless.

The other problem with the V6 PCM is that it isn't fully mapped out like the V8 PCM's are, so changing some parameters may affect other stuff that you can't see.

all that being said, I'm all about anything that will allow fellow enthusiasts to tune their car better.

 

The only reason the V8 stuff has more mapped out is because people were willing to spend the time on it so others could benefit. When I approached the V6 community on a number of sites last winter the impression I got was that about half of them would be better suited trying to find ways to run 4 barrel carbs and an HEI distributor then mess with anything computer related and the other half believed that coil packs, spark plugs and some fat plug wires were all they needed to dial their car in. I was speaking Greek and pretty much no one under stood why they would need anything like this. The one's that had some understanding of what I was discussing sited there was no reason for this since they had DHP or HPT and I was wasting my time.

 

yeah, that about sums up 90%(95%?) of the Fiero community that I don't interact with anymore...

 

Howdy......I'm trying to download LS Droid on a phone with Android 10. When the app opens it says "The version of Android on your device is below the min version number"
Is there a fix for this yet?
Thanks!

 

It is not working on Android 10 at this time. I do not have anything with that version of Android and an Emulator has not been enough to get the issue resolved. I've been looking for a "cheap" prepay phone but the hardware requirements on 10 are pretty steep compared to older versions.