Using your advice with the command stty I got to the point of seeing the raw traffic from the scanner with minicom. I put the command into the perl script and it doesn't complain about it but it errors trying to find readable codes. I will work more on it later.
I have been poking around and it looks like what I need is to find what PID coming from my OBDII port is the injector duty cycle/pulse width or something of the sorts. Looks like it should be there, but it is not published anywhere so I will need to find it .
The scanner I have can be set to monitor all parameters being spat out from the port, so I guess I would need to turn that on and log it and then decipher and eliminate until I could find what I need (assuming it is there somewhere). Might be a bigger job than I think.
That looks to be in line with what I was getting in windows with scantool. I haven't had a chance yet to log any data from the port, the thought of sorting through it all makes me squeamish .
I guess a good way would be to get a filter to get rid of any EPA set pid values and then sort through the rest to see what is available.
I am currently working on getting the computer set up to the point I can listen to something on the way to work. So that has taken higher priority for the moment.
No problem, I am doing my own contortions. One problem I am having is that the elmscan doesn't seem to "sync" or connect to the OBDII port. If the red LED is flashing, I am connected and ready to gather data. If the red LED is solid, then the PC is unable to connect to the elmscan. I can get the flashing red LED maybe one time in 30 connects (aka plug it into the car's OBD II socket). I submitted a ticket into the scantool support service.
I am hoping this freeware offers datalogging I can post-process, until I can (hopefully) get my own program running :