Goran_M Posted April 2, 2020 Report Posted April 2, 2020 This section of your log has me very concerned, as it appears to be a hardware issue (specifically, RAM). I can't say for sure. I've referred this to Saso, and maybe he can make more sense out of it. Someone will post back soon.
skiselkov Posted April 2, 2020 Report Posted April 2, 2020 This is definitely a bug in our code. It's being triggered when LOC mode is armed without a localizer being received. As a temporary workaround, make sure you are receiving the localizer before arming LOC mode. We will have a fix for this in the next build.
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now