LeCroy 6050A and PXEe 8108 RT

Hello

I have a LeCroy Waverunner 6050 A oscilloscope and I want to use it as a data acquisition equipment.

I want to use an SMU-8108 with a RT operating system to access the LeCroy oscilloscope with VISAS through a local network.

I can see the oscilloscope in MAX [3] and I can communicate using resources of e/s: 'VICP::169.254.103.3' in '169.254.103.1' work stations, but not the controller OR-PXIe8108 "169.254.103.2". [1]

The works of vi [2] simple when it is running on the workstation, but not OR-PXIe8108.

It returns the error:

1073807343 error occurred while opening VISA in LeCroy_hello.vi

Possible reasons:

VISA: (Hex 0xBFFF0011) insufficient location information or the device or resource is not present in the system.

I checked that the LeCroy can ping my computer and PXIe8108.

In MAX, I can add the oscilloscope under "My System" and "NO-PXIe8108".

The PXIe8108 use it:

System operating OR Real - Time PharLap 13.1

Firmware revision: 13.1

The LeCroy is configured to use the TCIP (ACIP) for remote connections

and its firmware version is 6.5.0.5.

Do I need to install some software (such as the Teledyne LeCroy ACIP Passpor) on the PXIe8108 and if so how?

Thank you and Bravo,

John.

[1] project.png

[2] hello_lecroy_vi.png

[3] MAX.png

Hi John,.

I have not worked with RT stuff in a while, so I don't know how to install it.  Do not port of $$ ACIP Pa well.  The alternative is to use the LXI(VXI-11) interface on the scope type.

With this interface, you can use a right TCPIP VISA resource.  i.e. TCPIP0::169.254.103.3::inst0:INSTR

This interface is slower than the ACIP interface during the transfer of large data sets.

We'll find the ACIP Pa$ $port is just a dll (two DLLs on my 64 bit OS, but the 64-bit version is 64-bit LabVIEW) who is on the PC at: C:\VXIPnp\WinNT\bin

See you soon,.

Leonard Brown

Engineer applciations

TeledyneLeCroy

Tags: NI Hardware

Similar Questions

  • Satellite Pro 6100 cannot start - message PXE - E61 and PXE - MOF

    My dad just bought me a satellite pro 6100 for United off ebay and when I turn it on the toshiba screen comes up, followed by: PXE - E61 and PXE - MOF. as I am a total blank computer I have not a clue what to do! any ideas...? :)

    Hello Naomi

    Don t worry, it sounds not very badly. I think that you will solve this problem by changing some settings in the BIOS. ;)

    To my knowledge, this message appears when the LAN option has been fixed at the beginning of the boot order. So solve this problem to get into the BIOS (ESC and F1) and then change the order of Boot CD Drive drive HARD etc...
    Please set the LAN at the end.

  • RIS and PXE boot does not

    I'm trying to start a toshiba SP6100 of ris, but is
    PXE - T01:File not found
    PXE - E3B: TFTP - file not found error
    PXE - MOF: Exit Intel PXE ROM.

    No problem what so ever while booting other mashies (other brands).

    When you try to boot from a remote boot disk, I get:
    Error: Could not find a supported network card...

    PC is running the latest bios (1.9)

    Any suggestions?

    Hello

    I found interesting the Article Q304992 Microsoft Knowledge Base.

    It deals with the method of PXE Boot and RIS server, maybe he could help you!

    Bossi

  • PXE - E61 and PXE - M0F errors when starting on Satellite L40 - 12 K

    I have satellite L40 - 12K, with vista home premium.
    After a while, I saw two in the start screen error messages.
    PXE - E61: Media test failure, check cable of
    PXE - M0F: Exit PXE ROM

    After contacting the helpline to a? ¬0, 50 per minute, they advised me to restore the PC hole. !!! @@$$%^^^&^%
    So I google on these errors and found to change the boot order.
    My default setting is:
    1 network (LAN)
    2 HARD DRIVE
    3 CD/DVD

    I changed it to:
    1 HARD DRIVE
    2 network (LAN)
    3 CD/DVD

    Now my error messages disappeared and see my screen to the user directly.

    Google so first of all, before you listen to paid helpdesk.

    Yes, sometimes they really Don t know the troubleshooting more simple that should be done by each call. So I hope someone writes good troubleshooting docs to improve their rate of success with such clients * easy * problems.

    Beautiful week

    Dennis

  • 61 PXE and corrupt OS

    I have a Lenovo desktop computer.  It did not work properly. When I tried to start as all other days she asks PXE - E61 media test failure, check cable and also PXE MOF from the PXE ROM. What could wrong? kindly help

    RN

    Hello

    you have another thread on this same issue in XP forums

    Here is the Vista forums

    http://answers.Microsoft.com/en-us/Windows/Forum/windows_xp-windows_install/what-is-PXE-61-media-test-failure-error-and-PXE/92714f32-ABC9-486b-B567-e3c8a05ebf35

    _________________________________________________________________

    and read this:

    Read the answers in this link on your problem below

    http://www.techsupportforum.com/forums/F16/PXE-MOF-exiting-Intel-PXE-ROM-41235.html

    and this

    http://en.community.Dell.com/support-forums/disk-drives/f/3534/t/3726795.aspx

    http://www.computerhope.com/issues/ch000706.htm

  • Error PXE - E61 satellite 1800-712

    During boot the laptop displays briefly messages PXE - E61 Media test failure check cable and PXE - M0F out Intel PXE ROM.

    It began after a couple of 'experts' tried to get a Combo CDRW/DVD drive replacement to work.

    It seems to be no real problem, although I noticed that Windows Media Player can not play music files when other applications are running - it might just be a coincidence.

    Can anyone suggest what I can do to solve what is this problem?

    Hello

    PXE is a way to boot a system on a network. You should have a right of option in the BIOS to disable/PXE boot over a network. Or, it may be listed as the first boot device. If so, change the first boot CD-ROM device and secondly to HD.

  • difference between the real time module and module fpga

    Hi experts,

    I was wondering if someone could tell me the difference between the FPGA and the module in real time (in short).

    My understanding is that the FPGA module facilitates code LV that can then be designed for the specific advice of RIO, I have used this a bit in the past.

    The real time module, I'm a little more unsure about, all I know is that it allows the creation of a 'real time' i.e. deterministic environment.

    My request is this: I wish I had several control loops running on two tables of RIO, with the host PC mainly used for recording data and user interface. I see that I have no need of RT on the host (Win XP should be good).

    Do I need the RT module?

    You are right.  In the scenario you describe, you won't need to LabVIEW RT. LabVIEW RT is used to create a deterministic execution on specific targets for intel such as the PXI-8106 and PXI-8108.  You can still use strings and floating point on RT.

  • PC Toshiba laptop tecra9100 receive a PXE - E61 error

    I have a Toshiba tecra9100 labtop and I get an error PXE - E61 message. It says Media Test failure, check cable (it is a laptop computer, it doesn't have the cables that I can see). This occurs while the system trying to boot. It was a gift from a friend, so I don't have the system disk, which he continues to ask. I went to the Toshiba site and they said to change the boot priority but none of the combinations that gives me the laptop work. I also called them and they said that there is an error in Windows. Is it possible that I can get a Windows XP system disc, or is there something else I need to do?

    * original title - I received a PXE - E61 and PXE - M0F my *.

    Hi Arochellet,

    These errors are not related to Windows, this would happen either by an incorrect setting in the basic input/output system (BIOS) or a bad boot as a bad hard drive device.

    Make sure your hard disk is configured and detected correctly in the basic input/output system (BIOS). Your computer should list an installed hard drive either the title of the home page or the page of the basic input/output system (BIOS) disks.

    Check the boot options are set correctly in the BIOS, almost all BIOS configurations must contain options specifying how your computer boots. For example, most computers should have their installation options to start similar to the example below.

    -Floppy drive
    -CD player
    -Hard drive

    Note: Change (CMOS) BIOS/complementary metal oxide semiconductor settings can cause serious problems that may prevent your computer from starting properly. Microsoft cannot guarantee that problems resulting from the configuration of the BIOS/CMOS settings can be solved. Changes to settings are at your own risk.

    I suggest that you take the laptop in a store local tech to check any hardware malfunction or internal connections.

  • PXE no longer works after upgrade SCCM 2012 R2 SP1 CU2 to SCCM 2012 R2 Sp1 CU3

    We have recently improved SCCM 2012 R SP1 CU2 Cu3 to SCCM and PXE has stopped working.

    We have about 55 DP servers in various locations, and all have active PXE. We have this problem in all locations.

    Until I did follow the troubleshooting steps below

    (1) uninstall WAIK 10,

    (2) removed from sccm boot images

    (3) installed WAIK 10

    Boot images 4) imported from sccm

    Boot images redistributed, but always PXE boot fails with the message "not received no boot PXE-53 file name."

    SMS PXE newspapers doesn't show any errors. Everyone has faced this problem. ?

    Hello Brice,.

    Thanks for posting your question on the Microsoft community.

    The question will be better suited to the audience of professionals on the TechNet forums.

    I would recommend posting your query in the TechNet forums.

    TechNet Forum
    https://social.technet.Microsoft.com/forums/en-us/home?Forum=configmanagerosd

    Thank you

  • When it is run Sysprep and Capture task requires user name and password and won't restart

    MDT 2012

    I have a Windows 7 reference image.  I should be able to start on this OS, map a drive to the scripts directory and run litetouch and select my task "sysprep and capture.  When I run that he just ask a local username and pass and don't restart or ask where I want to put my image.

    I also run sysprep manually and PXE-started and ran the task but same result.  A few dialogs that require local administrators and passowrd but never a location to copy the image from.

    When I created the sysprep and capture task, she prays for a picture that is strange.  why he poses for a picture when the sysprep and capture task is intended to create an image.

    Your question is the best answer in the IT Pro Forum: http://social.technet.microsoft.com/Forums/en-US/w7itproinstall/threads

    J W Stuart: http://www.pagestart.com

  • PXE error, pxe - e32 TFTP Open Timeout through vmnet

    Hi all

    I'm completely stuck because my installation has worked in recent weeks and has just stopped working today.


    I'm under VMware Fusion 6.02 on Max OS x I have two guest computers, the first is a Ubuntu 10.04 installation that is running a server dhcp and tftp to PXE Boot kernel images. The second is just a generic Ubuntu 64-bit virtual machine that PXE starts the image provided by the Ubuntu 10.04 VM.

    I've implemented a vmnet customized for two virtual machines by using the following commands:

    sudo /Applications/VMware\ Fusion.app/Contents/Library/vmnet-cfgcli vnetcfgadd VNET_6_DHCP no
    sudo /Applications/VMware\ Fusion.app/Contents/Library/vmnet-cfgcli vnetcfgadd VNET_6_HOSTONLY_SUBNET 192.168.0.0
    sudo /Applications/VMware\ Fusion.app/Contents/Library/vmnet-cfgcli vnetcfgadd VNET_6_HOSTONLY_NETMASK 255.255.255.0
    sudo /Applications/VMware\ Fusion.app/Contents/Library/vmnet-cfgcli vnetcfgadd VNET_6_VIRTUAL_ADAPTER yes

    With the help of vmnet-sniffer on my mac and wireshark in my Ubuntu 10.04 VM I see that packages make it started failing pxe vm for the virtual machine Ubuntu 10.04. The pxe boot vm correctly receives a DHCP address and does not work with PXE - E32 TFTP tftp open timeout.

    Packages of the present paper is the following:

    Len 590 CBC 00: 0C: 29:d0:4e:26 dst ff: ff: ff: ff: ff: ff CBC 0.0.0.0 255.255.255.255 UDP src port 68 dst dst port IP 67
    CBC Len 342 00: 0C: 29:f8:7 c: 77 dst ff: ff: ff: ff: ff: ff CBC 192.168.0.1 255.255.255.255 UDP src port 67 dst dst port IP 68
    Len 590 CBC 00: 0C: 29:d0:4e:26 dst ff: ff: ff: ff: ff: ff CBC 0.0.0.0 255.255.255.255 UDP src port 68 dst dst port IP 67
    CBC Len 342 00: 0C: 29:f8:7 c: 77 dst ff: ff: ff: ff: ff: ff CBC 192.168.0.1 255.255.255.255 UDP src port 67 dst dst port IP 68
    Len 42 00 src: 0C: 29:d0:4e:26 dst ff: ff: ff: ff: ff: ff ARP sender 00: 0C: 29:d0:4e:26 192.168.0.101 target 00:00:00:00:00:00 192.168.0.1 ARP request
    Len 42 src 00:50:56:c0:00:06 dst 00: 0C: 29:d0:4e:26 ARP sender 00:50:56:c0:00:06 192.168.0.1 target 00: 0C: 29:d0:4e:26 192.168.0.101 answer ARP
    Len 42 00 src: 0C: 29:f8:7 c: 77 00 dst: 0C: sender ARP 00 29:d0:4e:26: 0C: 29:f8:7 c: 77 192.168.0.1 target 00: 0C: 29:d0:4e:26 192.168.0.101 answer ARP
    Len 69 00 src: 0C: 29:d0:4e:26 00:50:56:c0:00:06 IP 192.168.0.101 src dst dst 192.168.0.1 UDP src port dst port 2070 69
    Len 70 src 00:50:56:c0:00:06 dst 00: 0C: 29:d0:4e:26 IP 192.168.0.1 src dst 192.168.0.101 unknown ICMP type 3
    Len 69 00 src: 0C: 29:d0:4e:26 00:50:56:c0:00:06 IP 192.168.0.101 src dst dst 192.168.0.1 UDP src port dst port 2071 69
    Len 70 src 00:50:56:c0:00:06 dst 00: 0C: 29:d0:4e:26 IP 192.168.0.1 src dst 192.168.0.101 unknown ICMP type 3

    So, I investigated the ICMP error unknown 3, which is Destination unreachable (Port Unreachable)

    a nmap - known localhost produced the following

    SERVICE OF THE PORT STATE
    67/udp open | filtered APS
    69/udp open | filtered tftp
    111/udp open | filtered rpcbind
    2049/udp open | filtered nfs
    5353/udp open | filtered zeroconf

    In addition, a netstat - nulp | grep '69' in addition confirms the tftp running daemon
    4:UDP 0 0.0.0.0:69 0 0.0.0.0: * 4159/in.tftpd

    The only major changes to the system have been an installation of the vmware tools on the vm Ubuntu 10.04 last week.

    I know that the server configurations are correct on the Ubuntu 10.04 VM. As I put the network card for the stroke of lightning Ethernet, which is able to get the addresses DHCP and PXE image to a physical machine connected to the mac via a switch. PXE boot fails only when you go through the vmnet custom on the other virtual machine.

    For any help or suggestion would be greatly appreciated.

    If you create a virtual card on that network, it'll be to default 192.168.0.1.  It seems that your DHCP/tftp server is also to 192.168.0.1.

    Move your DHCP/tftp server 192.168.0.2 and it should work.

    (Note: 00:50:56:c0:00:06 is the address MAC attributed to vmnet6 virtual card host... so the ICMP Port Unreachable message comes from the host, no server DHCP/tftp VM.)

    See you soon,.

    --

    Darius

  • Network preferences do not offer the physical Ethernet devices I (and necessary)

    When configuring network in vmware workstation Linux 9 it offers me only a selection of devices, apparently limited by too simple string-based filtering. I offered my < n > eth named devices, more a Linux already existing bridge.

    However, the device that I need to connect is called "ethmain1", which is a physical ethernet port and the only network where my DHCP and PXE servers are listening.

    There are also way incorrect "eth0", which I do not at all. This makes the automatic setting fails because it selects eth0 that does not exist.

    Is there a text file where I can just tell him the right name?

    Allright, so the answer for later use.  Thanks a lot for the support to help with this.

    / etc/VMware/Networking

    He has a copy, if the list of interfaces that vmware "compound" (people) have a "-1" at the end and it has the interface currently assigned to the gateway for vmware, with a '0' at the end. ".  You cannot edit with a correct list of the interfaces (with the "-1"), however, if you stay just the correct interface in the main entrance (with the '0' in the end, it will keep this setting.

    [code]

    VERSION = 1, 0

    response VNL_DEFAULT_BRIDGE_VNET-1

    add_bridge_mapping bridgestb-1

    eth0 add_bridge_mapping-1

    add_bridge_mapping ethmain1-1

    eth3-1 add_bridge_mapping

    add_bridge_mapping eth5-1

    tap4-1 add_bridge_mapping

    add_bridge_mapping ethmain1 0

    [/ code]

    First line "ethmain1" is ignored, but the last line sticks and things work.

  • Workstation 9 - broken PXE boot - works with 8 workstations

    VMware Workstation 9 newly released, the PXE boot is broken. It works on the same machine with VMware Workstation 8.


    Virtual machine specifications:

    -Windows 7 and Windows 7 x 64

    -Bridged networking

    -2 1 processor cores

    I tried on different hardware, without Windows Firewall, but the PXE boot is broken when you use Workstation 9. Any thoughts as to why her behave this way?

    We are trying to perform a PXE boot and it gets everything stuck by sending requests for the services of pre-launch on the remote server, however, it seems that the return packets are not received. On 8 workstations, these are received and PXE boot works correctly.

    There is no AV installed in the host operating system.

    Wow, okay, just confirmed this seems to be a MAJOR bug in the work station 9, concerning ONLY to run 2 hearts or 2 CPUs. I tested with my cell phone would support all configurations (this is a quad core with hyperthreading). This applies in my case to Novell Zenworks Imaging, but can affect more.

    Results
    Config PXE
    1 processor, 1 core Success
    1 CPU, Core 2 In case of failure
    1 CPU Core 3 Success
    1 CPU, Core 4 Success
    1 CPU, Core 6 Success
    1 CPU, Core 8 Success
    2 CPU, 1 core In case of failure
    2 CPU, Core 2 Success
    2 CPU, Core 3 Success
    2 CPU, Core 4 Success
    4 CPU, 1 core Success
    4 CPU, Core 2 Success
    8 CPU, 1 core Success

    Now here it gets crazy. My issue seems to be with the v11.2.0.0 of the Agent Novell PXE (Preboot Execution). It says "Sending queries to xxx.xxx.xxx.xxx" then he received never actually do anything to continue the boot process, but ANY other config except 2 CPU or 2 cores CPU works fine.

  • No cos found NIC error starting pxe for ESX 4.0

    Hello

    I am facing the following problem when trying to boot PXE Vmware Vsphere (ESX 4.0). I'm stuck at the error message which said 'no cos NICS found' Please find attached to this screenshot.

    I would like to briefly on what I'm trying to do here:

    I try to perform a boot PXE Vmware Vsphere on Vmware Workstation and have managed to a point, until I get this weird error mentioned above.

    (1) used Vmware Workstation version is 6.5.0

    (2) confg H/W:

    Lenovo T61 laptop computer with processor intel core duo x 86 and virtualization enabled in BIOS

    delivered with 2 physical network cards & wireless and 2 GB of RAM.

    (3) PXE server is running on RHEL5 32 bit platform. I have a DHCP, Kickstart and PXE server to run out of this box. DHCP works perfectly well without any problem but when it is a step for the identification of the host name.

    IP and so forth he said cos NICs not found and I see my dhcp server attempts to assign dynamic IP and it also displays no signal thank you.

    I have PXE starts ESX 3.5 with no problems and it worked like a charm. This is the first time, I ran into problems of this kind. I manually installed ESX 4.0 but it seems no more using the anaconda Installer and

    the installation of the Poles kickstart file created is very discreet and does not contain sufficient information to customize the script is below.

    Please find the entry that I have under the pxelinux.cfg directory on my PXE server:

    label esx4.0

    kernel esx4.0 - vmlinuz

    append initrd = esx4.0 - initrd.img mem = 512 M quiet ks = FTP:///pub/kickstart/ESX4.0.cfg ksdevice = vmnic0

    I'm also willing to share my script to start with you. Please find attached the script below. Kindly let me know how to proceed further. I would be really grateful if you could suggest if any changes to do to my

    startup script.

    See you soon,.

    Kunal

    Post edited by: kkalyanp80

    Post edited by: kkalyanp80

    Double post, please refer to this topic: No cos found NIC error starting pxe for ESX 4.0

    =========================================================================

    William Lam

    VMware vExpert 2009

    Scripts for VMware ESX/ESXi and resources at: http://engineering.ucsb.edu/~duonglt/vmware/

    repository scripts vGhetto

    VMware Code Central - Scripts/code samples for developers and administrators

    150 VMware developer

    Twitter: @lamw

    If you find this information useful, please give points to "correct" or "useful".

  • Satellite Pro 6100 himself turn off

    Hello

    I'm from the Italy. It is 3 days that my Satellite Pro 6100 after some time (it can be 30 minutes or 3 hours) close itself.
    I tried to update bios version 1.70 to 1.90 without any result. I tested my HARD drive and it works fine. I formatted and reinstalled Windows XP Home SP2 Pro edition but the problem that it is still there.
    When it crash, reboot, it seems 'BAD RTC BATTERY' and "BAD CMOS", I have to press F1, then I exit without changing anything.

    I saw that 3 weeks ago appears at the beginning of this message: "PXE - E61 MEDIA TEST FAILURE CHECK CABLE"and"PXE - MOF OUTGOING INTEL PXE ROM" but works laptop well until 2 days ago.

    I don't know why, but every time I restart now stop when WINDOWS XP is on the window (not the first logo on page WXP black) cyan, but the second on the window cyan; can do work that I have to press CTRL + ALT + CANCELLED and it go to the desktop.

    I don't know what to do? Center of Toshiba, it is far from my town, if you can help me will be appreciated.

    Sorry for my English, I read a few post but exactly with my problems, there is no job.
    Thanks in advance, it's a great laptop I jump to save it.

    p.s. There is no dust on it, I tried to lift the keyboard to clean, but it was already clean, even behind the fan.

    Hello supertraz,

    On 6100 laptop there is a soft spot between the control panel and from the motherboard, causing this malfunction. You will not be able to solve this problem simply raise your keyboard and blowing air into your laptop.

    A good description on this problem (I had, too) can be found on this forum posted by user seintaxx here:
    http://www.eXpansys.com/ft.aspx?i=104221&thread=7

    A photo of the defaulting party is here:
    http://img204.imageshack.us/img204/3/sp6100fixby1.jpg

    Good luck with it.

    Kind regards
    chain

Maybe you are looking for