![]() |
Well Bill is the expert, so if what he says diverges from whatever I post here, I encourage you to ignore me.
Flight ID should be the tail number unless you are operating with an official ATC call sign (such as a charity flight or life flight). The only exception I can think of is if operating in anonymous mode. A code of 1200 would push my thoughts in that direction, but then when you change to a discrete code I would expect the Flight ID to go back to being your tail number. The UAT should have your tail number programmed as a constant within the maintenance console. Might want to check that field. While you're at it, may as well make sure that your SL70 has your tail number programmed correctly. |
Thanks David - I did check the UAT and it had my tail number correct.
The SL-70 cannot be programmed with any data. The squawk code (1200 for VFR and as assigned by ATC) which I was referring to earlier is supposed to be sent from the SL-70 where it is set to the ADS600B for transmission along with the other info as the SL-70 is suppressed by pin 35 of the ADS600B. The FID I referred to was displayed in my MX20 (data sent to it by the ADS600B) which prompted me to look in the data stream (in the UAT console)...The data stream also shows my tail number correctly (from the ADS600B) and the 1200 - which did not change when I changed the setting in the SL-70. I think FID might be a misnomer from the MX20. Hope that clears the mud Not ignoring anyone - trying to learn as much as I can! |
Interesting. I thought the SL-70 was a Mode S transponder, but maybe it isn't.
I know with a TransMON it takes a certain number of replies before the UAT changes to the new squawk code. Sometimes as long as 15 seconds. It's not immediate. I don't know if that behavior is the same when using a databus connection. In other words, I don't know if the delay is a factor in the TransMON itself, or an internal characteristic of the UAT. As posted above, these systems work best when the transponder is replying to interrogations. What do you observe in the Flight ID during flight? |
Quote:
|
I have my SL-70 installed and functioning the way Jesse describes - gray code in to the SL-70 and serial out.
I haven't flown it yet to answer David's point but will wander down to some flight following where they issue me a different squawk code - we'll see what happens then! Can we get Bill to chime in?! |
Bill responded to my request for help with a couple of things to check.
One possibility is that my MX-20 is set up as the controller instead of the SL-70. Gotta figure out where that setting is and change if it is wrong! Then I can check the status field. Status update next weekend when I get to the hangar to try it out! |
Quote:
|
Quote:
If you don't have a TransMON, the GTX327 only has one data output port and it can only output one data format (squawk or altitude, not both). Possible that you have the control data (squawk) coming to the UAT from your GTX327 and you have the altitude from your encoder going into the UAT directly (and into the GTX). Or possibly you have the TransMON. The NavWorx UAT does not stop transmitting when you turn your transponder off. It simply transmits a message that says there is no control input data. So you are still in compliance with the rule. |
Quote:
|
You guys are correct. I wired this up two years ago and I've already forgotten.
How do you know the UAT is still transmitting when the transponder is in standby? I don't appear on my buddy's foreflight when I'm not squawking. |
| All times are GMT -6. The time now is 02:24 AM. |