Kate-2 & Kate-1 Receiver
Mx120 Firmware Ver 4.10.0 Released: Feb. 4, 2023 Download this firmware and save it to your local hard drive. Depending on your browser you may have to right click and select "save as..."
Use the Flight Data Analyzer software to update your receiver. Simply click 'Tools' on the Flight Data Analyzer menu bar and then select 'Update Firmware'.
|
New features included in this release:
1. Added various new call outs and announcements that will be made by Kate during a flight.
a. Kate will now announce when the Karman line is crossed, and the rocket is officially in space.
b. Kate will now announce motor burn out during ascent when motor burn time is 7.0 seconds or longer.
c. Kate will now announce max velocity and max accel during ascent if max velocity exceeds Mach 2. Otherwise, the announcements are made after apogee just like they always have been.
d. Kate will now call out the max altitude reached at apogee ASAP during descent, if it was not announced right after apogee due to the lack of a radio link.
e. Kate will no longer make altitude call outs based on the accelerometer if there has been a tumble other significant flight anomaly during ascent. Such as a cato, burn through, or other motor failure. Accelerometer data is not reliable in such situations because the rocket is not necessarily pointing in the direction it is traveling. Kate will now wait until the GPS resumes after the "event" and will call out GPS altitudes instead of accelerometer altitudes.
f. Added call outs for altitude and velocity using barometric pressure sensor data during descent if GPS data is unavailable. Such as when returning ballistically from a very high altitude and the descent velocity exceeds the GPS lockout limit. However, baro sensor data is only valid below 100K feet.
g. Added some announcements during the GPS lockout interval that explain Kate is waiting for the GPS to resume normal operation. This fills in the long gaps of silence that can happen on a space shot, as it free falls to a high speed while still above the atmosphere and locks out the GPS.
2. Added time since last GPS fix to the TELEMETRY screen if GPS is out during descent and Kate is using baro sensor data instead of GPS data.
3. Added an option to allow the user to select faster updates during Map Mode. The user can now set Map Mode into "FAST" mode. This sets the baud rate to 115,200 and provides up to five updates per second. Normally Map Mode uses a baud rate of 4800 and provides just one update per second.
4. Added ability to declare a flight anomaly so that the user can inform Kate in real time that something has gone wrong. This is done by accessing the PANIC MENU. It is accessed by simultaneously pressing and holding both the up and down arrow keys when the TELEMETRY screen is being displayed. Kate is supposed to automatically detect a flight anomaly, but if not, then this provides a way for the user to tell Kate one has occurred. It is optional. It is not required for the user to do so, but it may clean up some of the announcements Kate might otherwise make.
5. Removed support for all user specified units such as miles per hour for velocity and for all metric units. This was done to gain programming code space in the receiver in order to implement all the other changes outlined here.
6. GPS coordinates for latitude and longitude that are displayed as purely decimal degrees will now use plus and minus symbols rather than N,S,E,W indicators. This is in keeping with the standard way such coordinates are supposed to be displayed.
7. Fixed a bug that would allow the user to set the LCD screen display contrast too high. Which made it impossible to recover to a normal screen.
a. Kate will now announce when the Karman line is crossed, and the rocket is officially in space.
b. Kate will now announce motor burn out during ascent when motor burn time is 7.0 seconds or longer.
c. Kate will now announce max velocity and max accel during ascent if max velocity exceeds Mach 2. Otherwise, the announcements are made after apogee just like they always have been.
d. Kate will now call out the max altitude reached at apogee ASAP during descent, if it was not announced right after apogee due to the lack of a radio link.
e. Kate will no longer make altitude call outs based on the accelerometer if there has been a tumble other significant flight anomaly during ascent. Such as a cato, burn through, or other motor failure. Accelerometer data is not reliable in such situations because the rocket is not necessarily pointing in the direction it is traveling. Kate will now wait until the GPS resumes after the "event" and will call out GPS altitudes instead of accelerometer altitudes.
f. Added call outs for altitude and velocity using barometric pressure sensor data during descent if GPS data is unavailable. Such as when returning ballistically from a very high altitude and the descent velocity exceeds the GPS lockout limit. However, baro sensor data is only valid below 100K feet.
g. Added some announcements during the GPS lockout interval that explain Kate is waiting for the GPS to resume normal operation. This fills in the long gaps of silence that can happen on a space shot, as it free falls to a high speed while still above the atmosphere and locks out the GPS.
2. Added time since last GPS fix to the TELEMETRY screen if GPS is out during descent and Kate is using baro sensor data instead of GPS data.
3. Added an option to allow the user to select faster updates during Map Mode. The user can now set Map Mode into "FAST" mode. This sets the baud rate to 115,200 and provides up to five updates per second. Normally Map Mode uses a baud rate of 4800 and provides just one update per second.
4. Added ability to declare a flight anomaly so that the user can inform Kate in real time that something has gone wrong. This is done by accessing the PANIC MENU. It is accessed by simultaneously pressing and holding both the up and down arrow keys when the TELEMETRY screen is being displayed. Kate is supposed to automatically detect a flight anomaly, but if not, then this provides a way for the user to tell Kate one has occurred. It is optional. It is not required for the user to do so, but it may clean up some of the announcements Kate might otherwise make.
5. Removed support for all user specified units such as miles per hour for velocity and for all metric units. This was done to gain programming code space in the receiver in order to implement all the other changes outlined here.
6. GPS coordinates for latitude and longitude that are displayed as purely decimal degrees will now use plus and minus symbols rather than N,S,E,W indicators. This is in keeping with the standard way such coordinates are supposed to be displayed.
7. Fixed a bug that would allow the user to set the LCD screen display contrast too high. Which made it impossible to recover to a normal screen.
Previous version of receiver firmware (v4.8.2)