outbaxx

Thanks, it’s some work left before it’s really finished, adjustment of the AB zones and the buttons need some tuning. Started to work on it over 3 years ago but have no plans other than ever finish it :) The CK-37 Datapanel is slowly coming together: It’s never too late to give up

I’ve haven’t read that you should pull aft stick while braking, only when using thrust reverser, more thrust = more stick aft. It says that you should brake with even pressure and steer with the rudder pedals and only use asymmetrical braking if that isn’t enough. (My issue is that I always seem to brake asymmetrical due to the reason about the small physical range on my pedals I described above) But if guys start to skid using keyboard there must be something wrong? Different values on left/right brakes? Or why would they skid? It’s never too late to give up

Wheel brakes and symmetric braking It’s not double assigned and the dead zone does not do the trick here. I’ve done some testing and the issue is that the physical travel on the brake pedals are short so even if the difference between the pedals are very small, the difference in values in the sim get large and I end up having one brake brake harder than the other even if I think I brake them evenly. And when I try to adjust I press just a little harder on one pedal but that gives a high change in the sim and the aircraft steers hard. Maybe its time to see if I can change the spring in the brake pedals so it takes a lot more effort to move them? It’s never too late to give up

I don’t know if this is just me but I have a really hard time using the wheel brakes symmetric. As soon as I start applying brakes the aircraft starts to steer left or right and I try to compensate by either lift or press one one brake pedal and it ends by me flapping and flopping the brakes and steering the nose wheel left and right to try not to skid. And of course I skid... I using the Saitek combat rudder pedals and there aren’t much feedback in the brake pedals so it’s probably easy to brake asymmetrical and therefore start steering left or right. Is it possible to make the brakes brake symmetric if My brake pedals are in let’s say within 5% or degrees from each other? Regards F It’s never too late to give up

Big thank you RagnarDa for doing these sessions!! It’s so easy to point out “errors” but it’s even easier to forget how much work it can take to find and fix or create functions. (I won’t stop nagging about stuff I think needs fixes though ;) ) Again, big thank you for your work! Regards F It’s never too late to give up

** AJS-37 Changelog / Update Master List ** Its probably really close to the truth, the charts show a max at 13000m ISA -15 close to Mach 2.0. And when they tested for these charts they didn’t run it out of fuel :) Perhaps one should try to see the top speed when you have 20% fuel left or something. It’s never too late to give up

The problem is that it’s not modeled correctly. Blue zone: outside envelope, above 18aoa probably. Red zone: AB zone3 will flameout, AB won’t ignite and re-ignite. AB zone 1-2 don’t work Yellow zone: AB zone3 works but AB will not ignite/re-ignite. AB zone 1-2 don’t work Green zone: AB zone 1-3 work It’s never too late to give up

Afterburner flameout question No it should not. It shouldn’t flameout at high altitude if you fly fast and you should be able to re-ignite. There are some limits for igniting the afterburner and the different AB zones but the limit that is modeled now is not correct. http:// https://forums.eagle.ru/showthread.php?t=254364 It’s never too late to give up

+1 on this, My Megas are marked wrong too,didn’t remember that one. It’s never too late to give up

DCS-BIOS: Strange behaviour over RS485 Network You haven’t set 2 panels with the same id number in any sketch by mistake? Or check that you don’t have any strange delay() in the sketch for some reason? It’s never too late to give up

I was in for about 5mins, looked like some advanced QR-code, hard to read for a novice like me though. It’s never too late to give up

Sorry for the very late answer but a HUGE thanks for this!!! Works great! Very handy for me as I now can test my panels with my laptop and control the sim-computer with Remote Desktop. Regards F It’s never too late to give up

http:// CK37 Datapanel is my next panel to complete. It’s never too late to give up

Almost as funny as looking at a sundial in the shade for 1hr ;) It’s never too late to give up

I assigned it on friday, no issues. It’s never too late to give up

Why is the afterburner flaming out at high altitude and high speed? Max AB, M1.6 and not touching the throttle. I haven’t seen any documents supporting this so I’m a bit curious. The limits I’ve seen says that @14.5km and M0.5 there is a limit keeping the max Zone3 lit. And @14.5km you need to go faster than M1.2 to ignite the AB/ use zone 1-2. So I would be ok if I were in zone 2 below M1.2 and climbing towards 14km and the AB flames out but not if I’m in zone3. The charts show up to 16km as you were not supposed to go higher than that so the function limits is a bit of guessing after that. But I see no reason for a max zone 3 climb to 16k if you’re going faster than M0.9 to flameout the AB. And not only flames out, it literally dies, can’t get it to reignite even at low altitude. Regards F

There is only one detent, it’s between ground idle and flight idle. But the video I posted above show two detents. This video below show my setup doing a cold start where I go from cut off, engine start, some ground/flight idle play and then a take off:

This is what I’ve meant, there are two detents, I move the throttle between MTG and FTG but there are two “clicks” Regards F

Thanks for answering, that’s a bit much for this poor brain :) , I’ll just have to go back and install a button after all. Again big thanks for your answer, saved me a lot of time troubleshooting something that wouldn’t work the way I approached it!! Regards F

Ok, it’s not the actual range I’m after, I’ll make a video this afternoon, it’s easier to understand what I mean then. Regards

Ok, is it possible to read the physical Throttle position ie the windows value? The issue I’m having is that the “raw gauge value” of the throttle show the animated throttle position, so even if I put my physical throttle all the way back I won’t get a lower value than 3276 as the cut off animation waits for a input. If I advance my throttle, the next value is 6553, as the animation simulates a detent there, so I can’t read any value between 3276 and 6553. So, is it possible to read the physical throttle position values? Regards F

Haven’t seen it, thanks! But what seem to happen to me is that when you pass the 9% the throttle in the sim “jumps” to flight idle, and that’s ok, but it also do a jump when I pass 11% and that’s what I think is odd. Perhaps it’s just the animation of the throttle? But it shouldn’t do that jump as there is no detent between Flight idle and mil.

While trying to have a software cut off function I noticed this. Using DCS-BIOS I can read the throttle position in the sim. When I have the throttle all the way back(ground idle) I have a value of 3276. When I go to flight and idle it jumps to 6553. So far ok then. But if I advance just a tad more there is another jump to 9858. After this the throttle can be smoothly controlled. I get the first jump from 3276-6553 as we are simulating the MTG/FTG detent but the next one shouldn’t be there. Has anyone else seen this “double detent”? Regards F

The network feature is very handy for me, big improvement. I haven’t tried yet, but is it possible to connect a panel to my laptop usb and use it in DCS on my Sim-computer with this? Regards F

Thank you so much! It sort of worked:) it seems like the High Pressure Valve in the AJS37 doesn’t work like a on/off switch. The state can be 1 and if I set it to 1 again it will turn off the valve but the state is still 1, same goes for 0. Need to figure out how to read it’s position without reading the state as it can be both on and off in both state 1&0... Regards F