Evoscan Logging of Pin 8 voltage input on OP2?
Apr 4, 2011, 06:23 AM
#1
Evolved Member
Thread Starter
iTrader: (8)
Join Date: Apr 2003
Location: Georgia
Posts: 2,138
Likes: 0
Received 0 Likes
on
0 Posts
Evoscan Logging of Pin 8 voltage input on OP2?
Whats up everyone,
I submitted a support ticket to Hamish about this, but it seems he did not understand my question.
As some of you may be aware, with the Open Port 2.0 Stand alone logger, it is possible to log a voltage input on pin 8:
https://www.evolutionm.net/forums/09...0-pin-8-a.html
I have this working perfectly via the stand alone logger using the following config:
From the logcfg.txt standalone logger config file:
type=adc
paramname = AFR
paramid=8
;scalingrpn=x,0.001,*
scalingrpn=x,0.002,*,10,+
What I am trying to figure out is if you can setup evoscan to do the same thing as the stand alone logger, that is directly log a voltage input on pin 8 of the OP2 connector. Or to ask the same question in another way, what evoscan request id corresponds to pin8 on the op2 connector??
I submitted a support ticket to Hamish about this, but it seems he did not understand my question.
As some of you may be aware, with the Open Port 2.0 Stand alone logger, it is possible to log a voltage input on pin 8:
https://www.evolutionm.net/forums/09...0-pin-8-a.html
I have this working perfectly via the stand alone logger using the following config:
From the logcfg.txt standalone logger config file:
type=adc
paramname = AFR
paramid=8
;scalingrpn=x,0.001,*
scalingrpn=x,0.002,*,10,+
What I am trying to figure out is if you can setup evoscan to do the same thing as the stand alone logger, that is directly log a voltage input on pin 8 of the OP2 connector. Or to ask the same question in another way, what evoscan request id corresponds to pin8 on the op2 connector??
Apr 4, 2011, 07:48 AM
#3
Evolved Member
Thread Starter
iTrader: (8)
Join Date: Apr 2003
Location: Georgia
Posts: 2,138
Likes: 0
Received 0 Likes
on
0 Posts
Feel free to add to the support ticket then 
http://www.evoscan.org/helpdesk//tic...&Refresh=17007
It may not be supported currently, but perhaps if we get enough interest.......
http://www.evoscan.org/helpdesk//tic...&Refresh=17007
It may not be supported currently, but perhaps if we get enough interest.......
Apr 4, 2011, 06:22 PM
#4
Evolved Member
Feel free to add to the support ticket then
http://www.evoscan.org/helpdesk//tic...&Refresh=17007
It may not be supported currently, but perhaps if we get enough interest.......
http://www.evoscan.org/helpdesk//tic...&Refresh=17007
It may not be supported currently, but perhaps if we get enough interest.......
Rich
Mar 25, 2012, 03:07 PM
#6
Super Thread Necromancy... GO!!!!
Did this ever happen? I've got it working with the standalone method, but I'd like to be able to have access to it in EvoScan as well. It would just simplify a lot of things, since it seems some of the logcfg addresses don't exactly match up with the addresses in the xml definitions on EvoScan for a couple of things (for me anyway, but I'm also a noob)
Did this ever happen? I've got it working with the standalone method, but I'd like to be able to have access to it in EvoScan as well. It would just simplify a lot of things, since it seems some of the logcfg addresses don't exactly match up with the addresses in the xml definitions on EvoScan for a couple of things (for me anyway, but I'm also a noob)
Mar 25, 2012, 07:41 PM
#7
Evolved Member
Addresses are addresses - it doesn't matter if Evoscan or OP2.0 requests the data.
There are format differences, sure... like there's a "23" in front of 'em for Evoscan, and an 0x in front of 'em for OP2.0.
But it all comes down to the addresses in the end. If you ask for data at the same address, interpret it as 1- or 2-byte data, and scale it the same... it'll give you exactly the same information.
Rich
There are format differences, sure... like there's a "23" in front of 'em for Evoscan, and an 0x in front of 'em for OP2.0.
But it all comes down to the addresses in the end. If you ask for data at the same address, interpret it as 1- or 2-byte data, and scale it the same... it'll give you exactly the same information.
Rich
Trending Topics
Mar 25, 2012, 07:56 PM
#8
That's kinda what I figured. I actually used that concept to add STFT and MAFvolt values into my logcfg based on the requested addresses from EvoScan but switching the 23 with 0x.
My issue was that I just wasn't sure how to convert: "paramid=8" into something useable by EvoScan, would I just put an "8" in request id when adding a new data item to EvoScan? That just didn't seem like it would be right, I figured there would be more to it.
I also need to figure out why EvoScan gives me valid MAFv values but the values are off in Standalone mode, even though I used the exact same equation from EvoScan in my logcfg; but that's an issue for another thread
My issue was that I just wasn't sure how to convert: "paramid=8" into something useable by EvoScan, would I just put an "8" in request id when adding a new data item to EvoScan? That just didn't seem like it would be right, I figured there would be more to it.
I also need to figure out why EvoScan gives me valid MAFv values but the values are off in Standalone mode, even though I used the exact same equation from EvoScan in my logcfg; but that's an issue for another thread
Last edited by 03chi-town0Z; Mar 25, 2012 at 08:07 PM.
Nov 14, 2012, 01:45 AM
#10
Evolving Member
Join Date: Nov 2009
Location: Sydney, AUS
Posts: 197
Likes: 0
Received 0 Likes
on
0 Posts
^This. Bump for more info. Has anyone been successful with logging data off Pin 8 on the OP2.0. I need to log my AEM Failsafe Gauge asap and this method would be the best option for me.
Feb 23, 2014, 01:43 PM
#12
Did any one ever get this working?
I went ahead and tried putting in 12 (im using tip of 3/32 jack which maps to paramid of 12) for request ID, but it never read anything.
I have this working with standalone, so I know the wiring and scaling are correct, just not sure how to get evoscan to look at the openports ADC outputs.
I went ahead and tried putting in 12 (im using tip of 3/32 jack which maps to paramid of 12) for request ID, but it never read anything.
I have this working with standalone, so I know the wiring and scaling are correct, just not sure how to get evoscan to look at the openports ADC outputs.
Mar 14, 2014, 05:13 AM
#14
Newbie
Join Date: Apr 2012
Location: Australia
Posts: 33
Likes: 0
Received 0 Likes
on
0 Posts
Alternately you might consider using a DLPIO8. Apparently it works; see here and here
I really don't like digital gauges, much prefer analogue. Unfortunately analogue wideband gauges outputting serial data streams that suit Evoscan don't seem at all common. All I could locate that fitted the analogue gauge/RS232 output stream specification was an Innovate G2, G3, G4 or G5 gauge with LC2 controller. I ordered one in spite of some disquiet on this forum and others about reliability and lack of support. I hope mine is OK when it arrives and continues to operate OK.
Too bad I didn't find it (DLPIO8) before ordering the Innovate gear. In addition, 8 channels means that 7 channels could be used for other sensors. I'm thinking that wastegate displacement would be a very interesting plot if I could find a low cost (not $200+) linear sensor.
I really don't like digital gauges, much prefer analogue. Unfortunately analogue wideband gauges outputting serial data streams that suit Evoscan don't seem at all common. All I could locate that fitted the analogue gauge/RS232 output stream specification was an Innovate G2, G3, G4 or G5 gauge with LC2 controller. I ordered one in spite of some disquiet on this forum and others about reliability and lack of support. I hope mine is OK when it arrives and continues to operate OK.
Too bad I didn't find it (DLPIO8) before ordering the Innovate gear. In addition, 8 channels means that 7 channels could be used for other sensors. I'm thinking that wastegate displacement would be a very interesting plot if I could find a low cost (not $200+) linear sensor.
Thread
Thread Starter
Forum
Replies
Last Post
evoscan
Evo X Engine Management / Tuning Forums
52
Jun 20, 2017 01:46 AM
xPRimNT
Evo X Engine Management / Tuning Forums
239
Jun 2, 2016 10:40 PM
