Just ask all questions here and I will answer.
I am actually working on help right now. If I put the buttons in I am more likely to actually get it working. About 5% has help currently. It takes a long time between updates, new features, tutorials, and then the help all from me. If someone knows how to do something, that I havent outlined somewhere, then make a tutorial on it. I am not the only one that can post in the Documentation section, but I am the only one that has to. Version 2 had no help buttons at all as was in my mind more clear but a PITA to use... And it crashed a bit, but that is a different story!
This new version will catch almost all errors. Usually the description part of the error is what you need to look at. Monitor Type Error has to do with the type of object you are trying to monitor is not valid. The types are usually Digital Output, Analogue Input, and Variable. There are others at some parts, but Monitor Type is like category. You probably didnt type it in all the way, or didnt input one. After selecting Monitor Type, then you can select the Monitor ID, which is the actual object to monitor which must be of the same type as in the Monitor Type part.
As for boolean interfaces, if you right click the node, then hit about a little tooltip should popup explaining it. I will make a quick thread about this later this week as well.
The interface for placing them isnt too funky once you get it down. It is a little odd at first maybe. Basically select the module you want by left clicking on the symbol in the toolbar. Then move it where you want. Left click and it gets placed. If you want to move it around after placing it, then left click it (no holding down) and move the mouse and place it somewhere else. If you want to connect 2 together, right click a node (node is the black circle things on a module) then left click another node and voila connected. That's it. Let me know if that doesnt help.
Also functions and "if/then logic" are different. Functions can be called from if/then blocks, but are sort of like macros. Something that is generically based and can be called over and over without overlaying the same modules over and over. Functions are external xml files that any skin can use and are seperate from the main XML file FusionConfiguration.xml. But an if/then statement is built into the main XML file and cannot be shared outside the skin file because it relies on specifics in that file only.
So for example, a function would be a voltage to temperature function for our temp sensor which is there. Now to use it, you make an if/then block that calls that temperature function. And you can call it for each of your temp sensors and use only 1 external function instead of copy/pasting the insides of that function inside the if/then many many times. Make sense?
Also to experiment with the software without a fusion brain, just put in some filler in the Add a Brain form where it asks for the ID. As long as it isnt blank, it will be accepted. But make sure to change it once you get the Brain or nothing will work!