PicoScope 7 Software
Available on Windows, Mac and Linux
Trace intermittently freezes (most of it) when settings changed
Trace intermittently freezes (most of it) when settings changed
Hi all,
Wondering if anyone can help. I had a bit of a look through the forum and can't find anything that matches... apologies if I've missed something I should have seen.
I'm running a 2000-series picoscope on an old Win7 work machine (i3 with 4GB of RAM, 32-bit). Sometimes when I change a setting (it doesn't seem to matter which one) the majority of the trace will freeze. I will get one small section of the trace that is still active (out of 10 time divisions, maybe 0.3 of a division will still move) but the rest will be frozen. When this happens, I haven't found any way of fixing it except closing and restarting the picoscope software.
The fault doesn't seem to be any particular setting or mode, as if I save the settings when it's frozen as default settings and restart the software, it will run fine until I change maybe 1-10 settings at which point it freezes again.
I've read some hints about resource issues causing problems with the software, and looking under resource monitor I've noticed that when it freezes, the CPU maximum frequency (but not usage) immediately starts climbing up to 90%+.
Is this just a case of "computer is too old, need a new one"? I'm hoping there is something I can do short of that as upgrading will be a big job.
Any suggestions would be greatly appreciated.
Brett
Wondering if anyone can help. I had a bit of a look through the forum and can't find anything that matches... apologies if I've missed something I should have seen.
I'm running a 2000-series picoscope on an old Win7 work machine (i3 with 4GB of RAM, 32-bit). Sometimes when I change a setting (it doesn't seem to matter which one) the majority of the trace will freeze. I will get one small section of the trace that is still active (out of 10 time divisions, maybe 0.3 of a division will still move) but the rest will be frozen. When this happens, I haven't found any way of fixing it except closing and restarting the picoscope software.
The fault doesn't seem to be any particular setting or mode, as if I save the settings when it's frozen as default settings and restart the software, it will run fine until I change maybe 1-10 settings at which point it freezes again.
I've read some hints about resource issues causing problems with the software, and looking under resource monitor I've noticed that when it freezes, the CPU maximum frequency (but not usage) immediately starts climbing up to 90%+.
Is this just a case of "computer is too old, need a new one"? I'm hoping there is something I can do short of that as upgrading will be a big job.
Any suggestions would be greatly appreciated.
Brett
Re: Trace intermittently freezes (most of it) when settings changed
Hi Brett,
What appears to be happening is that the usage is not changing because the processor is effectively not taking on any more processing (which is why the screen is freezing) while it deals with clearing the decks in what is currently being processed and working hard to do it (which is why the speed is increasing).
I know how painful it can be, having to move from a machine on which you have built up a wealth of knowledge and experience of it's capabilities and workarounds, and on which you're happy and productive but, unfortunately, if this is happening too often, then it's probably time to move to a new, more capable machine.
Regards,
Gerry
What appears to be happening is that the usage is not changing because the processor is effectively not taking on any more processing (which is why the screen is freezing) while it deals with clearing the decks in what is currently being processed and working hard to do it (which is why the speed is increasing).
I know how painful it can be, having to move from a machine on which you have built up a wealth of knowledge and experience of it's capabilities and workarounds, and on which you're happy and productive but, unfortunately, if this is happening too often, then it's probably time to move to a new, more capable machine.
Regards,
Gerry
Gerry
Technical Specialist
Technical Specialist