RomRaider

It's still on my list.

Oh add me to the list too

I was worried about the power consumption from the sensors i was adding to the phidgets but heh it turns out they all use about 1.5-3mA. Total max consumption allowed for my 8/8/8 board is 400mA.

Cheers for working on this dschultz
Mario

Here's a sample display of the custom settings users can define for the Phidget InterfaceKit inputs. This should be available in the new release of RomRaider.

Converter Dialog (Plugins menu Phidget InterfaceKit)
Expression - can be any basic math equation which uses one variable 'x' as the raw data value from the sensor input.
Format - defines how the value will be displayed.

• #0 - means display with no decimal places
• #0.0 - means display with one decimal places
• #0.0000 - means display with four decimal places

Units - is the unit of measure for the real value (Alt-0176 can be used to enter the degree '°' symbol)
Min - is the minimum value expected (this can be negative if needed, as in -40°F)
Max - is the maximum value expected
Step - is used by the Dial gauge display to draw the major tick marks on the dial. Typically step is (maximum - minimum)/10

After setting the values press Save. You will need to un-select, re-select any Phidget item currently being logged to reset the units so the new value can take affect. You also need to load and resave any logging profiles with the Phidget items in them as the old units will not match the new units defined.


Externals Tab listing
A 'raw value' converter will be appended to the user defined converter for convenience.


Dial Gauge Display

Dschultz that is awesome man, thanks for all the hard work. This opens up alot for peeps using RR.

If you need me to test ill do it with my current setup as i currently log my phidgets, BUT have to manually convert after the fact, quite tiresome when on the side fo the road tuning when you do it 100 times..

Hi Dale.

Ok i have tested and it's like 98% there .

I have managed to change the expression, format's, min/max and the step value and all is 100% working. Logging is working like a dream once your unselect and re-select your logging parameter.

One problem i am having is that when i put in my expression for the calc the value is 0. I am using my phidget device to measure my AEM wideband failsafe device V to AFR.

This is my expression
2.375(x*0.004998779296875)+7.625 and the value it gives is 0

If i eg use (x*0.004998779296875)+7.625 the value displays correctly although wrong due to my afr calc.
and
If i eg use x*10 the value displays correctly although wrong due to my afr calc.

So im not sure if the field length for expression does not cater for such a long value\calc but when its my lengthly expression it does not work. Or is there any other format i should put my calc in?

Other than than everything else is spot on. Well done its awesome. I hope you know what this opens up for the RR comunity wrt sensors and logging. Basically anything external sensor wise can be converted and logged. Its great.

See my attached screen dumps and log created with values.

Instead of:
2.375(x*0.004998779296875)+7.625

Why not try:
2.375*(x*0.004998779296875)+7.625

or better yet, this:
x*0.0118721+7.625

I did try 2.375*(x*0.004998779296875)+7.625 but let me make sure as it might not have updated . Otherwise ill change to x*0.0118721+7.625.

Will let you know soonest..

This works for me. Your original version does not work so you need that *.

This is the cleanest equation to use.

Ok all works correctly, i might have not updated it correctly the first time. Either work.

I did a log with my LM2 and Aem Wb02 and pretty much tie up perfectly. Thanks so much for this.

Just to add something that might be of interest, i use the af Ohm val to keep a check on EGT's as i find this pretty accurate wrt to temps. Would it be possible to add a scalling or value on a logging parameter that is not from a phidget... Or should i just add the multiplier in the logger def file, would that work or be easier..

ie First generation Denso AF sensor resistance vs EGT ( under low to zero heater current )
25-24 Ohm 23-22 Ohm 20-19 Ohm
810-830°C 830-840°C 850-860°C 1600F (871C). MAX


Anyway thats another topic but you are the man Dale this stuff is awesome and so usefull, i need to order a bigger phidget now..

Kind Regards

One thing I did notice when updating any of the values on the Phidget dialog is that you *need* to tab or click out of the field you are editing or the new value will not get written to the underlying table model and just clicking save will not read the new value.

You could enter an additional conversion entry of your own to the logger.xml for that AF resistance parameter to convert ohm to ECT in °C. For the values you indicate use a formula of: -8.0124*x+1012.6

Edited my logger.xml and it now displays Egt temp. Tx alot

Now that this all works i am going to connect my ks4 in conjunction with my Wideband(AEM) to my phidget device, I know someone asked the question 'could i log ks4' on another post.

I will post my log with results if anyone is interested. I am keen to see the difference between the Oem knock sensor picking up knock compared to a external aftermarket knock sensor device like the phormula Ks4 in side by side columns. During tuning my Ks4 seems more sensitive and acurate to real knock.

Regards

I've submitted this plugin idea to the do something cool with Phidgets contest.

https://www.facebook.com/pages/Phidgets ... 5308506335
First day of Voting: September 23, 2013*
Last day of Voting: October 7, 2013*

Cool i'll be voting.

Hi guys,

I found this a while ago and thought it was pretty cool and I finally installed everything today. Given the amount of components and steps to make this work, I was impressed to see it work first try.

I haven't plotted the voltage/lambda curves but are they linear ? I read a little lower in AFR in romraider than I do with the gauge software itself maybe .3 or .2 at 14.7.

Are you guys pretty bang on with the equation at the bottom around 14.7 ?

Thanks