I'll download the libraries and install tomorrow morning and give it a test. I did try to toggle bits, but did not see the box toggle to green, but I did not load any library, thinking that it was already loaded with Driveline because I seen several phidget files in the main Driveline_app folder.
I don't have anything connected to the Phidget yet anyways, just getting ready.
The library exposes the actual hardware and will have an icon in task bar, if you double click on it will bring up your phidget device with serial number ect. What Clockwork includes are the .net files for phidgets... i think :) SNO
Ahh.. Ok, so I really have not yet installed it, just plugged it into the USB hub is all. I'll keep you updated.
Yes then it will work for sure, I also sent you a pm. SNO
installed driver library, and tested operational in Driveline! Going to wire up footwell lighting next weekend.
Now I have a big feature idea... How much work would it be to add an "If" "Then" page assigned to Phidgets in the Driveline setup, where the "If"s are tied to a digital inputs X or XX or XXX switching High, "Then" turn on Digital Output Y and YY and YYY?
Like I could have an output from the Onstar operator or message sent to the Digital In, and Digital Output a relay to cut acc power to my sound processor, in effect muting so I can hear the onstar message. :phone:
And I can install an accelerometer and set it to trip at hard breaking, then the phidget could turn on footwell lighting so i can see if my bucket of KFC is all over the passenger side floor! :doh:
Are you running the most current build of Driveline rray? compulsivecode.com has the most current version to date. Alot of changes. SNO
I have the latest, it has Phidget analog input naming.
The skin files already support "IF ... ELSE ..." statements. Check out Skin_SkinEvents.XML (especially the end of the file). However, I haven't come up with a way to customize these through the UI. Every user would have very different (and sometimes very complex) conditions they want to program. I'll investigate some ways to make this easier, but I don't know if I'll ever be able to make it truly easy. I'll start looking at the Phidgets functionality a little more over the next couple weeks to see what could be added.
Originally Posted by rray
Regarding your flying chicken scenario, I will probably try to add a few variables into DriveLine for monitoring current G-Force and acceleration/deceleration so you wouldn't need a separate accelerometer.
That would be awesome to set a phidget to trigger digital output for say "going over 80mph", "decelerating too fast", "tire pressure too low", and stuff like that.
Mabe we can create a list of things that are trigger able like that.
Sent from my SCH-I535 using Tapatalk 2
I just bought an old beater of a motorhome, so who knows what I will need my phidgets to do now. My mind is racing thinking of all my possiblities with this rig. I will start a new worklog just for it. SNO