07-26-2011 07:43 PM - edited 11-23-2020 05:35 PM
07-27-2011 08:16 AM
Dimitri,
What version of NI-VISA and is Scientific Linux 6.0 being run in 32-bit or 64-bit?
Randy Hoskin
07-28-2011 02:04 PM
Do you have 32 bit compatability enabled on these systems?
J. "Ox" Gibson
Systems Software/VISA Software Technician
08-02-2011 05:35 PM
Good to hear. I was setting up an image to verify the glibc to verify that was the issue, but didn't get a chance to validate it. Feel free to lat us know if you are having any other issues.
08-02-2011 06:01 PM - edited 11-23-2020 05:34 PM
..
12-19-2011 10:49 AM
Hi,
I'm trying to make NI-VISA NI-KAL etc running on SL54 (32bit).
UpdateNIDrivers worked fine (see below)
The only thing going wrong is that "driverwizard" doesn't allow me to select USB.
USB is greyed out ! 😞
I assume the kernel sources aren't configured correctly.
I've been seeking on Internet and I find alway the same story (only for openSUSE):
1. Ensure you have installed kernel-source and kernel-syms packages
corresponding to the version of the currently running kernel. The version of
the currently running kernel can be determined by issuing the command
"uname -r".
2. Change the directory to the /usr/src/linux-<version> directory, where
<version> corresponds to the currently running kernel version.
3. Run "zcat /boot/symvers-<version>.gz > Module.symvers" as root to prepare
modversion support.
4. Run "make cloneconfig" as root to configure the sources for the currently
running kernel.
5. Run "make modules_prepare" as root to prepare the headers for compilation.
6. Run the NI-KAL INSTALL script.
BUT UNDER Scientific Linux , "make cloneconfig" DOES NOT HAVE ANY EFFECTS.
How can I configure the current kernel in order to (using updateNIDriver utility) rebuilds the NI drivers using the new kernel sources???
Thanks indeed 😉
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
root@slinux sluser]# updateNIDrivers 2.6.18-274.12.1.el5
Unloading NI-KAL (nikal): WARNING: could not unload module nimru2k from memory
done
Removing NI-KAL (nikal): done
Configuring for linux kernel version 2.6.18-274.12.1.el5.
********************************* NOTE *********************************
Using kernel headers found in /lib/modules/2.6.18-274.12.1.el5/source.
If this does not correspond to the location of the 2.6.18-274.12.1.el5 headers,
then define KERNELHEADERS in your environment to point to the location
of the kernel headers, define KERNELTARGET as the version of the
kernel for which to compile, and then rerun ./configure.
********************************* NOTE *********************************
Kernel has reparent_to_init(): no
Number of arguments for do_munmap(): 3
pte_offset function: pte_offset_kernel()
Levels in page table: 4
Kernel has remap_pfn_range: yes
Kernel has kzalloc: yes
USB altsetting name: cur_altsetting
Kernel has usb_get_intf(): yes
Kernel has intf_cache member in usb_host_config: yes
Kernel has ep[] members in usb_device: yes
Kernel exports usb_set_configuration(): no
Units of USB_CTRL_GET_TIMEOUT: msec
Kernel has owner member in usb_driver: no
Kernel has put_page_testzero(): yes
Kernel has mutex method: yes
Kernel has wait_for_completion_interruptible: yes
Kernel has config.h: yes
Kernel has ioctl32.h: yes
IRQ handlers have pt_regs: yes
Kernel has work_struct and delayed_work: no
Kernel supports fault method in vm_operations_struct: no
Storing configuration in Makefile.in
If the values stored are incorrect they can be changed before running make.
Installing NI-KAL:
NI-KAL successfully updated.
Loading NI-KAL (nikal): done
Updating client modules:
WARNING: could not unload module nimru2k from memory
nipalk.ko successfully updated.
WARNING: could not unload module nimru2k from memory
niorbk.ko successfully updated.
WARNING: could not unload module nimru2k from memory
nidimk.ko successfully updated.
NiViPciK.ko successfully updated.
WARNING: could not unload module nimru2k from memory
nimdbgk.ko successfully updated.
WARNING: could not unload module nimru2k from memory
nimxdfk.ko successfully updated.
WARNING: could not unload module nimru2k from memory
nimru2k.ko successfully updated.
NiViPxiK.ko successfully updated.
gpibprtk.ko successfully updated.
nimxpk.ko successfully updated.
nistc2k.ko successfully updated.
nimstsk.ko successfully updated.
nidmxfk.ko successfully updated.
nimsdrk.ko successfully updated.
nicdrk.ko successfully updated.
nistcrk.ko successfully updated.
nidsark.ko successfully updated.
niwfrk.ko successfully updated.
nisdigk.ko successfully updated.
nisftk.ko successfully updated.
niscdk.ko successfully updated.
niswdk.ko successfully updated.
niesrk.ko successfully updated.
nitiork.ko successfully updated.
nixsrk.ko successfully updated.
nissrk.ko successfully updated.
nispdk.ko successfully updated.
WARNING: could not unload module nipxirmk from memory
nipxirmk.ko successfully updated.
Rebooting is required to ensure that National Instruments drivers
have been successfully updated.
Would you like to reboot now? [yes|no] no
Please reboot manually before attempting to use your NI drivers and products.
[root@slinux sluser]#
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
12-21-2011 01:19 PM
Vids65,
USB option is disabled by design on the DriverWizard on Linux. The reason for this is that you don't need to generate an inf for a USB device for you to be able to use it with NI-VISA on Linux (or any other non-windows platform). NI-VISA enumerates and binds to all USB interfaces found on the system that haven't been claimed by any other driver. So, you should be able to just plug in your device and have it working with NI-VISA (as long as no other driver claims it first).
Is there a reason you were trying to generate an inf for a USB device? Do you have an instrument that you are having trouble using with NI-VISA?
Pankaj
12-22-2011 07:28 AM
Hi Pankaj
Thanks indeed for this information. I didn't know that and it's clearer in my mind (still a long road to be cleared up!)
No, there is no reason to make any inf file for a USB device. I just need to commmunicate with it, that it's! 😉
So at that point I should be able to communicate but still nothing 😞
If I read on ttyUSB0 from a terminal (cat /dev/ttyUSB0) I get the right number when I read something (for testing I put a barCode reader RS232 and send the traffic on USB port).
When I try to read the USB port (USB RAW VISA ressources name : USB[board]::manufacturer ID::model code::serial number[::USB interface number]::RAW) through LabVIEW, it doen't work and give me an error 😞
I guess I don't use the right ressources or I don't put the right information in fields...
Still some job to do !! 😉
Thancks a LOT for that info and I'd be back to you if I can work out on my own ! Thanks again and have a nice Christmas
Vids
12-28-2011 04:22 PM
Vids,
It looks like you are using a USB-Serial device. That means, you can use this as a Serial resource from VISA. Unfortunately, VISA doesn't automatically enumerate serial resources on a system, so you will have to use the visaconf utility to create a static serial port and give it a binding of /dev/ttyUSB0. Then you should be able to use this resource from VISA. You might have to give non-root read/write access to /dev/ttyUSB0 for you to be able to use this resource from a non-root VISA app. Please let me know if you have other questions.
Pankaj
12-29-2011 02:19 AM
Hi Pankaj,
Yes you're perfectly right. I've done already what you said and it's works pretty well.
THANKS you a lot for these info. Have an excellent new year 😉
Best
Vids