Analog Baron Heading Knob
-
This is a very minor issue. I have replaced all of my old CH Products flight controllers with the Honeycomb controllers and am in the process of building various profiles in Span for them. I have the autopilot heading bug working with the Bravo's knob but I noticed that the in sim knob on the HSI does not rotate with the control input while the heading bug does. What variable should I be looking for in Spad to drive the knob in sim along with the heading bug?
I am absolutely amazed at what Spad can do and having a blast with it! Last night I figured out how to use conditions to operate the magnetos in the Baron independently with the magneto switch on the Alpha. Anyway, I just shared that and the picture of my new setup because I am excited haha!
-
Delightful! I hope you enjoy your new setup. I spot a DRM radio. For work, or amateur radio hobby?
Try B:INSTRUMENT_Heading_Bug_Inc and _Dec (there is also _set)
That should do the trick!
-
Thank you sir! I will give that a try this evening.
The radio is a loaner from a friend that is programmed for GMRS. I got a GMRS license a while back for fun and also picked up a couple Retevis RB27's to use in the backcountry while backpacking. The plan is to get a Ham license eventually as well - baby steps though!
-
@Black-Square, I wasn't able to get back to this until this morning and I am not finding that particular B event. I have the SIMCONNECT events HEADING_BUG_INC and ..._DEC assigned to the encoder. I am using the non-pressurized analog Baron.
-
Hm. HEADING_BUG_INC and _DEC are what I figured you were using, since those K:Events often do not bring the cockpit animations along for the ride. I got that B:Event name from the developer mode running in the aircraft, so I know that it's accessible, and SPAD should pick it up. I'm not an experiences SPAD user, but this video should cover what you need to know.
-
I will check that out and let you know how it goes. Still a LOT to learn with Spad!
-
I looked into it some tonight but am still not finding B:INSTRUMENT_Heading_Bug_Inc and _Dec. However, I did find B:INSTRUMENT_Heading_Bug and noted that when the heading bug is adjusted by either the knob on the HSI or the Bravo encoder knob, the associated value changes.
I am also having the same issue with the course knob but I am guessing that when I figure one out, the other won't be hard to solve.
This is just to verify we are both on the same page in case I am not communicating clearly:
-
Thank you for the annotation. Yes, we're on the same page. I was hoping that someone more experienced than me with SPAD would have jumped in by now. I'll still do my best. If you look at the 10 minute mark in the video I linked, you will see that in the Data Monitor Tab, where you found B:INSTRUMENT_Heading_Bug, those are readonly outputs, not events. At 7:45, you can see a method for finding the B:Event in developer mode, though I recommend using the InputEvents tab, instead of the Behaviors tab.
Did you see around 3:30, that the list of events for each aircraft are provided manually by other users, but in the "B" tab, the B:Events are loaded dynamically from the aircraft that's currently loaded in the simulator?
If you can't figure this out soon, some of the support guys at Just Flight are pretty good with SPAD, I believe. I can ask them specifically if someone is willing to help you out.
-
I will try the Spad Discord next. After following through those steps in the video, I am able to see the B events, B:INSTRUMENT_Heading_Bug_Inc & B:INSTRUMENT_Heading_Bug_Dec, using developer mode but am stuck on what to do next because they do not appear in Spad.
-
Sorry it's not so easy. Please let me know what they say, so we can both learn. Thank you!
-
I'm also very interested in this!
-
@Black-Square - I am sure the difficulty just comes from me being completely new to working in Spad!
-
After some back and forth on the Spad Discord I have learned it is not yet possible to access the _Inc and _Dec B events at this point. That is even pointed out in the beginning of the video you linked above (I just didn't fully grasp what it meant because I thought a workaround was being described). Essentially, Asobo hasn't given the end user access to certain B events yet as of SU14. Hopefully they will in the future.
-
Another question about the Bendix/King KI 525A and mapping it.
I'm able to use VOR1_OBI_DEC and VOR1_OBI_INC, but not VOR1_OBI_FAST_DEC and VOR1_OBI_FAST_INC (for making an acceleration for the knob).
-
I use the Asobo default templates for controlling the HSI, since I wanted to make sure that it worked well for users with hardware. That's unfortunate to hear. You can probably just try issuing the working commands 3-5 times at once for faster acceleration. I've done that in at least one aircraft in the past, and I believe it works just fine, though I didn't do it for anything as critical as an HSI.
-
@Black-Square Yes, that's what I did. And it seems to work ok. I thought the FAST_DEC and _INC were standard events, that's why I mentioned them, if Asobo don't use them either, using multiple commands is something my my slight OCD is perfectly happy with... 😅
-
R RoughLandings referenced this topic on
-
In the WB-Sim Cessna, they use animation events called:
CDI1: (L:INSTRUMENT_CDI_KNOB_COURSE_1_1, Number)
CDI2: (L:INSTRUMENT_CDI_KNOB_COURSE_2_1, Number)
HDG: (L:INSTRUMENT_HeadingIndicator_Knob_Heading_1, Number)It makes sense that the animation should be controlled by a separate event, as the course itself can, and should be adjusted by incrementing and decrementing the events with some acceleration, independent of the movement of the knob. I increment and decrement the following data events with acceleration:
NAV OBS:1
NAV OBS:2
AUTOPILOT HEADLOCK DIRI'm not sure if the former mentioned events that control the animation in the WB-Sim Cessna are default events, but at least these latter data events are the same I use to control the content of the knobs in the Black Square aircraft.
For knob-animation in the Black Square aircraft, it would be great if a similar approach as used by WB-Sim could be utilised in the upcoming Dukes - and in the updates of the previous aircrafts following...
