Now that I think about it.............this workaround WONT work because you still have no way of obtaining the value of the port in the monitor, that and it would seem that the threshold monitors only fire when it goes out of range (once) or when it goes back into range (once), which means even IF you could set a variable with the port's current value, it wont update...rendering that idea useless.....
i really hope shaun can find time to add an instance argument to the labelcode...
I spy with my little eye, reading analog inputs and having indicators on multiple brains :)
wait for it........
Guys im using BYRANGE to test numbers and execute certain things in my skin, how would i go about using live Analogue numbers coming from my air unit senders?
im confused a little bit on what direction, i have them as indicaters in my skin already, but how would i use them in my execTBL file?
SETVARBYCODE;MyVariable;RRFUSION_ANALOGINPUT;<brai n instance>;<brain port>;<input type RAW/VAL/OPT>
at least, that's how it's going to be shortly... right now there is no brain instance parameter in the analog input label code but will be shortly.
So sweet! i can finally see the finish line, im hoping i can install this into my ride, calibrate it and boom, running!! we'll see but!
but this brings me to the next question..
How do i calibrate this to read my airbag senders in psi.? so im guessing ill have to create a variable some how to read the 'RRFUSION_AnalogInput;1;Raw' and divide it by something to bring me into a .psi reading... how should i go about doing this..?
has someone done this? or should i do each one individually? guessing fill each corner to 200psi... read the raw format... and find a division till i get it sitting at a 200 result?
Thanks in advance guys, any help apreciated!
if you figure out the formula you need to convert raw -> psi i'll add it to rrfusion as a type.
Originally Posted by Ryann
i was under the impression some one had already acheived this?
i will try my best. altho i think each sender will be too inconsistent to come up with a standardised formula, we will see tho.
Ok guys so i have scrapped the idea of using the air senders.. moisture in the line and inconsistency in the air senders is just too much for my head to process... it was also more joints in the airline i was having trouble with as the smaller line fittings tend to be poorer quality. im now going to set up 4 potentiometers on suspension parts to get an accurate reading on each 4 side.
Seeing as these are 320deg PM's im really only going to use a maximum of 150deg is there anyway i can size the readings up and not lose accuracy? theres 1023 steps of resistance and ill at least half that...
heres a pic of what i will mount to chassis and build arms off to run to the suspension.
I need everyones feedback on v6 support. The com component for the v6 fusion brains requires .net4.0 to communicate. Being that RR is done in vb6 and i've gotten grief over forcing updates to higher versions of .net in the past should i just stick to the virtual com port method of talking to the v6 fusion brain? I guess the real question is would anyone disagree with RRFusion coming with a .net4.0 requirement?
Ah yes, the great .Net debate ;) Tough call, at some point, probably sooner than latter, that its gonna be required by something or another. And with the huge selection of fast carpc HW now a days, I think that the .Net debate is becoming more and more transparent. Well, that's just my thoughts on the subject, I know that's not what your looking for but it is feedback? :D