Prior to flight, the server wouldn't boot. Mike Paxton got it going. We are carrying along a spare server and installed a Linux laptop in L6. Kim reported that during the prior maintenance preflight that the power swap from ground to engines was very interrupted and set off a bunch of cockpit failures. There was no research power but this may be related to our issue. Possibly a power spike on the ground-return line. After landing in Tucson, I powered down the server and then back up with no issues.
Satcom had to be rebooted during preflight to come up.
Had to name FF01 to FF02 because the IPM header that we were instructed to use during this flight did not allow DSM 303 data to be displayed in Aeros. All nan's. I restarted, choosing FF02 and chose the default header. All worked fine.
Camera would not start. I used the terminal command and desktop icon with no success.
1 Comment
Kyle Holden
29Mar24
Flight Tech: Kyle
Takeoff: 18:36
Landing: 20:14
Prior to flight, the server wouldn't boot. Mike Paxton got it going. We are carrying along a spare server and installed a Linux laptop in L6. Kim reported that during the prior maintenance preflight that the power swap from ground to engines was very interrupted and set off a bunch of cockpit failures. There was no research power but this may be related to our issue. Possibly a power spike on the ground-return line. After landing in Tucson, I powered down the server and then back up with no issues.
Satcom had to be rebooted during preflight to come up.
Had to name FF01 to FF02 because the IPM header that we were instructed to use during this flight did not allow DSM 303 data to be displayed in Aeros. All nan's. I restarted, choosing FF02 and chose the default header. All worked fine.
Camera would not start. I used the terminal command and desktop icon with no success.