FS2Phidget5

[gokhotit]

Just downloaded FSP5, and it looks really cool, and figured I could give the old sim a fresh start (still using ver 429 variables) but I cant get it to work. All it does is sit there ding and refresh. If I keep the power off to the sim the 8/8/8 card is accessible, (but with no power nothing else works) I get an unhandled exception error (see below for details), and there are no variables. Am I doing something wrong???

I am running Win7, is that the problem??

thanx for your help, keep up the good work Alan.

Here are the details for that error:

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

************** Exception Text **************
System.ArgumentException: Empty path name is not legal.
at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, Boolean useAsync, String msgPath, Boolean bFromProxy)
at System.IO.FileStream..ctor(String path, FileMode mode)
at XSystem.fs2phProject.SaveSettings(Boolean _SaveAs)
at XSystem.frmMain.OpenProject()
at XSystem.frmMain.ToolBar1_ButtonClick(Object sender, ToolBarButtonClickEventArgs e)
at System.Windows.Forms.ToolBar.OnButtonClick(ToolBarButtonClickEventArgs e)
at System.Windows.Forms.ToolBar.WmReflectCommand(Message& m)
at System.Windows.Forms.ToolBar.WndProc(Message& m)
at System.Windows.Forms.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/windows/microsoft.net/framework/v1.1.4322/mscorlib.dll
----------------------------------------
FS2Phidget5
Assembly Version: 1.0.3655.23184
Win32 Version: 1.0.3655.23184
CodeBase: file:///C:/Program%20Files%20(x86)/FS2Phidget5/FS2Phidget5.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/windows/assembly/gac/system.windows.forms/1.0.5000.0__b77a5c561934e089/system.windows.forms.dll
----------------------------------------
System
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
----------------------------------------
System.Data
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/windows/assembly/gac/system.data/1.0.5000.0__b77a5c561934e089/system.data.dll
----------------------------------------
System.Xml
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/windows/assembly/gac/system.xml/1.0.5000.0__b77a5c561934e089/system.xml.dll
----------------------------------------
Microsoft.VisualBasic
Assembly Version: 7.0.5000.0
Win32 Version: 7.10.3052.4
CodeBase: file:///c:/windows/assembly/gac/microsoft.visualbasic/7.0.5000.0__b03f5f7f11d50a3a/microsoft.visualbasic.dll
----------------------------------------
System.Drawing
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/windows/assembly/gac/system.drawing/1.0.5000.0__b03f5f7f11d50a3a/system.drawing.dll
----------------------------------------
Interop.Phidget21COM
Assembly Version: 2.1.0.0
Win32 Version: 2.1.0.0
CodeBase: file:///C:/Program%20Files%20(x86)/FS2Phidget5/Interop.Phidget21COM.DLL
----------------------------------------

************** JIT Debugging **************
To enable just in time (JIT) debugging, the config file for this
application or machine (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 machine
rather than being handled by this dialog.

[CocnutAir]

Apologies for delayed response.
I did make some bug fixes based on mine and other feedback.
An updated version is currently in approval.
Don't think its a Windows7 issue. I had another builder test and was ok.
Send me your fs2phidget5.log to alan@coconuair.com

[CocnutAir]

I am in Phoenix the next few weeks and weekends.
Can always swing by with my laptop and debug.

[CocnutAir]

I was able to replicate on my system.
Was an old bug that I thought I had fixed.
There are 2 possible workarounds:

(1) Create a blank Project1.xml file in the FS2Phidget5\Projects\ folder using Notepad.
This will result in an "Invalid file" error when FS2Phidget5 is fired up, but just press OK and continue.

or

(2) Double-click on the FS2Phidget.xml file in the FS2Phidget\ folder.
This should launch your browser.
Note the line that reads: <LastProject>Project1.xml</LastProject>
Change the Project1.xml to read as below:
Line should now read <LastProject>Demo.xml</LastProject>
To edit xml file from browser right-click on the listing in browser
Select "View Source" from the pop-up menu.
This should launch Notepad.
You want to make sure you edit the file with a text editor like Notepad,
and NOT a word processor like Microsoft Word.
Word Processors put special formatting characters into the file that are normally hidden on the page.
Save the changes.
Fire up FS2Phidget5.

Regards,
Alan

[gokhotit]

Interesting update,

If I unplug my autopilot module, it works fine. However, it is not a hardware issue because the panel works good in FS2P4. When the AP is plugged in it just sits there makes the USB disconnect noise and dings over and over.

[CocnutAir]

G,

Regarding the dinging AP:

Is the ding your normal USB disconnect?

Do you have the demo project loaded at the time?
The demo has two sound components in the Decoder-2 circuit.
You could always delete those components and see if that fixes anything
or loading another project.

Regards,
A

[CocnutAir]

What Phidgets are in your AP?
I am guessing Interfacekit(s) and maybe Encoders and TextLCDs?

[gokhotit]

All that is in my ap is a 16/16 board..the pots go off to a different card. The panel works good with FS2P4. No text LCDs or anything like that (see my website in the sig for pics). the dinging sound is the normal USB disconnect, plus the ding sound for the program. As long as teh AP panel is disconnected it works..kinda.

[CocnutAir]

I don't have a 16/16 board with me to try out.
I will be home weekend after next.

When you unplug the AP, do you still have other 0/16/16 cards plugged in?
Is other card an 8/8/8 for the sensors?

[gokhotit]

yes my lightplate is connected to a 16/16 and it works fine, and the sensors go into an 8/8/8, and it works good. Havent figured out how to test my LED64 card yet.