-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sik radio update 2024-1-18 #3277
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…eter is not saved back to the modem.
…be reprogrammed immediately after programming.
…untry now appears to work well. However, programming RFD900+ seems to have regressed.
… immediately after programming firmware.
…ed SBUS, freq/band and antenna parameters * for RFD900x.
… in the wrong part of the ATI command response.
…hen RC out / SBUS out checked / unchecked.
…emote modems to display country code if locked to a country, * as requested by Moreton.
…e was a multiple of 128 bytes failed.
…s from a modem with multipoint firmware.
…tes (RFD900x and RFD900ux), it waits for * and acknowledgement of the EOT packet before sending the BOOTNEW command. This may or may not * resolve the intermittent issue in which firmware update results in the modem staying in bootloader mode. * Now programs version 3.01 as the reference firmware for RFD900x to check certified (instead of 3.00).
…tes (RFD900x and RFD900ux), it waits for * and acknowledgement of the EOT packet before sending the BOOTNEW command. This may or may not * resolve the intermittent issue in which firmware update results in the modem staying in bootloader mode. * Now programs version 3.01 as the reference firmware for RFD900x to check certified (instead of 3.00).
…ne button per local/remote modem. Made it so it is enabled * depending on GPO1_1R/COUT being set.
…nto RSSI reprting mode.
…ing of cases where it was unable to communicate
… after every firmware programming regardless of success or failure.
…it fails to determine which mode the modem is in when trying to program firmware.
…te modem weren't being parsed and used in the combo box e.g. for the min and max frequency ranges. Also, added a work-around for an issue in the RFDSiK RFD900x 3.07 firmware in which it didn't return the complete set of parameters in response to an RTI5? command.
…id for nodedestination parameter.
…ATLED, and GPO1_0TXEN485
… enabled would cause it to disable AES.
…t a multiple of 20 failed to be set in the settings GUI.
…I5? query response) only one option, it now greys-out the checkbox. This was to cater to the X modem 3.15 firmware in which the ECC paramater can't be changed and is always false.
…es, if the remote modem has the same firmware version as the
…firmware which doesn't support the RTI5? query. Now supports the
… modem firmware which doesn't yet have ATI10/RTI10 command. Tidied up GUI layout.
…o modem when doing the +++ sequence to change mode from transparent to AT command mode,
… firmware into modems regardless of type of modem. Removed 50ms delay between '+' characters transmitted to modem when doing the +++ sequence to change mode from transparent to AT command mode, as this is not required by any firmware.
…ad of the program folder, to prevent exception.
…inal, RSSI and settings pages.
…e from modems than looking at the string returned by ATI command.
…estination node ID.
…umerals (for 256 bit encryption).
…umerals (for 256 bit encryption).
… says it is DINIO. If it says it is DINIO, only allows DINIO firmware to be programmed into modem.
…ith country before locking to a country.
…ud rate other than 57600bps is used.
…modem which are unknown to this software. Supports the RSSI_IN_DBM, AUXSER_SPEED and AIR_FRAMELEN settings.
…ving settings to modem(s). Resolved issue in which itshowed erroneous "Set command error" message when saving encryption key to modem.
… an error message of 'Encryption key not valid hex number <=32[/64] hex numerals' when saving change to encryption level setting to the modem.
…or in a read only directory) trying to download it would result in an error because the file could not be opened. Resolved by making the file stream open the file in read only mode.
…n mission planner, as well as SikRadio stand-alone config program
so a few things |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Updates to Mission Planner's SikRadio config screen and the SiKRadio stand-alone program from RFDTools to support most recent RFD modem features and firmware programming.