Getting avt852 box working with dhp

Got powershell working. which i have no idea what that was before tonight. Lol Now I think i have to change my baud rates way down through my device manager in my control panel. I have to read up some more on what i have to enter in command prompt to get the avt synced. This may take a minute. As I said I have no idea what im doing. It be great if someone were to be like yea you're on the right track. haha all good though. Thanks too Scott. I just thought I was doing something wrong, but it seemed like I downloaded and redownloaded everything 5 plus times.

To be able to issue Serial commands, you must first enter PowerShell. Type powershell to get into PowerShell command mode.

https://cdn.sparkfun.com/assets/b/7/...2b568b4568.jpg

To see a list of all the available COM ports, type
[System.IO.Ports.SerialPort]::getportnames()
You should now see something like this..

https://cdn.sparkfun.com/assets/2/9/...ce2a8b456a.jpg

Now create an instance of the port you want with this command
$port= new-Object System.IO.Ports.SerialPort COM#,Baudrate,None,8,one
With that, you can now connect to and send data to or from that COM port.
$port.open()
$port.WriteLine("some string")
$port.ReadLine()
$port.Close()
Again, this method of serial communication is only recommended for advanced command line users.



So I was going to try this and put that string of 52 89 01 in the "some string" spot on this example. I am going to wait until tomorrow to see if anyone chimes in. Im not expert on command prompt. Im not sure if i have to turn my baud rates to zero in the driver manager or what before I even do this. Actually i think 9600 is lowest it will go or something. Also im not sure if i would have to just send 52 89 just to get it to recognize it or I dont know. Yea Im definitely waiting...

Let's start over, we're going in a weird direction here...

What issue are you getting with DHP? What error, specifically?

The updates mentioned in a prior post are related to the LIN protocol and not applicable to what we're doing here.

read the first page. pretty black and white.

It's not helping me to understand why it couldn't install. Did it fail? Was there an exception thrown?

May be I'm just having an off night for reading comprehension, but I don't know how we got into using PowerShell or why.

it wont register, he just bought it, so it might be missing something so it will register.

Prd2010, why don't you download the AVT Hex Terminal software and see if you can talk to the box that way? If it connects with Hex Terminal then you know the COM port is configured correctly and your computer can talk to it.

If you can talk to the AVT box, and everything else in DHP works (opening BINs, etc) except for cable registration, then it's related to whatever isn't being done by AVT now to make the boxes compatible with DHP.

Easiest place to start.

Ok i Have Hex terminal installed getting ready to run it.

ok now what do i do. my com port is opened and initialized it says. now i can send commands, or script files, or open some and other things that i dont know what they do.

maybe i need to send that command now in the command window. yes good call. I dont know if i should just do thta or not. but i get up at 430 am to work so i may have to proceed at a later time.

Once you select the COM port under "Configure Comms", the log should show "COM port initialized and opened." This indicates the port is open for communication.

You can then type "F1 A5" (without the quotes) and hit Send Command. This reboots the AVT box and it should spit out a response indicating that the reboot was successful. Don't send any other random commands to the 852 unless you know what they're doing.

If it does this, the communication with the PC is working.

http://superchargedv6.com/hexterm.png

another option would be to download UVScan from the repository and see if it will talk to the 852. It should be able to talk to the box, send commands to the PCM, and initiate a scan independently of the DHP software. At least then you'll know if the box and your OBD cables are functional, and you can get some scans while you're figuring out how to talk to the DHP box.

*configured

Quote:

---

Originally Posted by Prd2010

*configured

---

that mean its working now?

No i got the comport for sure working with the avt box in hex whatever. I will have to try the other stuff above tonight. At work now, and i have to throw some lateral links on my car after work.

I had sent another message and spelled configure wrong but apparently it didntt post

When you try to register the cable in DHP, does it just give you an error like it isn't connected at all?

It will try to read ( unless im on the wrong cpmport, then it does nothing) 75 percent of the loading bars way says unable to comunnicate. Then if i abort i can still run demo mode, load and look at bins. Just no editing.

i can tell you this, when its right it registers so fast you dont see that scroll bar at all. its a flash then says registration successful.

In that case, it really does sound like whatever response from the AVT box that PowrTuner is looking for is the issue.


I've been working to figure out exactly what occurs during the cable registration process. We know that all of the 852 boxes are (for the most part) hardware identical and the original 838 boxes that DHP shipped had some sort of custom flag to enable them to work. This was likely originally part of the credit system that DHP used.


As Mike (from AVT) stated in an email posted in another thread, someone reached out to him and asked for a box with changes (supplied by the purchaser) that would enable a standard AVT box to register successfully in PowrTuner. Someone out there knows how it works already.