Good stuff Charles! Thanks for posting that up.That diagram is the basic idea, but it will not run an IDM, except by blind chance, with that chance being like 1 in 10,000 that you happened to line everything up right.
In fact, looking closer, if you produced signals exactly like those, it would never run. 0% chance.
On Edit:
I thought I remembered one time arguing with people that the communications protocol between PCM and IDM would not support but XXX pw at XXXX rpm and had quickly generated the needed signals to show the limits of the com. protocol. Turns out it was still up on youtube, so, it just so happens that this is also the exact signal generation anyone needing to run a flow bench using a ford IDM (the preferred method) would need.
Look closely, because this is an accurate and real com link that would, and has run a 7.3 engine, as well as flowbench. I won't just spell out every last nook and cranny because that information was painstakingly earned and handed to me many years ago. Although I think it has all been stated in plain English since then, you are in fact wanting to build a flowbench, possibly to directly compete with those people. So, you need to do some legwork, but this is a proper, running com link I generated long ago.
https://www.youtube.com/watch?v=RfHF0hZdUZw
I made an edit to my last that you should not miss.
Btw, excuse the slow speech, I think I had been so worn down by idiots at that point that it was affecting my ability to care enough to speak clearly, lol. The same morons that continue being morons today were up in arms adamantly explaining how they could tune a truck to run hellacious pulsewidth at clearly impossible rpm points. Ever notice how the same idiots come up with the really dumb sh*t?
Anyway, turns out that video provides this thread with a good view at a real IDM com link.
I just changed the code to have a 500us FDCS off delay to match your duty cycle. The Arduino doesn't have a processor and the thought was it may be needed. The raspberry pi is similar but has a processor around $100.
You've got the basic idea, but you need to look really close at an engine running and zoom way in.
What you have there still won't be accepted from what I can see.
I'm sick as a dog and have been over 100* for around 6 days now, so I may be retarded, but is that over 5700rpm???
If so, calm down, lol.
I hope you feel better soon! Not cool being sick like that around Christmas time. Btw, I calculated 3000 RPM for that last pick before your post. Of course, I'm not the sharpest tool in the shed, so my math could be off.
Sucks bad. Just got a positive Flu test at the hospital. Had to send the Fam away, which really sucks bad. Now it's just me, a cattle dog and a bag of Tamiflu...
Maybe it'll kick ass in time for Christmas.
Sucks bad. Just got a positive Flu test at the hospital. Had to send the Fam away, which really sucks bad. Now it's just me, a cattle dog and a bag of Tamiflu...
Maybe it'll kick ass in time for Christmas.
I think you need to keep CID and FDCS in the same routine. Those cannot be run in seperate routines and everything work out in my experience. They are tied at the hip.
You know the "off time" on the FDCS is in between injectors, and the injector pulsewidth is defined by the time that FDCS is high after the leading edge of each event right? You don't pick the low, you pick the high and the low is just what's left before the next injector at the rpm in question.
Building a flowbench, pulsewidth and shot count are the bible.
Just build me a piezo controller and I'll be happy. I don't want to spend $150k...
Sent from my iPhone using Tapatalk
Piezo's are crazy fast. Fast enough to have multiple injection pulses per compression event.