First log with Logworks/Ecuflash
I'll try to figure this out myself, but when I try to run the OpenPort1.3 I get the error:
Run-time error 429:
ActiveX component can't create object
I think this is something to do with VB and certain dlls or something not being registered, but I figured I would ask if anyone knows without me having to figure this out.
Thanks,
Eric
Run-time error 429:
ActiveX component can't create object
I think this is something to do with VB and certain dlls or something not being registered, but I figured I would ask if anyone knows without me having to figure this out.
Thanks,
Eric
Hi,
The only objects that I can think of that are created dynamically are:
MathParser objects
MS DOM XML objects
Could you check your <Windows>\System32 directory and look for:
MTParserCOM.dll
MSXML2.dll
If both are present, you could try registering them and see if you get more specific error messages.
Sorry, I'm a little stumped on this one.
-jjf
The only objects that I can think of that are created dynamically are:
MathParser objects
MS DOM XML objects
Could you check your <Windows>\System32 directory and look for:
MTParserCOM.dll
MSXML2.dll
If both are present, you could try registering them and see if you get more specific error messages.
Sorry, I'm a little stumped on this one.
-jjf
This works!
jjf,
Thanks. This did the trick.
I have three PCs and I was having the problem on the two which I don't believe have XP SP2. I don't know if that is the culprit or not, but nonetheless, registering these two .dlls solved the problem.
Thanks,
Eric
P.S. For anyone that gets this error, what I mean by registering the .dlls is to open a command prompt, change directories to where the files are, such as \system32, then type:
regsvr32 mtparsercom.dll
then hit enter
do the same for the other file
Thanks. This did the trick.
I have three PCs and I was having the problem on the two which I don't believe have XP SP2. I don't know if that is the culprit or not, but nonetheless, registering these two .dlls solved the problem.
Thanks,
Eric
P.S. For anyone that gets this error, what I mean by registering the .dlls is to open a command prompt, change directories to where the files are, such as \system32, then type:
regsvr32 mtparsercom.dll
then hit enter
do the same for the other file
Last edited by l2r99gst; Dec 23, 2006 at 10:41 AM.
It isn't a big deal, I've already got Ghost images of the different versions/service packs. I just want to ring it out to make sure it isn't an installer issue.
Again, sorry you had problems.
-jjf
P.S. for NJ: I both sent and posted a fix for your half speed issue with LM-1. Based on raw log files I'd expect your power measurements for 3rd gear pulls to be quite close now.
It isn't a big deal, I've already got Ghost images of the different versions/service packs. I just want to ring it out to make sure it isn't an installer issue.
Again, sorry you had problems.
-jjf
P.S. for NJ: I both sent and posted a fix for your half speed issue with LM-1. Based on raw log files I'd expect your power measurements for 3rd gear pulls to be quite close now.
Again, sorry you had problems.
-jjf
P.S. for NJ: I both sent and posted a fix for your half speed issue with LM-1. Based on raw log files I'd expect your power measurements for 3rd gear pulls to be quite close now.
Yeah, you can restore your Ghost images to VMWare, I do that pretty regularly as I have different images of machines that go back to really early versions.
VMWare server works alot better, the only issue I've had was with the newest version of Ghost (the service) in windows XP, but only with a hard drive plugged in to the USB passthrough, and its really just a USB issue.
Oh, and the Tactrix cable works fine through VMWare on a linux host, running winxp as a guest.
VMWare server works alot better, the only issue I've had was with the newest version of Ghost (the service) in windows XP, but only with a hard drive plugged in to the USB passthrough, and its really just a USB issue.
Oh, and the Tactrix cable works fine through VMWare on a linux host, running winxp as a guest.
For the forum, Joe (if I may call him by his first name) sent me the the file @ 10:33 pm. He was working that late on a holiday evening. I am VERY VERY TOUCHED and IMPRESSED.
Just to bring some closure to this one -
A number of folks have emailed me asking about the results they have gotten from my simple power formula posted in this thread. In particular, difference between the results and the power chart in DLL. Clearly, a big part of the discrepency is that my simple calculation does not account for aerodynamics, so courtesy of Klaus:
Here's the RPM slope based formula that also does SAE correction and accounts for aerodynamic resistance:
?Vehicle weight in lb = m[3000]
?Tire diameter in inch = td[25]
?Gear ratio of run = gear_ratio[1.21]
?Final drive ratio = finaldrive[4.53]
?i Name of RPM channel = rpm[RPM]
?Frontal area of vehicle (sqft) = Ar[30]
?Drag coefficient = Cd[0.45]
?Current atmospheric pressure (inHg) = atmp[29.92]
?Current temperature (degF) = temp[94]
#SAE correction factor
SAEcf = (1.18 * ((29.235/atmp) * sqrt((temp + 459.67)/536.67)) )- 0.18
#air density
density = 0.0412236 * atmp/ (temp + 459.67)
# tire radius in ft
R = td/24
# acceleration in g
a = slope(RPM) * pi * td * 4.3153245 * 10^-5/(gear_ratio * finaldrive)
# speed in ft/sec
v = (RPM * R * pi ) / ( gear_ratio * finaldrive * 30)
# aerodynamic draq in lbforce
Fa = 0.5 * density * (v^2) * Ar * Cd
# Accelerating force (lbforce)
F = m * a + Fa
# engine torque
trq = F * R * SAEcf/ (gear_ratio * finaldrive)
MC(torque;lbft;0) = trq
MC(power;hp;0) = trq * rpm/5252
Again, you'll get better results if you either trim the session or just highlight the pull in question (see my post earlier in the thread).
I'm going to have to wrap up my participation here. It is very difficult for me to talk about technicalities without relating it to our specific products. This appears to put me squarely into forbidden territory. Rather than make more work and grief for the moderators, I'll lay low.
I hope my participation to this point is perceived by most folks here in the spirit I truly intended it.
Best Regards,
-jjf
A number of folks have emailed me asking about the results they have gotten from my simple power formula posted in this thread. In particular, difference between the results and the power chart in DLL. Clearly, a big part of the discrepency is that my simple calculation does not account for aerodynamics, so courtesy of Klaus:
Here's the RPM slope based formula that also does SAE correction and accounts for aerodynamic resistance:
?Vehicle weight in lb = m[3000]
?Tire diameter in inch = td[25]
?Gear ratio of run = gear_ratio[1.21]
?Final drive ratio = finaldrive[4.53]
?i Name of RPM channel = rpm[RPM]
?Frontal area of vehicle (sqft) = Ar[30]
?Drag coefficient = Cd[0.45]
?Current atmospheric pressure (inHg) = atmp[29.92]
?Current temperature (degF) = temp[94]
#SAE correction factor
SAEcf = (1.18 * ((29.235/atmp) * sqrt((temp + 459.67)/536.67)) )- 0.18
#air density
density = 0.0412236 * atmp/ (temp + 459.67)
# tire radius in ft
R = td/24
# acceleration in g
a = slope(RPM) * pi * td * 4.3153245 * 10^-5/(gear_ratio * finaldrive)
# speed in ft/sec
v = (RPM * R * pi ) / ( gear_ratio * finaldrive * 30)
# aerodynamic draq in lbforce
Fa = 0.5 * density * (v^2) * Ar * Cd
# Accelerating force (lbforce)
F = m * a + Fa
# engine torque
trq = F * R * SAEcf/ (gear_ratio * finaldrive)
MC(torque;lbft;0) = trq
MC(power;hp;0) = trq * rpm/5252
Again, you'll get better results if you either trim the session or just highlight the pull in question (see my post earlier in the thread).
I'm going to have to wrap up my participation here. It is very difficult for me to talk about technicalities without relating it to our specific products. This appears to put me squarely into forbidden territory. Rather than make more work and grief for the moderators, I'll lay low.
I hope my participation to this point is perceived by most folks here in the spirit I truly intended it.
Best Regards,
-jjf
One more variable which may be difficult use and varies from tire to tire, but good to be aware of is tire pressure. A difference of 5 psi can easily give or take a cm of the wheels overall rotation distance for one turn.
nj1266, thanks for coming by. I've parsed out the captured packets from your XEDE unit. I can definately read RPM and timing offset from the XEDE (I also can read the time stamps and flags - but I don't know what the flag bits mean
).
Unfortunately, I could not figure out the other params. For example, I could find the waste gate and injector bytes, but since there were all zero in the captured traces, I don't know what value is what.
I'll whip together a simple RPM and Timing offset test for you to try tomorrow. Once it is working, and if it is useful to other XEDE users, I'll put a little more effort into figuring out what all the other values are (and maybe try to figure out what the "V2" switch does!)
Thanks Again!
-jjf
).Unfortunately, I could not figure out the other params. For example, I could find the waste gate and injector bytes, but since there were all zero in the captured traces, I don't know what value is what.
I'll whip together a simple RPM and Timing offset test for you to try tomorrow. Once it is working, and if it is useful to other XEDE users, I'll put a little more effort into figuring out what all the other values are (and maybe try to figure out what the "V2" switch does!)
Thanks Again!
-jjf
nj1266, thanks for coming by. I've parsed out the captured packets from your XEDE unit. I can definately read RPM and timing offset from the XEDE (I also can read the time stamps and flags - but I don't know what the flag bits mean
).
Unfortunately, I could not figure out the other params. For example, I could find the waste gate and injector bytes, but since there were all zero in the captured traces, I don't know what value is what.
I'll whip together a simple RPM and Timing offset test for you to try tomorrow. Once it is working, and if it is useful to other XEDE users, I'll put a little more effort into figuring out what all the other values are (and maybe try to figure out what the "V2" switch does!)
Thanks Again!
-jjf
).Unfortunately, I could not figure out the other params. For example, I could find the waste gate and injector bytes, but since there were all zero in the captured traces, I don't know what value is what.
I'll whip together a simple RPM and Timing offset test for you to try tomorrow. Once it is working, and if it is useful to other XEDE users, I'll put a little more effort into figuring out what all the other values are (and maybe try to figure out what the "V2" switch does!)
Thanks Again!
-jjf



