1st Gen Haltech ECU Discussion

So off topic but also on topic. When I rolled my green truck (a 1995 model) I put everything (wiring harness, emissions shit, engine, trans) into the 1996 truck shell. In WA state at the time you had to pass emissions (no longer thankfully) and they would plug into or put your car on the rollers. My 95 model always went on the rollers because it was before OBDII was required... well it had OBDII but it was missing some of the evap monitors a 1996 has, so when they went and emissions tested my bastard 1996 model with 95 everything in it on the computer rather than the rollers it still passed despite not supporting the monitors a 96 would because they weren't supported instead of marked FAIL. That's why I think showing all not supported and no codes might still get you a pass.

 

Interesting... I wish you could just request a roller

It is very related btw. I plan on integrating a full ODBII response system into the CAN gauge and the binary made available as a paid upgrade. As ethically as possible ofc. eg: if your wideband isn't reporting, your catalyst readiness is going to be a Fail. But then you can hook it into a J1962F pigtail and read everything like a real car.

 

Think I improved my transient throttle a lot but I still get the feeling something isn't quite right. It's hard to tell why it's responding in some situations but I stopped it from interfering in the low load cruising parts of the map, it was making them insanely rich false tripping. But I can tell it is working better now since I no longer burble and pop even when decel cut is activated.

 

People pay good money for those burble and pops

 

I know how to dial those in separate for anyone interested haha. But stopping them was becoming a mystery.

 

I wouldn't mind having a burble & pop tune just for fun Fridays

Does it require a cat bypass?

 

Sounds better than Whistle-tip Wednesday

 

It's not good for the cat but a bypass isn't required necessarily. You just dial in extra fuel (enough to achieve 10:1 or so) in the overrun area of the fuel map and set your decel cut delay for how long you want it to make burbles. Pops and bangs are less fuel and a lot of timing retard but I wouldn't recommend that with a cat unless you want it to gut itself.

 

Ah ok, I guess I didn't process there was a distinction between the two

 

the more aggressive the gurgle and pop, the faster it blows out the cat.
I have a buddy with a focus RS that tuned it and his cat was gone in like a year. Sounded awesome though and shot flames under load.

Although hollowed out cat = more exhaust flow = mo powa

 

Yeah the loud pops and flames are no-no with cats, they don't last long.

same rules as two-step
https://youtube.com/shorts/oDB8zLLIICg?feature=share

Burbles don't hurt much, just a short moment of richness

 

After having two boards go bad, and spending an extreme amount of time trying to keep memory usage tiny, I think I might be better off basing this around an rpi pico for just a little bit higher hardware cost.

It works rn, but I'm at basically 80% capacity and have a good chunk more I want to add, and the ascii display library I'm using absolutely sucks for large format letters. Memory issues will get even worse when I move to a 240x240px display

 

Rpi is a great platform and the picos are a nice small size. Always good to have more headroom than be at the limit

 

I definitely think I'll prefer that - just ordered 5. I've only used the big boards before though - with the full OS, which is not what I want and why I think the Pico is better than the Zero in this case

 

Yea same. Only experience is with the full raspi's that I would use for streaming boxes.

 

Rpi pico...

 

What about it?

 

Oh man, let me tell you.

After spending literally all weekend dicking with it, I'm left wondering who actually uses these things unless they're paid full time to.
First off, they come pre-configured with a C++ interpreter which is not obvious when you're buying. No Windows support. They expect you to have either a dedicated Linux machine or full sized Rpi ready to go to program the thing.
The proper thing to do imo is replace the bootloader with a MicroPython interpreter so you can code in Python, then download a sketchy looking 3rd party IDE to use with it. This is basically in fine text in their documentation. After messing with that for literally 8 hours and coding my own font decoder for the display, I was unable to find a CAN library to work with the MCP2515 outside of yet another bootloader/interpreter called CircuitPython, which is essentially solely created and maintained by Adafruit. And ofc nothing I coded prior is a direct fit so I'd have to re-write everything AGAIN to get them to work with it.
In essence, documentation is limited, some outdated and no longer relevant (so even more trial/error), and extremely limited preconfigured libraries for off the shelf add-ons. To top it off, the adafruit libraries that are compatible with CircuitPython are all coupled through dependencies, so if you just want one or two things, it wants an excessive amount of backbone "just in case", which drastically exceeds the storage space of the Pico, requiring even more manual re-porting of said dependencies to narrow it down to what the bare minimum requirements are.

 

Do you have time to talk about our lord and savior, the pjrc Teensy? It’ll run your arduino code - fast.

 

If it has more SRAM, is under $10, and works with the Arduino IDE compiler, I'm sold