As far as I know - Octaves handling of Airplane mode is common to all of the current Octave devices as Airplane mode is a function of the WP7702 module - which is common to all the current Octave devices
Currently, there are no resources defined in Octave to monitor or control airplane mode for any of the Octave enabled devices. Ultra Low Power Mode (ULPM) can be configured in Octave. To effectively work with ULPM on the FX30, I would wait for Firmware version 2.1.4.
Thanks for the feedback - a public or accessible bug list would be very helpful with this sort of thing as we’re just discovering the already discovered.
I think there could be an issue with some mangOH yellow boards regarding airplane mode which has highlighted Octaves inability to handle this edge use case. We have eliminated the mangOH power source as the cause.
The problem is we are also experiencing the unrelated network registration issue at the same time which was making diag really difficult. I’m hoping the network registration workaround should help us focus purely on the airplane mode issue from now on
Hi John, referring to your initial question, when module radio goes off Octave will not try to activate it back, so your app has to handle that case. In this situation, if Octave has some data to send to the cloud they will be stored in the “store and forward” memory which will be flushed the next time the module will be connected.