Fleet Configurations
Deployments
Gliders
Projects
Payload Bays
Instruments
Users
API
Log In
Deployment ru26d-20101211T0245
Pilot Notes
Abort: Webb said was common last couple weeks, likely RUDICS or Iridium network issues. iridium no char timeout tripped after 5 min. Not sure why 5 and not sure why it never connected, here is dialog: 217391 Waking up Iridium... sending:AT+cbst=0,0,1 217396 52 Iridium driver received:[AT+cbst=0,0,1[0D][0D]] 217396 Iridium modem matched: OK 217400 54 Iridium waiting for registration... 217416 56 Iridium dialing [ATD0088160000592]........... 217416 Iridium waiting for connection... 217420 57 Iridium driver received:[ATD0088160000592[0D]] 217434 61 Iridium waiting for connection... 217452 64 Iridium waiting for connection... 217470 68 Iridium waiting for connection... 217487 73 Iridium waiting for connection... 217503 75 Iridium waiting for connection... 217521 80 Iridium waiting for connection... 217539 83 Iridium waiting for connection... 217557 87 Iridium waiting for connection... 217575 92 Iridium waiting for connection... 217596 95 Iridium waiting for connection... 217614 0 Iridium waiting for connection... :OOD:digifin_mgr_ctrl:OUT OF DEADBAND: M_FIN:0.0224 C_FIN:0.0000 217632 4 Iridium waiting for connection... 217649 7 Iridium waiting for connection... 217667 12 Iridium waiting for connection... 217685 16 Iridium waiting for connection... 217701 18 Iridium waiting for connection... :OOD:digifin_mgr_ctrl:OUT OF DEADBAND: M_FIN:-0.0249 C_FIN:0.0000 217719 23 Iridium waiting for connection... 217719 DRIVER_ERROR:iridium_ctrl():6:904:Iridium timeout..no chars recvd for a while 217719 iridium_make_call() returned 6!! 217719 call_and_queue_if_reqd(): device iridium TAKEN OUT OF SERVICE
Category
Informational
Alert
Action Needed
Action Taken
Operations
Update
Credentials Required
Username
Password