Re: [Flightgear-devel] Primus1000 / M877
Replying to some specifics, I'll let Syd comment in general since he's the Primus author, and has seem more documentation than me by far. On 18 Mar 2010, at 03:49, Max Hertling wrote: 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 GPS/FMS code generates its deflection this way, as an option, but some (many?) FMS/GPS devices defaults to showing a linear deflection (nautical miles left/right of course) instead of the angular deflection (bearing - legcourse). The GPS code supports *either* via a config property, and outputs the cdi-deflection property appropriately. However, since the GPS code has changed recently, I'm not sure where the Primus CDI is picking up that value (it may be using a proxy value from nav[0]) 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 GPS and route-manager have these functions, and there will (soon, not in 2.0.0 unfortunately) be menu items for the functions. Hooking up a cockpit button on a CDU to them is also easy. Naturally without seeing some documentation on the CDU I have no idea if this is realistic - from using simulated Boeing CDUs, you have to go the appropriate route page and activate a waypoint from there, I think. Again the core code is designed to support such operations, but I can't speak for the glue on top. 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. All that data is available in the property system (I think, or can be made available) - the piece that's missing, I think, is better 2D graphics support for cockpit instruments. Which is my next big project (for the summer, probably). And, as always, documentation on the real systems. Regards, James -- Download Intel#174; 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
Re: [Flightgear-devel] Primus1000 / M877
On 3/18/2010 9:55 AM, James Turner wrote: Replying to some specifics, I'll let Syd comment in general since he's the Primus author, and has seem more documentation than me by far. I've done some work on developing a Primus simulation package, albeit a standalone one for use with FS2004/FSX. It's based on the ERJ-145 version of the Primus 1000, and has a complete PFD, ND and EICAS. You can find it under http://openrj.stoneynet.nl/ , it's BSD licensed, so feel free to have a poke around in the source code ;) FWIW, here's some small things that are easily fixed: * VOR2 and ADF needles point horizontallly (west IIRC) when they are tuned to an out-of-range transmitter or tuned to nothing. * On FMS mode, the CDI should be in magenta, not green :) -- Download Intel#174; 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
Re: [Flightgear-devel] Primus1000 / M877
On 18 Mar 2010, at 13:01, Robin van Steenbergen wrote: You can find it under http://openrj.stoneynet.nl/ , it's BSD licensed, so feel free to have a poke around in the source code ;) I might have a chat with you about efficient anti-aliased rendering of digital displays via OpenGL in a couple of months :) Regards, James -- Download Intel#174; 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
Re: [Flightgear-devel] Primus1000 / M877
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#174; 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
[Flightgear-devel] Primus1000 / M877
Hello everyone, first let me say that I realy appreciate what you are doing. Flightgear is an awesome project, I realy love it. I've been watching it's development for a couple of months now and I would be glad to contribute. I'm using the Citation-Bravo and CitationX frequently, and currently am working on a couple of things I've been realy missing, and I want your opinion and maybe some hints: 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). 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. 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. 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? 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? 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?? 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. live long and prosper, makkes -- Download Intel#174; 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
