I've been having a huge difficult time attempting to get the wideband working. I tested the power, ground and signal. I'm getting a wb signal, just can't get it to show up on the screen.
I have - APU1 + LC-1
It shows up on the channel 2 on the a/d data. What am I missing?
wideband, yet again
Moderators: Mangus, robertisaar, dex
This thread may help.
You need to add the A/D channels to your ADS/XDL definition.
They are listed here.
http://forum.tunerpro.net/viewtopic.php ... highlight=
You need to add the A/D channels to your ADS/XDL definition.
They are listed here.
http://forum.tunerpro.net/viewtopic.php ... highlight=
Create the ADX "Value" item on the correct offset (word or channel #) with the conversion numbers below.
The ADPAC external channels for the AutoProm are 10 bit so they use 1024 steps for a zero to 5 volt input signal.
Set the size for 16 bit value.
Use 15.04 AFR span/1024 counts = 0.0146875 +7.35
(Actual typed in box is "X*0.0146875 +7.35"
Gives 0-5 volt range of 7.35 to 22.39:1 AFR
WB controller is set for values of 0-5 volt output = 7.35 to 22.39 AFR
your reading will be correct.
The ADPAC external channels for the AutoProm are 10 bit so they use 1024 steps for a zero to 5 volt input signal.
Set the size for 16 bit value.
Use 15.04 AFR span/1024 counts = 0.0146875 +7.35
(Actual typed in box is "X*0.0146875 +7.35"
Gives 0-5 volt range of 7.35 to 22.39:1 AFR
WB controller is set for values of 0-5 volt output = 7.35 to 22.39 AFR
your reading will be correct.
http://forum.tunerpro.net/viewtopic.php ... highlight=
I've read that thread soo many times, practically have it memorized.
I don't know-
how to add the channel,
understand what (h/d) values need to be,
where to place this info into tunerpro.
I don't want to give up. What I need is a write up with pics on how to
add a generic channel.
I've read that thread soo many times, practically have it memorized.
I don't know-
how to add the channel,
understand what (h/d) values need to be,
where to place this info into tunerpro.
I don't want to give up. What I need is a write up with pics on how to
add a generic channel.
OK,
Do you have a copy of the S_AUJP V4 1026 from Moates site?
Its under custom biniries IIRC.
Look at the attached documents with the package.
In there is a document describing how to use the extra channels on the 7730 ECM and how to set them up in TunerPro (or other program)
It covers scaling etc and why the things work the way they do.
Your situation is the same as described only your ADPAC channels are added to the end of your current datastream.
So whatever the last number is ($8D has 64 items) you would add them in after that.
From my example on the post above, the numbers are there along with the ADPAC channels they relate to.
HTH,
Jp
Do you have a copy of the S_AUJP V4 1026 from Moates site?
Its under custom biniries IIRC.
Look at the attached documents with the package.
In there is a document describing how to use the extra channels on the 7730 ECM and how to set them up in TunerPro (or other program)
It covers scaling etc and why the things work the way they do.
Your situation is the same as described only your ADPAC channels are added to the end of your current datastream.
So whatever the last number is ($8D has 64 items) you would add them in after that.
From my example on the post above, the numbers are there along with the ADPAC channels they relate to.
HTH,
Jp
Send me your 61.adx that works for logging if you can't get this to work.
To add to the end of it all of the channels for the APU1
I see the 61 is 160 baud with 20 data items in the datastream.
This change will add 6 to the end of that.
Channel 1 = 23-24
Channel 2 = 21-22
Channel 3 = 25-26
Go to Aquitition menu...
Edit Definition...
Goto "Values"
Add new item ... (button at bottom)
Name it at the top
Give it another name in the Unique ID box (same name usualy works)
...
Units display = AFR
Packet offset = 0x15 hex or 21 decimal
Source data 16 bit
Range Low = 7.35 Range high = 22.39
Alarm Low = 11.0 Alarm high = 16.0
Go to "Conversion" Tab
Click on "Set" button
enter the equation
X * 0.014687 + 7.350000
Set output format to "Floating Point"
Set digits to 2
SAVE
That will get the item to work if it comes in with the datastream.
For the 61.adx definition
I'm not sure on the next part that makes the datastream larger to include the channels from the APU1.
Aquition..Edit definition..
under commands...
select the 160 baud item (that is its name on the file I have)
notice the parameter settings on the right side indicate it has 20 items as the "Payload Size"
(Mine aslo says "0" for the "Body Size")
I think the body size needs to be increased to 26 to while leaving the payload alone.
You'll have to experiment with that if it doesn't work right away.
I wouldn't do anything to the command setup until trying it out with just the value for the WB added.
LMK how it goes.
Jp
To add to the end of it all of the channels for the APU1
I see the 61 is 160 baud with 20 data items in the datastream.
This change will add 6 to the end of that.
Channel 1 = 23-24
Channel 2 = 21-22
Channel 3 = 25-26
Go to Aquitition menu...
Edit Definition...
Goto "Values"
Add new item ... (button at bottom)
Name it at the top
Give it another name in the Unique ID box (same name usualy works)
...
Units display = AFR
Packet offset = 0x15 hex or 21 decimal
Source data 16 bit
Range Low = 7.35 Range high = 22.39
Alarm Low = 11.0 Alarm high = 16.0
Go to "Conversion" Tab
Click on "Set" button
enter the equation
X * 0.014687 + 7.350000
Set output format to "Floating Point"
Set digits to 2
SAVE
That will get the item to work if it comes in with the datastream.
For the 61.adx definition
I'm not sure on the next part that makes the datastream larger to include the channels from the APU1.
Aquition..Edit definition..
under commands...
select the 160 baud item (that is its name on the file I have)
notice the parameter settings on the right side indicate it has 20 items as the "Payload Size"
(Mine aslo says "0" for the "Body Size")
I think the body size needs to be increased to 26 to while leaving the payload alone.
You'll have to experiment with that if it doesn't work right away.
I wouldn't do anything to the command setup until trying it out with just the value for the WB added.
LMK how it goes.
Jp
Ok, this is the part giving me issues. Where do I type in 23 or 24?JP86SS wrote: I see the 61 is 160 baud with 20 data items in the datastream.
This change will add 6 to the end of that.
Channel 1 = 23-24
Channel 2 = 21-22
Channel 3 = 25-26
Done this several times, never works.JP86SS wrote: Go to Aquitition menu...
Edit Definition...
Goto "Values"
Add new item ... (button at bottom)
Name it at the top
Give it another name in the Unique ID box (same name usualy works)
...
Units display = AFR
Packet offset = 0x15 hex or 21 decimal
Source data 16 bit
Range Low = 7.35 Range high = 22.39
Alarm Low = 11.0 Alarm high = 16.0
Go to "Conversion" Tab
Click on "Set" button
enter the equation
X * 0.014687 + 7.350000
Set output format to "Floating Point"
Set digits to 2
SAVE
That will get the item to work if it comes in with the datastream.
I'm going to keep playing with it a few more days. Check your pm's on thursday or friday.[/quote]
The PACKET OFFSET will be :
Channel 1 = 23 (decimal, enter in the second box)
Channel 2 = 21
Channel 3 = 25
SET THEM FOR 16 BIT
The values indicate a double byte so 23 and 24 are the 16 bit value.
If the "Value" you have defined doesn't show data then it might be something with the total packet size (I don't know how to properly add the APU channels to the datastream correctly)
Something with the "Body Size" and "Payload Size" and possibly adding to the "Timout (ms) settings to get the data out correctly.
Might even be something due to the 160 baud rate.
Magnus would be the best to throw a dart at that if it still doesn't work right.
Jp
Channel 1 = 23 (decimal, enter in the second box)
Channel 2 = 21
Channel 3 = 25
SET THEM FOR 16 BIT
The values indicate a double byte so 23 and 24 are the 16 bit value.
If the "Value" you have defined doesn't show data then it might be something with the total packet size (I don't know how to properly add the APU channels to the datastream correctly)
Something with the "Body Size" and "Payload Size" and possibly adding to the "Timout (ms) settings to get the data out correctly.
Might even be something due to the 160 baud rate.
Magnus would be the best to throw a dart at that if it still doesn't work right.
Jp