PCMSCAN Release Beta

[BrianP]

Well, I finally feel like PCMSCAN is ready for beta. This is just the very first beta for this release. Over the next few weeks I hope to make several updates and upload new versions until all the features are working and all the bugs are fixed.

Things in this beta:
- Over 160 generic OBD-II parameters are now available.
- Over 12,000 DTC descriptions are now available from various manufacturers.
- There is a completely new data logging engine that supports per-PID time stamping and should perform faster.
- There is a new log file format (to go along with the new logging engine and time stamps). It saves files quicker and more efficiently.
- The PID time stamps can be exported through the log fie export dialog.
- Fixed numerous bugs (gauge type can be changed, mobydic connection issues fixed, etc., etc., etc.,).

Things not (yet) available in this beta:
- The aux input PIDs are not working yet with the new logging engine. I will work on them next, as well add support for the additional wideband sensors, etc.
- The OBD-II terminal is temporarily disabled.
- I'm sure there are other things, but I can't think of anything else right now. (I'm going to go get some sleep after I finish typing this...)


For those of you that want the beta, please post in this thread or PM me. I will only be giving it out to a select few individuals (probably 10 or less) for beta. Once all the features are tested and working it will be released to everyone (at no cost). I'll be expecting the beta testers to provide lots of feedback and to try out all the features of the software to make sure there are no regressions. I would also like to see data logging speed comparisons using the old and new versions (with the same number of PIDs selected) to make sure the new version isn't horribly slow.

Let the beta requests flow....

-Brian

[ChrisH]

Do we have to uninstall the old version before installing the new one?  If not, will the old one still be present and operating after installing the new beta version?

[BrianP]

That's a good question. And the answer is that the new version will uninstall and/or upgrade the old version to be the latest. Normally this would be the desired behavior, but in this case I guess it's not. However, you can always just make a backup copy of your C:\Program Files\PCMSCAN directory and run pcmscan.exe directly.

[BrianP]

Just cleaned up this thread a little bit.

I have just uploaded a new beta. It should fix some of the bugs reported so far (error 10 bugs). All beta testers, please download it and give it a try.

[BrianP]

I have just posted a new beta release that should fix some of the reported issues. If you're a beta tester, please download it and try it out and let me know if you are still seeing any problems.

[pcmedics_of_So_Tx]

Brian,

  Any update to the latest Beta release? Have there been other problems reported with the beta?

Rei

[BrianP]

  Any update to the latest Beta release? Have there been other problems reported with the beta?

Sorry for the lack of updates last week, but I was out of town for a few days. There have been some problems reported and I have fixed some of them. Now that I am back I will resume work on the remaining issues and post a new beta.

[dslrip32]

software still does not pick up the multiple ecu's as the previous version. on 2002 pontiac grand am

[dslrip32]

and it doesnt pick up the pid scan at all like the previous non beta version

[dslrip32]

do you want me to send you another tech log on 9?

[BrianP]

do you want me to send you another tech log on 9?

Yes, please. Send it to support@palmerperformance.com.

Also, what do you mean it doesn't pick up the PID scan at all?

[BrianP]

I'm getting ready to release another beta update. Can everyone please send me a list of unfixed beta issues to support@palmerperformance.com (and techlogs if you have any). I want to make sure I've addressed all the problems. Also, if anyone has had a chance to do any speed comparisons against the old version, I would like to hear about it. Once all the outstanding beta issues are fixed, I will add back in the aux input PID's and start work on the new aux input PID's. Thanks to everyone who has helped so far!

[dslrip32]

I'm getting ready to release another beta update. Can everyone please send me a list of unfixed beta issues to support@palmerperformance.com (and techlogs if you have any). I want to make sure I've addressed all the problems. Also, if anyone has had a chance to do any speed comparisons against the old version, I would like to hear about it. Once all the outstanding beta issues are fixed, I will add back in the aux input PID's and start work on the new aux input PID's. Thanks to everyone who has helped so far!

When it is doing the pid scan, it doesnt pick up any at all.. So far this version is still functioning like the previous one i used. only thing it will do on this vehicle is scan for trouble codes and clear them.. i will try to get another tech log on level 9 for you this evening.

[BrianP]

When it is doing the pid scan, it doesnt pick up any at all.. So far this version is still functioning like the previous one i used. only thing it will do on this vehicle is scan for trouble codes and clear them.. i will try to get another tech log on level 9 for you this evening.

Weren't you having some connection issues using the mobydic on the old version? Are you still having any of those connection issues with this new beta?

[dslrip32]

well yes, i think the connection issues were the communication to the onboard multi ecu's and the pid scan. it is still doing that with this version. the only thing i can do with this version which is the same as the last version is read trouble codes only, and clear them if they are found. it wont monitor any sensors, pid etc. do you think it may be because of that license issue? I uninstalled the old version and installed this version and it is still trying to apply that fake liscense. How can i get rid of it?

[dslrip32]

i just sent you the tech log

[bengteck]

will you be releasing a ppc version?

my current sw seems slow when booting up after i use the saved config file
talking more than one min boot up normal?

where can i download the beta?

BT

[BrianP]

will you be releasing a ppc version?

Not anytime in the near future, sorry.

my current sw seems slow when booting up after i use the saved config file
talking more than one min boot up normal?

This does seem excessivly long. How fast is your computer?

[bengteck]

i'm using HP omnibook 900 P3, 64mb ram winXP pro
before i use the config file it was lot more faster

[pcmedics_of_So_Tx]

Bengteck,

  The 900 P3 seems to be ok, but the 64MB is what is killing the moment.  Try adding some more memory to your system, if anything, try to max out to what your comp can handle.

Rei

pcmedicsofsouthtexas.com

[BrianP]

i'm using HP omnibook 900 P3, 64mb ram winXP pro
before i use the config file it was lot more faster

Try out the new beta version, it should improve the load times a bit. Let me know if it does.

[BrianP]

I have just uploaded a new beta version. All existing beta testers can download it from the same URL as last time.

This new release fixes all reported bugs except for the freeze frame data, which is still not working yet. However, the OBD-II terminal is back online.

[bengteck]

I've identified the problem for the slow startup:-
PID config selection causes the slow, currently mine at 90sec whereas no PID selected boot at 10secs.
I’ve downloaded the beta and running it but still the same slow speed with 46 PIDs selected.
My notebook should read ass 128 RAM start at 60secs (without OBD connected) and my table top P4 512RAM only at 20sec (46PIDs). That’s the best I can get?

I tested three versions on my Desktop PC 90PID selected (without connection to OBD)
V1.01.20 which was super fast that I lost count (with lesser PID selected)
V1.4.3 registered at 12sec (90 PID selected)
V1.4.91 comes in 35secs (90 PID selected)

Wonder why we cannot keep the old version as multi selection in our PC?

[BrianP]

I've identified the problem for the slow startup:-

Nice catch!

This is definitely the cause of a lot of the loading problems, especially with more PID's. I have fixed this and it will be available with the next beta.

[hornerm]

Bengteck,

  The 900 P3 seems to be ok, but the 64MB is what is killing the moment.  Try adding some more memory to your system, if anything, try to max out to what your comp can handle.

Rei

Bengteck

Ram chip may be little harder to find for notebook.  Try at local computer repair shop. They might have some old chip for notebook. Look for 128 ram. You will have to replace, not add on like desktop. If you have manual book for you notebook, look for kind of chip to fit inside. If you can remove the ram chip, take it out and take with you along the manual book to repair shop. Ask for old 128 ram chip (cheaper). Some regular computer store charge high price.

Try to get 256 chip.

Ebay is good place to look but make sure the chip fit. Chip for desktop will not fit in notebook.

Good luck

Microsoft XP need higher ram.  Did you upgrade to XP?

[SportCompact.biz - Kris]

I'm downloading the new version as I write this, I'll give it a whirl and let you know how I progress!

Cheers,
Kris

[bengteck]

hi hornerm,
thanks for your input, yes you're right i've upgraded the OS from Win98
XP required min 256 to run properly but I'm able to endure the problem as this ram are SUPER X here and diff to find
Singapore IT seem lot more advance than US as older stuff disappear fast

hi brianP,
I've not tested your latest beta but this is what i found out for .91
- This new version is not backward compatible as old log cannot be replay in this version.
- Playback of log file seems freeze.
- The status window showing the config file that initially loaded and pop on the screen seems to stay there but after shut down and restart the software never happen again.

initial test on .93 (dry run)
- same not backway compatible
- playback freeze - solved
- status window never disappear
- notebook need 75sec to load - worse

btw how to use OBD-II terminal, must i connect to veh to check the box?

[BrianP]

I have just uploaded beta v1.4.94. It includes the load time speed fix as well as full support for freeze frame values. Please test the freeze frame values against the old 1.4.3 version and make sure it is reporting the correct data.

[hornerm]

bengteck

Having 64 ram is kindly slow for Window XP.

Window XP trying to load the resort but all that background of running the XP getting full. That why loading the PCMSCAN take longer to load since it need diskswap with Window XP to shift the resort around the memory system. You problemly don't have any ram left on your notebook.

Try find the 256 ram chip for your notebook. This will help alot.

Ray

p.s. Try remove some task program that show on the bottom right hand side. Sample: Zip, PrintSceen, anti-virus, etc. Also try turn the anti-virus off. This will free some memory. Good luck

[bengteck]

brian
i believe i found a bug in the program, the rpm reading can reverse beyond my car max 7500rpm
i see the rpm goes beyond 17000revs, waah....

ray
i did say mine 128ram, its still workable
loading abit slow but not a concern as this is temp test pc
i'll later install a p3 vdc car pc with touch screen with 512ram
thanks for your input

[BrianP]

i believe i found a bug in the program, the rpm reading can reverse beyond my car max 7500rpm
i see the rpm goes beyond 17000revs, waah....

I'm pretty sure this was fixed in v1.4.91 or v1.4.92. I uploaded a new beta version last night. Can you download it and see if this is still a problem? If it is, can you send me a techlog on level 9?

[hornerm]

bengteck

128 ram should be ok since PCMSCAN do not need large ram. My laptop is window 98 and I don't remember what ram I have. But running PCMSCAM software is super on my laptop.

I will be testing the update beta soon, (hope this weekend). I will not be able to at night since the heat wave will travel over the state of VA this week.

Tonight project: get 'crossover cable' to connect between my old laptop (window 98 with PCMSCAN) to other laptop (window XP with PCMSCAN). My ideal to see if PCMSCAM on car side (using serial cable) and run on newer laptop (with crossover cable) somewhere else. Example: leave scantool and old laptop in car and run crossover cable to house and attacth to other laptop. And run everything in house. If work, next plan is wireless. I like to run PCMSCAN from inside of cool house instead in hot car. Note: crossover cable is cheaper than serial cable by foot. Hope it work.

[dslrip32]

""Tonight project: get 'crossover cable' to connect between my old laptop (window 98 with PCMSCAN) to other laptop (window XP with PCMSCAN). My ideal to see if PCMSCAM on car side (using serial cable) and run on newer laptop (with crossover cable) somewhere else. Example: leave scantool and old laptop in car and run crossover cable to house and attacth to other laptop. And run everything in house. If work, next plan is wireless. I like to run PCMSCAN from inside of cool house instead in hot car. Note: crossover cable is cheaper than serial cable by foot. Hope it work.""


I like that project! Let me know if it works out for you...

[BrianP]

I've uploaded yet another beta version (v1.4.95). All of the old aux input PID's have been added back in now, bringing the PID total to 183 PID's so far.

I have also implemented a new indicator feature on the data view panel. PCMSCAN will now update the PID values on the data view panel as soon as each PID's data is available, instead of waiting until the full frame of data is available before updating them all. PCMSCAN - bringing you closer to real time, all the time.

BTW - I'm not hearing too much from the beta testers anymore. How are things going?

[bengteck]

I'm pretty sure this was fixed in v1.4.91 or v1.4.92. I uploaded a new beta version last night. Can you download it and see if this is still a problem? If it is, can you send me a techlog on level 9?

i check the version and confirm its 1.4.93 but the pop out screen still show as 1.4.91
incl the HELP - ABOUT

[bengteck]

Tonight project: get 'crossover cable' to connect between my old laptop (window 98 with PCMSCAN) to other laptop (window XP with PCMSCAN). My ideal to see if PCMSCAM on car side (using serial cable) and run on newer laptop (with crossover cable) somewhere else. Example: leave scantool and old laptop in car and run crossover cable to house and attacth to other laptop. And run everything in house. If work, next plan is wireless. I like to run PCMSCAN from inside of cool house instead in hot car. Note: crossover cable is cheaper than serial cable by foot. Hope it work.

ray
why not try using BlueTooth - can get you 10meters from your car (sometimes more)
i'm using AIRCable Serial now to my tester notebook (wireless)
i always hide in aircondition Mcdonald if need to do some testing without staying in the car via BT

[hornerm]

bengteck

My old laptop do not have wireless system. I do have network PCM card. Other laptop do have built-in wireless and network port. I do not have wireless system.

I have hear many time about BlueTooth. Do I have to buy the hardware and software to run the wireless and/or BlueTooth? What is the total cost to install.  My 'crossover cable' for 10ft for only $5.99 (same for 25ft)(it on special local sale at Radio Shack).

p.s. could not work on last night due to hot weather. I may have to wait this weekend to be cooler. Sorry.

BrianP: Due to low count of testing beta software is because of hot weather around the USA for last two weeks . Maybe very soon will pickup

[rat]

BrianP: Due to low count of testing beta software is because of hot weather around the USA for last two weeks . Maybe very soon will pickup

My laptop can't take the heat in the car without a/c here in MI, it should cool down tomorrow though.

[bengteck]

hi ray

there are fewe types of bluetooth USB adaptor around that pluf direct to your notebook
over here it cost only S$35 from mist electronic hardware store - abt US20+ www.aircable.net/serial.html
USB serial cost US69 each but the use is limitless compare to the cumbersome cables
i've abandon cable for long time, most of my devices work on BT now, even updating of moblie phone address
BT will auto install for my WinXP but not sure it must setup for lower OS, meaning hw only

btw cannot compare technology cost over the ancient setup
that way why buy a OBD2 scanner?
i buy it to work for me not me work for it

over here even under hot sun we can park our car in public multi storey car park
 

Brian,

i did activate the log but -oops - forget to save them as drving halfway bat low
see pic
 

[BrianP]

Brian,

i did activate the log but -oops - forget to save them as drving halfway bat low
see pic

Very interesting. A techlog would definitely help. Turn the debug level to 9 and enable debug tracing. I'd prefer a smaller techlog as opposed to a larger one. They are easier to read if they still exhibit the problem.

Is anyone else seeing this problem?

[pcmedics_of_So_Tx]

Brian,

  This is one of the problems i've been having since the first beta.  Still having with this problem with the newest beta version (D).

Will work on other tech logs tonight.

Rei

www.pcmedicsofsouthtexas.com[/glow]]www.pcmedicsofsouthtexas.com

[bengteck]

I've two for you
one small one big

funny i get this problem after install V1.4.93 but was fine at V1.4.91
now i cannot even revert back to normal again even uninstall everything and install V1.4.93 or 95

btw the beta .95 load up fast now c/w FOC RPM problem
win some lost some

[BrianP]

Ok, got it fixed this time! I've uploaded a new beta (v1.4.96), which includes preliminary LC-1 support.

I've decided to make this a public beta now. Anyone can download the beta version from here: http://www.palmerperformance.com/download/pcmscan_beta.exe

Please let me know if anyone finds any problems, etc.

[BrianP]

I have just added AEM wide band support to PCMSCAN. Please download beta v1.4.97 and try it out. I had to make some assumptions about the AEM protocol since it's not very well documented. So I would appreciate it if anyone can send me a techlog (on level 9) with some data logging from their AEM unit in it.

[rat]

I have just added AEM wide band support to PCMSCAN. Please download beta v1.4.97 and try it out. I had to make some assumptions about the AEM protocol since it's not very well documented. So I would appreciate it if anyone can send me a techlog (on level 9) with some data logging from their AEM unit in it.

Awsome, Didn't work, but here is a log, and a tech log:

[bengteck]

same here, DON"T work
every beta getting from bad to worse

this .96 cannot activate the rec or minotor mode
and therefore not data can be seen on the meters

[BrianP]

Awsome, Didn't work, but here is a log, and a tech log:

It looks like the baud rate is wrong. I have set it to use 9600 baud. What is your AEM UEGO model number?

[BrianP]

same here, DON"T work
every beta getting from bad to worse

I really doubt that the beta's are going from bad to worse. All of the issues are getting resolved. In fact, every outstanding bug has been fixed, I'm just working on more feature enhancements now (wide band stuff). What is still not working?

this .96 cannot activate the rec or minotor mode
and therefore not data can be seen on the meters

I looked at this techlog. You need to validate the parameters before you can use the data logging. That is the reason why you cannot start the logging.

BTW - do you own an LM-1 or AEM wide band meter?

[rat]

Awsome, Didn't work, but here is a log, and a tech log:

It looks like the baud rate is wrong. I have set it to use 9600 baud. What is your AEM UEGO model number?

I think this is the p/n: 30-4111

The 9600 baud rate is correct when i use hyperterminal.  It might be the serial adapter i am using for it.  I know the serial adaper(keyspan) doesn't like to connect to the obd2, for logging the obd2 i use a belkin adapter.  I will have to give my pcmcia adapter a try.

[mecanicus]

Hello,
i scanned my alfa 156 twin spark model 4.2004 with your last official version and the beta version.
-no vehicle info in both versions
- no lambda in both versions
- 19  pids in official version recogniced
- 52  pids in beta version
but a lot of these pids deliver nothing

is there any a way to fill out the description  for the recogniced pids  or is it possible to write my own list of pids with the approbriate description and attach it to the beta?
Nice tool up to now :-)

mecanicus

[PantsOn]

I agree with you

VIN is mimimum request!

This should be done.

[BrianP]

Awsome, Didn't work, but here is a log, and a tech log:

It looks like the baud rate is wrong. I have set it to use 9600 baud. What is your AEM UEGO model number?

I think this is the p/n: 30-4111

The 9600 baud rate is correct when i use hyperterminal.  It might be the serial adapter i am using for it.  I know the serial adaper(keyspan) doesn't like to connect to the obd2, for logging the obd2 i use a belkin adapter.  I will have to give my pcmcia adapter a try.

Please give the other adapter a try and let me know what happens.

[BrianP]

Hello,
i scanned my alfa 156 twin spark model 4.2004 with your last official version and the beta version.
-no vehicle info in both versions
- no lambda in both versions
- 19  pids in official version recogniced
- 52  pids in beta version
but a lot of these pids deliver nothing

What do you mean when you say a lot of these PIDs deliver nothing?

PCMSCAN will only display the vehicle info that the vehicle will report. If your vehicle doesn't report any vehicle info, then PCMSCAN can't show it. If you'd like to send me a techlog, I'll take a look and see if any is going wrong.

is there any a way to fill out the description  for the recogniced pids  or is it possible to write my own list of pids with the approbriate description and attach it to the beta?
Nice tool up to now :-)

I'm not sure I understand what you're asking for here. What do you mean by fill out the description for the PIDs?

If you have a PID list that you'd like to see added to the beta, just send me a private message or an email and I'll see what I can do.

[furlongba]

Brian
The latest Beta does not appear to be password protected ?

[bengteck]

brian,
i remember clearly i did validate but suspect it was incomplete as it just close before the scan bar done
anyway i've reinstall and try again, it seem to work this time

but the RPM meter haywire once a while, observe it while i stop at traffic light but not in the highway
pls check the tech log as i close it immed after see the error, as it should be at the rear of the log
---latest update ---- i don't see it in the evening but will still monitor

-------------------------------------------------------------
last message removed as i'm mistaken on the nos of PIDs
its still 46 but appear in the center

[hornerm]

Brian
The latest Beta does not appear to be password protected ?

Last verison is release for everybody now. It is still on beta project. Therefore no password now.

Please post any problem and also send tech log to BrianP so he can take to look.

[Billdog350]

I need to attach some logs but the LC1 does not work on my beta.  I was able to view LC1 status with the program that they send with the LC1, but even when selecting the correct com ports and stuff, I didn't see any data in pcmscan.  I did select the LC1 pid that was validated (turned green) but it just wouldn't monitor or log.

We're getting closer!  Validating the pid means that pcmscan can see it....it just doesn't show it yet.

[BrianP]

brian,
i remember clearly i did validate but suspect it was incomplete as it just close before the scan bar done
anyway i've reinstall and try again, it seem to work this time

but the RPM meter haywire once a while, observe it while i stop at traffic light but not in the highway
pls check the tech log as i close it immed after see the error, as it should be at the rear of the log
---latest update ---- i don't see it in the evening but will still monitor

-------------------------------------------------------------
last message removed as i'm mistaken on the nos of PIDs
its still 46 but appear in the center

Thank you for this techlog. I see what the problem is now. It will take a bit of time to fix, but I'll have it fixed in the next beta release.

[BrianP]

I need to attach some logs but the LC1 does not work on my beta.  I was able to view LC1 status with the program that they send with the LC1, but even when selecting the correct com ports and stuff, I didn't see any data in pcmscan.  I did select the LC1 pid that was validated (turned green) but it just wouldn't monitor or log.

We're getting closer!  Validating the pid means that pcmscan can see it....it just doesn't show it yet.

Just send me a techlog, and I'll see what is going wrong. Please set the debug level to 9 and enable debug tracing.

[BrianP]

I have just uploaded a new beta version (v1.4.98). It contains fixes for the missing parameter names and bengteck's weird RPM value problem. Everyone please download this version and try it out.

This new beta does not contain any fixes for the aux input PID's (LC-1 & AEM) since I have not yet received any techlogs from anyone.

[Billdog350]

I'm gonna try to get home and get you a techlog for the LC1.....

[pcmedics_of_So_Tx]

Brian,

  I have not had any issues or problems with latest beta version, .98.  It is a bit faster in reading parameters.

Rei

www.pcmedicsofsouthtexas.com

[BrianP]

I'm gonna try to get home and get you a techlog for the LC1.....

Sounds good. As soon as I get this techlog I should be able to figure what's going wrong.

[Billdog350]

Ok, here you go.  I just logged this morning.  I let the LC1 warm up.  Checked it with the Log Works 2 program to verify that it is working, and then closed out log works completely. 

Opened up PCMSCAN, it detected the car and the LM1 (not LC1) and said we were good to go.

I turned on the pid for monitoring the LC1 as well as a few other normal pids like RPM.  It does the car fine, just no LC1.

[rat]

Awsome, Didn't work, but here is a log, and a tech log:

It looks like the baud rate is wrong. I have set it to use 9600 baud. What is your AEM UEGO model number?

I think this is the p/n: 30-4111

The 9600 baud rate is correct when i use hyperterminal.  It might be the serial adapter i am using for it.  I know the serial adaper(keyspan) doesn't like to connect to the obd2, for logging the obd2 i use a belkin adapter.  I will have to give my pcmcia adapter a try.

Please give the other adapter a try and let me know what happens.

Brian, Sorry for taking so long, but good news.  It works, and seems to work quite well.  Quick data recording, no dropped data like with the obd2 logging.  The problem was with the Keyspan Usb>Serial adapter i was using.  So, you can add that to the feature list.  If you need/want a datalog i could get one, but it may take a few days.

I do have an oddball request.  Would it be possible to have a feature to only log the aux input, and not the obd2?  I can do it now by starting it up, and unplugging the obd2 cord after it connects, but if there was a way to just log the wideband that would be handy.

[BrianP]

I have finished the initial TechEdge WBO2 support in PCMSCAN. I have just uploaded a new beta version that includes it. You can download it from: http://www.palmerperformance.com/pcmscan_beta.exe

[BrianP]

Brian, Sorry for taking so long, but good news.  It works, and seems to work quite well.  Quick data recording, no dropped data like with the obd2 logging.  The problem was with the Keyspan Usb>Serial adapter i was using.  So, you can add that to the feature list.  If you need/want a datalog i could get one, but it may take a few days.

I'm glad to hear that it's working! I would *definitely* want a techlog (on level 9) just so I can verify that the code is doing what it's supposed to do (even if it looks that way on the outside).

I'm not seeing what you describe as "dropped data like with the obd2 logging". Is anyone else seeing this? Can someone get me a techlog or something so I can look at the problem?

I do have an oddball request.  Would it be possible to have a feature to only log the aux input, and not the obd2?  I can do it now by starting it up, and unplugging the obd2 cord after it connects, but if there was a way to just log the wideband that would be handy.

The whole program has been designed around the concept of OBD-II data logging. To be able to connect to a device, without an OBD-II connection active, will take quite a bit of work. I'll just have to give this some thought and see if I can find a good way to make it all work. But right now, with all the other stuff that is being worked on, I'd say that this could take a while.

[BrianP]

Ok, here you go.  I just logged this morning.  I let the LC1 warm up.  Checked it with the Log Works 2 program to verify that it is working, and then closed out log works completely. 

Opened up PCMSCAN, it detected the car and the LM1 (not LC1) and said we were good to go.

I turned on the pid for monitoring the LC1 as well as a few other normal pids like RPM.  It does the car fine, just no LC1.

Please try the LC-1 stuff again with the latest beta version. I have fixed a bug in it. Let me know if it's working or not, and please get me a techlog (on level 9) also.

[rat]

The whole program has been designed around the concept of OBD-II data logging. To be able to connect to a device, without an OBD-II connection active, will take quite a bit of work. I'll just have to give this some thought and see if I can find a good way to make it all work. But right now, with all the other stuff that is being worked on, I'd say that this could take a while.

Don't worry about it then.  Deffinately not a big deal, and i don't see a lot of users needing anything like that.

I will try to take a techlog in the next couple days, i have the vehicle all torn apart right now for an intake manfiold swap.

[bengteck]

with the release of .99 we've back to bad old days
notice few weird problems at RPM, IAT & ECT

i've ever notice ECT showing -40C at ver 1.4.3 but not at the higher ver till .99
now also notice at IAT
and RPM weird reading back with 0 RPM when stop the car (which is not possible)

[pcmedics_of_So_Tx]

Brian,

  These are the same problems I'm having.  RPM, IAT, and ECT are wacking out and sometimes displaying zero.

Rei

PC MEDICS OF SOUTH TEXAS

[BrianP]

I have figured out the cause of this problem, and fixed the bug. I have uploaded a new beta version (v1.4.100) that contains the fix. You can get it from http://www.palmerperformance.com/download/pcmscan_beta.exe

Also in this version I have optimized the logging even more. It should provide improved logging speed, depending on the PIDs you have selected for logging. It also provides speed improvements with vehicles that have more than one OBD-II compliant ECU in them.

Please let me know how it works (feedback please)!

[Billdog350]

Ok, here you go.  I just logged this morning.  I let the LC1 warm up.  Checked it with the Log Works 2 program to verify that it is working, and then closed out log works completely. 

Opened up PCMSCAN, it detected the car and the LM1 (not LC1) and said we were good to go.

I turned on the pid for monitoring the LC1 as well as a few other normal pids like RPM.  It does the car fine, just no LC1.

Please try the LC-1 stuff again with the latest beta version. I have fixed a bug in it. Let me know if it's working or not, and please get me a techlog (on level 9) also.

Thanks, I've been on vacation and out of town for the past week so I was unable to respond by testing the newest version.  I'll be testing it today and I'll get back to you with a techlog if it doesn't work on my LC1.

[BrianP]

Thanks, I've been on vacation and out of town for the past week so I was unable to respond by testing the newest version.  I'll be testing it today and I'll get back to you with a techlog if it doesn't work on my LC1.

Even if it does work, please send me a small techlog (on level 9, with debug tracing enabled), if you can.

[bengteck]

brian,
sorry to report another fault discovered on the .100
now the negative value bug goes to SAE.SPARKADV, happen when stationary

forget to save the log.

just notice that my earlier pic post also show the same fault, maybe u can use the same log

[BrianP]

Bengteck, I have looked over that techlog and examined the responses that your vehicle is giving back. Everything is working correctly. Your vehicle is reporting -2 degrees of spark advance. Perhaps you were getting a knock condition?

[bengteck]

brian your guess might be right

but i browse thru my old records and found the scan for another 3 cars(same brand and model), two of them show the same problem like mine
including my old records for other releases, some of them do show the neg value

comments?


==================

updates

attached log, notice problem surfaced when idle

[rat]

Brian, Sorry for taking so long, but good news.  It works, and seems to work quite well.  Quick data recording, no dropped data like with the obd2 logging.  The problem was with the Keyspan Usb>Serial adapter i was using.  So, you can add that to the feature list.  If you need/want a datalog i could get one, but it may take a few days.

I'm glad to hear that it's working! I would *definitely* want a techlog (on level 9) just so I can verify that the code is doing what it's supposed to do (even if it looks that way on the outside).

I'm not seeing what you describe as "dropped data like with the obd2 logging". Is anyone else seeing this? Can someone get me a techlog or something so I can look at the problem?

Sorry for taking so long.

Within the last couple updates the "dropped" data problem seems to have been resolved.  Here are the logs with the aem activated.

[BrianP]

Sorry for taking so long.

Within the last couple updates the "dropped" data problem seems to have been resolved.  Here are the logs with the aem activated.

Excellent! Everything looks good.

[linolentino]

Hi Brian
i have tested beta v 100 on smart fortwo and i have look that O2. voltage sensor monitor value is wrong.
It show more tyhan 1 volt. I have reinstalled the 1.4.3 version ant it works ok, all value are under 1 volt.
When i have time i will do a log with beta 100.

REgards

[BrianP]

Hi Brian
i have tested beta v 100 on smart fortwo and i have look that O2. voltage sensor monitor value is wrong.
It show more tyhan 1 volt. I have reinstalled the 1.4.3 version ant it works ok, all value are under 1 volt.
When i have time i will do a log with beta 100.

REgards

Ok, get me a techlog (on level 9, debug tracing enabled) and I'll see if I can figure out what is going wrong.

[BrianP]

I have found the problem with the O2 sensor voltages, and it is fixed now.

The beta testing phase is now over. Thanks to everyone who helped!

You can download PCMSCAN v1.5.0 using the normal link on our website.