We have a problem with a monitoring application that leaves several Picoscope 4000s armed and waiting for triggers for 24/7/365. The PC CPU operates at 100% use with tremendous heat generation just so the driver can "wait" for the trigger. The setup (PC and scopes in an enclosed case) is on the outside of industrial equipment that also generates heat, which is outside in the hot sun all day. Needless to say, any normal industrial computer can handle the stress with a normal load, but not with 100% CPU all day and night for months. Is there a possibility of a driver that does not cause the 100% CPU use when "waiting" for trigger?
1) There are three scopes on this particular PC, but there are many installations around the country just like it.
2) Trigger level/settings seem to be irrelevant. Even in the Picoscope 6 software, if I use a 4000 series scope (even with only one attached), and i set it to trigger based on ANY set of settings, it will use 100% CPU (at least for one thread worth on one logical core) until it triggers.
3) It is armed to trigger all the time. When it triggers, it takes the data, stores it, and automatically rearms. It may trigger 30 times a day, or as little as once a week. The source of triggers is not man-made.
The other series scopes of Picoscope that I have used do not perform this way. You can arm them, and the CPU sits virtually idle until trigger.
The setup (PC and scopes in an enclosed case) is on the outside of industrial equipment that also generates heat, which is outside in the hot sun all day. Needless to say, any normal industrial computer can handle the stress with a normal load, but not with 100% CPU all day and night for months. Is there a possibility of a driver that does not cause the 100% CPU use when "waiting" for trigger.
________________________________
Want to get-on Google's first page and loads of traffic to your website? Hire a SEO specialist from Ocean Groupshttp://oceangroups.org/"> seo specialist