Thread: RRFusion- My Fusion Brain plugin for RR

What's the current status of this? Sonic's site appears to be down.

sorry guys my sites down for good and i've been goin thru some CRAZY stuff with my move.. but RRFusion is still active and there is a new version very much ready for action. Bare with me a few more days and i'll release the V4 compliant version.

Thanks for the update.

Forgive me for asking, but at this point in RRFusion's development, can buttons to control the FB be placed in RR skins alongside normal RR buttons? After reading the whole thread and doing some searching, the answers I found for this question all seemed to be a couple years old.

yes the buttons for RRFusion can be skinned and placed anywhere on a skin as long as the plugin is enabled. They work just like standard RR commands.

Fantastic. I got my relays and GM vacuum solenoid manifold last week, my FB should come this week. Needless to say, I'm excited.

Originally Posted by wrxyboy

Any updates on when the update will be posted. Thanks

Nope.. oh wait.. check post 1


NEW VERSION RELEASED!

I know its taken awhile but i'm all moved in and internet connected. The moving nightmare is OVER. So now i present RRFusion 3.0. Anyone thats used RRFusion prior til now will notices some changes that may affect .skin files. The primary changes from old versions is the change of the DIGITALOUT#TOGGLE command. This command is no more! Instead change your skin file to incorporate DIGITALOUT#;TOGGLE. Change was done to incorporate new control options. More on this later.

The other change from previous versions is the removal of FBAUTOCONNECT. The plugin no longer looks for this variable upon start. My suggestion for those who want the FB to connect when RR starts is to place FBCONNECT into the ONSKINSTART event in exectbl.ini. If you have a bunch of commands in that EVENT i suggest you place FBCONNECT on the end of the command chain.

Now for the additions/improvements. First and foremost the plugin is now V3 and V4 FB compatible. All thats required is using the fusionbrain_winusb.dll drivers. If you dont have these read up in the FB forum about them. I've also added the analog INS and digital OUTS for V4. Using these with a V3 FB will do nothing. No harm no foul. I've also added 2 NEW control options in addition to DIGITALOUT#;TOGGLE. First there's DIGITALOUT#SWITCH;<SECONDS>. This turns on the digital output for a user-specified amount of time then turns it off automatically. Then there's DIGITALOUT#;HOLD. This command controls digital outputs like momentary buttons. It requires the command DIGITALOUT#;RELEASE to turn the output off. So in your skin an example button would read:

Code:

B,X,X,X,X,"DIGITALOUT0;RELEASE",&DIGITALOUT0;HOLD&

See skin commands for more info on the new buttons. Also see the new .skin files which show each of these options at work. Thats all for now i believe! Hopefully this will be the last SINGLE INSTANCE version released.

Fantastic sonic! Been waiting for this! I will give it a try in the next day or so and let ya know how it went.

Well that was fast huh? What can I say, have been waiting for this plugin for some time heheh

It's a strange coincedence, as I just installed the FB yesterday, and started tinkering with it again. Its a fresh OS install, with the latest FB software as of yesterday, so the drivers and such are all up to date, and no old drivers were on the system to interfere.

Loading the fb.skin, I am getting a connected indicator now, and can see the values of the inputs, as well as control the 2 relays I have hooked to it.

The problem comes in when trying to use the momentry buttons that you just added. When I try to press and hold one of the momentary buttons, the relay clicks, and then I get a .net error. I have to ctrl-alt-del RR to be able to use the computer again.

Here is the error log that the error reports:
(I bolded what appears to be the problem in the code)

Code:

See the end of this message for details on invoking 
just-in-time (JIT) debugging instead of this dialog box.


************** Exception Text **************
System.InvalidCastException: Conversion from string "release" to type 'Double' is not valid. ---> System.FormatException: Input string was not in a correct format.
   at Microsoft.VisualBasic.CompilerServices.Conversions.ParseDouble(String Value, NumberFormatInfo NumberFormat)
   at Microsoft.VisualBasic.CompilerServices.Conversions.ToDouble(String Value, NumberFormatInfo NumberFormat)
   --- End of inner exception stack trace ---
   at Microsoft.VisualBasic.CompilerServices.Conversions.ToDouble(String Value, NumberFormatInfo NumberFormat)
   at Microsoft.VisualBasic.CompilerServices.Conversions.ToDouble(String Value)
   at RRFusion.Form1.Timer2_Tick(Object sender, EventArgs e)
   at System.Windows.Forms.Timer.OnTick(EventArgs e)
   at System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
    CodeBase: file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
RRFusion
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/Program%20Files/Road%20Runner/Plugins/RRFusion/RRFusion.DLL
----------------------------------------
Microsoft.VisualBasic
    Assembly Version: 8.0.0.0
    Win32 Version: 8.0.50727.1433 (REDBITS.050727-1400)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
FusionBrain_WinUSB
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/Program%20Files/Road%20Runner/Plugins/RRFusion/FusionBrain_WinUSB.DLL
----------------------------------------
System.Windows.Forms
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
Accessibility
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Accessibility/2.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
----------------------------------------
System.Web
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_32/System.Web/2.0.0.0__b03f5f7f11d50a3a/System.Web.dll
----------------------------------------
System.Xml
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.