540 doesn't sequence during SID

Also, one more question. Is there a way to activate the first leg (the fly runway heading leg) before the takeoff roll? I tried but it would only let me activate direct to ALTAM. The runway heading leg did activate on the roll but it's kind of disconcerting having no guidance on the HSI until you are rolling. It would be a lot better if you could have the HSI providing guidance before you take the active. 

scott wrote: Also, one more question. Is there a way to activate the first leg (the fly runway heading leg) before the takeoff roll? I tried but it would only let me activate direct to ALTAM. The runway heading leg did activate on the roll but it's kind of disconcerting having no guidance on the HSI until you are rolling. It would be a lot better if you could have the HSI providing guidance before you take the active.

Yes you can manually activate any leg. Check out the picture on page 2-3 of the pilot guide. If the light blue wrap-around cursor is not already around the point you care about, either touch the leg or use the bottom right knob to select it then press the "Activate Leg" LSK.

scott wrote: As for your second post, I don't see the photo you are describing on page 2-3. But I think I know what you mean. When you highlight a waypoint there is a Activate Leg LSK...

Speaking of altitude input, I'm still waiting for a response on this:
http://forums.avidyne.com/forum_posts.asp?TID=855&title=mode-c-pressure-altitude-bug-with-ifd540

Sorry I just read the post from Royski. I also have an AXP 340 which obviously is getting baro altitude from an encoder. Would the normal connection between the AXP 340 and the 540 provide the required altitude information to the 540, assuming that bug is fixed? My point here is I am trying to avoid going back and adding more wires behind the panel.

Thanks roltman. You answered a big question of mine. It seemed silly to provide uncompensated baro altitude as the basis for sequencing the waypoints as that is way less accurate than GPS altitude. But how does an ADC like the Sandia model provide compensated baro altitude when there is no way to set the altimeter setting? I can see how an Aspen or G600 does that because you are setting the local altimeter setting into the unit. But the Sandia ADC has no way to do that. Unless there is a place to enter the altimeter setting in the 540. 

OK so here's my question then. If you need baro corrected altitude to the 540 in order to automatically sequence waypoints, is there a way to get that besides having an Aspen or G600? An air data computer like the Sandia will still only provide uncorrected altitude because there is no way to set the local altimeter setting into the ADC. It would be no different than a regular encoder. Unless the 540 has a place to enter an altimeter setting so it could calculate it's own corrected altitude based on external uncorrected information. The reason this is so important is that you cannot manually sequence the waypoints unless there is a prompt from the 540. For example, if I highlight the CLIMB TO 1200' waypoint (see pic above) THERE IS NO LSK FOR ACTIVATING LEG OR MANUALLY SEQUENCING TO THAT WAYPOINT. I just tried it on the simulator and same in the real airplane. And in my experience, the 540 does not alway prompt me to sequence. It happened once on a SID from KTRK, but not on a MA or the SID from KLVK. So if the 540 doesn't prompt you, then you're screwed. You have no guidance and there is nothing you can do until you get to a point where you can go direct to a waypoint in the flight plan, not an intercept heading. AviJake, who can I talk to today about this? Is there someone at Avidyne that is familiar? I need a solution fast. Hard to believe this situation exists, unless I am missing something. 

 It should work. The simulator screenshots provided above aren’t a perfect representation of your condition because they assume (simulate) that there is an alt input and will always sequence past the alt terminated leg. In the real world with no alt input or uncorrected baro input, the active heading-to-alt leg will be active until manually sequenced. While on the fly 255deg/1200’ leg (active) the L3 butler will present a sequence leg option and a yellow CAS will be presented.  We used the simulation environment with the above scenario to verify the behavior (see image). There is no shortcut to automate the behavior short of installing corrected baro alt input.

From your description  however, it looks like you highlighted the Fly heading 020deg leg which would  be how you defeated the butler (the available LSK on the left).

One important note too:  There are some legs which cannot be manually activated by selecting the leg and using the "Activate Leg" LSK, heading legs being one of them.  Generally, if it's terminated by a fix, you can activate it, but there are exceptions even to that rule (e.g. holds, origin, et. al.)

What you're describing is not compliant with the system design. Can you get us the data logs to look at?

Also, are there any plans to add the function to input an altimeter setting into the 540 so that compensated altitude can be derived from the pressure altitude being sent to the 540 from the AXP 340? That would be really nice.

Is it possible you are looking for the button on the MAP page?  I recall (possibly incorrectly) that it only appears on the FMS page.

Ok will do thanks

Logs analyzed:

For the flight on 11/18/2015:
At 23:53:14, the pilot entered the LIVR1 departure, RW25[LR] transition
At 23:55:00, the flight plan became active, Course to 1200 leg being the active leg and, simultaneously, the "Manual Sequence Req'd" alert was issued.
At 23:55:13, the pilot commanded a direct to ALTAM. As a result, the alert was removed

I have a TAS1000 from Insight Avionics, would this qualify for the baro altitude. The TAS is an ADC but definitely not latest technology anymore. How should it be configured to get the data as my IFD also did not sequence.