Oodi Menaker

And, although the NMEA description for PASHR specifies Heading, we do not mind to put there ground track - if it updates faster then the heading (the heading updates every on second which is not enough). Thanks much

Hello This is a log with the new version and with offset 0x6040 (GPS GROUND MAGNETIC TRACK)FSUIPC6.log

Hi, Apologize for the delay as I was out of the office. The following are the logs. In the Terratem log you may see that the heading updates every one second. FSUIPC6.logteraterm26-6-23.logFSUIPC6.ini WideServer.log FSUIPC6.JoyScan.csv

the simulator does gets stuck every 5 or so seconds. It did not behave like this before. Does the logging put load on the system?

WideServer.logFSUIPC6.logFSUIPC6.iniFSUIPC6.JoyScan.csvWideServer0.log Hi These are new files from today. All of them generated today.

Hi We get no messages in 5 herz. Roll and pitch are fine, thank you. The track is still hanging see attached log (terraterm). I put the entries into the ini and also to the log interface but I do not find where the log is. Attached are the INI and the logs that are in the same directory. FSUIPC6.JoyScan.csv WideServer0.log FSUIPC6.log FSUIPC6.ini WideServer.log teraterm4.log

Hi, Thanks for the update. will work on it next week and report the results. BR Oodi Menaker

Hi. We checked the data and came up with the following observations: 1. We are getting data in 5 hz even though in the definitions we put every 100 msec (supposed to be 10 hz). 2. The true heading updates once a second. It stays the same number 5 message (see attached log).PASHR-log.docx 3. The sign of roll is reversed. Right bank should be positive. Left bank should be negative. It is reversed in the data we get. 4. The sign of pitch should be positive for nose above the horizon and negative for nose below the horizon. Currently looks reversed. It will help us much if this points are corrected. Thanks much Best regards Oodi Menaker

Hi, The softwrae person in charge if this code in our application will check it tomorrow and then I will be able to answer. In GNSS two units we use (Applanix and Novatel) there is a comma before the check sum so I assume we need it there. Currently it looks like we are getting the angles but the marker that is calculated based on the roll is not correct. So I assume there is an issue on our side. Will check and update. Thanks much for your fast support. Best regards Oodi Menaker

Thanks much. 🙂 Will install it now and test it.

please see the log - there is no coma between e and the * of the check sum and it looks like it is needed there.

Yes please, d need to be 1 and e needs to be 1 also there needs to ne a coma between e and the * of the check sum.

Hello, I checked the PASHR implementation. Most of it works but the last part of the sentence in which we probably use a slightly different flavor of PASHR. Parameters d and e needs to be a little different and the attached doc has the values. Currently we miss e, that is why our application still does not work well with the implementation. I also attached a log of the NMEA data as collected by the receiving computer PASHER.docxteraterm.log Appreciate if you can provide an updated DLL. it will help us much use flight sim with FSUIPC. Best regards Oodi Menaker

Thanks much. Will test and update.

For GNSS quality a value of 1 is good. For IMU alignment - the correct value is 4 For the heading pitch and roll - the values you picked are good. Once implemented - I will test for you.