Looks like they fixed the bug where the display would flip @ 507.1875 (2/2/2024) John
WD6ABC Member Premium Subscriber Joined Feb 2, 2018 Messages 91 Location Santa Ana, Ca. Feb 3, 2024 #1 Looks like they fixed the bug where the display would flip @ 507.1875 (2/2/2024) John
R0am3r Salt Water Conch Premium Subscriber Joined Apr 13, 2014 Messages 761 Location Oneida County, NY Feb 3, 2024 #2 Thanks John! I wonder if there are any other fixes?
belvdr No longer interested in living Joined Aug 2, 2013 Messages 2,567 Feb 3, 2024 #3 R0am3r said: Thanks John! I wonder if there are any other fixes? Click to expand... According to Uniden: 1.23.05 Main (2/2/2024) This firmware applies the following bug fix: Fixed a bug in Waterfall mode where the IF polarity was switched at a specific frequency and the carrier was displayed on the opposite side. Click to expand... SDS200FirmwareUpdate < UnidenMan4 < TWiki info.uniden.com
R0am3r said: Thanks John! I wonder if there are any other fixes? Click to expand... According to Uniden: 1.23.05 Main (2/2/2024) This firmware applies the following bug fix: Fixed a bug in Waterfall mode where the IF polarity was switched at a specific frequency and the carrier was displayed on the opposite side. Click to expand... SDS200FirmwareUpdate < UnidenMan4 < TWiki info.uniden.com
belvdr No longer interested in living Joined Aug 2, 2013 Messages 2,567 Feb 3, 2024 #4 New main firmware, no sub this time. I applied it successfully, but since I don't use the waterfall, I cannot test their fix. My Python scripts still work and it's still receiving well. Looks like I'm good so far.
New main firmware, no sub this time. I applied it successfully, but since I don't use the waterfall, I cannot test their fix. My Python scripts still work and it's still receiving well. Looks like I'm good so far.
JoeBearcat Active Member Uniden Representative Joined Jun 30, 2020 Messages 2,008 Feb 5, 2024 #5 It also resolved the issue of some users being 'stuck' at v1.23.03A since Sentinel saw that as being the same as 1.23.03.
It also resolved the issue of some users being 'stuck' at v1.23.03A since Sentinel saw that as being the same as 1.23.03.