Quote from Hangar45 Admin on November 30, 2017, 2:13 am

(Original thread started on 11-10-11 by Eric Williams)

Just trying to get my Display Unit bezels up and running. I can't find an offset or command in the Jet45 manuals for RA/BARO and STD on the PFD.

 

For now, I am sending the "B" keystroke for the STD. I can't find the STD in the JET45 FSUIPC Offset guide. However, I can find the RA/BARO explained in the Jet45 user guide, but I can't find it in the JET45 FSUIPC Offset guide. Maybe I am blind.

 

(Posted by Mark L. on 11-10-11)

That would be good to know unless that gets written directly to FSUIPC, in which case you can find it in Pete Dowson's manuals for FSUIPC.

 

0x0330

2 bytes

Altimeter pressure setting (―Kollsman‖ window). As millibars (hectoPascals) * 16

 

I found another address. Looking for the address to flip between radar and Baro mode.

 

0x31E4, Length 4 //Radar Altimeter

Radio Alt Offset / 19975.3721

FSUIPC conversion (65536 = 1 Meter --> 19975.3721 = 1 foot)

 

Never looked into this before, so can't say I know a whole lot more than you do about it right now. But it looks like we should probably be writing to a offset in Jet45 as there are some calculations to be done I think when reading the encoder depending on which mode is selected for setting minimums.

 

(Posted by Jason Hite on 11-11-11)

The PFD handles all of the setting of the altimeter internally. You only need to have your encoder setup correctly to write to the PFD encoder offsets: 73D2 for CAP PFD, or 73D3 for FO PFD.

 

(Posted by Mark L. on 11-11-11)

Jason, still missing some information on that. What offsets are the button presses set to and what? It would help to define this more clearly and get offset information for the following for each side:

 

Minimums Encoder

RA/BARO Button

BARO Encoder

Standard Button

 

In fact I need the information for the MFD buttons and Encoders as well if we are going to do this. Thanks

 

(Posted by Jason Hite on 11-14-11)

Per the manual: PFD Encoder Offsets are 73D2 and 72D3. They are handled just like the RMU encoder offsets.

 

Apparently I did not add any offsets for the PFD buttons! I will add those for the next release.

 

(Posted by Eric Tomlin on 11-18-11)

Jason is working on the CDU alpha right now and then once it's in beta then I'm thinking the PFD/MFD will be looked at again for several updates. With the upcoming update, you can also scroll through additional flight plans and not be limited to 9, a big request from the whole community it seems. I believe the new limit is 50.

 

(Posted by Eric Williams on 12-14-12)

I'm using an FDS SYS for the above and no matter what I seem to try- I have to hit my input button numerous times even when Interface IT is set to toggle the bit. What is the correct setup for this?

 

It seems when I toggle any bit (or set and reset etc) I need to hit the button 7-9 times before Jet45 reacts. It acts like it is counting and I can even see DEEC manual mode toggle during this.

 

(Posted by Jason Hite on 12-17-12)

The bit should not be set to toggle. We have seen issues with sticky offsets. In general Jet45 will read a bit in the offset, then clear it. If your FDS card is setup to toggle or setbit/clearbit, Jet45 may not read the value before your hardware clears it. Please use setbit operation and see how that works.

 

(Posted by Eric Williams on 12-17-12)

No Joy on bit 7 at all. Regardless I'm up and running on toggling bit 6 via FDS. When this is toggled it cycles through the 4 combinations of IAS/mach and RA/Baro (combined on/offs)

 

I'm good with this setup for now. I tried all combinations possible I think and couldn't get results otherwise. You may want to have someone else try. Also FYI the MCR works fine on the same offset. Thanks for looking in to it.

 

(Posted by Eric Tomlin on 12-18-12)

I wanted to take a moment to expound on the "sticky" offset comment(s). During JET45 development, we've seen cases where certain functions want to behave exactly like Eric G. pointed out- requiring multiple switch presses to solicit a reaction of that function. The FDS SYS card has a monitoring function that allows us to see that the switch is good, we can tell immediately via the monitor that both the switch and the interface card are working as directed.

 

So then we look at JET45 as it becomes the next suspect. After having someone else experience the same issue, it only seems to be JET45 but then when examining code it makes no sense. Finally as an attempt to bring sanity to the issue, we change the offset that is assigned to the function in the software and guess what? That has proven to fix the issue more times than not.

 

What can be said of this? It was highly unexpected, but many times it has fixed the issue of slow/no response. I cannot say for absolute certainty that it's not an InterfaceIT/SYS issue or someway JET45, but the fact that a simple reassignment of the offset used (as obtained from Pete Dowson for the software) is strange and thus, the realization that there are sometimes offsets that just seem to not work well for whatever reason.

 

(Posted by Eric Williams on 12-18-12)

Sounds good. Just to reiterate, setting the switch as described above actually works out fairly well for me anyhow. I can actually use that switch to toggle through IAS/Mach and BARO/RA both and each combination thereof.

 

Until something in Jet45/FSUIPC changes later you can consider my request resolved now that I have it reacting the same each and every time using bit 6. All good, it actually worked out as a plus!

 

(Posted by David Gutierrez on 12-18-12)

I think as Eric T. said, its got to be something to do with the offset. Before Eric G. posted that he was having an issue with the IAS/MACH and RA/BARO offsets, I ran with the same problem.

 

With FSUIPC, I was doing some tests with the jet45 demo. I was able to assign a lot of switches with other offsets for example for the DU's and more. But with the IAS/MACH offset I wasn't able to do it, every time I pressed the switch to toogle IAS/MACH the RA/BARO was behaving weird in the next press. In one press the IAS/MACH was toggled, with the next press the RA/BARO was toggled, I tried everything, lots of different bits, and lots of FSUIPC sets.

 

Every time with the same result, at the end I thought I wouldn't have the issue using the FDS-SYS board so I didn't say anything. But with all this evidence maybe its a faulty offset as you guys said. Hope this research helps to solve the issue.

 

(Posted by Shane Barnes on 03-29-13)

After some research I have found the correct parameter for the RA/BARO function. NOTE: You have to be updated to at least Jet45 version 1.0.0.5 or this will not work correctly. You can program the RA/BARO button thru the PoKeys card and FSUIPC. We were trying to use the wrong parameter. Bit 7 is 128 and when converted to hexadecimal = 0x80. Here is how you need to program it:

 

Pilot side:

OFFSET BYTE SET

OFFSET = 73D5 PARAMETER= x80

OFFSET BYTE CLRBIT

OFFSET = 73D5 PARAMETER = x80

 

First Officer side:

OFFSET BYTE SET

OFFSET= 73D6 PARAMETER= x80

OFFSET BYTE CLRBIT

OFFSET=73D6 PARAMETER= x80

 

UPDATE:

I was able to get this offset to work and toggle thru the RA/BARO settings. But I think it still is a sticky offset. It takes to many push of the button to toggle thru the settings. So hopefully at some point Jason will be able to take a look at the offset or the programming for this button and maybe find a solution.

 

Also if some of you with hardware interfaced can do some testing with the offset/parameter I provided I would appreciate it. I know Ron is not having any luck with the above setting. Report back with info such as how you are programming the button , whether it is thru a Pokey's card and FSUIPC or if you have it set up thru InterfaceIT. Also whether you are using Vince's DU's, I don't think this has anything to do with the issue but gives us an idea as to what hardware set up you are using.

 

(Posted by Chris Capkalu on 03-30-15)

My set up is wired to ArcazeUSB (German interface solution).

 

Shane, it works like a charm here, thanks a lot! [b]Also the button works correct and I don't have to wait with the next push, it cycles all three modes (RA/BARO/OFF) smooth and fast![/b] Maybe it depends on the interface setup. Within my cards I can set the response of the buttons (pulse width and pulse period). So I can determine at which intervals and how long Windows recognizes a push from the button.

 

Edit: I used the offset and parameter you provided. It is the correct one I think. My clue is that it depends on the interface and how fast/often FSUIPC polls the button. You can change the button poll in the FSUIPC.ini under [Buttons]. Decreasing the value will cause FSUIPC more often to poll the buttons.

 

(Posted by Ron Rollo on 03-30-15)

Hey Chris, that is some good info and a great place in investigate further!  In my case, I think I have an older version of Jet45 and the offsets have since been updated. (I think)

 

If that is not the case, I have no idea why Shane and I are at odds with the way his works versus mine.

 

(Posted by Alan Norris on 03-31-15)

How did you update JET45 without losing all the settings -- kept the old .ini file?

 

(Posted by Ron Roll on 03-31-15)

I did not have to reformat Client-1 or Client-2 which is where Jet45 resides. So everything stayed the same. Tomorrow I am going to see if I can update to the latest version of Jet45 to resolve the RA/BARO issue and hopefully an issue with the RMUs that want to keep dropping off after a few minutes.

 

I did try to update Jet45 about two months ago but I ran into issues with the product key and licensing issues. I need to contact the software vendor to resolve that issue first.

 

(Posted by Shane Barnes on 03-31-15)

Alan, I kept the old .ini files and placed them back into each folder after updating Jet45 last night. Everything seems to be working correctly.