Search found 40 matches

by bboyes
Mon Apr 29, 2019 5:36 am
Forum: PicoScope 6 for Windows
Topic: PS6 Windows memory leak crash
Replies: 17
Views: 10479

Re: PS6 Windows memory leak crash

Memory leaks are typically in the program, not the OS. The application memory usage should not grow over time if its settings are not changed.
by bboyes
Fri Apr 26, 2019 11:06 am
Forum: PicoScope 6 for Windows
Topic: PS6 Windows memory leak crash
Replies: 17
Views: 10479

Re: PS6 Windows memory leak crash

Thank you, I will run the interim release today. Installing it now. If I run task manager with the current stable version, I can actually see memory going away - after less than 24 hours, memory use has increased from 34% to 64%. I assume you have tested with some memory use monitor running. It seem...
by bboyes
Thu Apr 25, 2019 10:43 pm
Forum: PicoScope 6 for Windows
Topic: PS6 Windows memory leak crash
Replies: 17
Views: 10479

PS6 Windows memory leak crash

Yesterday PS6 on Win10 Pro crashed after not even two days. Here are the key lines from trace.xml Run.Pressed=True OutOfMemoryException handled i...
by bboyes
Thu Feb 07, 2019 11:57 pm
Forum: Projects
Topic: PicoScope 3425 doing a fantastic job capturing >300V p-p differential surges
Replies: 3
Views: 8640

Re: PicoScope 3425 doing a fantastic job capturing >300V p-p differential surges

Thanks for calling that to my attention. So that is one area the 3425 is better. I did also order two 442 probes... may need to get two more.
by bboyes
Wed Feb 06, 2019 5:30 pm
Forum: Projects
Topic: PicoScope 3425 doing a fantastic job capturing >300V p-p differential surges
Replies: 3
Views: 8640

PicoScope 3425 doing a fantastic job capturing >300V p-p differential surges

I recently purchased a used 3425 and it has turned out to be the key instrument on this project! We are looking for destructive voltage surges on railroad tracks. The PicoScope 6 software is fantastic and we are logging data 24/7 using alarms, and pushing into the Google cloud from a remote site. Th...
by bboyes
Wed Jan 30, 2019 10:58 pm
Forum: PicoScope 6 for Windows
Topic: No logic trigger (A||B||C||D) for 3425?
Replies: 3
Views: 2856

Re: No logic trigger (A||B||C||D) for 3425?

Can the 4444 do this type of triggering?
by bboyes
Wed Jan 30, 2019 4:14 pm
Forum: PicoScope 6 for Windows
Topic: How to log all active channels with Alarm trigger
Replies: 1
Views: 2532

How to log all active channels with Alarm trigger

Hi, I've been setting up a test case to capture and log to disk using alarms. But I am finding that only the trigger channel (not all active channels) get logged! I have a 4-channel 3425 and want to log ALL the channels at every trigger event. How can I do this?
by bboyes
Mon Jan 28, 2019 9:53 pm
Forum: USB PC Oscilloscopes
Topic: Test Leads for 3425 differential inputs
Replies: 1
Views: 2199

Test Leads for 3425 differential inputs

Hi, are the automotive leads such as TA128 3m long, or the PP718 set, or the TA200 5m long series, recommended to maintain the differential performance of the 3425? The Leads I have are shorter, about 1 meter, and labeled Alpha Wire P/N 5616B2001 20 AWG and end in red and black 4mm stacking connecto...
by bboyes
Mon Jan 28, 2019 4:54 pm
Forum: PicoScope 6 for Windows
Topic: No logic trigger (A||B||C||D) for 3425?
Replies: 3
Views: 2856

No logic trigger (A||B||C||D) for 3425?

Picoscope 6.13.15 help says there is a logic trigger to let me capture on any of the four channels of 3425 exceeding a level. But this feature seems not allowed on the 3425 when I try to use it - there is no such menu. Is there no way to do this on the 3425? What about on other PicoScopes? I could f...
by bboyes
Wed Dec 26, 2018 11:22 pm
Forum: PicoScope 6 for Linux
Topic: Any hope of autosaving captured events to disk in Linux?
Replies: 1
Views: 3149

Any hope of autosaving captured events to disk in Linux?

HI, we have an application need to wait unattended for very infrequent (hours, days, or weeks, at least) electrical events, trigger on them, and capture and log to disk analog channels to a file with a timestamp. Then when the next event happens, repeat to a new file. All automatically and unattende...