USBTMC Gaussmeter

Hey everybody!
I'm a total LabView newbie, so I've got a feeling that my question is probably answered in about a dozen places.  All help is appreciated, and please feel free to point me to other threads/tutorials/examples.
My company is using LabView 8.2.1 and a coworker has asked me to create a stepper motor that will rotate our device to next to a gaussmeter's probe.  The motor interface we can takle later, as for right now I'm trying to figure out the gaussmeter.  I'll be using a FW Bell 5180 hand held.  It's a USBTMC device, so it's commands are pretty straightforward.  I need to pass it strings and then read it's responses. 
The problem I'm having now is communication.  I know the device can communicate to my PC b/c the software that came with it works (displays current readings on the FW Bell software included with the device), but I cannot seem to get it to show up on NI-MAX.  I've not gone so far as creating my own USB RAW driver as described here:
http://zone.ni.com/devzone/cda/tut/p/id/4478
because, I believe that I don't need to according to section 3.  I guess my specific question is, how do I get my gaussmeter to 1. Show up in NI-MAX and 2. Get my gaussmeter to show up as an option under the VISA resource name dropdown menu on the Front Panel.
I'll try to answer any questions... 
Thanks again!

Dennis-
Not sure if this will help, but here's the fwb5100.inf file, copied and pasted directly (the only .inf included in the file folder):
[Version]
Signature = "$Chicago$"
provider  = %manufacturer%
DriverVer = 08/27/2006,0.1.12.0
CatalogFile = fwb5100.cat
CatalogFile.NT = fwb5100.cat
CatalogFile.NTAMD64 = fwb5100_x64.cat
Class = LibUsbDevices
ClassGUID = {EB781AAF-9C70-4523-A5DF-642A87ECA567}
[ClassInstall]
AddReg=libusb_class_install_add_reg
[ClassInstall32]
AddReg=libusb_class_install_add_reg
[libusb_class_install_add_reg]
HKR,,,,"LibUSB-Win32 Devices"
HKR,,Icon,,"-20"
[Manufacturer]
%manufacturer%=Devices,NT,NTAMD64
; Files
[SourceDisksNames]
1 = "Libusb-Win32 Driver Installation Disk",,
[SourceDisksFiles]
libusb0.sys = 1,,
libusb0.dll = 1,,
libusb0_x64.sys = 1,,
libusb0_x64.dll = 1,,
[DestinationDirs]
libusb_files_sys = 10,system32\drivers
libusb_files_sys_x64 = 10,system32\drivers
libusb_files_dll = 10,system32
libusb_files_dll_wow64 = 10,syswow64
libusb_files_dll_x64 = 10,system32
[libusb_files_sys]
libusb0.sys
[libusb_files_sys_x64]
libusb0.sys,libusb0_x64.sys
[libusb_files_dll]
libusb0.dll
[libusb_files_dll_wow64]
libusb0.dll
[libusb_files_dll_x64]
libusb0.dll,libusb0_x64.dll
; Device driver
[LIBUSB_DEV]
CopyFiles = libusb_files_sys, libusb_files_dll
AddReg    = libusb_add_reg
[LIBUSB_DEV.NT]
CopyFiles = libusb_files_sys, libusb_files_dll
[LIBUSB_DEV.NTAMD64]
CopyFiles = libusb_files_sys_x64, libusb_files_dll_wow64, libusb_files_dll_x64
[LIBUSB_DEV.HW]
DelReg = libusb_del_reg_hw
AddReg = libusb_add_reg_hw
[LIBUSB_DEV.NT.HW]
DelReg = libusb_del_reg_hw
AddReg = libusb_add_reg_hw
[LIBUSB_DEV.NTAMD64.HW]
DelReg = libusb_del_reg_hw
AddReg = libusb_add_reg_hw
[LIBUSB_DEV.NT.Services]
AddService = libusb0, 0x00000002, libusb_add_service
[LIBUSB_DEV.NTAMD64.Services]
AddService = libusb0, 0x00000002, libusb_add_service
[libusb_add_reg]
HKR,,DevLoader,,*ntkern
HKR,,NTMPDriver,,libusb0.sys
; Older versions of this .inf file installed filter drivers. They are not
; needed any more and must be removed
[libusb_del_reg_hw]
HKR,,LowerFilters
HKR,,UpperFilters
; Device properties
[libusb_add_reg_hw]
HKR,,SurpriseRemovalOK, 0x00010001, 1
; Services
[libusb_add_service]
DisplayName    = "LibUsb-Win32 - Kernel Driver 08/27/2006, 0.1.12.0"
ServiceType    = 1
StartType      = 3
ErrorControl   = 0
ServiceBinary  = %12%\libusb0.sys
; Devices
[Devices]
"FW Bell 5180 Gauss Meter"=LIBUSB_DEV, USB\VID_16a2&PID_5100
[Devices.NT]
"FW Bell 5180 Gauss Meter"=LIBUSB_DEV, USB\VID_16a2&PID_5100
[Devices.NTAMD64]
"FW Bell 5180 Gauss Meter"=LIBUSB_DEV, USB\VID_16a2&PID_5100
; Strings
[Strings]
manufacturer = "FW Bell"

Similar Messages

  • Hall effect gaussmeter

    Hey everybody!
    I'm a total LabView newbie, so maybe my question
    is probably answered in about a dozen places.  All help is appreciated,
    and please feel free to point me to other threads/tutorials/examples.
    What i'm trying to do is simulate a gaussmeter via labview.I have a hall effect sensor from honeywell,model  ss496a1 and a daq(NI USB-6008).How exactly can i build my gaussmeter?I know i have to supply my sensor with a Vc and then measure Voutunder the presence of a magnetic field,but i cant because obviously i'm doing something wrong!Can anyone tell me the exact steps i have to go through?
    Many thanks in advance!
    Solved!
    Go to Solution.

    You can use the separate buttons.  To be sure that only one button is pressed at a time, you would need to use local variables or property nodes to reset the others.
    I customized the radio button to look more like your panel.  The radio button has the "one button at a time" functionality built in so you do not need to program it yourself.  You could make the frame invisible using the coloring tools.
    Lynn 
    Attachments:
    Gaussmeter.3.vi ‏87 KB
    Gaussmeter Scale.ctl ‏6 KB

  • USBTMC device does not show up in MAX.

    I have a USB device that will not show up in MAX.  When I plug the device into the computer, it is recognized as a USBTMC device and Windows chooses NiUsbTmc.sys as the driver.  I believe it also uses niusbtmc.inf and niusbtmc.pnf.  After going through the process and rebooting, the device shows up in the Windows device manager as a USB Test & Measurement device.  When I open MAX, the device does not show up in the device tree, nor can I seem to find a way to communicate with it.  So I uninstalled the device, removed the files above to a temp directory, rebooted, and then created a new inf file using the VISA driver wizard.  After going through that whole process, rebooting and then plugging the device back into the computer, I directed Windows to use the new inf file.  The device now shows up in the Windows device manger as a NI-VISA device and the driver is NiViUsbK.sys.  I open MAX back up and the device is nowhere to be found.  I tried using the VISA Interactive control to find the device, but no luck.  What step or steps am I missing?

    Just plugging the instrument in should have made the device appear as USBTMC in MAX and using the driver wizard is not correct. I don't understand why it didn't show up in MAX with either method though. I've only a small amount of experience with USBTMC but have used the wizard a lot for internally developed USB instruments and they have always appeared in MAX. What version of VISA are you using? The latest version is 4.1 that can be downloaded from http://digital.ni.com/softlib.nsf/websearch/B1A783​7FFFD2826E8625729100689D3C?opendocument&node=13207​....

  • Getting an USB USBTMC device into MAX when it doesn�t detect it?

    I am trying to control an Agilent 33220A Function Generator over a USB connection.
    I am running LabVIEW 7.1, NI-VISA 3.1, and Max 3.1.1.
    Windows drivers for the generator are installed, and working. The generator shows up as a "USB Test and Measurement Device". I can connect to it with Agilent’s Waveform Editor.
    The problem I am having is the device does not show up in Measurement & Automation Explorer.
    I tried using ‘VISA Driver Development Wizard’ to create an inf file, and MAX was then able to detect the generator. However this caused it to be in USB RAW mode. None of the GPIB style commands are working this way.
    The generator is USBTMC compliant. How can I get MAX to detect it correctly? As near as I can tell Agilent’s installer wrote all the settings directly into the registry, there is no inf file.
    Thanks,
    Richard

    That’s basically the problem. The generator is currently not associated with NI-VISA. I can get it associated by generating an .inf file with NI’s VISA Driver Development Wizard. But then, when it shows up in MAX it’s a USB Raw Resource. Device ID: USB0::0x0957::0x0407::MY44000798::RAW.
    I cannot communicate with it in RAW mode. I need it to show up with an ::INSTR extension.
    All the threads I have read indicate that the VISA Driver Development Wizard should only be used for non-USBTMC complaint devices. USBTMC complaint devices are supposed to just show up automatically. Plug-and-Pray isn’t working.
    I need to get Agilents USB driver associated with NI-VISA. Not bypass it by creating a raw mode driver. Is there any way to do this?
    Thanks,
    Richard

  • Udev not loading the right driver for usbtmc device

    I have a usb beam profiler  and I'm trying to get it to work on arch linux. It works using NI-VISA, so I should be able to communicate with it using usbtmc. However, when I plug it in, it does not show up in /dev.
    I think the problem is that udev is not loading the tmc interface driver when I plug it in.
    Here's a snippet of the output from lsusb -v:
    Interface Descriptor:
    bLength 9
    bDescriptorType 4
    bInterfaceNumber 0
    bAlternateSetting 0
    bNumEndpoints 4
    bInterfaceClass 255 Vendor Specific Class
    bInterfaceSubClass 0
    bInterfaceProtocol 0
    iInterface 0
    I believe that bInterface* should look something like:
    bInterfaceClass 254 Application Specific Interface
    bInterfaceSubClass 3 Test and Measurement
    bInterfaceProtocol 1 TMC
    iInterface 5 TMC488
    Is there a way to force udev to load the right interface? Or is the problem that I'm missing something from my kernel?

    Could you post the entire output of lsusb -v for the device?
    Bus 001 Device 013: ID 1313:8019 ThorLabs
    Couldn't open device, some information will be missing
    Device Descriptor:
    bLength 18
    bDescriptorType 1
    bcdUSB 2.00
    bDeviceClass 0 (Defined at Interface level)
    bDeviceSubClass 0
    bDeviceProtocol 0
    bMaxPacketSize0 64
    idVendor 0x1313 ThorLabs
    idProduct 0x8019
    bcdDevice 0.00
    iManufacturer 1
    iProduct 2
    iSerial 3
    bNumConfigurations 1
    Configuration Descriptor:
    bLength 9
    bDescriptorType 2
    wTotalLength 46
    bNumInterfaces 1
    bConfigurationValue 1
    iConfiguration 0
    bmAttributes 0x80
    (Bus Powered)
    MaxPower 500mA
    Interface Descriptor:
    bLength 9
    bDescriptorType 4
    bInterfaceNumber 0
    bAlternateSetting 0
    bNumEndpoints 4
    bInterfaceClass 255 Vendor Specific Class
    bInterfaceSubClass 0
    bInterfaceProtocol 0
    iInterface 0
    Endpoint Descriptor:
    bLength 7
    bDescriptorType 5
    bEndpointAddress 0x02 EP 2 OUT
    bmAttributes 2
    Transfer Type Bulk
    Synch Type None
    Usage Type Data
    wMaxPacketSize 0x0200 1x 512 bytes
    bInterval 0
    Endpoint Descriptor:
    bLength 7
    bDescriptorType 5
    bEndpointAddress 0x04 EP 4 OUT
    bmAttributes 2
    Transfer Type Bulk
    Synch Type None
    Usage Type Data
    wMaxPacketSize 0x0200 1x 512 bytes
    bInterval 0
    Endpoint Descriptor:
    bLength 7
    bDescriptorType 5
    bEndpointAddress 0x86 EP 6 IN
    bmAttributes 2
    Transfer Type Bulk
    Synch Type None
    Usage Type Data
    wMaxPacketSize 0x0200 1x 512 bytes
    bInterval 0
    Endpoint Descriptor:
    bLength 7
    bDescriptorType 5
    bEndpointAddress 0x88 EP 8 IN
    bmAttributes 2
    Transfer Type Bulk
    Synch Type None
    Usage Type Data
    wMaxPacketSize 0x0200 1x 512 bytes
    bInterval 0
    What device node name are you expecting?
    Not sure, but probably /dev/usbtmc0
    Is there a chance that it is being instantiated as a HID device?  Does /dev/usbhid0 appear?
    Nope, don't have a /dev/usbhid0
    What does the journal say when the device has been attached?
    I'm not sure what you mean, but dmesg says:
    [ 6095.219400] usb 1-1.2: new high-speed USB device number 14 using ehci-pci
    and udevadm monitor says:
    KERNEL[6098.321484] add /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2 (usb)
    KERNEL[6098.321887] add /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0 (usb)
    UDEV [6098.324333] add /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2 (usb)
    UDEV [6098.325356] add /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0 (usb)

  • How do I get LabVIEW to recognise a Gaussmeter as a device through COM port 1?

    Hello everyone.
    I am trying to do display the readings from a GM05 Gaussmeter in LabVIEW through COM Port 1 on my computer.  I have installed the relevant drivers and MAX recognises that something is plugged in by listing COM 1, COM 2 and LPT 1 under devices, but it does not recognise the Gaussmeter as a device (it does not say 'device #' in brackets next to COM 1)..  Therefore when I come to create a new Virtual Channel in the Data Neighbourhood I cannot select my COM port as a device.  Can anyone help me to solve this problem, any advice would be greatly appreciated.
    Regards,
    Rob.

    Unlike GPIB the com port or serial communication usually does not have an identify query, so it wont auto recognize the device.  You should look in the manual of the device and send an appropriate string (there might be a self-test or identify string) and check for the correct response.  Not all devices communicate both ways (some are talkers, some are listeners and many are both).
    Paul
    Paul Falkenstein
    Coleman Technologies Inc.
    CLA, CPI, AIA-Vision
    Labview 4.0- 2013, RT, Vision, FPGA

  • What DAQ to use for a gaussmeter?

    Hello everyone!
    I am a pretty new LabVIEW user (built stuff from YouTube and used Arduino abit to light up LEDs), and now I have taken a project in my university that involves LabVIEW.
    My assignment for now is to meassure a strength of a magnetic field. The first part is to order the equipment.
    I was wondering which DAQ should I use?
    What sensors can be used with that DAQ?
    The sensors I found are: Allegro A1301, Melexis US1881 and the Panasonic DN6848.
    They all look pretty much the same, but if anyone can tip me off which one is best or if there is a different sensor that can be used, it would be great.
    And the most important is will these sensors work with the DAQ?
    Thanks alot for the help, I hope this is not a too newbie question 

    Hi VladFialkov
    If you are planning on using c series modules such as the ones you mention for the thermocouple measurement I would then suggest you to look for working all the acquisition system on the cDAQ plattform (instead of using the USB DAQs just for the magnetic field measurement). That way if you would want to make all the acquisitions in the same device and just get the AIO module to get the information from your sensor.
    In the following link you can fins the CompactDAQ advisor, where you can start your desired configuration step bystep to get the ideal final configuration for your system 
    Additionally I have done some research in our community and found two examples for the magnetic field measurement using  the myDAQ and myRIO, which are also options with a lower cost than a cDAQ system
    Magnetic Field Measurement / using myDAQ or NI ELVIS
    Magnetic Field Measuremetn / using myRIO
    Hope you can find this helpful !

  • NFS causes whole system hang

    I have a home server that I just set up recently that runs Arch linux.  It exports a couple of external hard drives via NFS.  I have been mouting them with autofs on my laptop.  However, after several hours the entire system completely hangs up.  I originally thought it had something to do with the rpc-gssd daemon that the NFS wiki page recommends running as it was dying in a strange way and I thought that may have been related to the hang ups.  After implementing a different workaround (blacklist rpcsec_gss_krb5) and disabling rpc-gssd, I am still having the same hang issue. 
    Here is what happens:
    I boot up my computer, start Firefox, Thunderbird, various terminals, etc.  I mount the NFS share with autofs by opening up the /media/net/atomic/qx2_data directory.  After a while, the NFS mounts in Thunar start disappering momentarily.  Then a little while later the system completely hangs and requires a hard reboot.  The end of the log from journalctl is posted below. 
    Right now I have disabled autofs and I will only mount the drives on the server via SFTP to avoid this problem, but I would really like to get this debugged.  Also, this is not likely related to any sort of a connection issue as both computers are hardwired to the same Gigabit Ethernet switch. 
    Any ideas on what might be going on here?
    /etc/autofs/auto.net:
    atomic -fstype=nfs4,rw,async,sec=sys,bg,intr atomic.local:/
    Log:
    Dec 17 16:33:35 watatsumi automount[19747]: key ".hidden" not found in map source(s).
    Dec 17 16:34:51 watatsumi automount[19747]: key ".hidden" not found in map source(s).
    Dec 17 16:36:07 watatsumi automount[19747]: key ".hidden" not found in map source(s).
    Dec 17 16:37:23 watatsumi automount[19747]: key ".hidden" not found in map source(s).
    Dec 17 16:38:35 watatsumi automount[19747]: key ".hidden" not found in map source(s).
    Dec 17 16:39:51 watatsumi automount[19747]: key ".hidden" not found in map source(s).
    Dec 17 16:41:07 watatsumi automount[19747]: key ".hidden" not found in map source(s).
    Dec 17 16:42:23 watatsumi automount[19747]: key ".hidden" not found in map source(s).
    Dec 17 16:43:39 watatsumi automount[19747]: key ".hidden" not found in map source(s).
    Dec 17 16:45:16 watatsumi kernel: BUG: soft lockup - CPU#5 stuck for 23s! [htop:2505]
    Dec 17 16:45:16 watatsumi kernel: Modules linked in: usbtmc auth_rpcgss oid_registry nfsv4 tun joydev snd_hda_codec_hdmi x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crct10dif_common crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd fuse nvidia(PO) iTCO_wdt iTCO_vendor_support uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core snd_usb_audio videodev snd_usbmidi_lib snd_rawmidi media snd_seq_device arc4 evdev microcode psmouse serio_raw iwldvm mac80211 snd_hda_codec_realtek iwlwifi snd_hda_intel snd_hda_codec cfg80211 snd_hwdep drm snd_pcm jme jmb38x_ms rfkill mii snd_page_alloc memstick snd_timer i2c_i801 mei_me snd i2c_core soundcore mei thermal shpchp wmi lpc_ich processor battery ac button video pcspkr nfs lockd
    Dec 17 16:45:16 watatsumi kernel: sunrpc fscache ext4 crc16 mbcache jbd2 sd_mod hid_generic usbhid hid ahci libahci libata ehci_pci firewire_ohci sdhci_pci xhci_hcd scsi_mod ehci_hcd sdhci firewire_core crc_itu_t mmc_core usbcore usb_common
    Dec 17 16:45:16 watatsumi kernel: CPU: 5 PID: 2505 Comm: htop Tainted: P O 3.12.5-1-ARCH #1
    Dec 17 16:45:16 watatsumi kernel: Hardware name: CLEVO P150HMx/P150HMx, BIOS 4.6.4 08/09/2011
    Dec 17 16:45:16 watatsumi kernel: task: ffff880801678000 ti: ffff8807dcbec000 task.ti: ffff8807dcbec000
    Dec 17 16:45:16 watatsumi kernel: RIP: 0010:[<ffffffff814f4f8e>] [<ffffffff814f4f8e>] _raw_spin_lock+0x2e/0x40
    Dec 17 16:45:16 watatsumi kernel: RSP: 0018:ffff8807dcbedd88 EFLAGS: 00000297
    Dec 17 16:45:16 watatsumi kernel: RAX: 0000000000000082 RBX: ffffffff81299133 RCX: 0000000000000000
    Dec 17 16:45:16 watatsumi kernel: RDX: 0000000000000083 RSI: ffffffff8172447b RDI: ffffffff818063c0
    Dec 17 16:45:16 watatsumi kernel: RBP: ffff8807dcbedd88 R08: 0000000000017b80 R09: ffff88080e83ce00
    Dec 17 16:45:16 watatsumi kernel: R10: ffff8807dcbedfd8 R11: ffffffff81209fbd R12: ffff8807dcbedea0
    Dec 17 16:45:16 watatsumi kernel: R13: ffff8807dcbede93 R14: ffffffff812981f2 R15: ffff8807dcbedcf8
    Dec 17 16:45:16 watatsumi kernel: FS: 00007f52ddf3c700(0000) GS:ffff88082f540000(0000) knlGS:0000000000000000
    Dec 17 16:45:16 watatsumi kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    Dec 17 16:45:16 watatsumi kernel: CR2: 00007f52ddf7d000 CR3: 00000007cb1d2000 CR4: 00000000000407e0
    Dec 17 16:45:16 watatsumi kernel: Stack:
    Dec 17 16:45:16 watatsumi kernel: ffff8807dcbedda0 ffffffff811bdee9 ffff88077db89c18 ffff8807dcbeddb8
    Dec 17 16:45:16 watatsumi kernel: ffffffff811c0089 ffff88064dd7d9c0 ffff8807dcbedde8 ffffffff8120d9db
    Dec 17 16:45:16 watatsumi kernel: ffff88064dd7d9c0 0000000000000005 ffff8807ba6dc480 ffffffff8120df90
    Dec 17 16:45:16 watatsumi kernel: Call Trace:
    Dec 17 16:45:16 watatsumi kernel: [<ffffffff811bdee9>] inode_sb_list_add+0x19/0x60
    Dec 17 16:45:16 watatsumi kernel: [<ffffffff811c0089>] new_inode+0x29/0x30
    Dec 17 16:45:16 watatsumi kernel: [<ffffffff8120d9db>] proc_pid_make_inode+0x1b/0x100
    Dec 17 16:45:16 watatsumi kernel: [<ffffffff8120df90>] ? proc_map_files_lookup+0x160/0x160
    Dec 17 16:45:16 watatsumi kernel: [<ffffffff8120dfab>] proc_task_instantiate+0x1b/0xc0
    Dec 17 16:45:16 watatsumi kernel: [<ffffffff8120e28f>] proc_fill_cache+0xbf/0xe0
    Dec 17 16:45:16 watatsumi kernel: [<ffffffff8120ea1d>] proc_task_readdir+0x18d/0x3b0
    Dec 17 16:45:16 watatsumi kernel: [<ffffffff811b75ad>] iterate_dir+0xad/0xe0
    Dec 17 16:45:16 watatsumi kernel: [<ffffffff811b79e2>] SyS_getdents+0x92/0x120
    Dec 17 16:45:16 watatsumi kernel: [<ffffffff811b76c0>] ? fillonedir+0xe0/0xe0
    Dec 17 16:45:16 watatsumi kernel: [<ffffffff814fcfed>] system_call_fastpath+0x1a/0x1f
    Dec 17 16:45:16 watatsumi kernel: Code: 66 90 55 65 48 8b 04 25 70 c7 00 00 48 89 e5 83 80 44 e0 ff ff 01 b8 00 01 00 00 f0 66 0f c1 07 0f b6 d4 38 c2 75 04 5d c3 f3 90 <0f> b6 07 38 d0 75 f7 5d c3 66 0f 1f 84 00 00 00 00 00 66 66 66
    Dec 17 16:45:16 watatsumi kernel: BUG: soft lockup - CPU#6 stuck for 23s! [umount.nfs4:30556]
    Dec 17 16:45:16 watatsumi kernel: Modules linked in: usbtmc auth_rpcgss oid_registry nfsv4 tun joydev snd_hda_codec_hdmi x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crct10dif_common crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd fuse nvidia(PO) iTCO_wdt iTCO_vendor_support uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core snd_usb_audio videodev snd_usbmidi_lib snd_rawmidi media snd_seq_device arc4 evdev microcode psmouse serio_raw iwldvm mac80211 snd_hda_codec_realtek iwlwifi snd_hda_intel snd_hda_codec cfg80211 snd_hwdep drm snd_pcm jme jmb38x_ms rfkill mii snd_page_alloc memstick snd_timer i2c_i801 mei_me snd i2c_core soundcore mei thermal shpchp wmi lpc_ich processor battery ac button video pcspkr nfs lockd
    Dec 17 16:45:16 watatsumi kernel: sunrpc fscache ext4 crc16 mbcache jbd2 sd_mod hid_generic usbhid hid ahci libahci libata ehci_pci firewire_ohci sdhci_pci xhci_hcd scsi_mod ehci_hcd sdhci firewire_core crc_itu_t mmc_core usbcore usb_common
    Dec 17 16:45:16 watatsumi kernel: CPU: 6 PID: 30556 Comm: umount.nfs4 Tainted: P O 3.12.5-1-ARCH #1
    Dec 17 16:45:16 watatsumi kernel: Hardware name: CLEVO P150HMx/P150HMx, BIOS 4.6.4 08/09/2011
    Dec 17 16:45:16 watatsumi kernel: task: ffff8807c902e840 ti: ffff88064fe5c000 task.ti: ffff88064fe5c000
    Dec 17 16:45:16 watatsumi kernel: RIP: 0010:[<ffffffff814f4f83>] [<ffffffff814f4f83>] _raw_spin_lock+0x23/0x40
    Dec 17 16:45:16 watatsumi kernel: RSP: 0018:ffff88064fe5ddb0 EFLAGS: 00000202
    Dec 17 16:45:16 watatsumi kernel: RAX: 0000000000002c2c RBX: f97a1072bc3dd003 RCX: ffffffff818c01e0
    Dec 17 16:45:16 watatsumi kernel: RDX: 000000000000002b RSI: 0000000000000001 RDI: ffff880667e6d438
    Dec 17 16:45:16 watatsumi kernel: RBP: ffff88064fe5ddb0 R08: 0000000000000000 R09: 0667f127400c0000
    Dec 17 16:45:16 watatsumi kernel: R10: f97a1072bc3dd003 R11: 0000000000000001 R12: ffff88064fe5dd30
    Dec 17 16:45:16 watatsumi kernel: R13: ffff88064fe5ddb0 R14: ffff880667f12730 R15: ffff880667f126a8
    Dec 17 16:45:16 watatsumi kernel: FS: 00007fdbfd3b3780(0000) GS:ffff88082f580000(0000) knlGS:0000000000000000
    Dec 17 16:45:16 watatsumi kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    Dec 17 16:45:16 watatsumi kernel: CR2: 00007f63631ff000 CR3: 00000006a0de3000 CR4: 00000000000407e0
    Dec 17 16:45:16 watatsumi kernel: Stack:
    Dec 17 16:45:16 watatsumi kernel: ffff88064fe5ddf8 ffffffff811e612c ffff880667f12730 0000000000000000
    Dec 17 16:45:16 watatsumi kernel: ffff8807d797e000 ffff8807d797e0a0 ffffffffa143fe40 ffff880099c279c0
    Dec 17 16:45:16 watatsumi kernel: ffff880674e30620 ffff88064fe5de20 ffffffff811a6a60 0000000000000025
    Dec 17 16:45:16 watatsumi kernel: Call Trace:
    Dec 17 16:45:16 watatsumi kernel: [<ffffffff811e612c>] fsnotify_unmount_inodes+0x11c/0x1b0
    Dec 17 16:45:16 watatsumi kernel: [<ffffffff811a6a60>] generic_shutdown_super+0x40/0xf0
    Dec 17 16:45:16 watatsumi kernel: [<ffffffff811a6cd2>] kill_anon_super+0x12/0x20
    Dec 17 16:45:16 watatsumi kernel: [<ffffffffa03eb18b>] nfs_kill_super+0x1b/0x30 [nfs]
    Dec 17 16:45:16 watatsumi kernel: [<ffffffff811a70bd>] deactivate_locked_super+0x3d/0x60
    Dec 17 16:45:16 watatsumi kernel: [<ffffffff811a76a6>] deactivate_super+0x46/0x60
    Dec 17 16:45:16 watatsumi kernel: [<ffffffff811c350f>] mntput_no_expire+0xef/0x150
    Dec 17 16:45:16 watatsumi kernel: [<ffffffff811c3596>] mntput+0x26/0x40
    Dec 17 16:45:16 watatsumi kernel: [<ffffffff811c36ad>] namespace_unlock+0xfd/0x110
    Dec 17 16:45:16 watatsumi kernel: [<ffffffff811c4803>] SyS_umount+0x1c3/0x3a0
    Dec 17 16:45:16 watatsumi kernel: [<ffffffff814fcfed>] system_call_fastpath+0x1a/0x1f
    Dec 17 16:45:16 watatsumi kernel: Code: 05 e8 52 84 da ff 5d c3 66 66 66 66 90 55 65 48 8b 04 25 70 c7 00 00 48 89 e5 83 80 44 e0 ff ff 01 b8 00 01 00 00 f0 66 0f c1 07 <0f> b6 d4 38 c2 75 04 5d c3 f3 90 0f b6 07 38 d0 75 f7 5d c3 66
    Dec 17 16:45:16 watatsumi kernel: BUG: soft lockup - CPU#7 stuck for 23s! [ifconfig:30557]
    Last edited by alex.forencich (2013-12-18 02:02:58)

    Hi Alex - autofs mounts on demand/request, and unmounts a filesystem after 10 minutes of non-use by default.  If you set the timeout to zero (auto.master), it disables this timeout.  If this is an NFSv4 umount bug, then I don't think this will help you as you'll have to umount at some stage (e.g. shutting down).

  • How do I send an array over endpoint 2 and receive an array over endpoint 1?

    Background:
    I'm a device developer.  I have an HID device that interrupt transfers over endpoint 1 and endpoint 2.  The device enumerates successfully as an HID on mac, windows, and linux.  I've use a couple different .dll files to communicate with the device using visual studio and python with some success and now I'd like to get it to work in labview.
    Status to date:
    1.  Successfully installed device hijacker driver so NI MAX can see the device as USB::0x####::0x####:erialNumber::RAW (# inserted to protect the innocent and SerialNumber is an actual number)
    2.  I can see the device in MAX.  Tried to send a line of numbers and something is sent back, but it isn't useful yet.
    3.  Tried interruptusb.vi and it doesn't do anything but timeout.
    4.  Tried Read USB Descriptor Snippet1.vi and an 18 byte array shows up and the VID and PID are parsed out correctly if the bRequest is Get Descriptor and the Descriptor Type is Device.  None of the endpoint descriptor types return anything.  A bRequest won't trigger a device function.  It needs an array over the out endpoint.
    The problem:
    Intuitively I'm at a loss of what to do next.  The device needs to receive a command from a 16 byte array gets passed through the out endpoint (2).  Then it will respond with a 16 byte array through the IN endpoint(1).  It seems as though the interruptusb.vi should work, but the interrupt transfer is a receive only demonstration.  How should I format a 16 byte array to go through the out endpoint? Does it need to be flattened?  

    Thanks for the tip.
    The nuggets were great for getting started and helped with installing the labview hijack driver for the HID device.  Closer examination may lead to the conclusion that the code I'm using is very very similar to the nugget with minor changes to the output.  Definitely the nuggets are useful, but for my device, there is more to it. 
    It is not USBTMC compliant.  It requires an array of bytes be sent and received.  The problem may have to do with timing and ensuring that the byte transfer is correct.  When communicating from visual studio, a declared array of characters works fine.  I tried that with this setup and it doesn't work consistently.  Of particular concern is why with this setup the device shows up, doesn't work properly until stopped, then works fine, but when the labview VI is stopped, the device disappears and no longer available in the VISA combobox.  The Device Manager still shows the device, but Labview must have an open handle to it. 
    I'd really like to be able to call the dll used in Visual Studio, so the user can choose to use the included software or a Labview VI without having to reinstall a driver.  Afterall, HID is great because the driver is under the hood.  Having to load one for Labview defeats the purpose of developing an HID device.  If I wanted to load a driver, I'd program the device to be a USB-Serial device and use the labview VISA serial vi's. 
    For now I'll be happy to get a stable version in Labview that will communicate consistently even if it is the hijacked driver.

  • How can I see my USB device in the measuremen​t&automati​on explorer?

    I'm trying to use an USB-device with LabView7.0.
    I followed the manual "using NI-VISA3.0 to control your USB device" which I found on the NI-webpage.
    I generated an .inf file using the VISA driver developement wizard and installed it in the INV folder of my system (I'm using Win2000).
    The following problems occured: after I connect my USB device the "add new hardware wizard" pops up and aks for a driver for the new hardware. when I direct it to the folder with the generated .inf file it doesn't accept this file as a driver.
    second: the USB device doesn't appear in the measurement&automation explorer. I assume that as long as my device doen't appear there it is not recognized by NI-VISA and the comm
    unication from LV wouldn't work?
    How can a make my USB device visible in the meas.&aut. explorer?
    Regards
    Tobias

    Tobias,
    In the VISA Driver Development Wizard, you are required to specify the Vendor and Product ID. These numbers are what Windows will use to determine whether a specific driver is appropriate for a given device. If these numbers do not match between your device and the Windows driver (INF file) that you generate, you will see the behavior that you describe. Check to make sure that you are using the appropriate values. Also, did you right click on the INF file and install it as directed in step 2.2.2?
    Page 5-87 of the VISA Programmer's reference manual specifies how to do a viOpen to a USB device in RAW mode, but you still need the same sorts of Product ID and Mfg ID that you needed for the INF file generation. Furthermore, if you are communicating with
    your instrument directly, you will need to know exactly what command set it expects, so make sure you get that from the manufacturer as well. Finally, I want to mention that if this device complies with the USBTMC standard, then none of this is necessary--the steps above are for setting up a RAW USB connection. See this link for information.
    Scott

  • Driver wizard does not allow USB to be selected

    I am trying to control a Keithley 2230-30-1 Tripple Channel DC Power supply with NI-VISA through USB.
    When I connect the power supply and go to VISA interactive control, there are no options for a usb device.  I know that the USB port I am using works, and that the PC recognizes that the device is manufactured by Keithley (using the lsusb command).
    In addition, when I attempt to use the NI-VISA Driver wizard, the option to set up a USB device is grayed out.
    So far I have had no success with this device.  However, this PC and this version of NI-VISA has been able to sucessfully connect to and control a GPIB device using both LabVIEW and PyVISA.
    I would appreciate any help I can get on this matter.  Thank you.
    Useful Information:
    PC: Dell Optiplex 755
    OS: Cern Scientific Linux 6 (SLC6) x86-64  (a distribution based on and
    VISA version: Version 5.4 (32-bit version as there is no 64 bit Linux VISA yet)
    I can post additional information if required.

    There is no need to run the wizard to use a USBTMC instrument with NI-VISA on any OS. Specifically on Linux, there is no need to run the wizard for any USB device. The reason is that NI-VISA will be able to find and use any USB device that is not claimed by another driver. I believe this is the root of the issue you are seeing. On some distributions, there is a default usbtmc driver that claims all USBTMC instruments and hence NI-VISA can't see them. To test this, just run 'rmmod usbtmc' as root and then launch NI-VISA interactive control to see if it shows up now. This will confirm if that is the issue. As long as the driver is present, it will claim the device any time it is unplugged and replugged the instrument (or you restart the machine). One way to prevent it is to black-list the usbtmc driver (echo blacklist usbtmc >> /etc/modprobe.d/blacklist.conf) and this may be an acceptable solution if you want to always use NI-VISA for your USBTMC instruments.
    There could also be the problem related to permission in addition to the above problem, and the document linked in the above post has information on how to add permissions so that a non-root user can access the USB instrument.

  • LabWindows​/CVI 5.5 for GPIB communicat​ion?

    Hello!
    I'm a GPIB rookie and can't get my GPIB devices to talk with LabWindos/CVI:
    For the GPIB devices I am using (FWBell 7030 Gaussmeter, Keithley 6514 Electrometer) are no instrument modules available (at least I can't find any).
    How can I talk with these devices, using the IEEE488(.2) functions in LabWindows 5.5?
    If I use these functions (i.e. Send / Receive), I allway get error messages and the devices don't redspond and sometimes they show error messages.
    How do I address a device on the GPIB Bus?
    Every idea is welcome, I need all the help I can get.
    Thank you!"

    Unfortunately I was unable to find a driver for this instrument either. This leaves you with one of a couple options. First, I would like you to submit a request for this driver at:
    http://zone.ni.com/idnet/other.htm
    We develop drivers based on demand and popularity so the more requests we have for it, the greater the possibility that we will develop one.
    If you would like to try developing your own instrument driver (or modify the existing one), we have documentation, model instrument drivers, and driver templates to help at :
    http://zone.ni.com/idnet/development.htm
    There may be a similar driver on ni.com/idnet that can be used as a model.
    We also have a syndicate of third party vendors that specialize in National Instruments'
    products and services. Some of the vendors specialize in driver development. I would suggest contacting one of the Alliance members at:
    http://www.ni.com/alliance

  • LabWindows/CVI 5.5 for GPIB communication

    Hello!
    I'm a GPIB rookie and can't get my GPIB devices to talk with LabWindos/CVI:
    For the GPIB devices I am using (FWBell 7030 Gaussmeter, Keithley 6514 Electrometer) are no instrument modules available (at least I can't find any).
    How can I talk with these devices, using the IEEE488(.2) functions in LabWindows 5.5?
    If I use these functions (i.e. Send / Receive), I allway get error messages and the devices don't redspond and sometimes they show error messages.
    How do I address a device on the GPIB Bus?
    Every idea is welcome, I need all the help I can get.
    Thank you!"

    Unfortunately I was unable to find a driver for this instrument either. This leaves you with one of a couple options. First, I would like you to submit a request for this driver at:
    http://zone.ni.com/idnet/other.htm
    We develop drivers based on demand and popularity so the more requests we have for it, the greater the possibility that we will develop one.
    If you would like to try developing your own instrument driver (or modify the existing one), we have documentation, model instrument drivers, and driver templates to help at :
    http://zone.ni.com/idnet/development.htm
    There may be a similar driver on ni.com/idnet that can be used as a model.
    We also have a syndicate of third party vendors that specialize in National Instruments'
    products and services. Some of the vendors specialize in driver development. I would suggest contacting one of the Alliance members at:
    http://www.ni.com/alliance

  • Support for Old Vibrating Sample Magnetometers

    Hello.
    I am a relative newcomer to LabView and I am trying to get some support for a few older Vibrating Sample Magnetometers (VSM) on behalf of my employer.  These machines are quite old and, although they have GPIB connectivity, I am having difficulty in being able to control them using LabView.  Although they use the IEEE-488 GPIB standard, they were built before the introduction of the Standard Commands for Programmable Instruments (SCPI), rather than the newer 488.2 standard.  As such, they work with their own proprietary commands, which are proving impossible to find.  I have a working LabView program that was written by a university student for a master's degree in physics.  However, I cannot communicate with the individual components, such as the gaussmeter, power supply, etc, using measurement and automation explorer.  They don't even respond to an "*IDN?" query without timing out, which I thought was standard.  I have tried lengthening the timeout time and tried to use drivers for similar instruments.  My question to anyone out there is, do you have the drivers or the programming manual for any of the components listed below?  The Vibrating Sample Magnetometers were built by the now defunct DMS/ADE.  The current owners of DMS/ADE can offer little support for such old equipment.  Likewise, is there something else I can try in lieu of these drivers and commands? 
    Devices:  1.) DMS Model 1660 VSM, 2.) DMS/ADE VSM Model 4, which includes the DMS/ADE model 32KP gaussmeter with its own GPIB port.
    Thank you for your time,
    Liam

    Hi Liam,
    As per GPIB 488.2, as I already mentioned, the ibEOSchar under Ibconfig is an 8 bit value so it will take value from 0 to 255 for which 3 number width is sufficient. Measurement and Automation Explorer also works in the same way. EOS byte value under Termination Settings section of GPIB settings accepts a decimal number from 0 to 255 and it will not allow any character and also value more than 255 as its field is limited to 3 numbers and even if you enter a value more than 255, it will be automatically changes to 255.
    So, As per 488.2, You cannot give both carriage return and linefeed characters together and you cannot use the same in MAX also.
    Try framing your entire command with EOS as per built in LabVIEW carriage return and linefeed functions and use GPIB Write.vi to send this entire frame. It may work.
    Also, I would like to see your VSM's communication manual and understand how these commands have been implemented.
    Coming to IBEOS command, its easily understandable and its used to Configure the end-of-string (EOS) termination mode or character. It have low byte and high byte.
    Low byte is always an 8 bit EOS character and high byte can take three forms which are A, B and C. Also High byte can have values with combination of A,B or C.
    For Example, ibeos (ud, 0x140A); means, Configure the software to end reads on newline character (hex 0A) for the unit descriptor. Here high byte is a combination of A and C where as low byte is the HEX equivalent of ASCII Line feed character.
    Regards,
    Naresh Narra

  • How to connect to Agilent DSO7104 through USB connection

    I want to connect to Agilent oscilloscope DSO7104 using USB interface.
    I have installed labview 8.0, ag6000a Instrument Driver and visa4.6.2.
    When I use Example of ag6000a Instrument Driver, the VISA resource name are COM1, COM3 and LPT1.
    What should I do to use USB interface?
    Thanks.

    There should be an inf driver file that comes with the instrument if it supports the USBTMC class.

Maybe you are looking for

  • Getting NEW FORUM creation error in Discussion Forum Portlet of Oracle 10g

    Hi, I have deployed “Discussion Forum” provided by Oracle. For deployment I have followed the document provided, which is available on http://www.oracle.com/technology/products/ias/portal/html/installing.integration.v2.html Our application running on

  • Why are existing songs updated sometimes?

    Does anyone know why it happens that, during a sync, I will get a message "updating files on _'s ipod" and that it is copying songs that are already on the ipod. Usually it is just a few song, but in my most recent sync it was 109 songs, all of which

  • How do I compress a video file so I can send it via email?

    I am trying to email a slideshow I just created in iPhoto.  My email won't accept the file because it is too large.  I tried to compress by right clicking on the file in the Finder application.  It gives me the option to compress it so I said yes.  I

  • Tap to Click - Second Finger

    This is a suggestion to improve Trackpad. An enhancement on "Tap to click" opstion. While we are navigating pointer with a finger (which may be index or middle finger) when we want to click on an item, we have two options: A- Push hard on trackpad un

  • Flash from ONE site won't play

    Here's a situation for y'all to ponder: 2 ea Bordermanager 3.8, SurfControl, about 9 total access rules, only denying access to Gambling, Games, and "Porn." Users (primarily public library users) are attempting to access a website to view traffic enf