Datalogging won't work and questions about payload

twinturbostang · Post by **twinturbostang** » Mon Apr 21, 2003 7:58 pm

Just got my car back on the road recently. It's been disassembled since last october, so this is my first go at the new version of CalEdit/Calcon.

First question... When I check all of the parameters to data log and then click the "payload" button, the checkmarks disapear. Is that normal?

Second question... Is the payload information stored in the .CCF files? I'd rather not have to re-enter all the payload info each time I change my file.

The other thing is I can't get datalogging to work. I've built the payload, and I checked the "datalog" box before writing to the TwEECer. But it still doesn't datalog. I read through the instructions in the FAQ, and the only thing I can think of is that I did not check the "write to file" box. I didn't want to write the log yet, just watch it in realtime. Is that disabled in this version or is it another problem?

Thanks,
Brian

desmo996 · Post by **desmo996** » Mon Apr 21, 2003 8:19 pm

1. that is a normal response.

2. You may have to rewrite all of your cal. files to the TwEECer, once you have built your payload, as the two are not compatible. Once the payload has been selected, you do not have to re-enter the payload everytime you make a change. You just do it once and when you write that file to the TwEECer, I believe that the payload is then stored there.

The only thing I can think of is to make sure that the appropriate car type is selected in your datalog, i.e. Fox, SN95. Sometimes I just start from scratch and everything then will work.

Good Luck

twinturbostang · Post by **twinturbostang** » Mon Apr 21, 2003 10:13 pm

Yeah, I knew I would have to re-write my cal files. I loaded my file, built the payload, saved it back to the file, clicked the "datalog" checkbox, and wrote to the TwEECer. Datalog didn't work. Although, I do still have cal files loaded to the other cal switch positions. I haven't switched to those positions (just using position 1 right now), but maybe that has something to do with it. I'll try writing the new file to all positions and see if that does it.

Oh yeah, it's an A3M, and yes it all comes up as the correct car/processor type. If I can't get anything going, then worst case would be to "read EEC" and start all over with my cal file, although I'd rather not have to go through all of that. Unless the copy table stuff from one cal file to another is working in this release now. Do you know if that works?

Brian

desmo996 · Post by **desmo996** » Tue Apr 22, 2003 11:06 am

Yes, the copy function works for me. I too have had to start from a fresh binary and copy everything over. The only thing that doesn't copy is the scalars, so you may want to write them down or something, they have to be retyped in.

twinturbostang · Post by **twinturbostang** » Tue Apr 22, 2003 11:23 am

Well, it's still not datalogging. I tried writing the bin to each memory location. Also tried logging to a file. Don't work.

And now I've got USB issues again. For some reason, every once and a while the USB "Found new hardware" Winblows thing comes up. Usually crashes communications between the laptop and the tweecer. So far my only fix is to uninstall CalEdit and then to re-install it again. Right now it's weird though.... when the laptop is plugged in to the tweecer, and the key is off, the electric fan comes on! WTF?!?! Mike, what's going on with this thing?? The laptop is an HP OmniBook 900 with a built in USB port, and running Win2K Pro.

Brian

twinturbostang · Post by **twinturbostang** » Tue Apr 22, 2003 4:58 pm

Ok, I got the USB issues solved once again. This time was more complicated to clear out the driver. But I got that straightened out. I can write to the TwEECer again.

BUT, the datalogging is still not working. I've started from scratch with a fresh stock A3M bin file and added all my changes. Did the payload thing, checked the "datalog" box, did the hoaky poaky, turned myself around, and it still won't work. :D I did notice a few things though.... When I click the "Start Logging" button, the "Real Time Data" indicator light turns on, and then goes off when I stop the logging. All of the gauges and stuff are blank though, so it apears that it is not logging. But I also noticed that it IS writing some kind of log file to the hard drive. But when I try and open it in CalCon, I get this error: Logfile is empty: Canceling Playback. A quick check at the files on the hard drive reveals they are only 2K in size. Most of the log files I've done in the past have been between 40K-300K.

Mike, ol' buddy ol' pal.... Really need your help on this one.... Help a fellow turbo guy out! :)

Brian

Update: Uh, ok. Something else very odd. Last file it "wrote" was 030422174244.dbf. Translated, that's 5:42PM on April 22, 2003 (today). However, Windows Explorer is saying the file was last modified on October 10, 2002 at 2:51AM! WTF?!?!?

93notch · Post by **93notch** » Tue Apr 22, 2003 5:26 pm

Uhhh, Brian please dont try to read more into things then there are. The file was copied from the template to the new name (created by calcon) but was never written to, so it has the same last updated date as the template......

Now, the important stuff, what they hell are you doing to my tweecer!?!?! Read your tweecer, save the file to disk and email it to me. I will check the payload stored in it. Also, include the file:

C:\program files\stkr\data\a9lpl.dbf so I can verify that it is correct. this will be a starting point.

twinturbostang · Post by **twinturbostang** » Tue Apr 22, 2003 5:39 pm

YOUR Tweecer?!?!? Chit... I paid plenty of money for it to be MY Tweecer!!! LOL

But anyways.... Yes Sansai. I will send what you asked tonight. :D

Brian

twinturbostang · Post by **twinturbostang** » Tue Apr 22, 2003 6:24 pm

... "you've got mail"....

twinturbostang · Post by **twinturbostang** » Tue Apr 22, 2003 10:26 pm

Ok, it works now! Mike pointed me to the drop down menu in CalCon that has to show Fox, SN95, etc. It was blank and I didn't pay any attention to it before. That's why it wasn't datalogging.

To the post in the FAQ about datalogging, I suggest we add two steps.... In between steps 9 and 10, add: "Close CalEdit". CalCon and CalEdit do not work together on the TwEECer, and some people might not know this. I know this issue has come up before so it would be good to mention it. Also add in between steps 10 and 11: "Select vehicle type from pull down menu (eg: Fox, Sn95, etc.)" That's why datalogging was not working for me. And since the menu was blank, I didn't even see it. I was not aware that had to be selected, so it might be a good idea to mention this as well. Perhaps also default the menu to either Fox, or determine what processor you are using so this is not an issue.

93notch · Post by **93notch** » Tue Apr 22, 2003 10:35 pm

Already fixed for 1.20 final.....autoselection of RT Method.

desmo996 · Post by **desmo996** » Wed Apr 23, 2003 8:11 am

Sounds like you have put a lot of work into 1.20 Final. I am anxious to see it in May. :D

klondike93 · Post by **klondike93** » Wed Apr 23, 2003 9:13 am

Do I hear June? July?

(I'm kidding Mike)

:?

Post by **Jon 94GT** » Tue May 06, 2003 10:29 am

twinturbostang wrote:To the post in the FAQ about datalogging, I suggest we add two steps.... In between steps 9 and 10, add: "Close CalEdit". CalCon and CalEdit do not work together on the TwEECer, and some people might not know this. I know this issue has come up before so it would be good to mention it.

I agree, I will add this in.

twinturbostang wrote:Also add in between steps 10 and 11: "Select vehicle type from pull down menu (eg: Fox, Sn95, etc.)" That's why datalogging was not working for me.

Actually...it's already there...see step 12.

dynoman · Post by **dynoman** » Wed May 14, 2003 11:29 pm

This is the exact same problem I am having with datalogging. But I have selected the processor type and it is still not working. I tried several different processors with no luck. any other help would be great.

going round and round. Just go this thing setup and it see's the TweecerRT and the light goes green on Calcon but not data.

HEEEEEEEEEEEEELP :(

Cobra4990 · Post by **Cobra4990** » Thu May 15, 2003 2:26 am

I can't get data logging to work either. Like it did for Brian before, I get the "Logfile is empty: Canceling Playback" error message. When starting a log, none of the gauges come to life either. I am selecting FOX, so that's not it. I have successfully written changes including the MAF Transfer, so I don't suspect any connector problems. :?

I have followed the FAQ instructions carefully, but I'm totally stuck. Any help would be most appreciated. Thanks everyone.

-Mark

twinturbostang · Post by **twinturbostang** » Thu May 15, 2003 9:22 am

Make sure you correctly build your payload, and then check the "datalog" box before writing to the tweecer.

dynoman · Post by **dynoman** » Thu May 15, 2003 3:23 pm

Process:

I make sure I select the items I want to datalog, click payload and all the check boxes clear. Then I go to input/output and make sure the Datalog box is checked, and then write tweecer. Everything is ok so far. I then close caledit, then open calcon, I select the strategy “fox” (have tried several types of strategies but no luck) make sure the “log to file box” Is checked, then click start datalog. I then start the car. Nothing, zilch, nada, nothing is displayed and when I try to playback it says the datalog file is empty, canceling playback. It does create a .dbf file though

Questions:
Is the Real Time Data light suppose to come on when it is logging data? It never comes on.
Is there some way I could build the payload incorrectly? How do I make sure I build the payload correctly? seems pretty easy, select what you want, then click payload, select datalog, then write tweecer.

Is it supposed to make the fuel pump come on when I write to tweecer? That only seems to happen when I first write to position 1 and 2 after I reset the computer. After that it doesn’t matter which location I write to or when, the fuel pump doesn’t come on when I write to tweecer.

twinturbostang · Post by **twinturbostang** » Thu May 15, 2003 5:00 pm

Have you tried starting the engine first, and then datalogging? This is something that has been broken/fixed/broken/etc. with different versions of Calcon.

BTW, every once and a while, my fuel pump and electric fan will turn on during writing tweecer also. Haven't been able to figure out why it does that, or for what reason, since it doesn't do it all the time.

Brian

klondike93 · Post by **klondike93** » Thu May 15, 2003 6:32 pm

My fuel pump only comes on when I turn the key on to write to the TwEECer, the fans have never come on during this process though.

When I create my payloads, I save the file first then write to the TwEECer and haven't had any problems yet with data logging. Give that a try and see what happens.

:?

dynoman · Post by **dynoman** » Thu May 15, 2003 6:33 pm

Been there and done that. tried to start the car, then data log. stop datalogging start datalogging, selecting a different system then start datalog. All with no luck. It just keeps creating different .dbf files which are empty. I will try it again tonight just for grins.

I sent a couple of my bin files to Mike Glover @ Tweecer and Ben Frazier @ v8 mustang to take a look at them and see if the payload is setup correctly. I will post again when I hear back from them.

93notch · Post by **93notch** » Fri May 16, 2003 1:01 am

I only found the payload in one of the 3 binaries you sent me. Ben's question regarding wether or not it is an RT is valid, I have shipped a Base unit ONCE before, thinking it was an RT. If I did screw up, I will pay for shipping back to us direct and back to you (I will overnight back to you) if it is my screw up. I have two boxes here (empty right now) that have RT's in one and Base in the other. I also have a 2yr old and 4yr old that crawl over me while I work.....

Did you answer Ben as to what board rev it displays?? If so, what is it?

dynoman · Post by **dynoman** » Fri May 16, 2003 10:59 am

Thanks Mike:
I understand about the kids. I will double check the board rev tonight and let you know and give you all the specs on board rev, computer, os, ect.

Cobra4990 · Post by **Cobra4990** » Wed May 21, 2003 9:56 pm

I'm still stuck. No logging.

My board rev is 5103R00D, that helps.

-Mark

Joe · Post by **Joe** » Mon May 26, 2003 4:43 pm

I'm having the same problem, except I get the message "Unable to open Tweecer" when I try to build a payload. This only happens when the tweecer is plugged into the computer.

klondike93 · Post by **klondike93** » Tue May 27, 2003 12:05 am

I went over to try and help Cobra 4990 try and get his TwEECer to data log and couldn't get it to work. I think we ruled out software cause his software worked fine on my TwEECer. But, my CalCon couldn't get his to data log at all, just a blank screen. You can read his TwEECer just fine but it just doesn't data log at all and it's the same board rev as mine so it should be a data log TwEECer.

:?

P.S. sweet car too :)

81 Flareside · Post by **81 Flareside** » Fri Aug 08, 2003 10:49 pm

Chuck,
What ever happened to this?
Kinda curious, cuz mine is doing it now......very strange

81 Flareside · Post by **81 Flareside** » Fri Aug 08, 2003 11:15 pm

Nevermind. I had a brain fart

klondike93 · Post by **klondike93** » Sat Aug 09, 2003 5:13 pm

What ever happened to this?

Well he ended up sending it back to Mike, who looked pronounced it fit and sent it back. He did send it back with a new A9L file, or maybe Cobra file in it and ever since then it's been working for him.

Datalogging won't work and questions about payload

Datalogging

Who is online