Thx Ziko . I had missed it on the specs. So presumably it will detect a TTL level change.
L.
Search found 74 matches
- Wed Apr 13, 2011 5:21 pm
- Forum: USB PC Oscilloscopes
- Topic: 4227 External Trigger
- Replies: 8
- Views: 3983
- Wed Apr 13, 2011 3:45 am
- Forum: USB PC Oscilloscopes
- Topic: 4227 External Trigger
- Replies: 8
- Views: 3983
4227 External Trigger
What type of trigger can the EXT input work with on a 4227 ? TTL (0-5V) digitial inputs? analog?
Thx.
Laurent
Thx.
Laurent
- Mon Apr 11, 2011 2:00 am
- Forum: LabVIEW
- Topic: ETS Example for LabVIEW
- Replies: 1
- Views: 1905
ETS Example for LabVIEW
There has been a few posts already asking for ETS LabVIEW examples. I was wondering when this would become available, as I am trying to get ETS running under LabVIEW as well, but the documentation is rather slim on this topics.
Thx.
L.
Thx.
L.
- Mon Apr 11, 2011 1:30 am
- Forum: LabVIEW
- Topic: GetUnitInfo string garbled 4227/4224
- Replies: 4
- Views: 3129
Re: GetUnitInfo string garbled 4227/4224
What seemed to be the problem was the fact that I am using a LabVIEW ring or enum to pass data to the Info parameter. Even though the ring or enum is set to the right data type, it still creates occasional problem when passing the paramter. If the iteration counter, or a straight number as opposed t...
- Thu Apr 07, 2011 7:46 pm
- Forum: General Software Discussions
- Topic: Kernel Driver install does not work
- Replies: 1
- Views: 2055
Kernel Driver install does not work
Hi, I am using a 4227 on XP, SDK r10.1.0.17 . I want to install the kernel driver on my PC but the information is not clear at all. In Picopp folder, USBReadme.txt suggests to copy picopp.inf and picopp.sys in the right place. Under winusb\x86, DPIsnt.exe is supposed to do the install, but after run...
- Tue Apr 05, 2011 5:49 pm
- Forum: USB PC Oscilloscopes
- Topic: High Altitude and Pico 4227
- Replies: 1
- Views: 1314
High Altitude and Pico 4227
Hi,
I was looking for the max altitude at which a 4227 digitizer can operate at without arcing issue between the lines of the PCB ? Any idea?
Thx.
Laurent
I was looking for the max altitude at which a 4227 digitizer can operate at without arcing issue between the lines of the PCB ? Any idea?
Thx.
Laurent
- Tue Apr 05, 2011 1:48 am
- Forum: LabVIEW
- Topic: GetUnitInfo string garbled 4227/4224
- Replies: 4
- Views: 3129
Re: GetUnitInfo string garbled 4227/4224
Hi Chris, The behavior is not consistent. I verified the parameters and they are correct. Of note though, the Info enumerated type expects a U8, not a U16 in the version of the dll I am using. However, there is still a small red dot at the Call Library Function connector in LabVIEW indicating there ...
- Thu Mar 31, 2011 5:45 am
- Forum: LabVIEW
- Topic: GetUnitInfo string garbled 4227/4224
- Replies: 4
- Views: 3129
GetUnitInfo string garbled 4227/4224
Has anyone experienced garbled responses from the driver when GetUnitInfo is called? I am using a 4227, and few month ago a 4224 and the same thing happened, somewhat inconsistently. Part of the strings in the response from the dll call appears garbled with funny characters... This is a problem, as ...
- Thu Mar 03, 2011 5:31 pm
- Forum: General Software Discussions
- Topic: PicoScope 4000 series driver and XP embedded
- Replies: 5
- Views: 4430
Re: PicoScope 4000 series driver and XP embedded
Yes in theory it should...
If anyone has hands-on experience with this, any insights are welcome. Thanks.
L
If anyone has hands-on experience with this, any insights are welcome. Thanks.

L
- Wed Mar 02, 2011 4:23 pm
- Forum: General Software Discussions
- Topic: PicoScope 4000 series driver and XP embedded
- Replies: 5
- Views: 4430
Re: PicoScope 4000 series driver and XP embedded
In this context "embedded" refers to the compartimentized version of the Windows OS.
Respectively, "Windows XP Embedded" (XPe) in relation to Win. XP, and "Windows Embedded Standard" in relation to Win. 7.
L.
Respectively, "Windows XP Embedded" (XPe) in relation to Win. XP, and "Windows Embedded Standard" in relation to Win. 7.
L.
- Tue Mar 01, 2011 7:38 pm
- Forum: General Software Discussions
- Topic: PicoScope 4000 series driver and XP embedded
- Replies: 5
- Views: 4430
PicoScope 4000 series driver and XP embedded

thx.
L.
- Fri May 14, 2010 2:31 pm
- Forum: LabVIEW
- Topic: Rapid Block Mode LabVIEW PS4224
- Replies: 34
- Views: 30563
Re: Rapid Block Mode LabVIEW PS4224
As per earlier conversation, the LabVIEW example you mention uses multiple API calls. This may be valid but it is not what we want to achieve. It is expected that multiple calls will generate more overhead both in the call and in the data stream resulting in more time for data transmission from the ...
- Fri May 14, 2010 3:52 am
- Forum: LabVIEW
- Topic: Rapid Block Mode LabVIEW PS4224
- Replies: 34
- Views: 30563
Re: Rapid Block Mode LabVIEW PS4224
The C code uses API calls that are different from the ones in the original LabVIEW example. Do you have a LabVIEW example of Rapid Block Mode?
thx.
Laurent
PS: do you have a skype # please. This is very inefficient to advance on this by posts. Thx. You can email it directly. Thx.
thx.
Laurent
PS: do you have a skype # please. This is very inefficient to advance on this by posts. Thx. You can email it directly. Thx.
- Wed May 12, 2010 3:34 pm
- Forum: LabVIEW
- Topic: Rapid Block Mode LabVIEW PS4224
- Replies: 34
- Views: 30563
Re: Rapid Block Mode LabVIEW PS4224
Hi, I have been trying to speed up the Rapid Block Mode example provided by Pico. In their example, the ps4000GetValueBlock is called for each segment. Since this API call allows for selecting fromSegmentIndex and toSegmentIndex, it seems possible to obtain all the data in a single call instead of c...