Being the Primus 1000 author and maintainer i guess i should pipe up :)
> 1) The Primus1000 always shows distance and bearing (the additional
> blueish and white needles) to the VOR-Stations tuned in, even if they
> are out of range. I think this is not how it is supposed to be. I
> changed it so that the DME-Display in the Primus-PFD shows ---.- if the
> VOR is out of range. I saw this on a picture of the P1000 (keep it
> real).
>
Yes , keep it real , I cant consider game or conveniance features with a
clear concience ;)
> In lack of better knowledge I made the blueish/white needles always
> point to the 12 o'clock position. If anyone of you knows how a real
> P1000 would behave in this situation, I would be glad to implement this.
> Anyway, I think this is better than having the needles pointing at some
> random direction pretending to know what they are doing.
>
> I based this work on a 298 page Primus 1000 document , but even in that
there's no description of NAV pointer behaviour , though the ADF needle
should point to 90 degrees when not active , not 0 . It would be fairly
dangerous to have these point to 0 when not active.Robin's tips sound much
more logical.
> 2) The white/blueish needles point to true-bearing-values while
> everything else shows magnetic-values. I changed that, assuming it's a
> mistake. If you know better, please explain.
>
> Yes it a mistake i missed in my last round of fixes.
> 3) I think it would be nice, if the CDI would show the course-deflection
> in FMS-Mode the same way it does in NAV-Mode. I implemented that by
> setting the deflection to deflection=bearing-legcourse, where the
> legcourse is the direction from the last waypoint to the current
> waypoint. I think this value should be divided by 5 (using degrees, not
> radians).
> Yet, I again do not know if this is supported by the real P1000. So what
> do you think?
>
> The CDI needs a lot of work and research ... it's barely functional as is.
> 4) I implemented a stop watch for the M877. Select the most-right
> position with the select-button. Start/Stop/Restart the timer with the
> other button. Nice when you are in a procedure-pattern. Do you want
> that?
>
> As long as the button press is accurate , and it behaves as the real one ,
any updates to this one I'd welcome .There are some pretty good instruction
manuals for this instrument. and a fair bit to be done to complete it .
> 5) I want... no... I need Buttons in the 3D-Cockpit to select
> previous/next Waypoint. There is this console called CDU in the middle.
> I think those buttons should go there. This CDU shows the first four or
> five Waypoints, I could also work on this. So what do you think? Maybe
> the Primus-MFD would also be a nice place for that. Suggestions??
>
> the Primus MFD ? No this belongs on the CDU ... but like I mentioned , that
could be greatly improved , though it might require a separate program to
run :)
> 6) I've been thinkink about the Primus-MFD assuming there are a lot of
> features that are not implemented. I would realy like to enhance this,
> but i cannot find any documentation on the thingy. Without knowing what
> a real P1000 can do...
> example: it would be nice to have a screen that shows the
> VOR-IDs/Bearing/Selected Radial/DME, as well as the current waypoint-id,
> distance, bearing and leg.
>
> I am having issues with the Autopilot in the Citation-Bravo. Doesnt't
> work at all. Holds altitude, anything else fails. But I didn't sort this
> out. Will let you know.
>
> Same here , and that's being worked on
> live long and prosper,
> makkes
>
> And welcome to FlightGear . Improvements are welcome , but accurate,
researched work is preferred ... not guesswork .
A search for primus 1000 should get you some good documentation , there also
used to be a BravoTrainingManual pfd out there that was pretty good to ,
explained how to use these systems properly.
Cheers
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
