Thread: ** NEW Fusion Brain Version 6, Pre-Order NOW **

There are both a Screen Capture file and a Trace file attached.

Looks pretty much the same as on the WindowsXP machine except on this test on the Mini-ITX with Windows 7, Core Duo 7600 processor, 3MB Memory, and the 945GM chip set, the Buttons no longer reflect in the LED10 on the Fusion Board.

Originally Posted by waltersaegir

There are both a Screen Capture file and a Trace file attached.

Looks pretty much the same as on the WindowsXP machine except on this test on the Mini-ITX with Windows 7, Core Duo 7600 processor, 3MB Memory, and the 945GM chip set, the Buttons no longer reflect in the LED10 on the Fusion Board.

Thanks that helps a lot. I can tell right away that it is not drawing textures, only primitives. You can even see the individual boxes for each letter for the text that overflows the button area. Now that I know what to look for, I can see if I can make a workaround.

As for the buttons not working, did you just copy your install files over? Make sure the "FB Details\Fusion Brain Instances.txt" wasn't copied over as this will be different for each system. It binds the FB to a specific hardware port instance forever. So it will always be instance X no matter how the USB bus is enumerated.

Yikes!

I'll delete that file. Assume it will recreate it upon first execute?!

Yep, you were right.

Top three buttons work now.

Havn't really looked closely enough to understand the forth button located at the bottom.

Originally Posted by waltersaegir

Yikes!

I'll delete that file. Assume it will recreate it upon first execute?!

Yes it will recreate by itself.

You actually only need the *.exe file. The Config xml file is needed for your personal settings. Right now that includes 3 random test buttons for Output10, and one label for the analogue input

Originally Posted by waltersaegir

Yep, you were right.

Top three buttons work now.

Havn't really looked closely enough to understand the forth button located at the bottom.

That is just a label. It shows the raw voltage in a forced strange format (all changeable). Hook up a sensor or just squeeze the port with your finger and you will see it move.

1 question/concern.

using the supplied temp sensor(s), I get a different reading on A15 than I do on A1-A14.

At ambient desk temp, I get .81xxV on ports 1-14, but I get .77xxV on port 15. Using 2 temp sensors is also repeatable (within normal variances, it seems)


Is there a software or hardware reason for this? seems to be repeatable & happens on both v6 I have here, if it can be corrected in software, no issue.

COM output: (switching sensors on the ports gives ~ same difference, so I don't think it's a sensor issue)
>a?
a?
0.0v
0.0v
0.0v
0.0v
0.0v
0.0v
0.0v
0.0v
0.0v
0.0v
0.0v
0.0v
0.0v
0.8032v
0.774v


******EDIT** The more I mess with it, the less sensor jitter I'm seeing. Sensor #1 is always reading .774V, Sensor 2 is always reading .741V on port 15. yesterday, I would see some jitter, but today I see NONE.

EDIT2: Just realized I could check the sensor by changing the temperature...... thanks Mt. Dew for reviving my limited mental capacity.
Port 15 is not responding to changes in temperature with either sensor. It is always reading between .774 & .741, and actually goes lower when I heat up one of the sensors (no change on the other).

Another question - why is D26 the always-on port? Won't that mess with arrays when setting multiple ports? It's not a big deal with the current COM or FuseGL methods, but I can see a big problem if I try to adapt my previous VB program to using this (skipping D26 every time through will be a bit of a PITA)

Originally Posted by Iamthehor

1 question/concern.

using the supplied temp sensor(s), I get a different reading on A15 than I do on A1-A14.

At ambient desk temp, I get .81xxV on ports 1-14, but I get .77xxV on port 15. Using 2 temp sensors is also repeatable (within normal variances, it seems)


Is there a software or hardware reason for this? seems to be repeatable & happens on both v6 I have here, if it can be corrected in software, no issue.

COM output: (switching sensors on the ports gives ~ same difference, so I don't think it's a sensor issue)
>a?
a?
0.0v
0.0v
0.0v
0.0v
0.0v
0.0v
0.0v
0.0v
0.0v
0.0v
0.0v
0.0v
0.0v
0.8032v
0.774v


******EDIT** The more I mess with it, the less sensor jitter I'm seeing. Sensor #1 is always reading .774V, Sensor 2 is always reading .741V on port 15. yesterday, I would see some jitter, but today I see NONE.

EDIT2: Just realized I could check the sensor by changing the temperature...... thanks Mt. Dew for reviving my limited mental capacity.
Port 15 is not responding to changes in temperature with either sensor. It is always reading between .774 & .741, and actually goes lower when I heat up one of the sensors (no change on the other).

Alright I will look into that. There is no hardware reason for it to be doing that. Maybe a rounding or bit manipulation thing that got messed up somewhere. I will see if I can reproduce.

Originally Posted by Iamthehor

Another question - why is D26 the always-on port? Won't that mess with arrays when setting multiple ports? It's not a big deal with the current COM or FuseGL methods, but I can see a big problem if I try to adapt my previous VB program to using this (skipping D26 every time through will be a bit of a PITA)

D26 is on because it was an accident. The port that is supposed to drive the control circuitry that then controls the output cannot be configured as such. It is a special USB pin under certain circumstances (which I don't use) and so it cannot source current, only sink it. So it needs to have a pullup between the gate and source of the npn on the flipside of the board for just that port. If you can solder an 0603 on it, it will work.