Page 2 of 2

PostPosted: Thu Sep 07, 2006 9:36 pm
by 4EVO2NV
Ill have my first crack at it after this weekend ill see how it goes!!! thanks!!!

PostPosted: Fri Sep 08, 2006 5:16 am
by Skidd
Just an FYI. The older OBD-I interface is not going to work yet. Some new info has been given to me, and I have a bit more work to do on that one. But.. I'll keep on it. be patient guys!

PostPosted: Mon Sep 11, 2006 3:20 am
by wetwilly
I upgraded to v0.4.2 and now get an error message immediately upon starting. Something like 'Cannot communicate on Comm 1'.

PostPosted: Mon Sep 11, 2006 5:33 am
by Skidd
Here is a few things to check for that "comm 1" error.

1. JDash isn't yet capable of looking up the available comm ports on your machine, so it's very important you spell it exactly correctly. On windows it should be "com1" or "com2" or "com4" or "com5", etc.
2. Make sure that "com1" is the correct port for your OBD cable. Are you using a Tactrix OpenPort USB Cable? Because they usually connect to "com5"
3. If the above still causes a failure, please try to start JDash from a command window. When it fails, it should produce some error output. Please post that output here, or email it to me directly at "sgspowell-jdash@yahoo.com".

Thanx.