I get the exact same error on my desk top. Not willing to chance loading it on my lap top yet...

Edited my earlier post on the conversion from WinTEC 3.5.6 to WinTEC 4.8.20.

Item 2 MAP/TPS acceleration enrichments - radio buttons changed, I reset them

Items 3.4.6 & 10 Found how to change row and colum tables, changed them back to where they were in 3.5.6.

Item 9 EGO / Wideband Calibration - Bin retains the earlier settings (they show on screen with values as before), but print out drops one voltage digit, screen has 3.

Item 12 Idle Control Sensitivity - Bin appears correct on screen but the print out reverses the values for Error Sensitivities (+ and - ).

First let me say that there was a great deal of time and energy put into ensuring this conversion happened properly. Several people spent several days making and converting many files to be certain everything converted as it should.

This a quite a list. I double checked everything here and this is what I found:



I'm not going to argue on this point other than to say this; The conversion IS more or less 1 to 1. The thing is that the MAP sensor is not read the same way it was before. To retain the PULSEWIDTH for a given MAP sensor voltage, modifications were needed to your TOG and IOT and subsequently every single pressure value in the existing program. This is why the table values are different, this is why the TOG and IOT are different. Look at the injector pulsewidth table under VE and compare that to the pulsewidth table under VE in WinTEC3. You will find that they are virtually identical.



You'd be surprised how rarely anyone is concerned by the table size. Richard Clewett had an issue with it. You'll note that unused rows and columns retain the same value as the last used row/column. This effectively cuts the table down to the size it previously was. There is not a way to make the table smaller than it is, other than this way. We don't tell our dealers how to bill. There are plenty of ways to 'run up the bill' other than blaming an over-large tuning table. As you can see, it's very easy to simply under-utilize the table as is.



I checked on all of these. I'm not really sure how you got 54.5 into ACE0, the highest available setting is 52.5. Assuming that is what you really had, this is the same as turning the TPS rate of change value off. In fact, in WinTEC3.2.1 and 3.5.6, the TPS radio button is set to OFF when 52.5 is typed into ACE0. ACE1 changed because of the MAP sensor changes. I was not able to replicate the other problems listed here.



See the notes above about the MAP sensor changes.



If sections 7 and 8 are new it's because WinTEC3 left them out of the printout. Those tables exist in WinTEC3 and as far as I can tell, convert properly.



I double checked these values and could not find any errors in the conversion here. The MAP sensor value is again changed due to the MAP sensor conversion.



This was actually a problem in the printout, I have fixed it for the next release.



Not really sure why you have this problem, it worked fine for me. Maybe you need to send me your BIN file so I can double check it?

TimZ and rb26powered74zcar:

Clearly the issue is that pre-Nissan Z.

ON a more serious note, fully uninstall and reinstall the software and see if it runs any better. I haven't have anyone else report that problem to me. Problems during startup are typically caused by a problem during installation.

Didn't help. I did have a lot of "your version is newer" prompts during the install, and I always opted to keep the existing file. This included the msjet40 dll and the dao360 dll among several others - I'm guessing that these were probably updated with service pack 3. Any idea what service pack your developer's build machine was on for the OS and for VB? XP SP3 and VB6 SP6 here.

Exact same scenario here guys....

Jon,

What are the benefits/improvements for a TECgt user in upgrading to the latest firmware/software?

Edit: 1 further question. My understanding is that the firmware and software versions should match, the firmware version bundled with software v4.8.20 download is WTL0205009.em3 - is this the right firmware? I expected to see something along the lines of WTL0208yyy.em3

Jon,

Thanks for your detailed review of my notes and your concern is appreciated.

My notes and your review did accomplish a display of what others might see after converting and should settle concerns, it has mine.

I will do another conversion of the same bin file and fix only the fan settings (I need the old settings because the electric fan is the only forced cooling there is, albeit the Tec3 is a backup to a hard wired switch located at the bottom radiator tank) and the warm up enrichmens/coolant table (which moved every value up one temperature bucket in the table).

If the VE/timing advance tables function as you said with the upper colums blank, no change there because I don't need more than 13 columns. I will revert to my preferred row scale as all my analysis spreadsheets are on that basis and I don't think the row scale change to the old values will change my tune (ref your comments about the MAP) to any great extent as it is a NA engine.

I will take you up on your offer and email the bin that is the subject of my notes for you use. (I did try to program the Tec3 last evening and it fails to program with a runtime error 11 (I believe), divide by zero.

Thanks,
JimK

When the "your version is newer" prompts come up, say No to All. I run XP SP1 on my developement machine, but I test installation on machines with SP2,3 and Vista. I have not had any problems with installation and operaion on any of those machines. Most problems stem from corruption or not replacing a database file required for WinTEC to operate. There was a work around added to the newer version that should have fixed that problem, but the results have been mixed. Allow all the files to be replaced and the software should work properly.

Benefits for TECgt:
Added a new Rev-limiter option: Revlimit approach retard, softens the landing at the revlimit
Fixed a problem with EGO correction when using blend
Improvements to Accerelation enrichments
Improvements to CAM syncing
A range of changes to WinTEC to improve usability but have no effect on the unit connected

Jon,

Thanks. I think I edited my post to include a question about the firmware version bundled with the download whilst you were writing this. Could you comment please?

Yes, but what else will that break? I don't really like the notion of having to back-date several .dll's to SP1 level. At all.

FWIW, and I know this is of no comfort to you, I have loaded v4.8.20 onto both a laptop and desktop running XP SP3 during the last 24 hours without any issues. I choose to keep the newer files on my machines during install.

That's good information to know - thanks!

Well I have just come up against a problem with uploading the new firmware (sort of brings me back to whether it is the correct version?). Tried 2 separate laptops, both found the TECgt, I then turned the TEC off and re-applied power to put it into upgrade mode (red light on). On trying to upload the new firmware both laptops just sat there doing nothing. Here's a snippet of the wintec log:
17:07:16 - Attempting Firmware Upgrade, Sending File...
17:07:16 - - C:\Program Files\WinTEC4\bin\WTL0205009.em3

That is as far as either laptop got. Progress bar just sat at 0%. Any ideas?

The latest firmware version for each unit included with every installation of WinTEC is detailed in the release notes for that version.

SlowMX5:
I have had that happen before. When that happens, don't turn the unit off or disconnect anything, just go back and select firmware upgrade again. The cause is some weird timing glitch that I haven't been able to isolate (it doesn't happen too often). But every time it's happened to me, the process is successful the second time it's selected.

TimZ:
Because WinTEC4 is written in VB6, pretty much all of the DLLs are kind of old anyway. I have told numerous people to do exactly that and there have not been any ill effects. If it really bothers you, watch the file names and keep the DLLs and OCXs. If any files come up that are not, allow the older file to replace the newer one.