07-28-2007 07:34 AM
07-30-2007 11:17 AM
08-01-2007 04:26 AM
08-01-2007 08:13 AM
Hi Marcin,
Alan from LeCroy Tech Support here...I see in your last note that you haven't heard back from LeCroy... Are you in the US? Sorry that no one has gotten back to you!!
Here's the basics on controlling your scope via remote control:
1. The scope comes standard with the Ethernet interface
2. GPIB is optional; you should buy the WR6-GPIB option (internal card) or the WS-GPIB adapter.
3. The best way to determine if GPIB is enabled on your scope is to go to the scope's Utilities screen and then to the Remote tab. This is where you choose TCP/IP or GPIB for the remote interface. If you don't have a GPIB card in your scope, or if you don't have the WS-GPIB cable attached, the GPIB option will be greyed out
4. NEVER install NI's GPIB card or NI's 488.2 driver on the scope, since the scope is a GPIB device and not a GPIB controller. This is important!
5. You never need to "see" the scope in MAX to control a LeCroy oscilloscope. An NI-GPIB card should showup in MAX, of course, and through this you can see that a LeCroy scope is attached, but there is never a need to explicitly "add" the scope in MAX. (MAX is an *excellent* utility, but it isn't required to use a LeCroy scope)
6. The lcwave and lecroy_wave_series drivers can be used to control the scope via either GPIB or TCP/IP since it is a VISA driver.
7. For the fastest throughput, use the TCP/IP interface. You need to install the LeCroy VICP Passport on your remote PC (here's a link to the download page: http://www.lecroy.com/tm/Library/Software/LabView/VICP.asp?menuid=8
8. In your first message, you showed a screenshot with the VISA resource control list. To connect to your LeCroy scope via GPIB, enter GPIB::N, where N is the GPIB address you've assigned to the scope. when connecting via TCP/IP, enter VICP::<ip address>, where <ip address> is the IP address of your scope. Don't forget to install the VICP Passport on your remote PC! (Not on your scope...)
9. Feel free to contact me directly, at 800-553-2769, or your local AE if you are not in the US or Canada.
Best Regards,
Alan
08-01-2007 10:04 AM
Hello,
ad. 1) OK
ad. 2 & 3 & 4) Looks like I need uninstall some things from the scope... Uninstalling now...
ad. 5) OK, I think I understand now...
ad. 6) Hmmm...
ad. 7) Installed ... on the scope and on the PC ...
ad. 😎 Works 🙂
Now I understand a little more and I can make more 🙂
a) I need to install VICP Passport on the where the LabVIEW is. If I need to control the scope from the remote PC it should be installed on this PC. If I need to run LabVIEW locally on the scope do I need the passport locally?
b) I need to enable TCP/IP control from X-Stream DSO application.
c) VICP::xxx.xxx.xxx.xxx needs to be used as VISA resource 🙂
Thanks for help Alan 🙂
With The Best Regards,
Marcin
08-01-2007 10:48 AM
Hi Marcin,
I love those smiley-faces!
a, b, c) When looking to run LabVIEW on the scope locally, you should install the VICP passport, as you have done, and setup the scope for TCP/IP remote operation. Don't use the scope's IP address, however. (I'm assuming you have it on a network, which need not be the case). Instead, use VICP::127.0.0.1. This is the "self-referencing" IP address.
A few notes about running LabVIEW on the scope... Be sure that your LabVIEW program is not hogging the memory or the CPU, since this will definitely impact the scope's performance. If you find at any time that the scope is behaving strangely, then you might find that you are using too much memory or CPU time. Creating an an executable using LabVIEW's Application Builder is a good idea, since this will allow you to run your program without also running LabVIEW itself.
Best Regards,
Alan
08-01-2007 01:55 PM
02-27-2008 06:38 AM
02-27-2008 08:14 AM
02-27-2008 08:59 AM