Forum Navigation
Please or Register to create posts and topics.

Jet45 AAS V1.0.0.3 - Bug Fix and Requests

(Original thread started on 06-17-10 by Eric Tomlin)

Jason and I are happy to have the latest version of JET45 AAS available to all the customers. I wanted to take some time to introduce some of the new features and fixes as well as talk about what's going on development-wise as I'm sure you would like to have a little bit of the inside info and the path we are currently taking.

 

First, the update to JET45 AAS

The package, as suggested by the Press Release, brings many new features, enhancements, and fixes that have both been requested by customers as well as brought about by our drive to continually make the product as realistic as possible.

 

Here's the list of fixes and enhancements:

* Fixed hardware interfacing issues with the Display Units

* Fixed the ADF's pointing direction

* Fixed an issue with loading FSX flight plans

* Improved the VSpeed updating to both PFDs

* Simplified hardware interfacing with the EFIS

* Provided a truly independent CRS1 and CRS2 for the PFDs

* Provided N1 SYNC Active/Caution message and interfacing for the EICAS N1 display (which will actually sync your N1 values via offset)

* Provided the correct Autopilot ON and OFF status as well as Yaw Damper OFF status (which is a timed advisory flashing) for the ADI

* Provided a Master Caution/Master Warning reset feature to acknowledge the condition (which will cause the CAS message, as well as the MC/MW to quit flashing)

* Provided an aural chime to sound when a new Caution/Warning message is generated

* Enhanced the CAS message window with new messages relating to Spoiler status, Trim Values and Engine Status message consolidation

* Enhanced the CAS message window with conditional display that changes from Advisory status to Warning status when criteria warrants the change

*Enhanced the CAS with graphical changes (white to red) when the aircraft's flap, trim, and spoiler systems are not set up properly

* Enhanced the XFR (Transfer) function for nav operations to a more realistic manner

* Other very minor updates, etc.

 

New Development:

Currently we are well into the development phase of the Flight Guidance Controller and getting it implemented into the existing package for seamless integration. I can say that fans of the LJ45 will absolutely love the additions that the FGC is bringing to the package-especially in the area of the proper ADI/Autopilot annunciations and modes. Throughout the process of R&D for this functionality, I have discovered much more about the capabilities of the LJ45's autopilot and features and I believe that once the FGC is available for the user, folks will see that this package will transform the way you fly the aircraft. With all the new modes considered, it will feel much more like the well-equipped sophisticated jet that it really is, than it does currently.

 

As stated in the Press Release, we have slowed development of the CDU/FMS so that we could get this major update released which is preparing the way for the CDU as well as the fact that it really is not possible to have the planned usage of the CDU without a FGC being available for proper operation and functionality. The FGC will play an important role in not only using the CDU, but also enhance your flights due to all the new mode information being displayed on the ADI. This being said, there will be enough new functionality brought about by the FGC implementation paired with this current release that will keep the users busy learning for quite a little while until we get the CDU ready for release.

 

Also, it should be noted that the "upgrade" option will be given to current customers to update their version of JET45 AAS to the new FGC-equipped version once the FGC is released at a discount. For any new customer that purchases JET45 AAS prior to the FGC release there will also be a discount given to upgrade their product upon the FGC release. After the FGC is available, the price of the product will reflect the addition of the new FGC component and will be an integral part of the package.

 

Intended Use and new versions:

I want to point out that although the product is developed for the Learjet 40/45, it still would work well for many other medium sized corporate jet aircraft with the exception of LJ-specific modes and messages. We have discussed making a different version for other airframes and weighed the time to perform the necessary R&D and then implement those differences for other potential customers (as some of those folks do visit here at Hangar 45). At this time, we are working to get through with the Flight Guidance Controller and CDU before pursuing another airframe-specific version of this software.

 

(Posted by Jason Hite on 06-17-10)

Thanks Eric, couldn't have said it better myself! Just a quick note on upgrading from v1.0.0.2 to 1.0.0.3:

 

Installation is as simple as backing up all of your .ini files (I can't stress this enough) and doing a fresh install of v1.0.0.3. Then simply replace your .ini files. This method assures you have the latest of everything but your configuration is unchanged.

 

NOTE:  The new site has a customers page on it that I would like to keep updated photos of your projects posted. Please send me your best photos of your projects using Jet45.

 

Lastly I would like to thank all of our customers here on the forum. Without you guys, all of the hard work would not be worth it. Seeing you guys get excited about the software and see it in use brings a smile to my face and I appreciate all of the support, comments, issue posting, and feedback that were critical in making Jet45 as functional and magnificent as it is....THANK YOU.

 

(Posted by Mark L. on 06-17-10)

Thanks! All done and upgraded! Really liking the changes so far that I see. In fact, the system scared the crap out of me when the chime went off the first time! Had the sound up too loud, usually nothing comes out of that PC. Really brought my attention to the messages that popped up. Nice work guys! Can't wait to hear what Jason will find wrong with my .ini files!

 

I am still having the issue with no external EFIS connected or external software configured, where if I execute the EFIS module, it loads and immediately the bottom left corner of the PDU where the heading info is displayed and the compass starts blinking (showing the other components of the compass) like crazy, when I unload it, it stops.

 

(Posted by Jason Hite on 06-17-10)

Please send me the .ini files for BOTH EFIS controllers and BOTH PFDs as well as a description of where your Jet45 components are installed relative to one another.

 

UPDATE:

A small update to Jet45 AAS 1.0.0.3 is now available.

 

Updates include:

* Display reversion switch handling fixes

* PFD VOR1/VOR2 start up fixes.

* PFD minimums encoder handling fixes.

 

Mark, I have spent some time this weekend working on a utility that will allow you to configure the PoKeys card for switches and encoders. This will allow you to run multiple PoKeys cards on your system and control Jet45. This setup worked flawlessly and with no discernible lag. I think the wait will be well worth it. It has worked so well that have chosen the PoKeys system as my I/O of choice for Jet45.

 

(Posted by Mark L. on 08-23-10)

I have 2 PCs currently in my configuration:

FSX PC - Runs FSX, REX and UTX. Nothing more, nor do I want anything else running on it other than FSX addons.

 

JET45 PC - Runs the Jet45 software suite, always has.

 

2 - PoKeys cards, one configured for my TQ, that's all that is on it. The other one has the 2 RMU's wired up and running. Both are plugged into the FSX PC.

 

To me, logic would dictate that the Pokey card with the RMU's would be plugged into the Jet45 PC, but this would require the Encoder utility to run on the JET45 PC and it won't function properly as it doesn't communicate with FSX via FSUIPC correctly in this manner. So I have to plug the card into the FSX PC AND run the Encoder utility on the FSX PC. (Side note: While it will function this way, all the buttons on the RMU's need to be manually configured in FSUIPC to work. The offsets that are available should be able to handle this via software but this has not yet been incorporated into the encoder utility? But this is not the cause or source of the problem observed.)

 

With the above configuration and no EFIS hardware configured or software configured for it, rogue or otherwise, the only way to change the settings is to launch the Jet45 EFIS emulator until I get the hardware I'm working on finished. When this is launched, the compass etc in the PDU's start blinking away. If I unload the EFIS emulator or do not load the Encoder utility, it will not do this. Obviously, once I have the hardware completed, this is a none issue and it's not a big deal anyway. I was just inquiring if this had been addressed as Jason stated he was going to work on expanding the encoder utility to work with handling the RMU's and as I understood it, the card could be plugged into the Jet45 PC.

 

There should be a clear and easy configuration to this as to which PC the Pokeys cards should be plugged into and to me, it should be the PC running the Jet45 suite. Jason, are you saying that the enhanced utility is coming or support for this has been included in this latest update? Either way, looking forward to these updates. Thanks guys.

 

(Posted by Jason Hite on 08-23-10)

A few points of clarification:

 

1. The PoKeys card can be on ANY PC in your network. It works directly with FSUIPC and absolutely does not need to be run on the Jet45 PC. All of the communication in Jet45 is done via FSUIPC.

 

2. The RMU encoders work with the utility as do all of the other Jet45 encoders. There is a parameter in RMU .ini that allows the encoders to write to the sim properly. It is called "[COM_WRITE_TO_SIM]", set it to 1. Otherwise it will only read the sim values instead of actually controlling the radios.

 

The utility is still in the works, but good progress was made this weekend. I began to develop a graphical interface for configuring the PoKeys cards. Once the utility is complete, you will be able to run as many cards as you want on any PC in the network and have a combination of encoders and switches on any card.

 

No matter which PC your use, the PoKeys card and the utility need to be on the same PC.

 

(Posted by Mark L. on 08-23-10)

Glad to hear it Jason, only a little more clarification is needed. I haven't downloaded and installed this latest version, but when I have the PoKeys plugged into the Jet45 PC to run the RMU's (that's all the encoders, buttons etc I have so far), it wasn't able to control the radios with the setting you mentioned. So with the current version of the encoder utility I have (as far as I know the latest one that was made available), which PC should that be run on? The FSX PC or the Jet45 PC? Currently if the Pokey card would be plugged into the Jet45 PC and the encoder utility run on the FSX PC, it can't see the card. What about the EFIS and FGC components that I will eventually add? Sorry if I seem like I'm nit picking here, just trying to make sure I understand what's available now and what's coming and where things go with only the knowledge of what has been.

 

Thanks! Keep up the great work. Looking forward to using everything in this Swiss Watch!

 

(Posted by Rand Mathews on 07-08-11)

I'm having an issue with the RMU's. The window frame around the RMU's is going out beyond the size of my monitor. So even if I save the position where I need it to be, when I start up again the position moves. I removed the bezel in the .ini but the window frame is of course the same size. Tried hitting "F" but still an issue. Plus a little item I brought up to Jason a long time ago, when you hit "F" it makes the original position smaller and keeps getting smaller every time you hit "F".

 

Curious if it would be possible for the RMU's to have an option without the bezels. Meaning the window frame will be just around the display area and not the entire bezel. Since most of us are building a physical bezel, then just have the window that will be seen through the physical bezel. Hard to explain....basically just have the window frame around the digits of the RMU.

 

Here is a picture of what I am trying to explain. The blue area (window frame) is what I was referring to, it would be easier to control and size:

Rand1

 

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

That's an odd issue. Don't think it's a bug, as I'm running without the bezels. I'll have to look at my settings to see if I spot anything.

 

(Posted by Rand Mathews on 07-08-11)

Thanks Mark. Well it may not be a bug then, but it sure is bugging me!

 

That becomes the issue, if something is not functioning then how does the user know if it's a bug or a setup and/or config problem? For instance I can't load flight plans on DU3, it will not highlight "LOAD" but it will highlight "PLAN". I haven't really looked into the issue that deep because I use P8R for those functions. But it would be nice if it worked.

 

Well the "F" key is an unresolved bug then.

 

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

This is my RMU .ini file:

[X_SIZE,Y_SIZE]

447,545

[X_POSITION,Y_POSITION]

942,855

[FRAMELESS_WINDOW(0-1)]

1

[DISPLAY_BEZEL(0-1)]

0

[RMU1=0,RMU2=1]

0

[COM_WRITE_TO_SIM]

1

[COM_MEMORY]

(freq listed here)

[NAV_MEMORY]

(freq listed here)

 

This is my MFDDU3 .ini file, make sure you have the file path shared where your flight plans are located:

[X_SIZE,Y_SIZE]

466,651

[X_POSITION,Y_POSITION]

1780,68

[FRAMELESS_WINDOW(0-1)]

1

[DISPLAY_BEZEL(0-1)]

1

[MFD=0,EICAS=1]

0

[PLAN_PATH]

"\\pcname\flightplans"

[PATH_TO_DU2]

"C:\Jet45\EICASDU2"

[PATH_TO_DU3]

"C:\Jet45\MFDDU3"

 

You should also find a file called planlist.txt in the directory where you store your flight plans which contains the list of flight plans (I believe this is created by Jet45 as I didn't create it). Of course it only displays the top 6?:

 

KDLH-KMSP.PLN

KGFK-KMSP.PLN

KMSP-KDSM.PLN

KMSP-KGFK.PLN

KSTP-KDLH.PLN

PHNL-KLAX.PLN

planlist.txt

 

This really needs to be redone. If I remember right, you should name your flight plans similar to what I show above as the length of text displayed is limited.

 

Personally, I think this is where one could deviate from the real thing and just display a bigger window or allow the code to just list all the flight plans in this folder to pick the flight plan desired, not restricting the filename and a max of 6 flight plans displayed etc.

 

I should add that unless I have forgotten something, it's a pain to create the flight plans and have to manually copy the plan file over to this 'flight plan' folder. This should work with the default FSX/FS9 setup in my opinion to avoid the extra steps.

 

(Posted by Rand Mathews on 07-09-11)

Like I mentioned I really haven't bothered that much with this because I use other software for flight planning. But it used to work before the update. As I recall you clicked once and the word "PLAN" would highlight click again and "Load" would highlight, right now it will not highlight. I've checked and rechecked the .ini and verified that I can access FSplans from networked computers.

 

I will dig into this later, but it's probably on my end since no on else is having issues.

 

Also I can't change the TCAS range, it stays on 6, tried + and - keys, but no change. Is there another way to change this? Thanks for the input guys!

 

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

I've made some changes and will see if that works as you stated now. I seemed to have never updated my flight plan paths since I built and fired up the new FSX box. It was pointed to my old one. Still, I don't see the point in limiting it to 50 files and then only display the newest 6, this needs to be addressed. Favorite flights get bumped out if I create new ones.

 

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

Sorry I haven't chimed in on these posts. So I will attempt to answer a few of them now.

 

In reference to adjusting TCAS range with + and - keys:

TCAS range is adjustable from the RMU bezel directly, or via the RMU offsets with hardware (LSK, Rotary Encoder on RMU). +- keys TCAS range adjustment was removed from the latest version (1.0.0.3) of the SW.

 

In reference to planlist.txt:

Jet45 creates a temporary file (planlist.txt) in order to gather the text of the flightplan names for loading. Jet45 only displays the top 6 since a scroll function is not yet implemented. A scrolling function should be added to the list of feature updates to alleviate the 6 plan limit.

 

In reference to a bigger window for flight plans:

A bigger window is not an option unless we want text running off of the display onto DU4. For some strange reason, FS creates extremely long flight plan names by default.

 

In reference to manually copying the plan file over:

If you set your DU flightplan path to your FS flight plan folder, you don't have to copy the plans. We intentionally did not set the path to the default FS plan folder in case you want to use other software to create flightplans (i.e. P8R etc) which could save plans in other folders. This gives you the flexibility to use whatever directory you want to store the plans.

 

In reference to the word "LOAD" being boxed:

LOAD” should never be boxed, it is an indication that when the user presses the LSK again, the plan will be loaded. The boxed item shows the currently active function, while any label above the box indicates what action will happen when the LSK is pressed again. The same will happen with the RTN label on the main MFD menu. If it was boxed in the previous version, then it was a bug and was fixed in the latest version.

 

NOTE: This is not applicable to NAV/APR labels on the MFD menu. In this case one or both will be boxed depending on selection.

 

Just so we keep a running list. Here are the requested feature/bug fixes:

- Continued pressed of the 'F' key shrinks RMU window. (Bug)

- Add a "small window" mode for RMU to upscale display area when bezel is not displayed. (Feature)

- Add scroll function to DU plan list, remove 6 plan display limit. (Feature)

 

(Posted by Rand Mathews on 07-11-11)

Hi Jason, nice to see you! The "F" key issue was brought up by me a long time ago. I first experienced it with the EFIS modules and wrote you about it. Hadn't really thought about it again until I was positioning the RMU's. As before, I was hitting the "F" key to remove the frames and hit it again, if not in the right place then to re-position, that's when I noticed that the window would get smaller every time I hit "F".

 

On the TCAS issue I did click on the DU3 screen before trying the + and -, but I'll try again. Also looked through the offsets and the only one I saw was changing the ND range. But might of missed it so I'll double check that too. Just thought of something, if the RMU is set to [COM_WRITE_TO_SIM] would that disable the TCAS range function?

 

Would that also effect setting up flight plans, because I still have an issue with that. I highlight FPLN but no text shows up, so I can't pick and LOAD. My paths have been double checked and checked again. Thought maybe I had too many in the FSplans folder so took all out and left 6. Read some old posts and created a plan using Simroutes, still nothing. So I'm lost on this one, but will try again later.

 

It's been a long time since I used the flight plan option until now, but if my old memory serves me right, I recall that you would click FPLN and click again then FPLN and LOAD would both be boxed. This is probably from the original release of Jet45, but didn't it used to do that?

 

Another issue to add to your running list: The known issue with the reversion between DU2 and DU3, when the lower half of DU3 doesn't appear, until you refresh it.

 

(Posted by Eric Williams on 08-13-11)

Some items I can't work out:

- ADF Frequency cannot be changed (can be boxed)

- TCAS range does not change (with encoders or keys, but can be boxed)

- Transponder cannot be changed (can be boxed)

- AP Speed reference doesn't show up on PFD (I thought I saw this work once on mine but doesn't come back now) EDIT- I think I found in the Jet45 manual that this isn't modeled- but it would be really nice if it was.

- Can't get out of NAV display on RMUs without boxing a value first.

-The "Takeoff Trim" in the CAS display. It comes on right when you land, is that realistic?

 

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

You know, after reading your post Eric, I'm wondering if that is my fault. I didn't code to allow adjusting of the ADF and ATC. Possibly an oversight by me as when I first wrote the software, I just followed what was in the Jet45 RMU documentation. Not sure about the TCAS.

 

Another question for Eric T and Jason though is how is the Jet45 s/w coded to allow adjust of the transponder. What is supposed to be the selection process to change each digit. Incrementing the whole thing is not going to work. In other words when you select or press the ATC button, what is the next key press to select the digit to change. Once I know this, I should be able to add the support for these.

 

Okay, looking at this a little closer, to change the freq of the transponder, would it be the pressing of the Encoder to set the position of which digit to change? Seems to me that's how it probably works. If so, that should prove fun to code up. Just need to verify that's how it should function. Eric? Jason?

 

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

In reference to the ADF frequency:

To change the ADF frequency you use the two encoders (try this by using the bezel graphics). The outer encoder changes the two lower digits, and the inner encoder changes the two higher digits.

 

So to clarify, the only real issue here is:

ISSUE:  Outer and inner encoder swapped for tuning ADF/Transponders.

SHOULD BE:  Outer knob adjust the left two digits, while the inner knob adjusts the right two digits.

 

In reference to the AP speed:

The AP speed reference is displayed above the airspeed tape and is functional. Not sure what you have going on that would preclude it from showing up.

 

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

Jason, cool, that makes more sense. I was just going off of what I observed on my FP Learjet, of course there was no guaranteeing they got it right either. At least that is what I observed. Anyway, I can get that to work, thanks!

 

Okay, I need Eric T and Jason to explain/look into why this isn't working. I modified my utility to allow changing the ATC (Squawk code) which works fine but only displays in FSX. IT DOES NOT UPDATE to the RMU's.

 

I have a feeling I'll get the same results when I add updating the ADF. This will need to be fixed asap, at least I think it is a high priority item.

 

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

Why do you need to add any code to adjust ATC/ADF? The RMU already handles that, the only thing you need to do is make sure your encoder sets the proper offsets. When you select the LSK next to ADF or ATC, you can adjust the digits with the encoders. What am I missing?

 

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

Well, then I am more confused than you! My utility captures the select 2 line and the encoder data via Pokeys. Unless I process and write the data somewhere how does it get updated?

 

My process:

- Read current 4 digit BCD value from 0x0354 to get the current squawk code

- I then have to break that down to increment the correct digit based on which encoder is turned.  (Must flip back to zero after reaching a value of 7)

- Then reassemble the digits and send back to FSX via FSUIPC to 0x0354

- There are no Jet45 offsets to write to, so I can only write to 0x0354.

 

NOTE:  The correct value is displayed in the RMU in FSX, but not in Jet45. Is there a different offset I didn't find that can make this easier?

 

The difference here is that with the COM and NAV frequencies, I'm updating Jet45 offsets. I don't have that option with this or at least I don't have any documentation that shows the offsets for it.

 

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

Again, all you need to do is increment offsets 73f4 - 73f7 by +- 1 according to the documentation to work the RMUs. That's it!

 

The RMU increments the value selected by the LSK when the encoder is turned. It will set the frequencies for COM, NAV, ADF, and ATC and send that to FSX as long as the user has set COM WRITE TO SIM in the .ini file.

 

[COM_WRITE_TO_SIM]

1

 

If this value is set to 0, then the RMU simply displays what is in FSX and cannot "control" the frequencies in the sim.

 

Here is how the RMU works in a nutshell.

If a line select key is pressed next to a frequency, then

If an encoder is turned and updated via offset 73F4-73F7 (RMU encoders), the frequency will be incremented/decremented appropriately.

 

You must set your I/O cards on a change in an encoder to increment/decrement 73F4 - 73F7 by 1 for the RMU to adjust the frequencies appropriately. From your post above, it sounds like you are bypassing using these offsets which is what is causing your problems.

 

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

[size=28]DUH![/size]

 

I had it in my head those offsets were for doing just com and NAV frequencies because I spent so much time with them getting my utility to where it is. So yes, I was trying to write directly to FSX. So much simpler now, I don't even mind deleting the code I wrote and redoing it!

 

Well, I changed the code and it's still broke and this time I believe the ball is in your court Jason. It increments past 7 and it increments the lower 2 digits and the upper 2 digits together. Digits shouldn't go past 7 and each digit should be adjusted separately depending on which way you turn the encoder. Otherwise, you'll be there all day twisting knobs to get the correct squawk code. go from 5742 and reset to 1200.

 

I added the flag to allow the ADF to be updated, but it's not doing anything, I'll recheck to make sure.

 

UPDATE:

Okay, I checked and updated my code, I forgot the flag for RMU2 to be processed for the ADF

 

A couple more things I observed. Are the ATC Squawk codes supposed to be independent (separate) between the RMU's? I don't see why that would be, but I don't have any documentation to confirm. Is that why there is the button for ATC On to activate that particular squawk? Can someone check on that please.

 

The ADF shows as 2 separate values as well, that might be normal, again, I don't know. But I'm also only seeing the upper 4 digits updated. I can't remember, but should we be able to or need to update the sub freq?

 

Jason, can you give me some info as to what I should be doing for TCAS - Range and the "Below"(not sure what other values should be there, is both of these changed by the encoder? If so, which offsets? Actually, does Line Selects 3, 5 & 8, do these do anything? (Supported?)

 

(Posted by Will Sasse on 08-14-11)

Jason, I still can't get my RMU encoder to work correctly on turning. The encoders are seen correctly in the raw values as inc/dec appropriately. I have 'offset byte cyclic inc'/'dec' for offset 73F4 to (~7) set as per manual, what parameters should I use? I have tried 1/255, 1/360, and a few others I can't remember, but I still don't get a one click for one increment/decrement.

 

I have tried Marks RMU utility, and get the same result. Before I start deleting/disabling programs to check for conflicts, I thought I'd better confirm all settings. Perhaps if you can point me to a good explanation of parameters and how they work and are determined/ set. Thanks

 

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

Will, please use FSInterrogate (see FSUIPC SDK) to look at the values of 73f4 - 73f7. They should only increment or decrement by one when you turn the encoder one click. This will tell you if you have your I/O card setup correctly.

 

Mark, in reference to the ATC frequency:

Yes, there are some issues with the ATC frequency. I too noticed today that if you increment the two left digits to 77, the last two digits go to 77 automatically. Transponder codes go from 0000 to 7777, so I don't understand your comment above about 5742 to 1200.

 

Per the real RMU, you [u]cannot adjust one digit at a time[/u], but you are welcome to implement that in your code if you can.

 

On the real RMU, you cannot adjust each digit separately. You are more than welcome to implement that in your code if you wish.

 

The TCAS rage is adjusted just like all other RMU frequencies, by selecting the LSK and turning the outer encoder. You must use the RMU encoder offsets for this to work. The real RMU allows you to give priority to aircraft above, at, or below your altitude. Currently, the Jet45 RMU does not model this. It will display all aircraft regardless of relative altitude.

 

If by LSK 3, 5, and 8, you mean those next to the "ATC On", "BELOW", and "ANT" annunciations on the radio page, they don't do anything. They do work on the other pages however.

 

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

Yes, fine, they auto jump to 7777, however, there are no 8's or 9's in squawk codes.

 

From Wikipedia:

"Transponder codes are four digit numbers transmitted by the transponder in an aircraft in response to a secondary surveillance radar interrogation signal to assist air traffic controllers in traffic separation. A discrete transponder code (often called a squawk code) is assigned by air traffic controllers to uniquely identify an aircraft. This allows easy identity of the aircraft on radar."

 

Squawk codes are four-digit octal numbers; the dials on a transponder read from zero to seven, inclusive. Thus the lowest possible squawk is 0000 and the highest is 7777. Four octal digits can represent up to 4096 different codes, which is why such transponders are often called "4096 code transponders." Care must be taken not to squawk any emergency code during a code change. For example, when changing from 1200 to 6501 (an assigned ATC squawk), one might turn the second wheel to a 5 (thus 1500), and then rotate the first wheel backwards in the sequence 1-0-7-6 to get to 6. This would momentarily have the transponder squawking a hijack code (7500), which might lead to more attention than one desires. Pilots are instructed not to place the transponder in "standby mode" while changing the codes, as it causes the loss of target information on the ATC radar screen, but instead to carefully change codes to avoid inadvertently selecting an emergency code. Additionally, modern digital transponders are operated by buttons to avoid this problem.

 

Forgot to add, my comment about 5742 to 1200. I was trying to point out that you will have to spin from 57 down to 12 and 42 down to 00. Since if you set 7777, it's a lot of spinning to get down to 1200 as it won't go past 7777. What I'm used to seeing is turn for example the inner encoder to the right, increments digit 0, turn it left, increments digit 1. Turn the outer encoder to the right, increments digit 2, turn the outer encoder left, increments digit 3.

 

There's no decrementing, everything increments separately and flipping from 7 to 0. Very quick and easy to set codes. I have no knowledge anymore (getting old and been along time since I flew the real thing and radios by different makers are different) of the real thing, just used to seeing it the way I described. Not saying it should or has to be this way, just my observation.

 

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

The way that it is coded, if you have DU2 in reversion mode (showing MFD/ND) then RMU 1 TCAS range would show there. In normal display modes, DU3 is the MFD/ND and RMU2 controls that TCAS display range.

 

Eric T. Can you verify this is how it is supposed to work? I suppose a quick look on some real LJ45 cockpit pics would quickly answer this.

 

(Posted by Eric Tomlin on 08-15-11)

Jason, the way you explained it coincides with my understanding after looking through reference material.

 

Mark, thanks again for the utility program. I think that Jason was full aware that the ATC Transponder goes only up to 7, but it's always best to be sure that we're all on the same page. As far as the TUNE knob for Xpnder codes, see:

 

TUNE Knobs – The TUNE knobs are used to set reply codes. The larger, outer knob controls the left two digits, and the smaller, inner knob controls the right two digits. The knobs are also used to select a mode, but only if the displayed mode is not STANDBY.

 

Regarding the 2 ATC windows (1 in each RMU)- When there is one Transponder on the aircraft (as in Flight Simulator) both RMUs show an identical 4 digit squawk code. When there's 2 transponders, then selecting the desired Xpnder will then allow you to tune the selected side and puts the other side in STBY mode. Since this is not the case, the Xpnder number should always be the same on both RMUs and tunable from either RMU.

 

ID button should be interfaced to the Squawk Box offset for IDENT and LSK L4 should be assigned to the Squawk Box STBY/Squawk offset.

 

See: 0x7b91 1 Transponder mode

0 = normal

1 = standby

 

SquawkBox reads this value to determine which transponder mode to send to the network. Your transponder gauge should set this offset when the user changes modes with your gauge.

 

Additionally, 0x7b93 1 Transponder Ident pressed. When the user presses the ident button on your transponder gauge, you should set this value to 1. When SquawkBox notices it is set to 1, it will transmit an ident on the network and reset the value to 0.

 

FURTHERMORE, you could also have the ATC Reply Light illuminate on the RMU per the following:

ATC Reply Light – The ATC reply light is either an empty green box, or a filled yellow box displayed to the right of the ATC window label, as shown in Figure D–23.

 

ATC Reply Light Annunciators

Figure D–23

 

The empty green box ( ) indicates the transponder has no reply in progress.

 

The filled yellow box ( ) is displayed when the transponder is sending a reply.

 

By using this from SB:

0x7b92 1 ATC activity indicator. This value is normally set to 0. When SquawkBox receives a ping from a nearby ATC, it sets this value to 1. If you want your gauge control to flash your ident light you should check this value periodically. As soon as you notice the value is set to 1, you must reset it to 0.

 

One more issue/question:

I enabled the encoders for the TCAS Range, click the select button and crank on the outer encoder and it will adjust it. But I don't see it updating the actual TCAS display. Any ideas?

 

UPDATE:

Okay, it works for me on RMU2, is there something I have to select to enable it to work from RMU1?  Note that I can have Range set to 30 on RMU1 and 70 on RMU2. Shouldn't these be the same?

 

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

Okay, so the tune knobs are correct, though not on my top 10 of UI. The rest of the items you mentioned then Eric, would fall on you and Jason to implement? Wasn't clear if it was how it should work and not to be implemented or put on the "To Do" list.

 

By the way, where do you find this info? Do you just make it up? Just kidding! I searched a lot trying to find that kind of info. Thanks for the help with this stuff Jason.

 

(Posted by Eric Tomlin on 08-16-11)

Hi Mark, yes- the rest of the items are actually "Enhancements", not a fix and it would fall on us to implement in the course of time.

 

Regarding where our info for JET45, let's just say that it's definitely not just made up. That's why it's the absolute best solution for the Learjet 45 anywhere on planet Earth, save the actual software from Honeywell.

 

Now, getting back on track- Let's be sure to keep this thread going for Fix Requests only so that we don't get off into the ditch too much. Kinda my fault on that last RMU feature update that I mention.

 

Additionally, I would like to get a gauge on the community for some Enhancements to JET45 for the Existing suite. We know the obvious things that are desired (CDU/FMS and a FGC) but those are separate modules for JET45. What we're trying to gather are ideas for the current product that you'd like to see enhanced, meaning enhancements to the following:

 

PFD

MFD

RMU

EFIS Display Controller

 

An example would be:

"Update the RMUs to have the Squawk Box offsets embedded for online flying in regards to IDENT, STBY, and Transmission Detection". This is actually an enhancement that [i]I [/i]made in the Fix Requests thread that should be here and not there.

 

Lastly, I feel it's time to address something publicly so that everyone is on the same page with Jason and me.

 

1) Jason's participation here at Hangar 45.  Jason, as some may know, is involved in a very technical job in the aerospace industry and is a very busy guy throughout the day. Jason depends on me to handle the Hangar support unless it's something I just cannot figure out or find a way to fix for the user and naturally no one can be here 24 hours a day. Please understand that I try to keep his support load as light as possible. I say all of this so that folks won’t think that he is uncaring or disconnected from the users.

 

2) Updates, new modules, etc. Some folks have made comments both publicly and privately that they feel that customers could be upset by waiting for updates, etc. It's very important for everyone to understand that when you purchased JET45AAS, you received in full what you paid for. The license agreement fully discloses that any updates or changes provided are at the discretion of FlightDeckSoft and that once purchased, there is nothing owed to the customer. This can be found in the Conditions of Use as well as items 4 and 6.

 

NOW, with that said it's important to remember that we've never charged for fixes because we are customers too and would not want to have to pay for fixes to something we've already paid for. However, we've went a step further and have provided tremendous updates to the product in the way of product enhancements/feature upgrades and have not charged anything more for it. It's important to know that just as with most any other product purchased, there will be a charge for NEW modules such as a CDU, FGC, Systems, etc. when and if they are released. Why? Because it's new and it calls for untold hours of R&D and testing.

 

Lastly, I want to make people aware that there absolutely no one here at Hangar 45 that wants JET45 to be 100% complete as soon as possible as I do. I know this to be true because I've had the privilege to work with some of the software that's been on the back burner and I know that it's possible to have our Learjets working as well as the 737 sim builders have. However, development takes time and all we can do is ask you to be patient as we work on new things once we've got bugs and fixes taken care of.

 

My personal request....

Enhancement to RMUs:

* Update the RMUs to have the Squawk Box offsets embedded for online flying in regards to IDENT, STBY, and Transmission Detection

 

Enhancement to PFDs:

* Low Speed Awareness adjust for high altitude and High Speed Awareness present for Mach along side IAS.

 

(Posted by Eric Williams on 08-18-11)

Enhancement of the MFD would be great- Integration with FSX so the real time Flight Plan/GPS route is displayed instead of having to load it manually. Would be very handy and functional.

 

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

Are you saying that you would like for the flight plan to update on the MFD if you change it via the GPS? Essentially, this is what a CDU/FMS will do (allow you to update and refresh the most current real-time FP entered without re-loading). If you are asking for this to be possible without the CDU, but to just read the most current GPS FP info, then we can consider this.

 

(Posted by Eric Williams on 08-18-11)

It would be an interim fix, as the CDU may not appear soon. Some programs (like EFB) will send a FP to the GPS. As well, they can update the GPS en-route with a new FP at any time during flight (like a fake CDU)

 

Without a CDU I will be using the EFB to send commands to the GPS during flight etc. Making the current display on the MFD useless over and over. In regards to the route updating, not other features-admin.  Just a thought on a method that may make people happy in the interim until the Jet45 CDU is available.

 

Additionally:

* Weather Radar would be another very nice enhancement.

* Request for engine fire modeling. As of now, the L/R Engine fire shows up as APU fire on CAS.

 

(Posted by Rand Mathews on 11-04-11)

Eric, I know this an old post, but you mentioned that you had no problems loading flight plans, would it be possible for you to make a short video detailing how you do that? Thanks.

 

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

Hey Rand, here's the video detailing how I load a flight plan into the MFD of JET45:




 

Sorry it's not the best quality, as I shot it on my iPhone and plus it's just a little washed out. However, you should see what's going on just fine as I walk through the steps. I also want to mention that any flight plan created that is compatible with FS is compatible with JET45 as far as I know. I use FSBuild by Ernie Alston and the JET45 MFD loads the plans just fine.

 

(Posted by Rand Mathews on 11-08-11)

Thanks Eric, that was really helpful. I see one thing that I was doing wrong. I'll go give it a try and see if it works.

 

Okay, I made it past one part and now seeing another.

 

My flight plans displayed on DU3 look like this:

((((((t ((((((g(((((((((((f((((((d((((((((((.pln

((((((((b(((((((((d(((((((((((w(((((( ((((.pln

 

Seems you must use the Microsoft default path for the flight plan. I made a folder called //FSplans and assigned the path on both MFD configs, DU2 and DU3, but it will not see that path. So when I use the default path, that's the stuff I see above.

 

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

There is a character limit for the file name of the flight plan. Make your flight plans' names something like "KDEN-KASE" instead of "Denver International to Aspen Colorado".

 

(Posted by Rand Mathews on 11-08-11)

Okay, so you can't use the default flight plan name? I think I remember seeing that many moons ago, but I thought that had been fixed. Thanks for the help guys, now I remember why I didn't use Jet45 for flight planning, kind of a PITA. Guess it's back to using P8R's FMC and ND until updates are made.

 

Not complaining, so don't take it wrong. But you have to admit, it is kind of a hassle. I'm anticipating updates in this area for the future. Fingers crossed!

 

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

When you load the 'filed' flight plan, it is displayed in the MFD, the route anyway or I'm not understanding your statement? The issue that Rand and I are talking about is loading the flight plan into the MFD with the current limitations of the number of files and filename length.

 

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

The file name length is realistic. No flight plan in any FMS is loaded in any other format other than by ICAO assigned codes. That's not an area that I see changing, plus it's just good practice to not only save the flight plans in the ICAO format, but as an aviator it's important to know the ICAO codes for the airports you're operating from/to.

 

What is ICAO?

https://en.wikipedia.org/wiki/International_Civil_Aviation_Organization

 

+1 on the number of FP's to choose from and is an issue to revisit.

 

(Posted by Eric Tomlin on 07-24-12)

JET45 v 1.0.0.4 has been released and this thread is being closed. Customers can update their versions now from 1.0.0.3 for free and those new to the software can try the demo. See the new Version 1.0.0.4 thread here at Hangar45.net.