why dont you just turn it off for data logging?

 

I tried that and I kept getting a com error on the Cobb. It only seemed to work completely when I unplugged the Good Box. Maybe something is wrong then?

 

possibly. i can turn mine off and the ap works fine.

 

Update, left the Good Box unplugged yesterday, plugged it in this morning and now it works fine, no more "comm error" on the AP when the Good Box is off

 

been a while since I've had anything to add to this thread. Pretty set on selling my Goodbox at this point. Haven't gotten around to installing it and can't say I'm at all impressed with how support has pretty much evaporated.

Went thru the trouble to buy a programmer as suggested by pieter3d with the expectation that he'd be releasing the code or at the very least providing updates but it appears that won't be happening either.

Both to be listed soon (New In Box) in the FS section.

 

I am happy with my purchase, pretty good item considering he developed and built it himself.

 

So where is he?

 

^ I agree. Kudos for coming up with something innovative, but if you're going to sell a product, it is only right to give support and advice, especially when it doesn't perform as it's supposed to. Otherwise, it seems as though you're only interested in the cash, not the customers.

If it wasn't tested sufficiently, should it have been brought to market?. I understand that people may have been rushing Pieter, saying 'I Want One, I Want One', but nobody was made aware of any problems. They were only brought to light by customers, not Pieter. We could at least have been made aware of the possible slot-machine effect, before purchase.

If i'd have bought this device from Corksport with no knowledge of this forum, I'd have returned it instantly when it made my display scroll, assuming that it was broken. As far as I know, there's still no official fix for this, just some suggestions.

It's pretty important to me to be able to plug another device into the OBDII. Will I be able to? At the moment, I feel like I'll only find out by working it out myself, or another customer offering information.

It'd be different if Pieter was actively working towards solutions to the problems mentioned, but as far as I know, he's not bothered about it any more. Communication has just stopped, and this is only since the problems have developed. I really don't want to flame the guy, but ...

I'd be super p*ssed-off if i'd have bought the programmer as well. It's wrong to tell people to buy extra stuff to update the device, then just forget about it

I just think that because we're a community willing to try to troubleshoot the device ourselves, and we don't want to complain too much, we're being neglected and taken advantage of.

I understand that there are people who are happy with the device, but you have to admit that any company selling a product would be given a very bad reputation for not attempting to resolve obvious defects, or communicating their progress with their customers.

As far as I can tell, these are the issues so far (still unresolved):

1. Scrolling screen
2. Dot present in FM radio mode
3. Problems pulling codes
4. Compatability with other OBDII devices. (I expected and want both devices turned on at the same time. I don't think this is too much to ask, as we were told that this would not be a problem)

To me, this is enough of a variation from expected performance to warrant alot of attention. I also don't really like the idea of shipping the device backwards and forwards, because it takes so long and because I don't think that I should have to pay to fix the devices inherent faults. Having said this, If an effort was shown to remedy the problems, I would still be prepared to pay for a programmer (which I shouldn't really have to do) so internet based updates should be in place, or at least given a time scale.

C'mon Pieter. You got alot of respect for coming up with this device. Don't ruin it now.

 

Guys, you need to remember that at this point there's not a company behind the product but just a guy. These things take time to set up. Just because Corkstport offers the product on the website doesn't mean they're willing to stand behind it and support it either.

I helped manufacture this product and am working on getting the support infrastructure built up. There will be a process for RMA repairs/updates/firmware flashing/etc., either on your own if you have the tool or by mail in. There will soon be a company behind the product instead of a guy and all this will be easier. Timeframe is Octoberish for this to be ready.

Regarding the issues mentioned above:

1. I think this is the 'slow machine' effect. Can anyone confirm that adding the resistors does NOT fix the problem? If that looks like the answer I'll update the manufacturing side so the next run has the fix built in.
2. The dot is gone in the next firmware release.
3. Can you explain what you mean? Is there a problem reading codes off the computer?
4. Other ODBII devices. I've confirmed that you can use other devices with the GB turned off but I believe since they both poll the same data that you can't have two operating at the same time. This may be a system limitation but at the moment you can hit the button to turn off the GB and everything works as expected. Please let me know if this it not the case so we can look at updating hw/fw.

This is the first run at the product and some bugs are expected. It's impossible to encounter every scenario in testing and the community really helps to improve products like these with their input.

Anyway, sorry for the rant but I wanted to let you guys know that there are folks out there working to get this product to market with proper post sales support.

 

And we wonder why people don't want to spend time and R&D making new innovative products for our platform

Quit bitching and give the guy a chance.....

Just my 2cents

 

Pieter is not responding here from a month and I too was thinking no more support and making me to regret the purchase. Now dondo comes and says he is involved in this also. See... that really makes me fill better about the GB already. Just letting people know you are still here is a very good thing.
@dondo, if you are in this to you better keep an eye on this thread. Not knowing about the GB not reading codes doesn't sound good.
And the resistor does not solves the "slot machine" effect. Like I said already earlier I suspect the weak connector on the back of the GB.

Anyway, it's good to know the support is not dead although I'll believe it when I hear it from Pieter.
No offense.

 

^ Amen Dan. This is a great product that I was skeptical would ever come out and it did, so I purchased right away all the while knowing issues are a given considering it was built quickly and not tested widely. I like this product, it can only get better.

 

Thanks for the update Dondo

What? Who's bitching?. I think the GB is a fantastic idea, and like I said, Kudos to Pieter for devising it.

What my point is, is that no communication suggests that nothing is being done. Especially when people are posting genuine concerns.

 

No communication? Every time I have sent Pieter a message with a question he has responded right away and answered my question(s).

 

Thanks guys.

I will go through the whole thread once I'm through the current concerns and make sure nothing was left out. At the moment I'm focusing on the slot machine fix and firmware enhancements which I see as the priority.

 

That's great, dondo. Keep us posted please.

 

Some input on the slot machine. Yesterday my GB got super stuck in the slot machine. Usually turning off the car and moving it fixes it for me, but not yesterday. I tried 4 times.

I tried pushing the back button multiple times then turning the car off and back on (stationary)

I tried turning the A/C off then turning the car off and back on.

I tried driving slowly and turning the key to off and taking it out, then putting in and turning car on w/o A/C

I tried unplugging the GB while slot machine was happening and the LCD continued to slot machine. So maybe it's got something to do with a signal the GB is sending to the faceplate at some point.

When I finally got home I unplugged the GB again and the display stopped on M1|||||||||||||||||||||||||||||||||||||||||||||||| |||||. Then when I plugged the GB in I was greeted and it functioned normally.

Just some input, more to work from.

 

Pieter explained to me how to eliminate the slot machine effect but I have yet to find it.

 

The only way to stop the slot machine effect in my experience has been to unplug the connector on the back. I have added the resistor as specified earlier in the thread and have had better results. I really only drive my car on the weekends but recently took a 2500 mile trip with the car and used it everyday for a week, the *effect* only happened once.

 

I've noticed that I can tell whether the slot machine effect will happen before turning on my car. With the key at ON but without starting the engine I may get the slot machine effect.

If I do see it, I can simply remove the key and try again a few times until it clears.

The same way of clearing works for me the times I've had the problem (cycling on and off), but I would't do it if I've just started a cold engine.

 

No not all the time...
Happens randomly. I've had it happen about 10 times in the few months that I've had it.

 

Made a start on my install today:

 

You're going to beat me to it. I have had the temp sensor and associated installation equipment for about three weeks and haven't even got the chance to run wires..

 

I need to correct this post from page 6: the place I suggested to Tee into a line to get a manifold vacuum reading doesn't work! I need to find a better location and will update when I get a chance to fiddle with it again.

 

I confess I've had some role in working out these issues, though I've been out of the loop for the past 4 weeks 'cause of being in China. There were quite a few problems with the initial programming of my GB mostly having to do with how strings were handled for the AUX inputs. I sent the GB back for the initial fix, but problems remained, so Pieter sent me a programming box and we went back and forth a few times until that part now functions properly, as well as getting his solution to the FM dot problem. (I am very much an amateur when it comes to writing code, but my day job often involves debugging such code at the operational level.)

Besides a very occasional slot machine effect, I've had no further problems and the COBB seems to work just fine as long as the GB is switched off. It was also discovered that there is a difference in how the '04/05 models treat the accessory switch vs. the later models. If I remember correctly, the CAN comes on in one case and not in the other - which also necessitated some changes in the GB programming. This may account for some differences in reported difficulties.

I still have the programming box at present, but consider it "community property". "My" version of the firmware works well, but perhaps there have been updates to that. As soon as the firmware is stabilized (and version numbered ) I'm willing to send the programmer on to the next guy, he can send it to someone else, and so on. It's not exactly self-evident how to get the program into the GB however, so I'm not sure how well this mode of updating will work for without detailed written instructions or support over the phone. With relatively few GB's out there however, I'm sure there's a way to get everyone updated pretty quickly.

Still, regardless of the difficulties, it's I think it's very cool to have my coolant temp and oil pressure in particular, displayed up near my line of sight while driving and don't regret buying the GB.