FAQs | Troubleshoot - Need help? Ask questions here.

[2009Prius]

FAQs | Troubleshoot - Need help? Ask questions here. (Visit the main thread and project home page if you haven't.)

1. List of gauges and description.
2. Does it work with gen 3? Short answer:not yet. Long answer here.
3. How to set baud rate of OBD device?
4. XWin Server does not start?
5. Segmentation fault?

[usbseawolf2000]

I installed Cygwin with the components specified. When I started the Xwin Server, nothing appears, no error.

I can run Cygwin Bash Shell. Any idea why the Xwin Server didn't run for me? I have Windows XP.

[2009Prius]

That's strange. I have an XP laptop and it runs OK. Usually it will open up an X-window on the desktop and also start a tray icon in the lower right corner of the task bar where the clock is (I forgot the official name of that area). Sometimes it does not open up the X-window, but the tray icon has always been showing up for me. In that case I could right click the tray icon - Applications - xterm to open an X-window or I could right click the tray icon - Exit... to quit and restart the whole thing from the Start menu.

First, make sure the cygwin has been installed with the components listed here or here. The setup program will select additional dependent components. Keep those selected as well.

Could you take a look

1. in the tray icon area to see if the tray icon is there?
2. in the task manager to see if XWin.exe and/or xterm.exe is running?

If so then quit and/or terminate them and try starting from the Start menu again.

For XP you could also download and install "Process Explorer" from Microsoft (part of "power toys") which may give more system diagnostic info.

Update: I googled and found some possible solutions:
Cygwin/X Frequently Asked Questions

2.4. Nothing appears to happen when I try to start the X server using the "XWin Server" start menu shortcut.

A1:
Task manager shows the startxwin.exe process starting, spawning XWin.exe and xterm.exe, but no windows are shown. Running startxwin.exe from a bash shell works correctly. This is caused by having tty in the CYGWIN environment variable set through the Windows control panel. Removing tty resolves this issue.
If you really need CYGWIN=tty for working with cmd.exe windows, you'll have to arrange to set that by some other means before invoking cygwin.bat.

A2:
Try running startxwin.exe from a bash shell, it should output some error message which should indicate why it's not able to start.

[spiderman]

I assume but thought I would check that program would be compatible with the GenIII.?

[2009Prius]

Originally Posted by spiderman

I assume but thought I would check that program would be compatible with the GenIII.?

Sorry the software is written for gen 2 so if you run it with gen 3 then all of the "interesting" gauges such as HV current and inverter temps won't work - only standard "uninteresting" OBD queries would and there are very few of them implemented. Toyota has changed the CAN messaging between gen 2 and gen 3, plus I have no access to gen 3 car, so I won't be able to help, at least not in the near future. Hopefully someone with the time and knowledge will modify the code and make a version for gen 3.

[usbseawolf2000]

Ok, I got it to run. Initially, I did not include the Default selections because I thought I only need to install the components you listed. I re-installed it by keeping the Default selections and included additional components. That did it.

[usbseawolf2000]

I hit the GO button and the program started. The clock started to tick but no information was populated (other than MPG showing 999.99). After awhile, the program stopped with "Segmentation fault (core dumped)" message in xterm.

This is the content in the priidash.exe.stackdump file:

PHP Code:

Exception: STATUS_ACCESS_VIOLATION at eip=6D2628A5
eax=1933CD18 ebx=00000000 ecx=00000034 edx=1933CD18 esi=1933C398 edi=1933CD18
ebp=1932BC98 esp=1932BC80 program=C:priidashbinpriidash.exe, pid 2124, thread unknown (0xF7C)
cs=001B ds=0023 es=0023 fs=003B gs=0000 ss=0023
Stack trace:
Frame     Function  Args
1932BC98  6D2628A5  (00000000, 1933CD18, 00000013, 1933CD18)
1932BCB8  6D262A48  (00000000, 1933CD18, 00000013, 4E08BE08)
1932BCD8  6D262A9B  (00000000, 1933CD18, 004B0364, 0041A990)
1933CD48  00403202  (004FC318, 004FC318, 00000000, 00000000)
1933CD78  63CC1BF7  (004FC318, 00000000, 00000000, 00000000)
1933CDB8  610E7455  (004E8B80, 1933CDF4, 610E73A0, 004E8B80)
End of stack trace 


I was so close. Maybe OBDLink SX does not function exactly the same as the original OBDLink?

I have confirmed my OBDLink SX works by using the supplied OBDWiz software.

[2009Prius]

Was there any other error message showing in the X window where PriiDash was running from? If so please post.
Did you set up the port number, directories and files as outlined here or here?
Could you zip and attach the log file "f:\OBDLog\logyyyymmdd_hhmmss.txt" which should have been generated?
It's also a good idea to use a cmd.exe window to do a "chkdsk f:" after a segmentation fault. Just to be safe.

[usbseawolf2000]

Yup, I made it COM7, created ODO.txt and the OBDLog folder was created on my F drive.

I am attaching two .txt files. The bigger one was the one that caused the segmentation fault.

In the instruction, you said "Connect the hardware and set the baud rate to 2M bps." Where do I do that? The property of the com port advanced setting only goes up to just under 1 Mbps.

BTW, windows chkdsk found no issue with my F:.

[2009Prius]

Yes if the baud rate is not right then the program can not communicate with the OBD device as is in your case (shown in the log files).

To set the baud rate: Use any terminal program to connect to the virtual serial port. For example I use "STN term" which can be downloaded from here. Talk to the OBD device using its current baud rate. To set the baud rate to 2M bps, issue the following commands and make sure each one comes back with an "OK":

ATPP 0C SV 02
ATPP 0C ON

These set the frequency divider to 2 (base frequency is 4M) and turn it on. Now reset the device by issuing

ATZ

Now the connection should be lost since the baud rate is changed. Change the terminal program's baud rate to 2M to re-establish connection. Issue

ATPPS

to see that the value 0C is set to 02 and turned on. Now you can quit the terminal program and run PriiDash(TM).

Hope this helps.