Update - 10/24/17

[joncleve]

Yes, disabling FlexStep worked.

Thank you

 

[daddyjohn]

I had exact same problem with my trx1 and the frequency issue. Was driving me nuts until I figured out to disable flex step. What changed? I have always had it enabled before.

Sent from my SAMSUNG-SM-T337A using Tapatalk

 

[pa0pvv]

Happy Tuesday everyone!

There will be an update tonight around 5pm CT for the PC apps and the TRX 1&2 CPU.


TRX-1 and TRX-2 PC apps


•Fixed issue where the application would fail to download the CPU Firmware update with a 404 error when CPU firmware 5.5 has been loaded onto the radio.

•Fixed an issue where the talkgroup ID of one recording may be carried over to the next recording in some cases in the audio file list.

•Fixed issue where the blink settings on presets for the LED were not being set correctly when using the Load Preset options.

•Added option to allow the deletion of multiple trunked systems at the same time.

•Added an update options section to the Set Location screen.


WS1080 and WS1095 pc apps


•Fixed an issue where the talkgroup ID of one recording may be carried over to the next recording in some cases in the audio file list.

•Fixed issue where the blink settings on presets for the LED were not being set correctly when using the Load Preset options.

•Added option to allow the deletion of multiple trunked systems at the same time.

•Added an update options section to the Set Location screen.

CPU Updates

TRX-1 and TRX-2

addresses a NAC exclusion bug and adds a bit more time to acquire SACCH message during NXDN

Dear Whistler Wendy,

My trx1 scanner works fine is it nessesary to update de firmware and dsp and what is improved.
I only see small improvements is this correct?.

 

[Ubbe]

With each update there have been bug fixes and even operational changes without informing us.
You should probably wait for the followup update that fixes the things they missed this time.
Flexstep works backwards, AU bandplan missing and probably more that haven't been discovered.
They touched the audio log to get rid of trunked TGs that where "held" and logged in next conventional log
but now it seems to miss a lot av subtones in the log. The subtones can clearly be heard in the audio recording but it has no stored info about it.

/Ubbe

 

[pa0pvv]

trx1 firmware

I am sorry that we do not be informed when the new firmware content.
It can change many things what you don't want.
Whistler I will send an email about these problems.

pa0pvv (Piet)

 

[daddyjohn]

I just wish we could revert back to the previous version but they do not have it on their website. :-(

Sent from my SAMSUNG-SM-G890A using Tapatalk

 

[pa0pvv]

I find that a company that firmware made also brings to an previous firmware available .
Or as a download, or a way to backup the existing firmware first.


Piet (pa0pvv)

 

[wbswetnam]

I updated my WS-1095 and my TRX-1 without a hitch.

 

[tumegpc]

Backlight/LED Preset colors are wrong

In the updated notes for version 3.10 states " Fixed issue where the blink settings on presets for the LED were not being set correctly when using the Load Preset options."

I noticed that the Backlight/LED Presets are opposite on some. Blue is red and red is blue.

 

[allend]

updated the software to the latest version first. Then upgraded my TRX-2 with no issues. All is good.

 

[W2GLD]

Not sure if there is an issue of not; however, the latest version of the TRX-1 Ez-Scan software was flagged by Microsoft Security and removed, they say it contains the following: "Trojan:Win32/Azden.B!cl" and was labeled as severe and remove from my Windows 10 PC as of 5:00pm ET today. Anyone else see or have this same issue? I tested this on two clean Windows 10 VM's as well and in both instances, Windows Security Center kills the application and removes the .EXE

For what it's worth, they haven't flagged the TRX-2 version, I have that installed as well.

 

[ebplayer]

Anyone notice hearing more traffic on NXDN systems? I have 3 in my area and qualitatively notice slightly more traffic on them. I also am hearing private calls on one of them for the first time, again maybe it's just a coincidence but I never once heard NXDN private calls since I purchased this scanner in February.

 

[tumegpc]

Anyone notice hearing more traffic on NXDN systems? I have 3 in my area and qualitatively notice slightly more traffic on them. I also am hearing private calls on one of them for the first time, again maybe it's just a coincidence but I never once heard NXDN private calls since I purchased this scanner in February.

I recently posted that there was no need for me to spend the extra $$$ for the TRX-1 over the WS1088. Well I was wrong. After checking out https://digitalfrequencysearch.com I found that there are plenty of NXDN frequencies. Bought a used TRX-1 and did the latest firmware upgrade and happy to say that it's picking up NXDN better than ever.

Looks like I'll be selling the 436HP and picking up TRX-2.

 

[devicelab]

Not sure if there is an issue of not; however, the latest version of the TRX-1 Ez-Scan software was flagged by Microsoft Security and removed, they say it contains the following: "Trojan:Win32/Azden.B!cl" and was labeled as severe and remove from my Windows 10 PC as of 5:00pm ET today. Anyone else see or have this same issue? I tested this on two clean Windows 10 VM's as well and in both instances, Windows Security Center kills the application and removes the .EXE

For what it's worth, they haven't flagged the TRX-2 version, I have that installed as well.

I hit this too. I submitted the TRX-1.exe app as a submission sample to MS. It's a false positive. It was detected by their validation system too -- but I think they'll correct it soon.

I'm now running the latest definitions and it's not warning me about the application any longer. Possibly a bug in the definition file.

 

[W2GLD]

Well something is still wrong here; I'm running the latest definitions as well and when trying to install the TRX-1 EzScan software this morning on clean Windows 10 VM's, it's instantly flagged and removed and the install executable is deleted from the system as well.

I hit this too. I submitted the TRX-1.exe app as a submission sample to MS. It's a false positive. It was detected by their validation system too -- but I think they'll correct it soon.

I'm now running the latest definitions and it's not warning me about the application any longer. Possibly a bug in the definition file.

 

[devicelab]

Ah well in fairness I am using Win7-64... Win10 is clearly being more aggressive...

 

[djeplett]

Well something is still wrong here; I'm running the latest definitions as well and when trying to install the TRX-1 EzScan software this morning on clean Windows 10 VM's, it's instantly flagged and removed and the install executable is deleted from the system as well.

Same issue here. Running Windows 10 Pro x64 here.

 

[radio3353]

As usual, Whistler puts out an update full of problems and goes silent when people seek answers..

 

[djeplett]

As devicelab mentioned, it is a false positive. That can be either Whistler's or Micro$oft's fault. Either way, it will get rectified soon, I'm sure. Redmond's focus is never on the very few who have a problem with their software, either.

To temporarily fix and allow me to install the update again I have set exclusions in Windows Defender for both the install download and the TRX-1 executable and it has worked for me.

 

[Wackyracer]

As usual, Whistler puts out an update full of problems and goes silent when people seek answers..

Windows 10 tighter security accounts for much of the problem, Whistler needs to adjust to compensate for changes in Windows 10 security.
Apply some of the suggested fixes in this thread then report back..or switch to windows 7.