Standback logging issues?

[NJSPEED3]

I have been having issues logging with my standback for about 3 months now. I've tried trouble shooting with very little success and I'm wondering if there are any others members here having the same issue.

list of members with this issue
@bmylez
@RichieRichness
@MattJackson86
@rigor

here's the issue

Once you go to take a log with the standback as soon as the ecu seems to see load or open loop not sure which first, the log stops and we get an error message saying sb log recording halted. Sometimes the sb software freezes as well.

Im my experience since this issue has started happening, I have randomly been able to log properly, I'd say maybe 2-3 times in 3 months.

Here's is my thread explaining exactly what Im saying
http://www.mazdaspeedforum.org/forum/foru...tml#post702665


I've already contacted Sanders to assist me with this issue and so has Jake while he was with CPE. The main reason for this thread is to see how many others out there have or have had this problem.

Thanks
Gerry

[Cue]

What OS?

If Windows 7, switch to 32bit and it works just fine... Plus, the DH will work too.

[rigor]

mine is 64 bit works fine, but not the dashhawk, how do you switch to 32 bit?

i data logged today, and it sad halted do to loss of connectivity ?

and sometimes it flat won't hu to the sb @ all, but it will eventually

[Cue]

A reinstall with a Windows 7 32bit version. Same key you have now (on your 64bit) will work.

Your SB will not lose connection when running a 32 bit OS. XP or Windows 7 for example. And you DH will work.

I had to do this (32bit) cause I didn't want to buy a second computer. My new one was perfect for me but had the 64 bit version installed. So I changed it, and all my issues went away (losing connection with SB, logging, and DH software not working).

[NJSPEED3]

Sb will work fine on 32bit or 64 I have both, no thats not the issue and no you cant log for timing with the dashhawk if you have flashes like I and Rigor do. There some parameters like timing which are scaled by the sb in open loop.

What you're talking about is the very well known glitch that the sb software has, when logging the software loses connections with the standback. Im referring to something different read my op or go to my thread thanks.

Anyways this thread is to figure out who else has this issue not to help me figure it out although I do appreciate it. If you are getting a error code recording halted please post on here.

[rodrigo]

2 weeks

[NJSPEED3]

^^^ haha fucker if it happens it happens ohh well I gave the SB+flashes a good run

[Cue]

Originally Posted by NJSPEED3 Im referring to something different read my op or go to my thread thanks.

I'm reffering to the same issue you have with logging in your OP. I switched to 32bit and that issue went away for me. Perhaps a different version? The last version i downloaded was from Dec 2010.

[RichieRichness]

I'm on XP 32 bit and I have the same problem.

[NJSPEED3]

I have tried

windows 7 64 bit
windows xp 32 bit

both with the same results, for the record.

Thanks Richierichness the more people with this issue the more of a change to get cpe to figure this out guys for us guys.

I'll add you to the op.


Please make sure that you are having the exact same issues I am. Go suft threw my bt thread to confim please and then post on here and I'll add your name to the list.

[MattJackson86]

Originally Posted by Cue Your SB will not lose connection when running a 32 bit OS. XP or Windows 7 for example.

Not true. I have logging issues too with the SB running on XP 32 bit. Tried it on multiple laptops. Sometime it works, but 95% of the time I can not log for more than a couple seconds. I also lose connection a lot too with the SB. This has been discussed in the Standback Tuning thread and multiple people reported the issue there. This has been occurring for longer than I remember with me.

Originally Posted by NJSPEED3 Thanks Richierichness the more people with this issue the more of a change to get cpe to figure this out guys for us guys.

CP-E are aware of the issues. I have spoken personally to Sander and Josh about these issues. Last I heard is that they are talking to their developer about a fix. No ETA.

This is a very frustrating issue I agree. Not having the ability to log is major in my mind and I hope they get it fixed.

[NJSPEED3]

^^^^ This is not the issue at hand please read into the error code before posting. The connection issue has nothing to do with what OS you are running its a software problem with the standback, different OS seem to help and so do certain versions of the sb software.


Please stick to the topic everyone so we can have this resolved.
I'll say it again the connectivity issue I am well aware of and so id CPE. This is a logging problem. Go OP and read the last 2 pages on my bt thread.

[MattJackson86]

Sorry, my statement is about both the logging and connection issues. Not just specifically connection.

And I will say again, I have spoken to Josh and Sander about the software and the bugs it contains. They are aware of them.

[NJSPEED3]

Originally Posted by MattJackson86 Sorry, my statement is about both the logging and connection issues. Not just specifically connection. And I will say again, I have spoken to Josh and Sander about the software and the bugs it contains. They are aware of them.

Im aware they know about the connection issue, but not the logging issue with the "halted error code" < lets call it this from now on so we dont get people confused.

I dealt with Jake,Loe, Josh and now Sanders. From what the led me to understand this is all new to them.

How the hell is not being able to log acceptable! Remember guys if you have the flashes you CAN not use the dashhawk for certain parameter logging. Whats the sense of having a tuning solution with out being able to log for the proper calibration adjustments.

[jhershorin]

The flashes aren't interfering with logging - its that the standback scales things (not flashes)...

Until recently there weren't reports of logs not working. Lately it is an issue. We used to be able to log with Gerry's and then it stopped being able to a few months back.

[cpolly69]

Gerry I just had a thought. It might mean shit at this point, but I thought I'd point it out. Some of the older versions of the normal software (not the BBX stuff) seemed to have different reactions to the status of the pc's power and where it was supplied from. I'm pretty sure 2.52 had something on it to show where the pc was with charge. I know in my car if I tried to supply power to my laptop via a ac charger plugged in the dc outlet it would do funny stuff and drop the connection.
So what are you doing for power to the laptop while you are trying to do this? Battery or plugged in some how?

[NJSPEED3]

thanks Chris yeah I'm aware of this, guess you shared this with Sanders. I use the battery on my laptop.

[NJSPEED3]

Originally Posted by jhershorin The flashes aren't interfering with logging - its that the standback scales things (not flashes)... Until recently there weren't reports of logs not working. Lately it is an issue. We used to be able to log with Gerry's and then it stopped being able to a few months back.

I dont wana get off topic here Jake, but explain for the record how this works, please.

I remember seeing logs back in the day from loosh showing timing on his dashhawk logs. Once I got the full control flash I could no longer get proper timing logs with the dashawk. I know something from the sb or flashes throws off dh logs on certain parameters.

[jhershorin]

The standback throws things off not the flashes. Timing and fuel psi are not accurate on a dash hawk when tuning with the standback since things are offset and scaled.

[NJSPEED3]

I'm going to bump this thread every so often. Im positive there are a lot of other members out there with this problem.

If you have a standback and have never logged with it, please do so. This will help us see the the percentage of users with the issue. Im afraid if we don't do this CPE will simply say that its an individual hardware problem and not a software flaw. So even if you have a dashhawk please try log a wot pull and see if you get the halted error code.

[superskaterxes]

gerry i hate to bring this thing more off topic but it seems like the only versions of windows you tried working with are the ones with problems. at the very least try a windows 7 32 bit or another OS that you 100% know that no one ever have problems with.


this is 100% why i never got a SB because the variability between units and peoples cars is insane.

[cpolly69]

Originally Posted by superskaterxes gerry i hate to bring this thing more off topic but it seems like the only versions of windows you tried working with are the ones with problems. at the very least try a windows 7 32 bit or another OS that you 100% know that no one ever have problems with. this is 100% why i never got a SB because the variability between units and peoples cars is insane.

I'm pretty sure he's done a normal version of XP at this point....But I could be wrong.

[NJSPEED3]

I have tried xp 32 bit
and win 7 64

I guess I could try win 7 32bit, I have no problem trying different things for the sake of getting this resolved by CPE.

[NJSPEED3]

and another one!

http://www.mazdaspeedforum.org/forum/foru...tml#post704243

[stefan]

mhh i've only taken 3 logs or so when i was on the dyno but that worked fine on windumb xp professional 32 bit.



i can haz osx support pls?

[NJSPEED3]

For some reason its seems to only be happening after you do a number of logs. Its really weird how this comes about. I know nothing about software programming but I have have been informed, and it does lead to the sb software some how.

[superskaterxes]

does the SB SW have a section to store the logs? i know on the AP it would only let u store like 5 logs at once so maby its filling up?

[the_caruch]

Originally Posted by superskaterxes does the SB SW have a section to store the logs? i know on the AP it would only let u store like 5 logs at once so maby its filling up?

no, you can tell it where to store them on your computer. no logs get stored on the actual standback itself. so space isn't an issue.

I'll go ahead and report i had a similar issue. I did NOT have the "halted" message, but it was a logging issue.
If you want, for the sake of troubleshooting i can load the older SB software on another laptop and try to reproduce it again.

on the 2.59e version
-I would hit record
-go WOT
-log would stop and freeze the software after a second or 2 into the run
-restart sb software
-repeat

Every once and a while, if i was quick enough to stop the log right after my run, it would hold out and i would get a successful log.

My problems went away when i updated to the 2.59q version.

edit: i have the SB on my fuse box and ECU is in the stock location

[MattJackson86]

How is everyone's USB cable run from the SB to the car? Mine is through the passenger side grommet. It runs behind the firewall heat shields.

[SSinstaller]

Have any of you having issues tried logging from within the BBX software instead of the SB software?

[the_caruch]

Originally Posted by MattJackson86 How is everyone's USB cable run from the SB to the car? Mine is through the passenger side grommet. It runs behind the firewall heat shields.

i have mine go between the weather stripping and the hood, through my window to my laptop. so i only have the usb cable plugged it in when needed

it's ghetto but it works

[MattJackson86]

I think we need to find people who do not have any issues logging and see how they are setup versus us that do have issues. Do they use the PnP? Software version? USB Cable setup? Anything and everything to narrow this down.

[stefan]

Originally Posted by MattJackson86 I think we need to find people who do not have any issues logging and see how they are setup versus us that do have issues. Do they use the PnP? Software version? USB Cable setup? Anything and everything to narrow this down.

i will get together with gerry one of these days to play around with our standbacks (no homo).

like i said i've only done 3-4 logs total which all came out good. However I have updated the software to 2.04.16 since then so we'll see what happens.

[djuosnteisn]

Originally Posted by diddiyo i will get together with gerry one of these days to play around with our standbacks (no homo).

Broken Stand Back Mountain

[rigor]

mine is the same as nj and i actually have a short extender on the usb 3 ft is their a certain length you cannot exceed?

mine worked today!

and im also running win7 64bit also

[NJSPEED3]

I know that frequency noise has alot to do with this issue. Some cars are noisier than others. This is definitely part of the problem. In early 09 CPE's fix was implementing filters inside the sb. The software is the other part of the issue imo

In my case I think as I started making more power the frequency noise became much stronger making the software to act up. I bet if I run a map with much less power I would be able to log. As I/we make more power this problem is only going to get worse. I really hope that cpe finds a solution, but I wont hold my breath on this.

Im just getting tired of all this quite honestly. I want to focus on my car not troubleshooting and finding the source of an issue that should have been tested by the manufacturer.

At this point if I were to go with the AP I would have to eat the flashes. I dont think this is fair considering its not my fault that I cant complete my tune.

[MattJackson86]

Out of the people getting this error "recording halted" message, how many of you are using the SB software that allows you to enter boost over 20psi?

Maybe we all have the same error but the ones who can enter >20 psi boost are obviously using different code that us that can not. Maybe that code has error messaging and ours do not, so it looks like different errors but is really the same.... ?

[SilverDemon]

If noise is causing this issue, try changing the condenser on the ignition system. It might be the problem, and it will be cheap to try out.....

[MattJackson86]

I have spoken to Sander about one fix that seems to have resolved the issue for me. He is testing it out and so are a couple people in this thread. It is definitely a noise issue combined with inadequate software. We just need to wait a few days and see what peoples tests say. As far as I know though this issue is being worked on mainly by customers and not CP-E's engineering department. Hopefully they can chime in on what their thoughts are.

[www.cp-e.com]

Gerry, I'm shipping your cable out tomorrow morning. Please call me when you get it with some feedback. Thanks.

-Sander