Thread: Fusion Brain Version 6 -- Beta Testing

http://www.fusioncontrolcentre.com/F...2011-04-12.zip

Ok, that is the alpha software. Keep in mind the last code changes are not optimized yet, so CPU usage is higher than it will be. Currently it uses 1% to 2% of my CPU, and I hope to get that down by a factor or two once I am at that stage.

Just download the zip, and open the FuseGL.exe. Right now there are two buttons. The first one will turn on output 0.10. The second one will turn off output 0.10. The first one's text value only changes when you click it. The second one changes any time the digital output changes. Take a peek in UserGUIConfig.xml as well as the included "FlyCompile_ButtonManipulationCodeTest.cs".

The framework all this is running on has taken me a very long time to write. But now that it is inplace, adding the actual elements should be so much easier. It has nothing in common with MDX.

Please just let me know if you can open it, and if the buttons do anything.

---------- Post added at 04:09 AM ---------- Previous post was at 04:01 AM ----------

Originally Posted by VegasGuy

Thanks for the update. I don't really know what the time frame is moving CF towards 4.0 and frankly am not sure what advantages it would bring at this point, but who knows.

Cheers!

VegasGuy

I wouldn't have a clue what their motivation would be, or if/when they would do it. But there is really no reason not to other than there might be compatibility issues introduced for little to no advantages in some code written in older styles.

FuseGL however is a different beast. When the Beta of Visual Studio 2010 came out early last year, I was all over it. I scrapped my previous efforts because of some of the newly introduced methods and advantages. And so FuseGL was born. Only last month was anything more than a black screen with some console output achieved. But all the work under the hood is codegasmic. It is amazing what a high level language can do.

At this point neither RRFusion or Centrafusion is ready for V6 really. I've got RRFusion talking to my v6 via the virtual serial port, but honestly i havent tested it enough to call it reliable with all of the existing functions of the software.

The zip you uploaded is working fine to me. I took a look at the .cs expecting to see some connection routines, but i'm assuming that is being done by one of the referenced .dlls in this case?

I was sort of waiting for the API connection routines to become public, but honestly the fact that the VCP allows bidirectional communication on the fly kinda makes me want to primarily support that method.

Originally Posted by Sonicxtacy02

At this point neither RRFusion or Centrafusion is ready for V6 really. I've got RRFusion talking to my v6 via the virtual serial port, but honestly i havent tested it enough to call it reliable with all of the existing functions of the software.

The zip you uploaded is working fine to me. I took a look at the .cs expecting to see some connection routines, but i'm assuming that is being done by one of the referenced .dlls in this case?

I was sort of waiting for the API connection routines to become public, but honestly the fact that the VCP allows bidirectional communication on the fly kinda makes me want to primarily support that method.

Yes the FB_USB_2011.dll is doing the work.

And the new USB protocol allows for bidirectional on the fly too. You can send only the digital output commands you want when you want, or never. And you can read the analogue inputs anytime you want, and whenever.

Code:

                byte[] _toSendArray = new byte[3];
                _toSendArray[0] = 0x21;
                _toSendArray[1] = (byte)(port_i++ << 3);
                _toSendArray[2] = 0x01;
                MainUSBClass.allFusionBrains[0].SendDataToFusionBrain(_toSendArray, 0x01);

                byte[] _allDigitalOutputReadStates = new byte[64];
                byte[] _allAnalogues = new byte[1024];
                MainUSBClass.allFusionBrains[0].ReadDataFromFusionBrain(ref _allDigitalOutputReadStates, 0x01);
                MainUSBClass.allFusionBrains[0].ReadDataFromFusionBrain(ref _allAnalogues, 0x02);

Note that you can read as many analoglue inputs past values as you want by using a larger buffer like 1024 instead of 64.

The reading and writing can be done asynchronously, but not at the same time. So you cannot interrupt a read to do a write.

---------- Post added at 11:41 AM ---------- Previous post was at 11:30 AM ----------

Also the *.cs file is being called from within a button. It shows that a GUI object can "own" it's own little code segment that does ANYTHING. In this case the GUI object is listening into an event that the Digital Output port raises everytime a new signal is received.

I believe this to be a much more free way of styling. Seriously, any object in the program can be passed into these little extra code files and manipulated. All settings and images are all derived from a single dynamic class and can be accessed by anything. I am a little stunned that I was able to pull it off.

So Sonic (and anyone else who has tried the *.zip), what sort of CPU usage did you get on what hardware? And did the button correctly turn on/off the LED?

New program: http://www.fusioncontrolcentre.com/F...011-04-12b.zip

Buttons work, top button turns the output on, bottom button turns the output off. It caused some memory "hard faults" according to resource monitor when the program started, and it has a little memory leak, slowly growing and growing. I don't do code, so I have no idea. At least there is something that turns on something else!

Update: http://www.fusioncontrolcentre.com/F...2011-04-16.zip

This one finally made public the most important part of FuseGL.

I will let you experiment for yourself. It is rough and limited in its current implementation, but workable.

Press F10 after the application opens to open up a world of awesomeness...

---------- Post added at 12:35 AM ---------- Previous post was at 12:30 AM ----------

Also I am guessing the memory leak you are referring to is the internal trace file. Does the "leak" continue to happen when you move the cursor out of the application area and leave it alone for a while?

The trace file will eventually do dumps to the HD periodically instead of piling it into RAM and waiting for the application to exit.

The memory faults on loading is because it eats RAM on startup. The program compiles and extracts itself, then decompresses thousands of internal files, links them, and compiles a few of them. This makes it powerful, but requires a bit more resources than "normal" to get going. However, if RAM is limited (like on a CarPC) it will be OK, just take a little longer. There will be more faults, but it will use the HD to store some of its extractions.

Update: http://www.fusioncontrolcentre.com/F...2011-04-17.zip

---------- Post added at 12:53 AM ---------- Previous post was at 12:51 AM ----------

Where you guys at?

Downloading now! Sorry, I'm deep in the middle of sound deadening the Lexus and my hands are bleeding It started raining again so I'll have some more time to test your software out.

---------- Post added at 12:24 AM ---------- Previous post was at 12:16 AM ----------

What am I supposed to be doing?? Pressing F10 lets me create a button that doesn't work, then stalls the program out and I have to exit. I was hoping for a PWM test method!

What else is it supposed to do?

Originally Posted by dscustoms

Downloading now! Sorry, I'm deep in the middle of sound deadening the Lexus and my hands are bleeding It started raining again so I'll have some more time to test your software out.[COLOR="Silver"]

No worries. Sound deadening a Lexus? They start uber quiet so you are going to make it silent I suppose!

What am I supposed to be doing?? Pressing F10 lets me create a button that doesn't work, then stalls the program out and I have to exit. I was hoping for a PWM test method!

What else is it supposed to do?

After you make the button, exit configurator mode by pressing F10 again. Once in config mode, you will be able to add/remove/configure things. Then things will "work" again once you get back to regular mode (F10 again to exit the mode). As long as you have graph lines, you are in config mode. (Or if you press G and toggle them on/off).

Right now you can only make a button that controls a digital output, but you can do it from within the program and while the program is running. Once you exit config mode, the button works without the need to reset or anything.