Printable View
Little off topic to the subject at the moment, but i just wanted to mention that the fusion brain v6 received a TON of interest at AFKFest. It was mentioned in my presentation as well as others ( I gave it the best improved product for 2011 :) ). Keep up the good work.
The message box worked. The box lost focus though so it was acting kinda strange as a new message box would pop up.
Is there anyway for FuseGL to run the startup events when the FB is connected after FuseGL has already started?
Awesome and thankyou! It's a high honour, and it means a lot. I am just really disappointed that I missed it this year. I will be there next year, I am committing now lol.Quote:
Originally Posted by Sonicxtacy02
Well the box wont necessarily have focus, but it will display in your system tray. It was just an example to show that it can work, not the way it should work.Quote:
Originally Posted by rEegLer
Startup events are run when the program is started, that's all. This is where you setup things to call later. For instance it is setting up an event that fires every so often, or that first when new analogue data is received or something like that. If you lock onto the new analogue value received event, then that will only be called when the FB is connected and it receives new analogue data.
So what are you trying to do (big and small pictures) and then I can try and point you towards the correct solution.
Yea I know, it was just confusing me because it seemed sporadic at first but then the realization came to me that they were being set out of focus and I have my taskbar hid as I have Rocket Dock.Quote:
Well the box wont necessarily have focus, but it will display in your system tray. It was just an example to show that it can work, not the way it should work.
Well first off, I haven't looked into yet but have you fixed the problem where FuseGL crashes when the PC comes out of sleep mode?Quote:
So what are you trying to do (big and small pictures) and then I can try and point you towards the correct solution.
My process order is this:
PC wakes from sleep, once windows has 'booted', FuseGL will be running (it was running when PC went into sleep), when FuseGL and FB are connected, output X will turn on to tell my audio amplifier to turn on, from there it will be reading various voltages (steering wheel, battery voltages...) and then logic will take out.
Off-topic question: Are you using darlington's or mosfets to switch the outputs? I know for V4 you have two darlington arrays.
I didn't realize it was a problem, I have never seen that. Does it happen every time, or some of the times?Quote:
Originally Posted by rEegLer
Ok, so you need it to be attached to the on-device connect action, not the startup event. There is a way to do this as I use it internally, I will just have to code up an example and make sure all those internal hooks are exposed properly. I get it now.Quote:
My process order is this:
PC wakes from sleep, once windows has 'booted', FuseGL will be running (it was running when PC went into sleep), when FuseGL and FB are connected, output X will turn on to tell my audio amplifier to turn on, from there it will be reading various voltages (steering wheel, battery voltages...) and then logic will take out.
V3 and V4 both use the ULN2xxx series which are darlington arrays. The V6 you probably have individual NPN darlingtons. I have a batch with individual FETs and I am putting those through the tests. I have sent a few of them out for others to test as well but I don't think they are "mainstream public" yet. The difference is these FETs only have a switching capability of 200-300mA instead of the 400mA-500mA the darlingtons can do. Still enough for the relays we sell, and I prefer the FETs as there is almost no leakage. But I know some people depend on using generic relays that take lots of umph to turn on, so I am debating whether or not to sell a "dash-1" product like the FBv6-1 which is the FET enabled device, and the FBv6 would remain the NPN darlington device.Quote:
Off-topic question: Are you using darlington's or mosfets to switch the outputs? I know for V4 you have two darlington arrays.
I had mentioned the sleep mode problem in a previous post but it works fine now.
In MDX, I just put in the config file that the default state was ON. Is there a simple way of doing this in the config file?Quote:
Ok, so you need it to be attached to the on-device connect action, not the startup event. There is a way to do this as I use it internally, I will just have to code up an example and make sure all those internal hooks are exposed properly. I get it now.
Also, where is the timer interval defined? Is it internal? I know I cab define the timer interval in the cs code you supplied but just replacing the parameter "how_often_in_milliseconds" with a numeric value but just wondering where that parameter is.
I altered the C# code you provided so that it works with in-between statements and message box's but I'm still confused on how to use the SendKeys method. Do I need to define ("using") anything? Or maybe give a program focus? I'm just manually giving Notepad focus so I would think that would be enough.
Sorry I keep posting but I can still only have one output toggled at a time. For example, If I toggle output 10 and then toggle output 1, output 10 turns off and so on. I thought this was addressed on a previous firmware update (I'm up-to-date on my firmware).
What does the action look like in your xml file for those buttons?Quote:
Originally Posted by rEegLer