There doesn’t seem to be really any improvements for people not relying on QZSS or SPARTN.. But the thing is that they pulled the 1.30 firmware from their website.
And your configuration file will complain there’s a version mismatch.
We think it’s just a minor firmware upgrade with bugfixes.
The release notes seem overly terse.
Clearly some of the SPARTN related crypto or decompression was crashing the modules.
Or move to a method that doesn’t shotgun the entire key space, documented and undocumented, but uses the Series 9 configuration files, which would be less opaque and less fostering of script kidz
From cursory soak testing on some dual stacks, FW 1.32 seems more solid
But there’s plenty of people that don’t know hex that are gonna be pissed because they updated to the last fw, and there’s no easy way to set the right settings. Oddly enough, I see the 1.32 file is already provided instead for certain use cases.
They were decomposed into less opaque Series 9 configuration files
https://github.com/cturvey/RandomNinjaChef/tree/main/ArduSimpleScripts
>>.. there’s plenty of people that don’t know hex that are gonna be pissed because they updated to the last fw, and there’s no easy way to set the right settings.
They could chose to read some documentation, or review the white papers, turning the anger into some learning experience. The underlying configuration and settings are not unduly complex, and don’t need hex skills.
People are already angered enough that their harvester broke down in the middle of a field at noon. Or that their geological site got flooded. Or that their trigonometric model for tracking the IMU is still subpar.
I admire learning, but there is simply too much in this world to pretend everybody could know everything.
It seems also pretty ironic to still keep up the files for 1.30, as if that wasn’t just good for the people that managed to download that firmware in the short window of 4 months, two months ago by now.
Please login or Register to submit your answer