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
Restarted SSDR and it was running about 55 MB. DAX and CAT are also running. No other programs, and have not touched SSDR - not even the vol. slider.
After 15 min, I am now up to 93 MB - WOW - The radio just keeps taking and taking.
lets wait a few more minutes ahh - now I am at 102 MB.
For kicks, I started running through the band switching and within about 30 sec. I was up to 260 MB.
For people with small memory, I suppose this could just keep going until the computer just quits?
Time to shut down SSDR and start up again - back to 55 MB, but here we go, it slowly starts to climb on its own.
Win 8.1 - using Task Manager.
Opps - just hit 125 MB still going - now at 128MB . . . glad I have 16 GB on hand . . .
Will watch this and see if it ever stops . . .
Good Luck Tim - maybe pour a few pints for you there lad ?
after another 10 min. it seems to be running between 130 - 135 MB. and has not gone up any - with the radio sitting on 80 meters and not touched. Maybe its topped-off?
But when I start doing band changes, I can drive it up a lot higher. I am now at 305 MB - was making band changes every 2 sec. for about a min. Seems to go up 4 MB per band change. I also did a few memory selection band changes.
Lets see if it goes anyway else on its own . . untouched for 5 min. and its showing 291 MB.
Will let it run for 12 hours and see where it is. I will let Flex decide if there is an issue - since I do not scan and I have left my radio on for months, it can't be too bad. But maybe an indicator.
Cheers ! Will grab a few pints myself - its almost friday afternoon . . .
I will lodge another help ticket over the weekend - no time today- but here are the basics again:
W10 i5 very recent tower pc with 16gb of fast memory and nvidia 10 card
Connected via 100mb old switch in shack to router downstairs via cat 5
Pc had been running for last week as had the radio on 80 scheds.
D4 always running for time synchro
N1mm+. Set up in so2r mode
Tvtr is Kuhne tr70h. Turned down to 4w driving a Gemini 4 solid state pa
I used wsjt 10 for first hour working jt6m mode for one longer distance sched contact
Then went onto mainly ssb with occasional cw for next hour
In the last hour, whilst running on ssb, the audio started breaking up ( I record my cq using the red button and play it back with the green button with footswitch for ptt - crude I know but it works)
I knew the crash was coming from last experience and was watching the network monitor at the time - it never went lower than the full green bar reading and son in the same room was gaming in his pc on same network and had no disruption to his connection off the same switch.
I think as it was crashing either it spiked the power a bit via the tvtr port or the swr changed as my solid state pa tripped out
My audio from the voice recorder within ssdr started breaking up and the sure enough the radio disconnected
And disappeared from the ssdr window.
A button press did not restart the radio
It required the long press to reboot the radio
It came back on but in the 80m frequency I had he morning
I reloaded my 4m tvtr profile and the radio returned to 4m on my run frequency ( rather than the freq of 70200 which is stored in the profile -wierd? )
Hope that helps- I will submit a help ticket over the weekend
As I reported yesterday, I have been playing around with the configuration of panadapters and slices throughout the day while watching the memory used by SmartSDR steadily increase. Late yesterday, I took a snapshot of Task Manager with only 4 panadapters open and 4 slices. Here's the snapshot.
Then sometime this morning while I was gone, the following.
Please note: I am running SmartSDR v18.104.22.168. I was able to restart SmartSDR without restarting the 6700. The 6700 itself did not lock up or emit any noise. Only SmartSDR failed.
I restarted SmartSDR, memory usage was initially at 124.8MB but continues to climb. The last time I looked, it was around 1543.8MB.
It looks like a memory leak to me!
I've been running this version for quite a while now without any issues. The only thing I can think of is that there have been a few Windows updates and it is possible something changed within the OS that is making it hard for SmartSDR to release memory.
Seems to be an issue though!
In both cases the 6700 had been on for about 4 hours; It was decoding 4 wsjtx slices;
win10, 1607; i7-6850; 32GB ram; machine was pretty idle.
This is almost as annoying as the dax corruption....
What is considered the normal range of memory usage for SmartSDR connected to a 6700 running 8 slices?
Upon restarting smart sdr, it wasnt very smart about the slices. While I had 8 pans, I only had 4 slices randomly distributed, all were in cw mode before I had 4 cw, 4 digu.
Just slightly off topic and I did not want to start a new thread for this question but...It is my understanding that SmartSDR will be announced at Hamvention 2017 but will it also be available for purchase during Hamvention or is just going to be the announcement?
I exported my profiles, performed a factory reset on my 6700, imported my profiles and haven't run into any more issues. It might just be a coincidence though.
Will do a two button reset; this is very annoying..
V1.10.16 with Win10 home, I7-6700, running PCALE (no scanning) and WSJT, Memory 650MB
> Long button reset
> No P.S. reboot.
> Unit had been on for abt 3 hrs and made a few short cw qso's.
> No SSB mode used in several yrs.
> I can't remember when I ever experienced a crash like this.
> Semi-dedicated (CAT5 LAN) Win 7 Pro
> Not normally connected to internet and was not when crash occurred.
> DAX, CAT running normally
> SKCCLogger program running
> No XVTR setups
The only possible link is I was running CW skimmer with one Dax IQ channel which I haven't been running for a bit, I would have been running the skimmer when I experienced the problem before.
This conversation is no longer open for comments or replies.
This conversation is no longer open for comments or replies.