Beyond Confusing for Me

**Dougw133** · 10-31-2008, 05:56 AM

It is understood that this forum, this product, and carppc's in general require somewhat of a tech level. The rest that you don't know you find here. I have been excited about the brain for a while and finally ordered it. I have been using the MDX for the past 3 days and have made little progress... I have read the tutorials which seem to give basic overview and in an orderly and understandable fashion. I think the ninja kitty of doom is a HUGE step in the right direction for this still new piece of technology. I hope in the future the smarter can make this dumber! It's not the hardware aspect at all, it's the software. I am capable of running RR, managing the skin. Adapting my SWC and using girder, heck I even wrote a VB script to start and stop a dial up connection! This seems to still go over my head. Skinning in general. I find bits and pieces of what I need, however mostly in a bit higher of a level than I need. It's like it's geared towards people who already know the basics, which in my case the basics are not so basic. I am not complaining by any means, just kindly ask for some really dumbed down help!

I run RR and the DFX4 skin (best skin ever!).

Let's start with the questions:

1.) All I want to do is have a page of buttons that when pressed carry out there correlating commands to the FB. It seems to me that this can be done with the MDX embedded in RR. So would I need the RRfusion plugin any ways?

2.) If no to the above, then what exactly does the RRfusion plugin accomplish that the MDX is not?

3.) If anyone is willing to baby step me through what I need to do to come up wit this. I will have 3 buttons... Roof Lights , Ground Lights, and garage door. That's it for now. Where do I begin, whats my best approach?

**Sonicxtacy02** · 10-31-2008, 09:09 AM

Originally Posted by Dougw133

It is understood that this forum, this product, and carppc's in general require somewhat of a tech level. The rest that you don't know you find here. I have been excited about the brain for a while and finally ordered it. I have been using the MDX for the past 3 days and have made little progress... I have read the tutorials which seem to give basic overview and in an orderly and understandable fashion. I think the ninja kitty of doom is a HUGE step in the right direction for this still new piece of technology. I hope in the future the smarter can make this dumber! It's not the hardware aspect at all, it's the software. I am capable of running RR, managing the skin. Adapting my SWC and using girder, heck I even wrote a VB script to start and stop a dial up connection! This seems to still go over my head. Skinning in general. I find bits and pieces of what I need, however mostly in a bit higher of a level than I need. It's like it's geared towards people who already know the basics, which in my case the basics are not so basic. I am not complaining by any means, just kindly ask for some really dumbed down help!

I run RR and the DFX4 skin (best skin ever!).

Let's start with the questions:

1.) All I want to do is have a page of buttons that when pressed carry out there correlating commands to the FB. It seems to me that this can be done with the MDX embedded in RR. So would I need the RRfusion plugin any ways?

Yes MDX embedded in RR is just fine. you do NOT need RRFusion if you choose to do it this way

2.) If no to the above, then what exactly does the RRfusion plugin accomplish that the MDX is not?

RRFusion is a built-in RR extension plugin. It doesnt "embed" like an external application... from an operators standpoint its "built-in" to RR. At the time of creation i didnt understand the fusion control centre software as it was in its early stages... i just wanted something that i could easily skin that could control and read my FB with. I've never installed MDX so i know nothing about it... but i do know that having a plugin built into RR while using RR gives you tremendous advantages should you need them. Being able to display sensor data or control digital ports from anywhere in RR as i see fit was a major plus for me.

3.) If anyone is willing to baby step me through what I need to do to come up wit this. I will have 3 buttons... Roof Lights , Ground Lights, and garage door. That's it for now. Where do I begin, whats my best approach?

The easy way for you wont be the easiest way for others. You have to decide what you want from your hardware/software combination. If all you want to do is install SOMETHING, set it up ONCE and have it work 100% of the time then use RRFusion. Its not a knock on the FB guys work at all they do amazing stuff.. but the whole point of RRFusion is "noob" control of a fusion brain. Sounds just what u want. So come on back over to the RRFusion thread... attempt an install and if you have any questions lemme know.

**Dougw133** · 10-31-2008, 06:40 PM

Thanks for the fast response. I like the idea of the plugin better. I like being able to spread things amongst RR rather than going into the MDX and being limited to FB control in there. I can't even get the Plugin installed. I don't know what I am doing wrong. I have installed other plugins before such as Traffic Cams from enforcer but it's been a while. But I'll get help with that over in the RRfusion forum.

I guess a good start would be "what do I need to learn" to be able to skind/code/create the stuff I want to do with the brain. Where should I start?

**2k1Toaster** · 11-01-2008, 04:29 PM

Originally Posted by Dougw133

It is understood that this forum, this product, and carppc's in general require somewhat of a tech level. The rest that you don't know you find here. I have been excited about the brain for a while and finally ordered it. I have been using the MDX for the past 3 days and have made little progress... I have read the tutorials which seem to give basic overview and in an orderly and understandable fashion. I think the ninja kitty of doom is a HUGE step in the right direction for this still new piece of technology. I hope in the future the smarter can make this dumber! It's not the hardware aspect at all, it's the software. I am capable of running RR, managing the skin. Adapting my SWC and using girder, heck I even wrote a VB script to start and stop a dial up connection! This seems to still go over my head. Skinning in general. I find bits and pieces of what I need, however mostly in a bit higher of a level than I need. It's like it's geared towards people who already know the basics, which in my case the basics are not so basic. I am not complaining by any means, just kindly ask for some really dumbed down help!

I run RR and the DFX4 skin (best skin ever!).

Let's start with the questions:

1.) All I want to do is have a page of buttons that when pressed carry out there correlating commands to the FB. It seems to me that this can be done with the MDX embedded in RR. So would I need the RRfusion plugin any ways?

2.) If no to the above, then what exactly does the RRfusion plugin accomplish that the MDX is not?

3.) If anyone is willing to baby step me through what I need to do to come up wit this. I will have 3 buttons... Roof Lights , Ground Lights, and garage door. That's it for now. Where do I begin, whats my best approach?

1) You can either use MDX embedded into RR just like a GPS app. OR you can use MDX's plugin for RR. OR you can use RRFusion which we did not author and do not support but Sonic did and will as long as he wants to.

2) RRFusion came out prior to a RoadRunner plugin from us directly. RRFusion does basics simply through RR. MDX's RRPlugin does everything in MDX through RR.

3) Either one of us can help but you need to decide which you want to use. If you want MDX embedded, or MDX Plugin, then we will help. If you want RRFusion, then it is up to Sonic.

**Dougw133** · 11-03-2008, 12:45 AM

Well, didn't get my brain yet but believe RRfusion will work better for me. I think I'll wait until it's hooked up to the laptop and sending commands. It would be appropriate for me to learn the hardware aspect of inside and out before I com on here asking for help again. I will be certain to follow up and talk with Sonic or anyone else about RR fusion..

Thanks for the support.

**Dougw133** · 11-16-2008, 01:40 AM

Well I got my brain and have been fiddling around with MDX configurator which has been a nightmare. With the default configuration file I can hit "Digital Output 11" and it will switch the relay I have hooked up to that correlating port. If I make my own configuration file using Ninja Kitty Wizard of Doom, when I hit the button which is simply to toggle Digital output port 11, the relay goes nut's clicking on and off rapidly. I don't see the difference of what I am doing here. It is set for toggle and not momentary. Otherwise the hardware is working as I can tell and everything shipped packaged nicely and neatly!

**Dougw133** · 11-16-2008, 02:15 AM

Well...I hooked up my temp sensors to the analog in's and am having problems. First I noticed the pins for the A ins are slightly bent outward on 4 of 10 outside pins as if it had been used. When I run MDX all of the analog in values are picking up the temp sensor only hooked up to 3 correct Analog in 1- pins...It doesn't matter which analog pinout I hook up to, All of the analog in values change. Not all are the same but all change. I was wondering what was up when after doing the Celsius to Fahrenheit conversion, that the temp was 15 degrees off. Also I had to analog in's mapped out and noticed even though they were mapped for separate ports they both displayed info. One which I was saving for my other temp sensor. One of values displayed the correct temp. It seems even with one sensor hooked up all ports read data, and the data seems to step down by to lower numbers each port down...I don't understand...

**Dougw133** · 11-16-2008, 02:52 AM

I found this...

"When a sensor is connected, unused ports show activity as well NOT A PROBLEM

The solution to this is to just put a jumper from Ground to the Voltage Input on the unused inputs. In the software however, if you are not using an input, do not configure it in the skin setting. "

But...That doesn't make sense to me..I want to use 2 inputs. Even before the second sensor is attached to the pins it's still spitting out data from the other sensor..So even when I hook it up it isn't reading it's own isolated data but combined or whatever it's doing here. Aslo, you're saying for all the unused Analog ins, I have to but a ground wire to all of them>??

**mx270a** · 11-16-2008, 10:42 AM

The Analog to Digital converter reads through all ports in a loop. The converter has almost no resistance, so if there is voltage on one of the ports, it carries over to the next port. If you plug a sensor in to any port, that port will read correct, but each port after that will be slightly less voltage.

If you don't have anything plugged in to a port, then you have no reason to care what the it reads. If it bothers you, you can just use jumper to connect the input to the ground pin.

I think the problem here is that you're configuring the software to read two inputs, and only have one connected. Just put a jumper on the other one for right now. When your other sensor is available, pull the jumper and plug the sensor in.

**Dougw133** · 11-16-2008, 01:26 PM

Originally Posted by mx270a

The Analog to Digital converter reads through all ports in a loop. The converter has almost no resistance, so if there is voltage on one of the ports, it carries over to the next port. If you plug a sensor in to any port, that port will read correct, but each port after that will be slightly less voltage.

If you don't have anything plugged in to a port, then you have no reason to care what the it reads. If it bothers you, you can just use jumper to connect the input to the ground pin.

I think the problem here is that you're configuring the software to read two inputs, and only have one connected. Just put a jumper on the other one for right now. When your other sensor is available, pull the jumper and plug the sensor in.

Nope...I have the software to read 2 inputs and have 2 sensors connected, but the reading on the software is from one of the sensors only. Doesn't matter whether that second sensor is connected or not. I get the same reading which is less than the correct reading for the first port/sensor.