rjhussel

Sorry I meant simPluginsFSUIPC Version, not the FSUIPC Version.

What version is your FSUIPC Interface? It should be 2.6 as well. If not you need to upgrade it to match the Panel Builder Version.You also need to use the FSX version of the Fuel Gauges.

Thank you for reporting this issue, This has been fixed and will be included in the next update (2.61) which will be available in about 2 weeks.

Sorry about this, but I think I found the issue. The default Port Number of the Fuel Gauges for FSX is wrong. When you look in the list if Instruments after starting Panel Builder you see that the Fuel Gauge is set to Port Number 42007, this is wrong it should be 42004. You can fix this by double clicking on the instrument (in the list of instruments) and change the port number to the correct value. All fuel gauges should use 42004. I have fixed this and the new program update has this change applied.

Can you try to download 2.6 again and re-install? There was a problem with som earlier build of the release. Also make sure you configure the fuel capacities in the gauge itself (right-click then settings).

I'll probably issue an upgrade in October. It will have more accurate C172 engine gauges,

Great write-up! Thanks.

I can do a relational gauge. The reason is that FSX SimConnect doesn't have a relative wind direction whereas X-Plane does. I'll have to make a version for FSX. I do one for the next update.

The wind dir is showing where the wind is blowing from, like a weather vane. It would not change with the heading of the airplane as it shows the general wind direction, not in relation to the airplane.

No problem. I didn't even notice.

This problem has been fixed. Please update your software by following the update instructions. (http://simplugins.com/html/updates.html).

I have a look at it and let you know.

Thanks for the praise. Yes we are considering an add-on for Boeing and Airbus. This will be just like any other add-on we have (like the EFIS). Its unlikely we can do an add-on by this year, but that also depends on how complex we want to go. Any input regarding what is needed to make it useful is greatly appreciated.

Panel Builder Version 2.6 has been released. Go to http://www.simplugins.com . The announcement is on the front page and also has links about whats new and how to upgrade.

I just wanted to confirm, yes there is a problem with the RPM gauge. It has been fixed and will be available in Version 2.6 (which will be released probably tomorrow, Saturday).

OK, let me have a look if there is a problem with the gauge. There will be an update to Panel Builder coming shortly and I can include the fix in it (if one is required).

1. There is a feature in the RPM gauge (just as in many other gauges) to adjust the range of the instrument. Start the Panel then right-click in the RPM instrument. Select 'Settings' from the pop-up menu and adjust the maximum of the display for the gauge, any any color ranges as well if required. I assume you have tried this. 2. It is possible that the Ants Tecnam Eaglet add-on does not set the Prop RPM in FSX correctly. You could try Engine RPM instead (I don't know if the Tecnam Eaglet uses a gear between the prop and the Engine, in this case it would not show you the Prop RPM). 3. Another option is to select Engine RPM and add a calculation in the simPluginsFSX Interface if you know what the gear ratio is between engine and prop. You can download our test program that shows you the actual values coming out of FSX. Download it from here: http://www.simplugins.com/CommsCheckerInstall.exe . Install it then start FSX then start and connect simPluginsFSX, then start the CommsChecker, select the RPM instrument and click connect. It will show you the values coming from FSX,

That's great! I'm sure there are many others who can use this information. I'll mark your post as solved.

Got a short update, according to Pete Dowson (FSUIPC) the range for custom offsets is 66C0 to 66FF inclusive. So, our interface should be able to read those.

Thanks for all the feedback. I can do some more testing shortly and let you know about the outcome. Is there any reason you could not re-use an existing offset? (We know that this will work). Our FSUIPC Interface is fully configurable and lets you change offsets for all instruments within Panel Builder.

The Flight Director is already in the EFIS Add-On for the standard Panel Builder. The EFIS PanelBuilder version will have it added for version 2.6, which will be released next week (its a free upgrade from 2.52, the current version). We can look into adding the DH bars. If its not that much work, we add it for 2.6 as well.

Just wanted to confirm the solution. Yes it would be a problem when both computers are not set to the same language because of the decimal separator.

I can purchase an A2A product and test it with Panel Builder. Any particular A2A add-on you are interested in?

The Panel Builder FSUIPC Interface requires FSUIPC offsets and should handle any custom offsets. I'm not sure why the Panel Builder FSUIPC interface would not read custom offsets, its just an address and we use the latest FSUIPC SDK. We have Panel Builder for Dodosim 206 (an addon for FSX) that uses custom data and Panel Builder works for this. But Dodosim is re-using an existing offset to write their data into. For example 2F28 (Concorde nose visor %.) to write their annunciator light status into it. They have an external program (basically what you are trying to do with a LUA script) to write to this offset. Maybe you can try this and find an offset of the correct size and write to this. I have a look and see if there is anything else we can do and why a custom offset like 66C8 doesn't work.

Yes, it definitely looks like a networking issue. 'Reliable MultiCast protocol' is not really needed, I haven't used it before, so I can't really comment on it. I have a test program that you can install on your Panel Builder PC. You use it instead of running Panel Builder. It allows you to see any data sent to the instruments. To use it: 1. Download from here: http://www.simplugins.com/CommsCheckerInstall.exe 2. Install on your Panel Builder PC 3. Start FSX, start simPluginsFSX or simPluginsFSUIPC , then lick Connect (just what you normally do) 4. On your Panel Builder PC start 'Comms Checker' (the test program) 5. Select an instrument from the dropdown and click on connect 6. Now you should see data showing in the box below. Another question, why do both PCs have a static IP and are not being served by DHCP. I'm wondering if there is a routing issue. We are using Multicast Groups (its like a virtual network with its own IP address range) that relies on proper routing. Maybe you can try and set them both up using DHCP and see if this makes any difference.