Printable View
I'm been expecting documentation in the style of the extensive amount that I see on the fusionbrainconrollcenter web site and haven't seen it.
I do see mini and maxi relay boards and signal-to-voltage board. All of which look pretty interesting.
Is there more documentation coming? What's left for this current Beta?
Hardware, it is not in beta. Software is. What type of documentation are you looking for?
Thought Fusion Brain Version 6 included hardware and software.
http://www.fusioncontrolcentre.com includes gobs of verbiage with pretty extensive FAQ and impressively zoomie words i.e "Fusion Control Centre" and "Uber MDX Edition"
The FAQ talks about:
"What makes Fusion Control Centre so special" and "is the most sophisticated piece of software in its class. Most software has a list of predefined actions that can be performed hard-coded in. However MDX is different. Three features make MDX different from other programs out there."
"The first and most noticeable of these is MDX's ability to be completely skinned."
"The second being MDX's fully programmable logic section."
"The most important of these features is the new voting system. Instead of buttons and logic evaluations turning on an output or performing any other action, it votes what it thinks should happen with an attached priority."
I may be missing key understanding related to Fusion Brain Version 6, but I don't see similar functionality. It appears that you have an API that is accessible through user C# code that is place in a file executed by your software engine.
I cannot tell how much of the functionality from Fusion Control Centre MDX and the FAQ verbiage is or will ever be available.
In the past I have written tons of 'c' code, but I did not budget that level of work here. I do not want to reinvent the wheel, but I do want to be clear what is(or will be) available to use and at a low level that would include API information that does not require reverse engineering.
Originally (and from all the web site verbiage), I had accepted that there was significant leverage-able functionality that would require minimal code to quickly explore various scenarios of reading analog signals, converting them to digital, display them in a web browser, drive relays etc.
Now, I cannot tell how much of the functionality from Fusion Control Centre MDX and the FAQ verbiage is or will ever be available. i.e "Three features".
Following this thread with much interest!
It does: http://www.fusioncontrolcentre.com/F...g/software.phpQuote:
Originally Posted by waltersaegir
All true for both FuseGL (new) and MDX (old).Quote:
http://www.fusioncontrolcentre.com includes gobs of verbiage with pretty extensive FAQ and impressively zoomie words i.e "Fusion Control Centre" and "Uber MDX Edition"
The FAQ talks about:
"What makes Fusion Control Centre so special" and "is the most sophisticated piece of software in its class. Most software has a list of predefined actions that can be performed hard-coded in. However MDX is different. Three features make MDX different from other programs out there."
"The first and most noticeable of these is MDX's ability to be completely skinned."
"The second being MDX's fully programmable logic section."
"The most important of these features is the new voting system. Instead of buttons and logic evaluations turning on an output or performing any other action, it votes what it thinks should happen with an attached priority."
All of that functionality is present because of the extensions via C# code. The only thing left to do with FuseGL is to add pre-built C# functions. But anything you want to do, is doable.Quote:
I may be missing key understanding related to Fusion Brain Version 6, but I don't see similar functionality. It appears that you have an API that is accessible through user C# code that is place in a file executed by your software engine.
All of it.Quote:
I cannot tell how much of the functionality from Fusion Control Centre MDX and the FAQ verbiage is or will ever be available.
You need 0 coding for displaying analogue values, sensors, turning on outputs and so on. To display them in a web browser would require a little coding in C# for FuseGL.Quote:
In the past I have written tons of 'c' code, but I did not budget that level of work here. I do not want to reinvent the wheel, but I do want to be clear what is(or will be) available to use and at a low level that would include API information that does not require reverse engineering.
Originally (and from all the web site verbiage), I had accepted that there was significant leverage-able functionality that would require minimal code to quickly explore various scenarios of reading analog signals, converting them to digital, display them in a web browser, drive relays etc.
Now, I cannot tell how much of the functionality from Fusion Control Centre MDX and the FAQ verbiage is or will ever be available. i.e "Three features".
Alternatively you can use RRFusion or CFFusion (written by sonic) to incorporate into RoadRunner or Centrafuse and use everything they have too.
We currently have no plans for RoadRunner or Cenreafuse. Does that leave us out?Quote:
Originally Posted by 2k1Toaster
Documentation is limited as it always has been. I try to put everything on the forums for it to be a growing deposit of documentation. I try to answer all questions via mp3car posts, email, and store contacts promptly.
Those are MDX specific features. So to answer for MDX, when you use the configurator everything you add is customizable. So when you put in a multi-image, or a static-image, or a button, or whatever you get asked for which images you want, where you want it, what text you want to display, and everything. (Point #1) If you look in the logic section you will notice lots of boolean, arithmetic, and conditional statements that can be "hooked" together to create whatever logic you want. (Point #2) Every "action" or "anti-action" (the gavel icon) has an associated priority with it. If one says turn on, and the other says turn off, the higher priority wins. If 2 say turn off, and 1 says turn on all with the same priority, it will turn off because of 2 vs 1. (Point #3)Quote:
Originally Posted by waltersaegir
For FuseGL, skinning is currently done via XML. This is similar to MDX, because the configurator only spits out an XML file that MDX reads. There is no external FuseGL Configurator, it is built in. And currently you can move things, add things, delete things, and resize things all within FuseGL live using the configuration mode. If you want to change the image itself, you need to specify it in the XML manually. It is all there, just not as accessible. The logic in FuseGL has been shifted from an XML logic structure as MDX used to raw compilable C# on the fly. This allows you to do anything you can do in the C# world (everything under the sun). It also allows for someone to make something (say Widget A that does Action X) and send that file around. All you do is add it to your folder and a line in your config file where you want to use it, and it is done. You don't have to copy/paste and insert hundreds of lines of XML anymore. It is also all reusable unlike the logic in MDX where everything is separated. Voting is no longer a requirement because things are done instantly, not only when the specified timer happens. So no two things can be done exactly at the same time because the CPU just doesn't work that way.
It is. But you don't have to. It is an option, and it is flexible.Quote:
Originally Posted by waltersaegir
Here on the forums, and by email. There is a wealth of info in this thread and in the announcement thread. If you have not pressed F10 in the program, then do so. It may help answer some questions.Quote:
Originally Posted by waltersaegir
Quote:
Originally Posted by waltersaegir
I am however working on the web control support for V6, so by the time you are ready, you may not need any coding.Quote:
To display them in a web browser would require a little coding in C# for FuseGL.
If you don't want to use RR or CF, then it leaves you out of plugins for them.Quote:
Originally Posted by waltersaegir
Clearly you've done a lot of good work. Now the challenge/task is understanding what/how is available.
Will FuseGL read (and use) MDX's XML output (or some part of it that could be cut/pasted into a file) and would this provide a modifiable base for skinning?
I think that I do understand that FuseGL has the capability of executing C# code on the fly, even though I'm not clear on the format and FuseGL API specific options.
If FuseGL is using XML, I would expect that there is capability to display in a web browser. I'm I correct (or close)?
FuseGL and MDX share no similar XML structures. So unfortunately there is no copy/paste/merging between the two different programs.Quote:
Originally Posted by waltersaegir
The format of the C# is fairly straightforwards and as you can see in this thread I try to provide C# when asked. If you ask "how do I do ________" I post how to do it as soon as I get a chance. There really isn't an API in the sense that you must adhere to strict guidelines and only certain things are accessible. Everything internal to FuseGL is accessible and everything built into C# is accessible.
XML is a data storage medium. You can open the XML in the browser, but you will just see static configuration XML.
So is FuseGL output accessible externally to FuseGL from HTML5-Java Script-XML?
Took a quick look at RRFusion. It looks to use fusionbrain_winusb.dll. Is that still viable or did I miss something?
Been a while since I tried FuseGL. Windows 8 didn't *seem to like it*. Sorry for the vagueness here. Maybe I just forgot how to install it.