quick and nasty datalogger
quick and nasty datalogger
(OP)
Does anyone know if there is a quick and nasty way to log a crude digital signal?
Rather than use the correct kit, is there a way to make use of let's say an audio recorder, using the microphone input socket to record a pretty raw / rough digital signal, even if it's barely recognisable as a digital signal?
I don't really care about the quality at all.
I just want to do a live test on my car to prove there is some activity while driving.
I want to T into the wire that pulses a solenoid on the car, and record the live data.
Am I being silly?
I know when I open a WAV file for example in a WAV editor, that the sample rate is 44100 per second, so I presume that is the rate it can be recorded at if I use a the microphone input?
I'm even just thinking of winding a small diameter copper wire around the solenoid control wire that provides the pulses, and hopefully even a small inductive signal can be recorded.
I only want to know when the solenoid is being pulsed, and the duty cycle at the time.
Just before someone suggests OBD, I have no kit to do that and I don't really intend buying any.
I just want to know if my crude solution is feasible or am I missing something?
I have a minidisc recorder, so the plan is to use that.
I think as long as the voltage doesn't go above 1.2V there shouldn't be a problem.
Does that make sense?
I just don't want to damage my minidisc recorder.
Thanks
Rather than use the correct kit, is there a way to make use of let's say an audio recorder, using the microphone input socket to record a pretty raw / rough digital signal, even if it's barely recognisable as a digital signal?
I don't really care about the quality at all.
I just want to do a live test on my car to prove there is some activity while driving.
I want to T into the wire that pulses a solenoid on the car, and record the live data.
Am I being silly?
I know when I open a WAV file for example in a WAV editor, that the sample rate is 44100 per second, so I presume that is the rate it can be recorded at if I use a the microphone input?
I'm even just thinking of winding a small diameter copper wire around the solenoid control wire that provides the pulses, and hopefully even a small inductive signal can be recorded.
I only want to know when the solenoid is being pulsed, and the duty cycle at the time.
Just before someone suggests OBD, I have no kit to do that and I don't really intend buying any.
I just want to know if my crude solution is feasible or am I missing something?
I have a minidisc recorder, so the plan is to use that.
I think as long as the voltage doesn't go above 1.2V there shouldn't be a problem.
Does that make sense?
I just don't want to damage my minidisc recorder.
Thanks





RE: quick and nasty datalogger
TTFN

FAQ731-376: Eng-Tips.com Forum Policies
Need help writing a question or understanding a reply? forum1529: Translation Assistance for Engineers
RE: quick and nasty datalogger
Dan - Owner
http://www.Hi-TecDesigns.com
RE: quick and nasty datalogger
It might work if the signal is a varible PWM signal to the coil.
But then, why not just connect a meter or light bulb or buzzer as already suggested to the wire to see if it turns on and off?
RE: quick and nasty datalogger
RE: quick and nasty datalogger
In any event, building the interface is going to cost you way more than $20 in parts and trips to Radio Shack.
Buy the datalogger.
Star to imcjoek.
Mike Halloran
Pembroke Pines, FL, USA
RE: quick and nasty datalogger
I have a 5 wire EGR valve.
2 wires go to the solenoid which gets a square wave pulse, as and when the ECU demands some pintel movement.
The other 3 wires are for feedback to tell the ECU the pintel postion, i.e. a 5V supply to a pot, a GND to the pot, and a signal wire connected to the pot's wiper.
I'm convinced there is some strange activity regarding the control of this valve.
I have attached my scope to the wire which pulses the solenoid, but trying to operate the scope and drive the car is proving a bit of a challenge.
Because the EGR activity is programmed for control under driving conditions, doing any testing while parked is a not very conclusive, since it's not so easy to remain at certain throttle positions for any real duration and since the engine speed v throttle postion v vehicle speed etc are all factors in the EGR's map, any stationary test would be pretty useless anyway.
I had hoped to be able to somehow simply record the square pulse, then take a look at it once I come to a halt.
I have a simple square wave generator which I hooked up to my sound card today and the result wan't too bad.
At least it looks a bit like a square wave.
The $20 device looks good, but 1. I'm not sure if 50Hz is adequate, and 2. I know absolutely nothing about how to use such a thing. I know absolutely nothing about UART and so on.
My main aim is to determine if the behaviour is consistent.
I think sometimes it works and sometimes it doesn't.
I want to just do some respetitive acceleration runs, recording the square wave pulses sent to the solenoid and then compare the different runs to see if there is any similarity.
I know for sure the solenoid is controlled by a PWM since I have seen it on my scope.
The attached image shows what I recorded from my square wave generator via my sound card today.
It did record symmetrical on the zero line, but it is just offset because I was messing with the DC offset and that's why it looks like it does.
I will give it a try soon on the car for real.
Thanks again
RE: quick and nasty datalogger
Note that your generator probably puts out less than 1V, while your solenoid signal is likely to be at least 12V, and possibly more if there's no snubber in the circuit.
Seems to me that the buzzer producing sound for the recorder is still a viable option.
TTFN

FAQ731-376: Eng-Tips.com Forum Policies
Need help writing a question or understanding a reply? forum1529: Translation Assistance for Engineers
RE: quick and nasty datalogger
RE: quick and nasty datalogger
Cheers
Greg Locock
New here? Try reading these, they might help FAQ731-376: Eng-Tips.com Forum Policies http://eng-tips.com/market.cfm?
RE: quick and nasty datalogger
RE: quick and nasty datalogger
RE: quick and nasty datalogger
I'm saying that the frequency of the data you need to capture is fairly low, you don't need huge sampling frequencies - in fact your real problem is that you can't record down to DC on domestic gear.
Cheers
Greg Locock
New here? Try reading these, they might help FAQ731-376: Eng-Tips.com Forum Policies http://eng-tips.com/market.cfm?
RE: quick and nasty datalogger
There's no particular reason to derive it from a high speed clock, either, but there has been a bragging rights race among autoEEs, so current ECUs have many more bits of bus width and many more MHz of clock speed than they actually need to stay ahead of an engine. ... which has the side effect that the PWM frequency _could_ be higher than the ignition frequency. ... or, not. Since we don't know which ECU or vehicle make/model/year is being monitored here, we can't even offer a decent guess.
However, even if a too-low sampling rate causes aliasing, it will still probably detect the _presence_ of EGR control valve command activity, which seems the logical next step.
>>>
I just want to do a live test on my car to prove there is some activity while driving.<<<
By the way, what does the official factory shop manual say is the next step in the diagnostic tree?
Is there anything wrong with the vehicle, or are you just poking around?
Mike Halloran
Pembroke Pines, FL, USA
RE: quick and nasty datalogger
The next logical step in my mind would be to determine if the intermittent problem is due to an intermittent electrical problem. Is it a intermittent break in the control pulse wire circuit to the solenoid, or an intermittent break in feedback signal circuit. Until I can do some live recording I can't really know very much more. If I see an intermittent problem on a wire, then I will try to T into the same wire up at the ECU to determine if the temporary interruption is outside the ECU or inside.
This might sound silly, but I don't even want to mention the make / model, because I'm not particularly looking for someone else to fix the car so to speak. That way I don't learn anything. I personally find I learn most by hands on experimentation. I could easily pay someone else to do that job, but my intention is to try to learn more about the bare bones of how these things work.
Thanks for your reply
RE: quick and nasty datalogger
I was only pointing out that there are lots of activities under the bonnet (hood) that occur many more times faster than engine speed, so that's why I was saying the 50Hz value calculated relative to mechanical frequency seemed irrelevant.
RE: quick and nasty datalogger
TTFN

FAQ731-376: Eng-Tips.com Forum Policies
Need help writing a question or understanding a reply? forum1529: Translation Assistance for Engineers
RE: quick and nasty datalogger
That said, an old cranky fellow not far from here rebuilds carburetors for a living. ... or maybe for beer money. So as to not waste his time, he insists on an MMO treatment before removal from the vehicle.
I.e., put a pint of Marvel Mystery Oil in the fuel tank and go for a drive. If it's going to work at all, the difference will be noticeable inside of 20 miles. That will mostly eliminate transient problems associated with dirt/gum/varnish in the fuel and air systems. ( No other fuel additive has ever made a detectable difference for me, and the difference that MMO can make, even in a fuelie car, is dramatic. I have no financial involvement in MMO; I wish I did. )
Shop manuals from the sixties are better for educational purposes, but even the modern ones intended for use by unskilled labor will contain some useful clues. Aftermarket books carried by, e.g. Pep Boys, are better than nothing, but not nearly as good as official factory manuals. Chances are yours is available at helminc.com. Buy the schematics even if they are separate/extra.
Oh. A Helminc manual will cost more than the typical college textbook, but you won't regret buying it.
Mike Halloran
Pembroke Pines, FL, USA
RE: quick and nasty datalogger
It turns out it is spot on as quick and nasty recorder. (See attachment).
I had the scope attached at the same time as the minidisc, so you can see they are both in agreement.
(If my scope had a bigger memory this thread probably wouldn't exist).
110Hz and 35% duty.
Prior to this minidisc test, I did grab a few shots from the scope while driving and recorded 14.1V, i.e. battery voltage.
So, before hooking up the minidisc I created a voltage divider to limit the minidisc exposure to 1V maximum.
You can see that I also put the probes on back to front, so the scope is showing a duty of about 65% while the minidisc 35%.
(When I recorded the 14.1V trace, the scope was connected correctly and showed 35% duty also).
The bottom right corner of the top trace from the audio file shows 0.092 seconds interval for the highlighted 10 cycles.
Now that I have established I can record an interpretable trace, it's time to get back out and see if I can see any correlation with regards the car's behaviour and EGR activity.
I also discovered I got an added bonus from doing the test, which sort of comes back to IRstuff's suggestion.
I had the earphones plugged into the minidisc during recording, so there is immediate feedback to the driver when the EGR is being pulsed.
Thanks for your input.
RE: quick and nasty datalogger
Furthermore, the source code for the datalogger is provided, and by removing the delays encoded in the source code, you should be able to run the datalogger at the maximum frequency of the ADC. Of course, that will severely limit the logging time. Since the ATtiny24 also has an analog comparator, one could code the logger to only collect when PA1 and PA2 detect a transition, and you can log a single counter value. This would substantially extend the logging time.
TTFN

FAQ731-376: Eng-Tips.com Forum Policies
Need help writing a question or understanding a reply? forum1529: Translation Assistance for Engineers