Printable View
Ok, that's much much better. Gauge is now a little behind ie: in 180 degrees on the screen, gauge will move 150 deg.
Also, when the needle gets to the bottom (relative bearing data goes from 1222 to 0, or the val goes from +32765 to -32765, the needle does a full 360 deg turn plus another 30degress.
Seems like it's getting close.
Ok edit that line to that.
ADF1RelDataIn = val + 32765;
That was the reason why i ask you to fly a lot of 360th. I expected that error.Quote:
Also, when the needle gets to the bottom (relative bearing data goes from 1222 to 0, or the val goes from +32765 to -32765, the needle does a full 360 deg turn plus another 30degress.
We need something like a counter that count how many full cirrcles the Data input turn. With that we can add full circle steps to the output.
That is a good homework for us.
Stefan
Is this the number to edit and play around with until the ratio is correct?Quote:
Originally Posted by sgaert
no that is to change the signed Value in an unsigned value.
Ok, so this is what I need to change: static int ADF1RelNeedleStep = 1150;?
That is the nummber of Steps for a full 360.
I will do some calculations tomorrow to work out a little more accurately the number of steps.
Just another thing, in the FSUIPC SDK the offset I'm using states this:
relative bearing to NDB ( *360/65536 for degrees, –ve
left, +ve right)
so if I divide 65536 by 2 would be 32768. Should this be the number in this line: ADF1RelDataIn = val + 32765;
maybe, you write that the values are -32765 to 32765.
Hey guys
Ok i put a new 8535 in and flashed fine, set bits and BO no problems. BUT - during a flight same issue but this time it was VS and CRS that stopped working.
Do you know if the new DLL would fix these problems? When will it be released?