Now that a back-port will be done next to create a 1.11 release, I imagine it will be a long time before this bug gets addressed.
- 72 Posts
- 42 Reply Likes
Posted 2 years ago
Chris Tate - N6WM, Elmer
- 814 Posts
- 219 Reply Likes
Perhaps you should open a helpdesk ticket with flex. This is not typical behavior and may be a local issue rather than a bug. Im sure the gang would be happy to try and figure out whats going on.
- 3181 Posts
- 706 Reply Likes
Mack McCormick, Elmer
- 366 Posts
- 125 Reply Likes
Open a help desk ticket. This is not typical. My radio and various clients have been connected continuously for weeks. Try a direct LAN cable connection between your computer and the radio and test there. Also be sure your ethernet adapter is not going to sleep in power saving mode.
Mack
W4AX
Alpha Team
Tim - W4TME, Customer Experience Manager
- 9153 Posts
- 3497 Reply Likes
That is an incorrect assumption.
I am working with Rick via his HelPDesk ticket. If anyone else is experiencing an issue similar to this one, please submit a HelpDesk support ticket for issue resolution.
- 193 Posts
- 36 Reply Likes
Tim - W4TME, Customer Experience Manager
- 9153 Posts
- 3497 Reply Likes
- 104 Posts
- 23 Reply Likes
73 steve gw0gei / gw9j
Tim - W4TME, Customer Experience Manager
- 9153 Posts
- 3497 Reply Likes
From the short time that SmartSDR v2 has been out, the incident rate of the crashes has decreased dramatically, meaning we addressed a majority of the issues causing problems. But it looks like we may have a lingering issue or two we need to deal with.
The situation has improved and that is a step forward in the right direction. We just have a little more work to do to resolve these outliers.
- 168 Posts
- 35 Reply Likes
Hi Steve / Rick
Rick - Sorry to hear your problems persist.
I have upgraded to V2 and so far been lockup free, that said my lockups were quite intermittent and tended to be grouped together. Also my operating conditions / setup are different at the moment running V2.with me testing remote operation.
Have you had the lockup when running remote?
Tim - Would it be worth a separate post asking people who suffered the 1.10.16 lockup to post just there experience on V2. Plus ask that the post is restricted to that response with no diversion of the thread topic. Might help you understand if Rick's problem is the "Normal" flex lockup if other users have the problem carry over to V2.
- 72 Posts
- 42 Reply Likes
I haven't attempted to operate 2.0 in remote mode due to the still frequent lock-ups. God forbid that such a lock-up occur while in transmit mode. At this point I'm not inclined to make the additional hardware investment in the added items I'd need to ensure that I could still shut down the radio from my remote location under virtually all circumstances where that might occur.
Are you still crash free? May I ask what panadapters and slice receivers you normally have configured?
73,
Rick
- 25 Posts
- 6 Reply Likes
Like Andy I have been crash free since I installed V2 the day it came out. With Version 1.10.16 my lock-ups were several times a week (as reported). I am running 8 instances of WSJT-X with my 6700 24hours for several days now. I have done some remote, but only SSB with my iPad with no issues. So far so good.
73, Frédéric, HB9CQK
- 168 Posts
- 35 Reply Likes
My normal setup on my 6500 was 2 panadaptors and 3 slices. SSB and WSJT on the one pan. CW feeding a skimmer on the other.
But as I said I have been testing the remote quite a lot with one pan and slice only.
I will let you know if I experience any problems but so far so good.
Ken - NM9P, Elmer
- 4074 Posts
- 1267 Reply Likes
- 72 Posts
- 42 Reply Likes
I'm glad to hear that some of you appear to be stable on 2.0. I hope that remains the case.
73, Rick, W7YP
- 104 Posts
- 23 Reply Likes
I havnt experienced a crash on my 6300, which is still on 1.10.16, for around two months now, and it's been on for days at a time and been off and on every few days. Seems to have been stable since i last had to do a full uninstall and install due to a dax corruption issue again. However i no longer have a kuhne transverter attached to it and neither have i been using wsjt or wsjt-x modes in rx or tx, so my operating practices have changed. I will give wsjt-x another go on 6m next weekend to see if its still crash free after hours of wsjt mode monitoring.
I have been using a pair of k3 radios or a ic7800mk2 in recent contests such as iota but hope to regain confidence in the 6300 before the September hf contest season restarts.
Hope frs can sort out your crash problem Rick and put this issue finally to bed in the new code.
73 steve gw0gei / gw9j
Related Categories
-
FLEX-6700 Signature Series SDR
- 2851 Conversations
- 591 Followers
-
FLEX-6500 Signature Series SDR
- 3386 Conversations
- 875 Followers
-
FLEX-6700R Signature Series SDR
- 792 Conversations
- 146 Followers
-
FLEX-6300 Signature Series SDR
- 2778 Conversations
- 801 Followers
-
Maestro
- 1050 Conversations
- 266 Followers
-
FLEX-6400 Signature Series SDR
- 730 Conversations
- 122 Followers
-
FLEX-6400M Signature Series SDR
- 709 Conversations
- 102 Followers
-
FLEX-6600 Signature Series SDR
- 811 Conversations
- 127 Followers
-
FLEX-6600M Signature Series SDR
- 839 Conversations
- 123 Followers
Rick W7YP
This is not a 'local issue'. The radio is receiving extremely clean DC power and there's no RFI making it into my shack (I'm an EE who's worked in RF and embedded systems for 30+ years.) A very fast 6-core PC is controlling the radio through a high end gigabit managed switch. Crashes occur even when directly connected to the radio.
Since the Signature Series has a client-server architecture, NOTHING on the client side should cause the server (6700) to crash.
I do perhaps have a somewhat unique setup in that I have the DEMI 2m LPDA amplifier hooked up to one of the 6700's USB ports and an SPE Expert 1.3K-FA on the other USB port. I also have the internal GPSDO. So, system timing in my setup is undoubtedly different from that in many others. Based upon my years of experience in embedded systems, this has the feel of a timing-related issue.
But thanks for the suggestions. I appreciate the desire to help.
Rick, W7YP