Recently discovered Axiom, coming from the MegaSquirt world like some here probably are. Love the idea of taking the MS concept to the next level as a clean-sheet top tier product — and if you know MS, the software feels familiar right away.
Cool to see I am member #20! My car is a Factory Five 818S with a turbocharged VW VR6 12v and fully custom wiring harness built for this precise car. Currently troubleshooting a cranking/sync issue, but long-term I'm very interested in Axiom as an upgrade path. Some questions/comments below — no rush on answers, and hopefully some of this is useful feedback too:
Technical:
- Do the DBW outputs drive the throttle body motor directly (half-bridge), or is an external DBW controller still required?
- For coil packs like MSD-8224, is an external high-current driver still required (same as MS), or can the spark outputs drive them directly? If they cannot drive them directly, what's the reasoning (cost, accuracy, flexibility, relevance)? No strong opinion either way, just curious about the design tradeoff.
- What chip/strategy handles Crank and Cam signal conditioning — adaptive threshold or fixed threshold? What was the reasoning to select one over the other?
- How does it handle LC ringing near or at the gap tooth on VR signals — is the adaptive threshold (if equipped with) tolerant of that, or does ringing risk false triggers?
- I noticed shunt options selectable in the software for the VR/Hall inputs — what's the input capacitance/impedance these are working against, and is there any onboard clamping (TVS or similar) on these inputs as well?
- Same edge-polarity behavior as MS (i.e., signal inversion such that a clean falling edge on the scope means selecting Rising Edge in software)?
- Out of curiosity, has anyone run a 60-2 wheel (or maybe 36-1) with a high-output VR sensor (like 800Ω+ class)? If yes, any sync issues at 4000+RPM, or has that combo been clean across the board?
- What overvoltage/clamping protection exists on the inputs — both for normal high-RPM VR signal levels and edge cases like a disconnected ground or main ground feeding voltage back into a signal pin?
- I recall reading about a built-in oscilloscope feature — if I was not mistaken about its existence, is that a true raw-signal capture at the ADC front end (pre-processing), like an external scope would show?
- For the integrated wideband O2 controllers — can the signal feed an external gauge/display, or ECU-only?
- No onboard MAP sensor, correct? — I don't see a barb fitting on the case. If that's right, what's the reasoning (cost, accuracy, flexibility, relevance)? I don't mind, mostly curious.
- GPS input is supported but there's no onboard GPS module, correct?
UI/software feedback (Linux build):
- At the moment, how can one mimic a composite/tooth logger?
- The "+" button next to the Home tab doesn't appear to do anything.
- Widening the left sidebar via the drag separator snaps back to default width.
- Projects save to with no apparent option to choose a different folder.
Code: Select all
~/Documents/AxiomEFI/ - Pure-text sidebar navigation makes it easy to click a parent menu vs. a sub-item by mistake — could be tricky for in-car tuning, especially on a topless/no-windows car in direct sunlight.
- Expanded sidebar menus push everything else down, so the main menu structure scrolls out of view — hard to keep the big picture while navigating, unlike when using buttons.
- Long-term UI vision for the dashboard sidebar — staying as a list of live values, or eventually supporting gauges, custom layouts, high/low alerts, etc.?
- And please keep the Linux build alive.
Thanks!