FabInterpreter help

Hi,

Super excited about the Fab@Home printer. I finished assembling my printer and everything is connected per the instructions.

I installed FabStudio_v1_Beta.exe (for my Windows based computer) and have played around to familiarize myself with it.

Then I downloaded FabInterpreter_win32_installer_(exe) and installed the program.

I followed the directions and found my laptop assigned the USB connection to COM port 4, and I edited (only) the COM port line of code in the Printer Configs folder for each of the tool head applications to match COM 4.

Next instructions:

“6. Open FAB2.exe which is the FabInterpreter.

7. Hit Initialize and load the printer config file (default location is in 'Printer Configs' folder under FabAtHome program files directory).
If all is right it will populate fields with axis and numbers. If connection fails, it will show a message , "0 of N modules Found". If all the cables are secure and the device is correctly recognized by the computer, the most likely problem is an incorrectly configured COM port.”

My problem: I can’t proceed to Step 7. I opened FAB2.exe and got pic#1. There is no place “initialize” or place to “load the printer config file”. It doesn’t give me a failed message or anything.

I follow all the steps to print an object and the FabStudio works great. When I click Send to Printer, it gives me the same thing. I selected the Advanced Features option in FabStudio and saved a .fab print file (from one of the objects in the Wiki library). Then I opened FAB2.exe, clicked “Load New Config”, opened my saved .fab file, and got the following message:

“A fatal error occurred
Arugment on line 58 of file c:users\jeffery
lipton\code\c++\fabathome-model2\trunk\software\projects\fabinterpreter v0.1
(not a stable build)\util/Util.h was false but expected to be true.
Cannot be interpreted as the required datatype.
Press OK to terminate the program.”

The laptop I’m using is 64x based with System 7. I wondered if that was the problem, so I installed everything following the exact same steps on an older desktop running Windows XP. And it exhibits the exact same results…

I'm sure I must be missing something simple. Help!

Mike