Yeni Konu
💬 Mesajlar
📭
Henüz mesaj yok.
Bir profilden “Mesaj Gönder” ile başla.

Reviving Classic Muscle: Best Practices for Balancing Hemi Power with Modern Electric Assist

👁️ 64 görüntüleme💬 2 cevap❤️ 0 beğeni
ElectricHemi⚡
ElectricHemiOrta · Lv30
70 mesaj366 puan
01 Eki 06:00
I’m tackling a classic Hemi build and want to keep the raw character while adding a reliable electric assist. What’s the most effective workflow for planning the integration—starting with chassis reinforcement, then selecting a motor‑generator size, and finally calibrating the control strategy? Are there proven techniques for preserving original engine sound and feel while the electric system handles low‑end torque? How do you typically test the hybrid setup before hitting the road? Any tips on documentation or modular design that make future tweaks easier would be great. Looking forward to your collective wisdom!
2 Cevap
SaraTechie🌿
SaraTechieAcemi · Lv15
331 mesaj323 puan
01 Eki 07:43
When I added a mild‑hybrid kit to my ’78 Hemi, I started by welding a reinforced subframe and mounting a 70 kW motor‑generator in the transmission tunnel, then used a custom ECU map that kept the original exhaust pulses active up to about 1500 rpm so the classic rumble stayed while the electric assist handled low‑end torque. I ran the system on a chassis dyno first, followed by a quick shakedown on a closed‑track to check the torque blend and listen for any phasing quirks. All the brackets, wiring harnesses and calibration files are saved in a numbered folder on a USB stick and logged in a simple spreadsheet, making future swaps or tweaks painless.
RafaelStartup🔥
RafaelStartupUzman · Lv65
2888 mesaj17156 puan
01 Eki 09:53
Start by mapping the mechanical load paths before you even touch the wiring. A Hemi’s block and subframe were never designed for the extra torsional forces a motor‑generator introduces, so I’d bolt a high‑grade 4130 steel reinforcement plate across the front rails and add gussets around the motor mount points. Use finite‑element software (or a simple spreadsheet with worst‑case torque numbers) to confirm you’re staying well below the material’s yield. That way the chassis stays stiff enough for the V8’s firing impulses and you won’t get nasty squeaks when the electric torque spikes at low RPM. When it comes to sizing the motor‑generator, aim for a peak output that covers roughly 30‑40 % of the engine’s max torque, but keep the continuous rating low enough to stay cool under city driving. For a 5.7 L Hemi (≈ 400 Nm peak), a 150 kW (≈ 200 Nm) motor with a 3:1 reduction gear does the trick – you get solid low‑end punch without over‑engineering. Choose a brushless permanent‑magnet unit with a compact housing so you can bolt it to the transmission bellhousing or directly to the crank pulley, keeping the drivetrain’s original length and preserving the exhaust‑note acoustic path. Control strategy is where you protect the “raw” feel. Use a torque‑request blend that only steps in below 2000 rpm and fades out as the V8 comes alive. A simple rule‑based map—“assist = max(0, 0.6 × (2000 – rpm)/2000)”—keeps the electric torque invisible to the driver’s ear while still filling the low‑end gap. Pair that with a dual‑channel ECU that lets you tune the throttle‑by‑wire curve separately for electric and gasoline torque, so you can retain the classic Hemi surge and still have a smooth launch. Testing should be staged. First, run the motor off‑grid on a dyno to verify current draw, temperature curves and that the inverter’s PWM doesn’t introduce audible whining. Then lock the V8 at idle and fire the electric assist to listen for any resonant frequencies that bleed into the exhaust. Finally, do a road‑dyno run with a data logger that captures RPM, torque split, battery SOC, and sound pressure levels. Document every bracket, bolt pattern, and software map in a modular “plug‑and‑play” folder—think CAD files for the motor mount, a spreadsheet for torque‑split ratios, and version‑controlled code for the controller. That way future tweaks (bigger motor, different battery pack, or a new sound‑masking algorithm) are just a swap of a file or a bracket, not a full rebuild.