For that to work you need additional hardware to intercept, integrate, and re-transmit the data back to the proper software on your laptop.īack in the old days all of your hardware had jumpers that had to be manually switched into different configurations for each new piece of hardware to function without conflicting.
I'm in above my head here, but I think what they have been discussing is that the ALDL data stream your vehicle can understand does not support extra information being transmitted simultaneously. Six_Shooter wrote:The part I don't understand is that there are extra A/D inputswhen using an AutoProm, so why can't the same thing be done with a stand alone ALDL cable? Unless I misunderstand the issue that you're suggesting I fix. This is how TunerPro detects the AutoProm, Flash & Burn, Romulator, etc. The other devices that you mention have specific commands that can be sent to identify the device. Plugging the cable into a vehicle with the key on can cause errant data to be present before the echo. The "test" button in TunerPro simply sends data out and looks for the echo - a property that exists only because the tx and rx lines are tied together for GM ALDL interfaces. I don't have this issue with my printer, USB mouse, TunerCat OBDII, EFI Live or Innovate LC-1 WB?įixing what issue? The difference between an ALDL cable and all of the devices you mention above, including your AutoProm, is that the ALDL cable is a passthrough device it doesn't have any defined communication scheme, so there's no way for software to truly detect the device. Somehow fixing this issue would be the best thing TunerPro could do, more importantly for new users. For some reason it will be 2 of the three USB ports on my laptop. With my AutoProm set to find on startup I know real quick if I'm plugged into correct USB port. End-user must tie the data source defined in TunerPro settings to the data source defined in the ADX.
What should this UI look like?ģ) End-user loads ADX that pulls from multiple sources. For instance, source 1 is ALDL, source 2 is A/D BoxĢ) End-user plugs in his devices, and in TunerPro settings, assigns COM ports to data sources. Keep in mind that virtual COM ports (such as those used for USB devices) will be different for different users, and can even be different for the same user if the user plugs the devices into different ports each time.ġ) Definition author creates ADX that pulls data in from two sources. I'm willing to implement multi-port data acquisition in TunerPro if you (or Mark) can come up with a good UI design that makes it not-so-confusing to the end-user to tie a particular input to a particular COM port, as defined in the definition. You're right that doing this would, at the moment, require a plug-in to pull in the data from both sources, combine them, and return them to TunerPro. Just hoping for an easy fix with the stuff I already have available. If all else fails I can probably wire my wideband into something I can log that is not being used.
#RED DEVIL RIVER ALDL CODE#
I downloaded the DataQ SDK and peeked inside for info, but it was just the stuff someone would need to code it in to their own application. I have no idea how hard it would be to implement. I'm hoping that there is a way to use it with Tunerpro too. I've used Binary Editor and Calcon in the past on my Ford vehicles and both support extra information from a DataQ box that I already own. I'm trying to find a way for Tunerpro to log the car from an ALDL source and add in the data from a second source that is already being delivered to the laptop. That setup was incorporating external channels in to a single ALDL data stream. I read over that article in my previous searches, but it looked to me like it required some kind of Moates hardware that was emulating an eprom. Moates had some A/D ports to wire into your cable. EagleMark wrote:This will help you get going: