Flex Lockup on 1.10.16

  • 8
  • Problem
  • Updated 2 years ago
  • In Progress

Hi,

I had successfuly run my Flex 6500 on Previous full release 1.9.13 for a few months often leaving it running for 24 hrs without any lockups.

I could not use the first recent Beta release due to numerous lockups with continuous audio tone requiring a long button press to reset.

I updated tp 1.10.16 on release and was lockup free until tonight when I experienced a lockup whilst listening to the radio. Same symptoms continuous audio tone and long button press required to reset.

Anybody else have lockup issues on 1.10.16 and does flex acknowledge that the problem still exists.

Not what I really want for the WPX contest.

Regards Andy M5ZAP

Photo of Andy M5ZAP

Andy M5ZAP

  • 201 Posts
  • 40 Reply Likes

Posted 3 years ago

  • 8
Photo of AH0U

AH0U

  • 56 Posts
  • 1 Reply Like
My 6700 running .16 software frequently locks up in the TX mode and I must turn it off and restart to get back to rec.
Photo of Cal Spreitzer

Cal Spreitzer

  • 449 Posts
  • 113 Reply Likes

I've had one lockup on my 6500 since upgrading to 1.10.16.   It was while operating remote and I was unable to turn off the radio via remote (WIMO).  it would not respond to a remote power off command.  I had to get my wife to turn off power supply. 

Cal/N3CAL

(Edited)
Photo of Jerry  WA9UKB

Jerry WA9UKB

  • 42 Posts
  • 7 Reply Likes
This might be a handy item to have , not sure of cost or availability.

Jerry,

http://www.digital-loggers.com/din.html
Photo of Larry - W8LLL

Larry - W8LLL

  • 533 Posts
  • 116 Reply Likes
I upgraded to 1.10.16 on my 6500 (WIN 7 PRO) the day It became available and it was fine until yesterday Sunday I lost connection 2 times during the day and today after work it lost a connection and got the solid tone that required the button held in until the radio restarted. The only thing I can think of that has changed is the NVidia Graphics driver I upgraded to from Microsoft updates Saturday night before I shut down the computer for the night. I just rolled back to the last beta to see how that reacts, and if it still happens I will roll back my graphics driver.
(Edited)
Photo of Chuck - KJ6HT

Chuck - KJ6HT

  • 49 Posts
  • 9 Reply Likes
I have had 1 lockup since upgrading about a week ago. Same symptoms, continuous audio tone and long button press required to reset.
Photo of David Livingston

David Livingston

  • 122 Posts
  • 28 Reply Likes
Over the past two weekend I have had several lockups with very heavy use on QSO party's. This only happened while I was using VOX. Worked fine using the mic key.
Photo of Andy M5ZAP

Andy M5ZAP

  • 201 Posts
  • 40 Reply Likes
Ok, it appears that there is still a lockup occurring on the released 1.10.16. software on other people transceivers as well as my own.

Do flex acknowledge this is an ongoing problem? and if so do they understand the root cause and have a solution in the pipeline or is this something I have to put up with.

Do we all need to raise a support ticket or do flex have it covered?
(Edited)
Photo of Tim - W4TME

Tim - W4TME, Customer Experience Manager

  • 9199 Posts
  • 3560 Reply Likes
Andy, have you cold booted the radio by powering it off and momentarily removing DC power from the radio?  This will ensure that all of the internal processors reboot.  If so and you are still experiencing the issue, please open a HelpDesk support ticket.
Photo of Andy M5ZAP

Andy M5ZAP

  • 201 Posts
  • 40 Reply Likes
Hi Tim,
I did remove the DC power lead from the radio so it had been cold booted. I am also not running any USB devices. As Paul below already has a trouble ticket in on the problem do you want me to raise another one?

Were the lockup issues present on the Beta software fully resolved ?

Thanks
Photo of Tim - W4TME

Tim - W4TME, Customer Experience Manager

  • 9199 Posts
  • 3560 Reply Likes
One definite issue was identified and resolved.  This doesn't mean there isn't another process that is causing other issues. As Eric indicated, any info we can get that might be unique to your particular configuration that can help narrow down where to look.  It is very challenging for engineering to find root cause and fix it for issues that we cannot reproduce in-house.

Regarding a trouble ticket, at this juncture, I am not sure how much we can do.
Photo of Andy M5ZAP

Andy M5ZAP

  • 201 Posts
  • 40 Reply Likes
Tim,

When you say "you are not sure how much you can do" do you mean for me individually or with regards to the problem as a whole.

I am not bothered about an ticket for myself personally but would be a little disappointed if you were not doing anything to look into and resolve an issue which is affecting a number of owners.

If there is anything I can do to help to try and log data during an event I am more than willing to help.
Photo of Craig Williams

Craig Williams

  • 89 Posts
  • 35 Reply Likes
So, I am paying $4000.00 for a radio and it locks up all the time. Not looking forward to that. I thought the industry was beyond these problems? Reminds me of the 80's and the 8088 where they had to add watchdog timers to keep the thing from going to sleep.
Photo of Eric - KE5DTO

Eric - KE5DTO, Official Rep

  • 919 Posts
  • 346 Reply Likes
Was everyone that has seen this problem in v1.10.16 using VOX?
(Edited)
Photo of Larry - W8LLL

Larry - W8LLL

  • 533 Posts
  • 116 Reply Likes
I do not use vox.
Photo of Cal Spreitzer

Cal Spreitzer

  • 449 Posts
  • 113 Reply Likes
I do not use VOX.   I also do not have any USB adapters attached to the back of the radio however I do have a NWDigital DSTAR Thumbdrive attached. 

Cal/N3CAL
(Edited)
Photo of Chuck - KJ6HT

Chuck - KJ6HT

  • 49 Posts
  • 9 Reply Likes
I do not use VOX. Just so you are aware, the issue has not happened again and my 6500 is active 12 - 14 hours a day.
Photo of Eric - KE5DTO

Eric - KE5DTO, Official Rep

  • 919 Posts
  • 346 Reply Likes
Roger that.  Thanks for the input.  Looking for clues.
Photo of Rob Fissel

Rob Fissel

  • 270 Posts
  • 48 Reply Likes
I do use VOX about 50% of the time, and have been experiencing lock ups on my 6300. It typically locks up overnight while not in use. I haven't had it lock up on me in person. 
Photo of Andy M5ZAP

Andy M5ZAP

  • 201 Posts
  • 40 Reply Likes
Hi. No my lockup occurred whilst listening. I use a foot switch so VOX is not enabled.
Photo of Don, VE2HJ

Don, VE2HJ

  • 38 Posts
  • 2 Reply Likes

Hi.

I must report that i had a lost of communication with the radio  a couple of days after opgrading .

SSDR : 1.10.16 174

Radio : 1.10.16.91 ( Flex 6500 )

The opgrade was made after unintalling all previous version of SSDR on my computer. ( Using the uninstal program )

The FlexVSP driver  was not removed.

The crash hapened when  i was not using the radio .

It happened when i open my portable , and when i read my eMail.

The portable is wifi to the same router of the computer and the radio

73


Photo of Tim - W4TME

Tim - W4TME, Customer Experience Manager

  • 9199 Posts
  • 3559 Reply Likes
It is a reasonable suggestion, but I suspect the form would either be too short or very long to cover the bases ;-)

This issue is intermittent and does not affect everyone.  In addition, some people have experienced very few incidences, others it happens more frequently.  And because the issue does not generate any user-visible data when it happens, it makes debugging very challenging.  If it was happening reliably to radios under our physical control (in the office), we have a very good chance in determining root cause and fix it.

We suspect that the issue is partly environmental in nature, meaning that things in your shack connected to the radio either physically or via the network may play a role.  We do believe that using particular features of the radio is a probable triggering mechanism, but there isn't a direct causation (press this button, radio crashes).

The type of information that is helpful is version of software you are running, radio model, the frequency of the radio faults (radio is not accessible by client software and a long-press of the power button or removing the DC power is needed to recover), the operating mode, what is physically connected to the radio hardware, they type of client and software connected to the radio and what you were doing with the radio at the time of the fault (operating digital modes, contesting, rag chewing, chasing DX, etc..).

Occasionally we'll ask a few people who are having these types of to open a HelpDesk ticket so we can do more detailed diagnostics in a one-on-one manner if we feel that we can glean some useful information by doing so.  In particular, if someone experiences the issue only once a week or every few days, then that is not as useful as some who experiences the issue several times a day.  We need to have multiple opportunities to catch the issue when it happens so that we have a better probability of getting good diagnostics in order to get to root cause.

We take these types of issues very seriously and we are working on it.  We completely understand your frustration and want this issue resolved as much or even more that you do.  Thanks for your understanding.
Photo of Don, VE2HJ

Don, VE2HJ

  • 38 Posts
  • 2 Reply Likes

Hi Tim,

This morning at exactly 10h00Z i experienced a new lost of connection with the radio. ( the popup message ). At this very moment i was looking at the "Network Diagnostics" window in SSDR.

The network was excellent and zero paket drop.

Since it happened at exactly 10h00Z and the fact that we had a time change to daylight saving time; this make me think the lost are time related.

Many digital modes need time sync. For this i do'nt use the ethernet time. I run a program called "Dimension 4" set to sync my computer time clock to a time server evary 10 minutes. 

To recover the connection i clic the OK botton and the "Radio Setup" appeared but no radio in the radio chooser. I tryed a quick press of the power botton and no usual arasing of my message and shutting down message. But to my supprise after about a minute the radio tuned off.

After powering the radio on it came back with only one Pan while i had two open. The setting of tha pan was all good.

I noted many setting so if you need more info i'll be glad to send you.


Software : v 1.10.16 174

Radio : Flex 6500 ; v 1.10.16.91




Photo of Andy M5ZAP

Andy M5ZAP

  • 196 Posts
  • 40 Reply Likes

Hi


I run dimension 4 and I was just preparing a post to say one of my lockups was after a dimension 4 time reset. But only 0.2 second time correction.

I could tell that they were aligned because the WSJT-X last log was aligned to a time resync, I re-sync every 30 mins, as you I re-sync for digital modes operation.

I will do a full post later as to the full scenario around my latest Lockup / Lost connection as I went onto to have 4 further lockups / lost connections afterwards.

(Edited)
Photo of Eric - KE5DTO

Eric - KE5DTO, Official Rep

  • 918 Posts
  • 346 Reply Likes
Donald, VE2HJ: Thanks very much for the detailed report.  This is helpful.
Photo of N5LB - Lionel B

N5LB - Lionel B

  • 228 Posts
  • 70 Reply Likes
I experienced my first lockup (6300) a few days ago, just receiving, mode cw.    A S/D of SSDR (not the 6300) and restart and all was back to normal.   I also noticed that on the Radio Setup form only the first two tabs were working.  All of the others did nothing when selected. Another restart was required. 

At no point did I have to reboot the 6300. I never received a comms lost message. 

SSDR 1.10.16
OS Windows 10x64 Creators update, clean install two days before this the only lockup.
Dimension 4 running in background - also new to the system in the past week. 

I have seen some other weird, non SSDR, errors in Event Viewer and suspect W10x64 is the likely cause for these. 

I'll get better data if it locks up again. 
Photo of k0eoo

k0eoo

  • 638 Posts
  • 89 Reply Likes
I have had two lockup's since I went from 1.9.13 to 1.10.16. The first time was three days ago and the second time was this afternoon.  In both cases I was in receive just monitoring a frequency on either 40m or 20m as I recall.  The first case I was not in the shack, when I got to the radio SSDR was frozen on the screen and nothing moving.  I closed SSDR and tried to reopen SSDR-Win, which showed no radio present.  I then had to hold down the power button to power down my 6500.  I then dropped the 12VDC supply for about 15 seconds and brought up the 6500 with no problems, my 6500 showed up in SSDR-Win and all ran just fine.

The second freeze up was this afternoon while I was sitting in front of the radio.  This time I got the same frozen screen and a distorted tone in the radio's powered speakers that Andy spoke of.  I went through the same restart as the first time and all came up just fine.

Again, in this case I was in LSB mode in receive and I may have been tuning around with the Flex Knob when my 6500 locked up, and the screen froze.

This has never happened before in the 3 years I have been using my 6500.

I might add that I shutdown my 6500 and PS every night and restart every morning.

If you have any specific questions about my setup let me know.

Dennis, k0eoo
(Edited)
Photo of Andy M5ZAP

Andy M5ZAP

  • 201 Posts
  • 40 Reply Likes
Hi Dennis

Same experience as myself. I did try the Beta softwares between 1.9.13 and 1.10.16 and they also caused the flex to lockup, each time I had to revert back to 1.9.13.

It appears the only answer until flex fix the issue is to revert back to 1.9.13
Photo of Tim - W4TME

Tim - W4TME, Customer Experience Manager

  • 9199 Posts
  • 3560 Reply Likes
How frequently were the lockups happening when running 1.10.16?  Looks like from your report it was only once.
Photo of Andy M5ZAP

Andy M5ZAP

  • 201 Posts
  • 40 Reply Likes
On 1.10.16 I have had one lockup.
On 1.9.13 I had zero
On the beta software I had 3 or 4 before reverting back to 1.9.13
(Edited)
Photo of Tim - W4TME

Tim - W4TME, Customer Experience Manager

  • 9199 Posts
  • 3560 Reply Likes
Thanks for the reports.  If anyone has any information that might point to a triggering factor, please let us know.  We are actively working on this issue.
Photo of Andy M5ZAP

Andy M5ZAP

  • 201 Posts
  • 40 Reply Likes

Hi Tim,

I had a series of lockups today the details are as follows,

1 - Flex was left switched on over night with nothing connected after I had used  SmartSDR from a laptop on the same network the night before.

2 - This morning I switched on the main station PC and started the following softeware.

Dax

Smart SDR Cat

Smart SDR (2 panadapters 4 Slice receivers all on 15m Band, exact freq available))

WSJT-X (Slice C cat comms and dax audio)

Jt Alert-X

Dx Lab (Complete Suite of programs Ip comms from commander and audio (Slice A) from Dax for winwarbler )

Dimension 4 (PC Time Sync)

3 -System left monitoring 15m

4 - Returning to sytem 1 hour later the flex was unresponsive and the "Lost connection" error message was displayed.

5 - Flex needed long button press to reset

6 - On restart smart sdr had both panadapters on 40m and no slices

7 - went back to 15m and the system locked up shortly afterwards this happended 3 times. item 6 occurred each time.

8 - Powered everything down and unplugged power from radio. Rebooted everything and ran ok all day.

Looking at the last time the WSJT-X decoded before the first lockup this aligned with the time that Dimension 4 time corrected a small correction of 0.2 seconds.

The other lockups could easily of aligned with time correction but as 15m was closed I couldnt use the last decode to confirm this. After rebooting everything forcing Dimension 4 to do further time corrections and setting to correct every 5 mins (Originally every 30 mins) did not reproduce the problem.

Tomorrow I will try and reproduce the exact same conditions.

Regards Andy M5ZAP


Photo of David Altekruse

David Altekruse

  • 18 Posts
  • 6 Reply Likes
I've noticed strange Flexradio behavior (but not loss of communications) when my Windows 10 screen saver kicks in.  Just out of curiosity, did anything like a screen saver (or sleep mode, of course) occur between your step 3 and step 4?
Photo of Andy M5ZAP

Andy M5ZAP

  • 201 Posts
  • 40 Reply Likes

There is no screensaver.

The loss of communication occurs because the Flex has locked-up/crashed.

Sorry forgot to add all the software is latest version.

Smart SDR Version Client software v1.10.16.174


(Edited)
Photo of Don, VE2HJ

Don, VE2HJ

  • 38 Posts
  • 2 Reply Likes

Hi Andy,

Tel me, do you have the GPSDO board installed ?


Donald, VE2HJ

Photo of Andy M5ZAP

Andy M5ZAP

  • 201 Posts
  • 40 Reply Likes
Hi Donald

No I don't.

Andy M5ZAP
Photo of Paul Mandel

Paul Mandel

  • 84 Posts
  • 21 Reply Likes
Tim - it seems that it loses connection with the radio a few times requiring the radio to be turned off.  On/Off button works at this point. This could happen a few times.  Then after a while you get a total freeze which requires a power off of the radio via the power supply to recover.  On the loss of connection the radio does not show in the chooser until you power cycle the radio.  The last time it froze no other software was running on the computer other than SmartSDR, Kaspersky and the system.
(Edited)
Photo of Tim - W4TME

Tim - W4TME, Customer Experience Manager

  • 9199 Posts
  • 3560 Reply Likes
A few times over what time period?  A day?  Several days?  A week?  More?
Photo of ka7gzr

ka7gzr

  • 221 Posts
  • 36 Reply Likes

Although this looks like a Flex 6000 issue it would be interesting to note what the PC CPU loading was during the problems and the Win version?

I have a 6700 with a Lap-Top running Win10 with no problems as reported. I run the 6700 at least 12 hours a day. 

Jim

ka7gzr

(Edited)
Photo of Paul Mandel

Paul Mandel

  • 84 Posts
  • 21 Reply Likes
Hours
Photo of Tim - W4TME

Tim - W4TME, Customer Experience Manager

  • 9199 Posts
  • 3560 Reply Likes
Paul. Please open a HelpDesk support ticket. I'd like to talk to you more in detail. If another support representative picks up your ticket before I do, please instruct them to assign it to me. Thanks.
(Edited)
Photo of Paul Mandel

Paul Mandel

  • 84 Posts
  • 21 Reply Likes
There is one open and I have given Dudley the same information as posted here.   For me, if I totally power offer the radio when it loses connection then I do not seem to have the freeze.  If I power down the radio after a freeze (the radio does not appear in the chooser window at this point) then I will get a few more loss of connection and then a freeze.  It seems to happen more in Digu mode but I spend most of my time in Digu or CW.  I have had freezes in CW but not in the last week.   I did have loss of connections with 1.9.9 but no hard freeze.  I have not been on Phone enough to give and opinion.   

I changed the network hub, change from an AMD to an i5 Intel with only the system, WSJT-X 17.0 r7405 and SmartSDR.  I have had shutdowns and freezes occur.   Let me know if you want me to try anything else.  What I have not tried is if it is freezing with my profiles.  This weekend I plan to run with just the standard profiles and see if I have any of the anomalies.  My profiles were previously in a 6300.  
Photo of Tim - W4TME

Tim - W4TME, Customer Experience Manager

  • 9199 Posts
  • 3560 Reply Likes
Did you instruct Dudley to assign the ticket to as requested?  I do not see it in my work queue.
(Edited)
Photo of Paul Mandel

Paul Mandel

  • 84 Posts
  • 21 Reply Likes
Just did, those pesky clients got in the way of my hobby.
Photo of Andy M5ZAP

Andy M5ZAP

  • 201 Posts
  • 40 Reply Likes
I run Smart SDR on  a high end PC recent  i7 processor. When running smartSDR it never goes over 20% and usually around 10% to 12% max.

The PC is running up to date Windows 10

It is always zero lost packets and <1mS latency.

As stated before it has never locked up on 1.9.13 during many hours of operating.
(Edited)
Photo of Eric - KE5DTO

Eric - KE5DTO, Official Rep

  • 919 Posts
  • 346 Reply Likes
How many of those that are having these kind of lock-ups are running the Dimension 4 (PC Time Sync) application?
Photo of Paul Mandel

Paul Mandel

  • 84 Posts
  • 21 Reply Likes
I do.
Photo of Cal Spreitzer

Cal Spreitzer

  • 449 Posts
  • 113 Reply Likes
Yes,  I have Dimension 4 running on my Windows 10 computer that also runs SSDR,  DDUTIL, WSJT-X, JTALERT, HRD Logbook and HRD Rotor..

Cal/N3CAL
Photo of Kevin - KS0CW

Kevin - KS0CW

  • 90 Posts
  • 11 Reply Likes
I just had my first lockup, it happened 1 hour after powering up the DC power supply & 6300 (sw 1.10.16.91) along with the windows 10 client. The only applications running were Dimension 4 and SmartSDR 1.10.16 with no radio manipulation/operating or band activity as it was still on the dummy load as i was out  tending to chores. Needless to say i was was welcomed back by a SmartSDR dialog box indicating it lost communications to the radio with the radios power button being  unresponsive. I removed DC power and powered backup and clicking along just fine as if nothing happened.
Kevin/KS0CW
Photo of Andy M5ZAP

Andy M5ZAP

  • 201 Posts
  • 40 Reply Likes

I do, as per my post.

My be interesting to ask if anybody has lock ups that doesn't run dimension 4. As Dimension 4 is often run if running data mode programs.

Photo of k0eoo

k0eoo

  • 638 Posts
  • 89 Reply Likes
How do I check if that program is running?  I checked the task manager and didn't see that program.
Photo of Andy M5ZAP

Andy M5ZAP

  • 201 Posts
  • 40 Reply Likes

You will see an icon in the system tray, hover your mouse over it and it will tell you the last time sync status. Alternatively look in the Task manager for apps running it is listed as "Dimension 4"

It will only be running if you installed the program, it is a utility to sync the PC time to a web based time server.

Photo of k0eoo

k0eoo

  • 638 Posts
  • 89 Reply Likes
I check and NO Dim 4....
Photo of Steve Gw0gei

Steve Gw0gei

  • 193 Posts
  • 50 Reply Likes

I am also using dimension 4 for time checking and syncing. However, although I had the beep lockup for the first time on the first beta version, I had no lockups using the alpha version I was given access to after submitting a help ticket. Since the latest public release came out a few weeks ago I have had no lock ups with that either and have left my 6300running on rx with wsjt-x latest version for 24hrs plus and also had it running all weekend in 80-10m cw contest last weekend with no lockup issues. Although I am not a regular user of wsjt 10 or wsjt-x the one lock up with the beep I did have was running rx only with wsjt-x monitoring on 6m for msk144 mode signals whilst I was out at work. Dimension 4 time checking is always running on both my w7 laptop and the new w10 pc I have just installed. I never use vox - ptt is either footswitch connected to the 6300 in the shack, with everything connected to lan via cat 5 to an old 16 port lan switch in the shack;  or I use mox if running remote from laptop elsewhere in the house on wfifi. I don't have dstar or digivoice waveforms installed.  Not sure if that info helps at all but mainly thought I ought to confirm that dimension 4 is also (always) in use here but I have not had any more lockups with this latest public version.

73 Steve gw0gei / gw9j

Photo of Dave-N9CHM

Dave-N9CHM

  • 68 Posts
  • 10 Reply Likes
Had my 1st lock up (with audio tone) since updating to v1.10.16.174 on the day it was released.

Radio: FLEX 6500 Limited (Aug 2013, Inv AB-7300)

Connection: Radio directly connected to Computer

Computer: HP EliteDesk 705 AMD A8 PRO-7600B, 8GB RAM, dedicated to only running the FLEX

OS: Win 7 64-bit, Service Pack 1

CPU Usage 25%  Physical Memory 36%

I run no digital modes (only SSB), so I have no applications for such installed, and no Dimension 4 either.

No other applications were running on the HP, only FLEX. 

Locked up while rag chewing 7.128 (VOX), power off/on (with front panel button) to re-set. The radio is on ~4-5 hrs per day since updated software was installed.

 

73, Dave

(Edited)
Photo of Dave-N9CHM

Dave-N9CHM

  • 68 Posts
  • 10 Reply Likes
FYI, TP-LINK TL-SG105 Gigabit switch Ports: #1= HP computer controlling FLEX, #2=2nd HP computer for Internet browsing, #3= Cat5 to Netgear WNDR3800 Router, #4= FLEX 6500, #5=unused.
Photo of Kevin - KS0CW

Kevin - KS0CW

  • 90 Posts
  • 11 Reply Likes
I just had my first lockup, it happened 1 hour after powering up the DC power supply & 6300 (sw 1.10.16.91) along with the windows 10 client. The only applications running were Dimension 4 and SmartSDR 1.10.16 with no radio manipulation/operating or band activity as it was still on the dummy load as i was out  tending to chores. Needless to say i was was welcomed back by a SmartSDR dialog box indicating it lost communications to the radio with the radios power button being  unresponsive. I removed DC power and powered backup and clicking along just fine as if nothing happened.
Kevin/KS0CW
Photo of Eric - KE5DTO

Eric - KE5DTO, Official Rep

  • 919 Posts
  • 346 Reply Likes
To each of you that have had this issue (hard lockup of the radio while running SmartSDR v1.10.16 requiring a long press on the button or a power cycle to correct):
Could you tell us what your network looks like?  Primarily, we are interested in the path from the DHCP server to your radio.  Most often, a home network will look like a router with everything connected directly to that router.
What brand/model is your router (if this is your DHCP server)?  
Do you know what the DHCP lease time is set to?  If you can't look this up in the router, you can open an admin command console and do: ipconfig /release followed by ipconfig /renew.  Then do an ipconfig /all and look at the lease times (origin and expiration).  The delta is the lease length.
(Edited)
Photo of Dave-N9CHM

Dave-N9CHM

  • 68 Posts
  • 10 Reply Likes
My Flex and HP computer are connected to each other through a TP-LINK TL-SG105 Gigabit 5 port switch. This Gigabit switch, is CAT5 wired to a Netgear WNDR3800 Wireless N600 Dual Band Gigabit Router. Latency is <1ms. Lease time is 24 hrs. Only 1 lockup in ~100 hrs of SSB operation since 2/23/17.
Photo of Cal Spreitzer

Cal Spreitzer

  • 449 Posts
  • 113 Reply Likes
Eric,

My home router is a D-Link DIR-868L connected to a Cisco SG200-8 Gigabit Switch which services my shack.  Both my Windows 10 computer and my Flex-6500 are connected to this switch.  Lease time is 7 days. 

Cal/N3CAL 
Photo of Rob Fissel

Rob Fissel

  • 270 Posts
  • 48 Reply Likes
Router for the home that handles DHCP is an ASUS RT-AC66R, with the 6300 connected to one of the gigabit ports. There is an Airport Extreme attached to the ASUS, acting as an AP only for WLAN. WLAN radios are turned off on the ASUS. The lease time is 1 day. Shack PC is Windows 7 Pro.
Photo of Andy M5ZAP

Andy M5ZAP

  • 201 Posts
  • 40 Reply Likes
Router is BT Home Hub 5 (made under licence by Sagem or Huawei) the BT router is the DHCP server.

Router connected to TP link Gigabit switches (4 switches in total in different rooms) Switch models are TL-SG1005D or TL-SG1007D (5 or 7 port versions of same switch).

Ethernet cabling to each switch is Cat 5e

Switch in Radio room (TP link TL-SG1005D) is connected to Computer and Flex 6500 with Cat 6 Cables. Nothing else is connected to that switch.

DHCP lease time is 24hrs

Network Health reported by Smart SDR and Windows 10 utility
Latency <1mS
Dropped packets is always zero
(Edited)
Photo of k0eoo

k0eoo

  • 638 Posts
  • 89 Reply Likes
My 6500 and PC W10 connected to Netgear ProSAFE FS105NA fast switch via 3' ea ethernet cable and switch is connected to ASUS RT-AC66U router via 25' ethernet cable.....  Might add, since my last lockup a week or so ago I have had NO problems of any kind, knock on wood....
Photo of Dave - WB5NHL

Dave - WB5NHL

  • 289 Posts
  • 67 Reply Likes
Flex and desktop computer are connected  to 5-port Trendnet TEG-S80g gigabit switch which feeds a central whole house 16-port TrendNet TEG-S16Dg gigabit switch.  DHCP server is Amahi 7 NAS.  Lease lengths are 4 hours
(Edited)
Photo of Dave - WB5NHL

Dave - WB5NHL

  • 289 Posts
  • 67 Reply Likes
Eric;
Have you thought that the lockup issue is related to Windows 10 etc updates/ improvements(???).  I had a couple of lockups occur awhile ago (some weeks).  I noticed that just recently Windows 10 did an update. Comparing Windows updates might shed some light i.e. service stack updates  I am running Win 10 ver 1607 with the updates shown below ( I don't list updates with a specific purpose i.e. Adobe, NVIDIA)

KB3150513    3/18/2017 This update provides the latest set of definitions for compatibility diagnostics that are performed on the system. The updated definitions will help enable Microsoft and its partners to ensure compatibility for all customers who want to install the latest Windows operating system. Installing this update also makes sure that the latest Windows operating system version is correctly offered through Windows Update, based on compatibility results.

This update may not be offered concurrently to all platforms. It will be available only to platforms for which there are new definitions available.

KB4013418    3/17/2017  This update makes stability improvements for the Windows 10 Version 1607 and Windows Server 2016 servicing stack.

KB4013429    3/17/2017  Long list of fixes some might apply  applies to Win 10,8.1,7 etc

KB3211320    1/25/2017   This update makes stability improvements for the Windows 10 Version 1607 servicing stack.
Photo of Tim - W4TME

Tim - W4TME, Customer Experience Manager

  • 9199 Posts
  • 3560 Reply Likes
Thanks for the info.  I have added all comments to the defect detail.
Photo of Rob Fissel

Rob Fissel

  • 270 Posts
  • 48 Reply Likes
FYI Ria asked me to re-upgrade my 6300 to 1.10.16 (I had rolled back after the lockups), uninstall DImension 4, and run Meinberg. This had no effect on preventing the lockups - I had two within about an 8 hour span. Also, the first install I did of 1.10.16 a month ago took 4 attempts to get a successful upgrade. The first three attempts to flash the box hung. This most recent attempt took 3 times, the third finally being successful. 
Photo of Kevin - KS0CW

Kevin - KS0CW

  • 90 Posts
  • 11 Reply Likes
FWIW -- experienced another lockup, this time it hung in transmit working JT65... long power button press to shutdown/recover.

This conversation is no longer open for comments or replies.