*NEW* USB Input/Output Board -- Fusion Brain

[2k1Toaster]

Sure go for it 2k1Toaster.

BTW, send me the source and blah blah since it seems the program has changed some since the last time (3 weeks) u sent me the latest one.

David

No, you didn't miss anything.

I just havent gotten around to posting it. I will put it on the website in the next few minutes and post a link.

Please keep in mind that this software is still beta. Pretty much 2 day old beta, before it was alpha. Being such, there are things that still need tweaking, and things that don't work, but show up as options.

Things that work and dont work, or are not implemented as of now:
Everything for the digital outs except being able to tie them together. This will come later. Basically you can control all the outputs to be either of or on at your beckon call and also make animations for them as of now. What does not work, or even begin to exist is for example pushing output 1 which is tied to output 2 so with 1 press, they both go on. and 1 press they both go off. This might be useful in led animations where you want it timed perfectly and easily.

Right now the analogue ins will show and display all their values correctly. The graphs are still a work in progress. Some work, some dont.

Also the temperature sensor is set to the MCP9700 right now so if you have the MCP9701, you will have to wait another day or so to get proper readings because that is not coded. It will display the temperature, but will be off by some factor.

Also the biggun. The API sending is not done. I've been having trouble figuring out how to send keystrokes to an application through windows api... Basically it is a horror. And I do not have, and cannot find Spy++. THe other I have tried crash and burn, or display nothing. So it is a slow process trying to figure it out.

Also the OSK right now has a button for -/: and soon it will be -/+ because the colon is a string parser right now, so the use of "::" will reak havoc, so that option will go away. So for now, stay away from double colons.

Also, the skin file cannot yet change the location of buttons. But it will very very soon. So within the next day or so as well.



Alright, and some things to mention, the speed at which the outputs update and the analogues update are user settable in the FusionForm.skin file. Look in the >>MAIN section and it will be quite obvious. If you have questions about what those things in the skin do, go ahead and ask, and I will try to respond fast.

Also please be advised that after you change a setting in the config page, you must click save for the settings to take effect.

So this should be enough to wet your pallettes, and to figure out the basics of the program. So start making some skins, and showing off to your friends! You now hold the power of a thousand suns! (Well beta-suns)

Fusion Control Centre Beta Version 0.2
http://www.fusioncontrolcentre.com/S...L_Beta_0.2.zip

How about the driver?

Here you go: http://www.fusioncontrolcentre.com/S...on_Drivers.zip

Ok, new update to the program: http://www.fusioncontrolcentre.com/S...2024-04-07.zip

Just replace the current *.exe with this one.

Changes for 24-04-07:
* Graphs now work again
* Took off protection timer for analogue timers. Now you can update at a theoretical 1mS interval. This is getting us around 17 kilobytes a second in data transfer. Which is more than enough resolution.
* Added some program protection.

More updates will come soon.

Those links are for the driver, main program with all the images and everything, and then the last exe is just to replace the current one in the first zipped file because it has some updates. It is a direct replacement.

I have another exe I am testing now that WILL NOT BE compatable with the userconfig.atom file, so with the newest exe hopefully coming in a day or two, you will either need to manually edit the userconfig.atom file to the correct string defaults, or delete those files, and redo the config. Just a heads up.

[greenman100]

Any other hardware bug reports? How are the sensors/relay working?

[P3D4T0R]

Well... I figured tonight since I wasn't tired I would work some more on this and while I was planning on how to mount it into my car I accidentally crossed to power wires and fried the voltage regulator. I was able to replace it with an equal alternative (non surface mounted) but I fear I may have fried the PIC because it is recognized by the computer but windows device manager says that the device has failed to start... I may be out of the beta testing before I could even really get a good test done on the software...

[2k1Toaster]

Well... I figured tonight since I wasn't tired I would work some more on this and while I was planning on how to mount it into my car I accidentally crossed to power wires and fried the voltage regulator. I was able to replace it with an equal alternative (non surface mounted) but I fear I may have fried the PIC because it is recognized by the computer but windows device manager says that the device has failed to start... I may be out of the beta testing before I could even really get a good test done on the software...

Holy crap!

Well we have version 2 of the firmware being shipped to you guys really soon. So you get a new PIC with that. You are supposed to return the old one, but we'll figure something out.

Now by crossing power wires, do you mean you hooked up the + to the - and visa versa, or did you just short some pins somewhere? We might be able to implement some protection...

Just to give some other stories too:

Both Tim and I have accidentally shorted the +12v to ground, and when I did it, my heart skipped a beat and the PIC shut off. Unplug/Replug and worked like a charm. I have accidentally shorted the +5v to ground, and same sort of thing. Then my board also fell off the table, did a George of the Jungle swing into the open +12v line from the hacked ATX PSU I am using. Nice spark and a black spot on the bottom of the board. Wiped it off, and it was all fine again afterwards.

So basically Tim and I have put these boards through hell, and they seem to work ok. Sorry for your bad luck...

[JC-S60]

Haven't been following lately but it seems this is a great product! Nice work!

Joachim

[Focal]

hey one thing i was wondering? maybe it could be added...


ok lets say output 1 (in my case will turn on supercharger) my system uses a electronic clutching system to activate/deactivate.

so say when you press "Supercharger" button an audio file opens *but doesn't interrupt what musics playing* and plays a WAV recorded something like "Supercharger Engaged Please Disengage Clutch Maintain Less Then 2 Thousand RPM" and lets say set a delay of 7 seconds, and lets say the recording was 7 seconds and at the last second it says "Engaged" and BOOM its on. after then when I Un-click it(turn it off), could it play another WAV file like "Supercharger disengaging, please disengage clutch and maintain low engine RPM's"

is this a feature anyone else would thinks cool?

[P3D4T0R]

Holy crap!

Well we have version 2 of the firmware being shipped to you guys really soon. So you get a new PIC with that. You are supposed to return the old one, but we'll figure something out.

Now by crossing power wires, do you mean you hooked up the + to the - and visa versa, or did you just short some pins somewhere? We might be able to implement some protection...

Just to give some other stories too:

Both Tim and I have accidentally shorted the +12v to ground, and when I did it, my heart skipped a beat and the PIC shut off. Unplug/Replug and worked like a charm. I have accidentally shorted the +5v to ground, and same sort of thing. Then my board also fell off the table, did a George of the Jungle swing into the open +12v line from the hacked ATX PSU I am using. Nice spark and a black spot on the bottom of the board. Wiped it off, and it was all fine again afterwards.

So basically Tim and I have put these boards through hell, and they seem to work ok. Sorry for your bad luck...

Ha, That nice to know for future reference but unfortunately for me it was + to - and - to + and I then that all to familiar smell of burning electronics (no smoke this time though). I tested with my multimeter on the voltage reg and it was giving out like 0.3v or something like that so i replaced it (Ill post a pic later). I took the PIC off to check to see if their was any damage to it and both the to and the underside appear fine with a slight smell of burnt electronics to it. So, I put it back on reapplied power and the USB and now my computer doesn't even see it I hope the new PIC's you send out fix this...

[2k1Toaster]

Ha, That nice to know for future reference but unfortunately for me it was + to - and - to + and I then that all to familiar smell of burning electronics (no smoke this time though). I tested with my multimeter on the voltage reg and it was giving out like 0.3v or something like that so i replaced it (Ill post a pic later). I took the PIC off to check to see if their was any damage to it and both the to and the underside appear fine with a slight smell of burnt electronics to it. So, I put it back on reapplied power and the USB and now my computer doesn't even see it I hope the new PIC's you send out fix this...

Well as long as you are still getting a nice 5v in, and the traces didn't melt or anything, it should be ok. You may have blown the LED's as well with that much reverse voltage, but they are in parallel to the outputs. So if you did blow an led, the actual relay drivers will still work. The relay driver chips (2 smd by the outputs, uln2003) should have enough protection for a short burst. But not a sustained reverse voltage.

Also the fuse on the board, may very well have just done its job, and heated up really high. It may not have though because I dont think it was meant to protect reversed, just excess... But try again tomorrow after it has a chance to cool off.

And while you are waiting for a new PIC, might as well, work on the software, or check the board for trace damage or something!

And please do answer Focal's question. Basically how many people want the ability to play custom sound files when a button is clicked? 1 for the ON state and 1 for the OFF state. Settable in the skin file?

Well I am off to bed, so goodnight everyone.

[2k1Toaster]

Oh, and I guess since both you and turbocad soldered onto the board, we need to know who did it first! Who was the first Fusion hacker?

Maybe I will make a portion of the website for "Hacked Brains" and you guys can post your picts of them.

[P3D4T0R]

hey one thing i was wondering? maybe it could be added...


ok lets say output 1 (in my case will turn on supercharger) my system uses a electronic clutching system to activate/deactivate.

so say when you press "Supercharger" button an audio file opens *but doesn't interrupt what musics playing* and plays a WAV recorded something like "Supercharger Engaged Please Disengage Clutch Maintain Less Then 2 Thousand RPM" and lets say set a delay of 7 seconds, and lets say the recording was 7 seconds and at the last second it says "Engaged" and BOOM its on. after then when I Un-click it(turn it off), could it play another WAV file like "Supercharger disengaging, please disengage clutch and maintain low engine RPM's"

is this a feature anyone else would thinks cool?

I personally probably wouldn't ever use something like that but I can see a valid reason for adding it plus the WOW factor, so Id say add it if its not to much trouble.

Oh, and I guess since both you and turbocad soldered onto the board, we need to know who did it first! Who was the first Fusion hacker?

Maybe I will make a portion of the website for "Hacked Brains" and you guys can post your picts of them.

Not sure who was first, I guess I did my first soldering yesterday (04/24/2007) to fix that short in the leads. When did you start turbocad? Id be willing to bet you beat me... A section of the site with "Hacked Brains" would be sick, plus it would also make me want to hack it just to post pictures :P