DSD+ 2.254

[dave3825]

I just updated thru DSDplus and it seems not to like my fmp.

 

[mtindor]

I just updated thru DSDplus and it seems not to like my fmp.

View attachment 85905

Dave,

My guess is that one of your previous updates did not fully apply. I would go back and re-apply 2.246 and then re-apply 2.254.

You need to have at least these FMP* versions:

FMP24 2.65

FMPA 2.36

FMPP 1.13

And those are in 2.246.

Mike

 

[dave3825]

@mtindor I have been out of the game for a little while. The last copy I was emailed was 2.228. Then I started updates thru the program. The latest saved copy I can locate is DSD+ 2.235 . I believe DSD+ 2.235 was the last update I did until this morning. What is the trick to download 2.246?

 

[mtindor]

You should take your last known good DSDPlus link and substitute the latest version number.

Ex:

http://www.dsdplus.com/dsdplusuploads/FastLane/##########_DSDPlus2p228.zip

Change to:

http://www.dsdplus.com/dsdplusuploads/FastLane/##########_DSDPlus2p246.zip

The ########## is unique to _you_.

Mike

 

[dave3825]

@mtindor You Rock ! ! Worked perfectly. Thank you...

 

[mtindor]

@mtindor You Rock ! ! Worked perfectly. Thank you...

Just keep in mind that only the latest 2-3 versions are stored on the server, if my memory serves me correctly. So if you or anyone else need to fetch versions older than 2-3 releases ago, you would then have to email dsdplusfastlane@gmail.com. And, everyone whose last email notification was 2.228 (which means anyone who had purchased DSDPlus on or before about 12-21-2019), you should make sure and hold onto that email (and the password within it) for dear life, because that is the password to be used for unarchiving future versions. Of course, if you didn't obtain Fast Lane until after that date, your password would have been senet in an email referencing the first Fast Lane release you got after signing up.

Glad that worked for you!

Mike

 

[n8jsw]

Is there a way to change the time frame from 4 hours to 24 hours or does it do it by its self on the two new windows

 

[vince48]

yes, look in the "event log" under "window", "current seen radio(or group)", "max age"

 

[Muxlow]

So ill assume its only tracking RID/TG for P25 systems?

Iv tried it on a DMR connect plus system and a NXDN trunked system and no worky. But does on P25

 

[Forts]

So ill assume its only tracking RID/TG for P25 systems?

Iv tried it on a DMR connect plus system and a NXDN trunked system and no worky. But does on P25

See post #20... maybe double check the files he mentioned.

 

[Muxlow]

Just checked and i do have the system in the site-loader, network file and sites
Was monitoring a P25 system then switched back to a NXDN and nada

 

[batdude]

The primary systems that I monitor are a 380 MHz P1 trunk and a 406 MHz P2 trunk. Since rolling to 2.254, I see what can best be described as "phantom keyups". it's like someone is ker-chunking multiple talkgroups with no audio. I see this on >BOTH< of these OBT systems. A Wistler scanner sitting here on these two systems >DOES NOT< see these "phantom" keyups - not unmuting or stopping on the ker-chunked TG.... Now the odd part ---- in the VC activity window, there is indication that a voice channel is active. So i'm not sure what is going on..... I would possibly buy radio maintenance if this wasn't happening on two totally separate systems.

a local 800 mhz system works 100%. Not a problem at all.

I run 2 AirSpy TCP linked units with one assigned to CC and the other to VC, using the current version of FMPA and the DSD+ 2.254FL release.

after closing the session, then restarting / cold reboot ---- DSD+ 2.254 started and the new group and TG ID tracking windows were gone... not minimized - gone. (yes, checked to make sure I started the correct version)

did a complete rebuild of the DSD+ directory (man, what a PITA that is.... it sucks chasing down all these DLL files....) - and now, it seems to be working again - at least on 800mhz.

will update later...


doug

 

[Muxlow]

Been using DSD since its came out (never had a crash of lockup), and with this latest version now DSD keeps freezing. Sometimes it will run for 10 mins, or few hours then DSD will freeze but FMP still runs fine. Have to exit out and load it back up and shes good to go. If i close the current group/radio windows i dont seem to have any issues

Its strange because i can click the Input, Output, Decoder and so on at the top and that works but all the info on the channel activity and event log have froze.

 

[ATCTech]

If you mean specifically the two new windows available in 2.254, Con+, NXDN48 and NXDN96 radio and T/G captures are shown here. Works fine.

Cheers!

 

[stmills]

Updated and love the new screens- however left my two systems running over night, found them both frozen when I got up this morning. 1 froze in 1.5 hours the other in 7 hours. This is the log from 1 of the computers:
2020.06.02 6:31:12 Sync:+P25p1 NAC:402 TSDU SCCB RFSS=1 Site=2 [ch=851.9375 SSC=04] [ch=852.8875 SSC=04]
2020.06.02 6:31:12 ADJ_STS_BCST SysID=40F LRA=0 RFSS=1 Site=1 CC=860.2375 SC=70 CFVA=3: Networked
2020.06.02 6:31:12 ADJ_STS_BCST SysID=40F LRA=0 RFSS=1 Site=9 CC=852.0375 SC=70 CFVA=3: Networked
2020.06.02 6:31:12 Sync:+P25p1 NAC:402 TSDU Opcode=9 MFID=90 09 90 0F 00 00 00 00 00 00 00
2020.06.02 6:31:12 U_REG_RSP SysID=40F SID=107908 Src=107908 Resp=ACCEPT
2020.06.02 6:31:12 GRP_V_CH_GRANT_UPDT TG=2100 ch=851.6875
2020.06.02 6:31:12 Sync:+P25p1 NAC:402 TSDU ERR11 U_REG_RSP SysID=40F SID=107908 Src=107908 Resp=ACCEPT
2020.06.02 6:31:12 ERR13 MOT_PATCH_ANN Supergroup=802 Subgroup=810
2020.06.02 6:31:12 IDEN_UP ID=0 Base=851.00625 Offset=-45 Spacing=6.25 BW=12.5
2020.06.02 6:31:12 Sync:+P25p1 TSDU ERR7 MOT_PATCH_ANN Supergroup=11518 Subgroup=11516
2020.06.02 6:31:12 CRC FAIL
2020.06.02 6:31:12 CRC FAIL
2020.06.02 6:31:12 Sync:+P25p1 TDULC ERR20 UNHANDLED EXPLICIT OPCODE: #1 90000322000000C1

 

[mrc333777]

Been using DSD since its came out (never had a crash of lockup), and with this latest version now DSD keeps freezing. Sometimes it will run for 10 mins, or few hours then DSD will freeze but FMP still runs fine. Have to exit out and load it back up and shes good to go. If i close the current group/radio windows i dont seem to have any issues

Its strange because i can click the Input, Output, Decoder and so on at the top and that works but all the info on the channel activity and event log have froze.

same thing is happening to me, if i close the fmp24 window it will show tcplink lost , and if i reload the fmp24 it says tcp is back, but no activity with dsd other than that. so i have to kill the process . i noticed some files get corrupted too.

 

[batdude]

my computer was locked up this morning as well after leaving DSD+ running last night.


doug

 

[RaleighGuy]

As a newbie, I'm happy to see these reports of DSD+ locking up because now I know it's not me.

 

[ATCTech]

FWIW it's been running here since about 7AM this morning, so about 10 hours now, and is still working fine. I'll be keeping an eye on it though.

 

[stmills]

I turned down the time window on my system that locked up in 1.5 hours last night and so far it has run for over 6 hours without locking up.