Is anyone else still having issues after upgrading to 1.11

  • 1
  • Question
  • Updated 2 years ago
  • (Edited)
I upgraded to 1.11 on the release day and ran for ~36 hours without issue.   Yesterday I had three sudden quit where the banner indicated lost communications.   Two required a long push to quit and one just required a normal quit.  If I am the sole one remaining who is still having issues I wonder if I have a hardware issue that is masking itself as a software issue.

The operating condition is direct to the computer with no internet access.  No other programs installed on the i5 running Windows 10 up to date as of five days ago.

Paul -W4PGM
Photo of Paul Mandel

Paul Mandel

  • 83 Posts
  • 21 Reply Likes

Posted 2 years ago

  • 1
Photo of Mike Hoing

Mike Hoing

  • 281 Posts
  • 43 Reply Likes
I am running Finn on the 6300 with W10

Mike
NN9DD
Photo of Rory - N6OIL

Rory - N6OIL

  • 301 Posts
  • 55 Reply Likes
Ditto on what Mike said, running on a Dell T3600 16gb ram 1TB SCSI Xeon 3.2GHz 6 cores and no issues at all.
(Edited)
Photo of Cal Spreitzer

Cal Spreitzer

  • 449 Posts
  • 113 Reply Likes
I've been running new release (1.11.12) since release on Monday 24/7 without any issues.  Zero packet loss reported so far.  Running on a Win 10 Machine as well.

Cal/N3CAL
(Edited)
Photo of Andre KM4OVH

Andre KM4OVH

  • 4 Posts
  • 1 Reply Like
I am going to recommend you try something that I learned the hard way during 27 years of supporting computer systems.
Have you tried a different network cable between the radio and computer?
Does the network cable run near any other equipment that could be introducing problems?
If possible try a different computer.
I wasted a lot of time in my computer career tracking down problems that in the end were solved by replacing bad cables or cable ends, or just rerouting away from possible interference.
Photo of Paul Mandel

Paul Mandel

  • 83 Posts
  • 21 Reply Likes
Andre - Thanks for the reply.  in order:

Yes - 3- CAT 6 and 2- CAT 7.  Different lengths and different companies.
It goes from the back of the radio to the computer.  Nothing else between or near.
I have tried 5 different computers; 3 desktops, 2 laptops.   This one is a never used  i5 desktop left over from a project at the office.   It is only running windows.  Nothing else, no time sync, no HRD, no Office, no mail and no internet.

Also,  I have put the power supply on the bench an checked it out for lag and ripple and it is fine. While on the bench I ran the radio from a new Alinco 330 switcher and still had crashes.  The power in the radio room is on it's own 50AMP breaker and sub-panel. Total house draw is 48 amps nominal.  The computer is on a pure sine-wave UPS but it fails on or off conditioned power. 

Lastly, the radio crashes most of the time (99.9%) in receive; many time after being up for hours just receiving.

Today I move the computer to my home office room and put the radio on a QOS hub.  
I had a crash both before and after the move.

Any other things that you can think of I am glad to try but I think it may have to go back to MECCA for a checkout.  I am out of things to try.

Thanks again.

Paul - W4PGM
Photo of Jon - KF2E

Jon - KF2E

  • 677 Posts
  • 222 Reply Likes
Paul,

I would hold off sending it back to Flex if you can. I shipped mine back a month ago today and still don't have an estimate for getting it back.

Jon...kf2e
Photo of Bill -VA3WTB

Bill -VA3WTB

  • 3799 Posts
  • 918 Reply Likes
Paul,,  how did things go when you worked with Flex over the help desk?
Photo of Steve Jones

Steve Jones

  • 104 Posts
  • 23 Reply Likes
Since upgrading to 1.11 last Monday all seemed fine on rx and tx after upgrade, including during a 180 mins 80m ssb contest on Monday evening. Left my 6300 on since then and was fine until this morning when I left it on rx after working an 80m local net on ssb. I did some gardening afterwards and when I came into the shack a few hours later I found the radio had disconnected itself and was not showing in the radios available window. A single touch on the off button of the 6300 did not work, so I pulled the power supply off it for 30 mins whilst I had lunch. Powered back on after lunch and booted up as usual - now left it running on 20m cw rx to see if it happens again over rest of this weekend. Disappointed as am planning on doing multi two from home in cqww ssb and cw legs with friends and will have to fal back on my new ic7300 to run alongside a k3 if the random crashing problem is still a problem by them.

Short answer, no you are not alone!  6300 here is connected to an old  network switch in the shack along with the main radio contesting i5 w10 pc and an i3 w7 laptop for day to day logging. Fed by cat 5 from the bt router hub downstairs. No wifi in use and full green bars with no reported packet losses.
Steve GW0GEI / GW9J 
Photo of Paul Mandel

Paul Mandel

  • 83 Posts
  • 21 Reply Likes
Steve - I'm not sure if I am happy that I am not the only one or sad for the same reason.   Thanks for the update.  My e-mail is good on QRZ if you want to share symptoms offline.    

Thanks again,

Paul W4PGM
Photo of Tim - W4TME

Tim - W4TME, Customer Experience Manager

  • 9186 Posts
  • 3541 Reply Likes
Steve, so you have only had one incident of a crash in over a week?  Is that correct?
Photo of Steve Gw0gei

Steve Gw0gei

  • 193 Posts
  • 50 Reply Likes
Yes çorrect Tim. Since it crashed on Saturday morning (had been on only a couple of hours as I had been away for a few days) it has been up and running on 20m and 80m. I will leave it on now to see if it happens again - running over 48hrs now since the crash (which happened on rx only). But I had been eight weeks without a crash on 1.10.160 prior to upgrading last Monday. When I did the upgrade the previous versions were not deleted and I followed the upgrade guidance to the letter (as usual).
Photo of Tim - W4TME

Tim - W4TME, Customer Experience Manager

  • 9186 Posts
  • 3541 Reply Likes
Thanks for the clarification.
Photo of Alan W4FBI

Alan W4FBI

  • 269 Posts
  • 31 Reply Likes
Maybe not the issue, but check "power management' tab of your Network Interface device/properties in control panel/device manager. Make sure the box 'Allow the computer to turn off this device to save power' is not checked...

Another Oops by Microsoft: right click on your hard drive and go to 'properties'. Click on the tools tab. Click on Optimize. You will find that it defaults to ON. You don't want this. Check Scheduled Optimization and turn that OFF. With Optimize (defragment) running, it slows the computer profoundly.

You'll find that the file system used by Windows 10 (NTFS) - does not need defragmenting. The older operating systems used FAT file system, and did require some defraging.

My .02

Alan
Photo of Paul Mandel

Paul Mandel

  • 83 Posts
  • 21 Reply Likes
Tim - Traveling this week. Will call you when I get back to discuss.

Paul -W4PGM
Photo of Tim - W4TME

Tim - W4TME, Customer Experience Manager

  • 9197 Posts
  • 3557 Reply Likes
Paul - FYI.  I'll be OOO from Thursday through Monday.
Photo of Alan W4FBI

Alan W4FBI

  • 269 Posts
  • 31 Reply Likes
NTFS does not need defraging for SSD's. And for other drives, it surely doesn't need it weekly (as the default is)
Photo of Peter K1PGV

Peter K1PGV, Elmer

  • 553 Posts
  • 322 Reply Likes
NTFS does not need defraging for SSD's. And for other drives, it surely doesn't need it weekly (as the default is)
With all due respect: Windows does not generally defrag SSDs (though it will in extreme cases). It most typically "optimizes" them by issuing trim/retrim commands.  This needs done periodically and by default is done weekly. I believe this started back in, oh, Windows Vista, I think.

Whether your rotating media (NTFS or otherwise) needs defragged weekly or not depends on the activity on the media.  Defragging rotating media weekly causes no harm, and may do some good on certain systems.

Bottom line: Like most things, Windows is smarter than most people give it credit for.  As long as you're running a version of Windows that's SSD aware (as I said, I believe this is Windows Vista), I would advise you to leave the default settings alone unless you're sure you know what you're doing.

Peter
K1PGV
(Edited)
Photo of Alan W4FBI

Alan W4FBI

  • 269 Posts
  • 31 Reply Likes
OK, Peter. You win.

I haven't defragged my HD in two years and it is at 3% fragmentation.
Photo of Peter Kirsop

Peter Kirsop

  • 36 Posts
  • 4 Reply Likes
I have experienced a loss of connectivity several times since going to v1.11.  I noticed that from time to time the network quality indicator would go yellow, then red, then back to yellow and finally green again.  The network diagnostics showed that this was a latency issue which was up to 278 the last time the radio disconnected.  The radio then needed the power cycling before it would connect again.  Gone back to v1.10, and all is OK with no issues at all.  Radio is 6300, PC i5 Win 10 with 16GB RAM.  I am not concerned as v1.10 works great for me but thought I would mention as others seem to having the same issue.
Peter GM4WCE
Photo of Steve Jones

Steve Jones

  • 104 Posts
  • 23 Reply Likes
Peter, how is your 6300 connected to the pc? Direct via cable, via a switch?, or is your pc connected to your network via wifi? I am all hard wired and dont see anything other than full green bars all of the time with no packet loss.
Regards
Steve gw0gei / gw9j
Photo of Peter Kirsop

Peter Kirsop

  • 36 Posts
  • 4 Reply Likes
Hi Steve, my 6300 is connected to a switch and the PC is connected to the same switch.
Photo of Steve Jones

Steve Jones

  • 104 Posts
  • 23 Reply Likes
Same as my set up then. I did have an issue with 1.10 that sounds the same and i traced it to some sort of conflict with the desktop app of my antennas genius switch. I had droppinf connectivty and then crashes despite reinstalling antenna genius app twice afresh. I ended up doing a full fresh install of ssdr and that worked and no problems for lastvtwo months on 1.10.

My 6300 has been on rx since its first crash on 1.11 last saturday and did another 180min rsgb cw contest with it this eveninf with no issues. Am leaving it on to see if it stays stable. Your issue sounds similar to the one i had before on 1.10 so might be worth trying a fresh install of ssdr?
73
Steve Gw0gei / gw9j
Photo of Rick Ciotti

Rick Ciotti

  • 16 Posts
  • 5 Reply Likes
Maestro wired directly to the 6500 with a gigabit switch in line.
After the update sometimes the radio is not displayed at power up. A few times the Maestro has defaulted to the radio page but the radio is not there. Could not power off, had to kill the PS to reboot. No issues like this prior to the update.
(Edited)
Photo of Rick Ciotti

Rick Ciotti

  • 16 Posts
  • 5 Reply Likes
I submitted a ticket for this, afterwards I noticed a software update twice at power up.
There has not been a crash since then. Only issue...sometimes it takes longer for the Maestro to detect the radio. Waiting a min. or so it eventually discovers the 6500. There was no delay like this with the previous version SW. I am OK with this, the radio works vry FB otherwise. FRS will figure it out.
W3DIY
Photo of Steve Jones

Steve Jones

  • 104 Posts
  • 23 Reply Likes
That sounds similar to the one crash i have had on 1.11 at the weekend as i had to pull the power off to get the 6300 to reboot. Its been ok since doinf that on Saturday lunchtime
Photo of Steve Gw0gei

Steve Gw0gei

  • 193 Posts
  • 50 Reply Likes
I had my second 1.11 crash overnight. 6300 had been on since last Saturday morning when I recovered it from the first crash. It's lasted almost a week but not quite on rx all time and with occasional use in morning 80m nets. Once again I had to cut the power to the radio this morning as single press on button would not close it down. Have left it running on rx only since this morning to see how long it lasts this time.
Photo of Tim - W4TME

Tim - W4TME, Customer Experience Manager

  • 9197 Posts
  • 3557 Reply Likes
We have an open defect for these reports (#5222) and all applicable data reported has been added to the report detail.
Photo of Steve Jones

Steve Jones

  • 104 Posts
  • 23 Reply Likes
6300 has been on all week with no issues until again today it started to crash. On this, my third since upgrading to 1.11, I was operating in the uk/ei ssb contest at the time, so I was able to observe what was happening (previous two occasions have been on rx only when I was out of the shack). I had been band hopping for around an hour or so and was cqing on 40m ssb when the receive audio audio started distorting, and I could hear via my monitor in my headphones that my tx was also starting to go darlek like. I stopped calling cq but it kept on distorting on rx - very similar issue to what I observed doing a few contests on ssb with 1.10.160 a few months ago, and I noticed the network latency increasing and going from full green bars down to one or two red ones. Rather than wait for the inevitable crash I decided to close down ssdr 1.11 to see if re opening it would sort the issue out. A reload of ssdr did not sort out the problem as the network indicator was still drifting down and then drifting back up without my doing any tx. Now, before someone says its my network, I use cat 5 direct to router from the shack switch and no wifi is in use, plus none else in the house was on a pc or other device and we have 14mbps download speed on broadband. I decided to reboot the radio, which did switch off with just the usual one touch on the switch. When it rebooted it seemed to take longer than usual to boot back up, but when it did I was able to carry on contesting with full green network indicators again and no distortion on rx or tx.

So, from the above, I think I have narrowed it down to something happening in the 6300 over a period of time, which ends up affecting the network connection via the shack switch and eventually causing the audio to distort on rx and tx - I am sure it would have crashed eventually if I had not intervened and re booted the radio, since the two recent crashes on 1.11 have both been on rx only when I have been out of the shack. I am suspecting that multiple band changes and general profile hopping this pm may have been a contributing factor possibly?

I will carry on giving away points in the contest later on tonight and tomorrow, with lots of band hopping to see if it brings on another crash.

Tim, I hope the above may assist in narrowing down the issue which is causing the crash problem. Its definitely not a network issue as my other laptop pc on the bench was still working fine on the same switch and network with dx lab running and some web sites on explorer.

Back to the bands, 73

Steve gw9j / gw0gei
Photo of Peter Kirsop

Peter Kirsop

  • 36 Posts
  • 4 Reply Likes
That is the exact same sequence of events I get here with 1.11.
Photo of Tim - W4TME

Tim - W4TME, Customer Experience Manager

  • 9197 Posts
  • 3557 Reply Likes
Steve and Peter,

This report helps a lot.  I have entered a new defect in our bug tracker (#5277) to address this specific issue of audio distortion and degraded network performance that requires a radio reboot to mitigate.  Thank you.
Photo of Steve Gw0gei

Steve Gw0gei

  • 193 Posts
  • 50 Reply Likes
No problem Tim, and hope it helps. It's displaying exactly the same symptoms prior to crash that the previous 1.10.160 displayed, so hopefully once found the fix will solve this long term issue. I shut the 6300 down again last night as I needed to allow w10 do its big upgrade - went ok so 6300 was back up upgain this evening for an hour long domestic cw contest on 80m. I will be leaving it on again now 24/7 to see how long it goes - as I work during the week it's mainly used for 15 min sched on 80m ssb some mornings, and short 80m contests mid week evenings - it's only at weekends that it gets more band hopping and general profile hopping in longer hf contests.
Photo of Steve Jones

Steve Jones

  • 104 Posts
  • 23 Reply Likes
Radio had crashed again yesterday morning when i returned to the shack - had been running 24/7 on receive since Wednesday morning. It required the power supply to be cut as single button push did not switch the 6300 off.


I was playing with n1mm set up for cqww ssb multi two yesterday pm and mentoring a team member in the use of the 6300 in so2r dual band use - carried on testing the contest set up after he had gone home and noticed that network bars were going yellow and red when i was moving bands via my profiles list - the radio didnt crash but green bars came back a couple of minutes after each general profile band change selection. Further evidence that this crash problem is both time and band hopping profile swapping related?


I am going to keep my ic7300 on the bench for cqww ssb m2 next weekend in case we have more 6300 crash issues with all of the band hopping we will be doing.

Steve gw0gei / gw9j in cqww
(Edited)
Photo of Steve Jones

Steve Jones

  • 104 Posts
  • 23 Reply Likes
Glad I kept the ic7300 on the bench for cqww - I had two crashes on ssdr in the first couple of hours of the contest - distorted rx audio again and then tx audio and then disconnect. Rebooted the radio after having to remove the power supply to get it to switch off. Within 45 mins it crashed again, so I gave up, and spent ten minutes reconfiguring n1mm for the ic7300 as the main radio in so1v mode and that radio was fine for the rest of the contest, alongside a friend's k3 in the other room.

I am now retiring my 6300 for contesting use until such time as frs fix this long standing problem. It is very disappointing, and embarrassing, given that I have been advocating flex 6000 radios to friends and young contesters, only to now have to admit that the current 1.11 ssdr is no more reliable than the 1.10.160 or the version before that.  
(Edited)
Photo of Norm - W7CK

Norm - W7CK

  • 759 Posts
  • 164 Reply Likes
Try wiring your 6300 directly to your Maestro.  No switch between them. 
Photo of Steve Jones

Steve Jones

  • 104 Posts
  • 23 Reply Likes
I dont own or use a maestro Norm. I just use mouse and flex knob
Photo of Steve Gw0gei

Steve Gw0gei

  • 193 Posts
  • 50 Reply Likes
My 6300 crashed again last night during an hour long 80m ssb contest. Just suddenly disconnected with no warning this time. It crashed still in tx and I had to remove the power to get it to reboot. It lost persistence when it did reboot, so I lost my run frequency. It's now the subject of a trade in discussion with our nearest radio shop as I have finally reached the end of my patience with this bug.
Steve gw0gei / gw9j
Photo of Steve Jones

Steve Jones

  • 104 Posts
  • 23 Reply Likes
Well no uk dealer wants to trade a 6300 and no luck selling it myself despite reducing the price to below 1300.  I guess I am stuck with the radio, back in its box, until FRS resolve the ssdr bugs causing the random disconnects. Hopefully those of us affected by this problem  may get an update in the next FRS newsletter? Steve gw0gei / gw9j