GPIB to USB in 16 Bit Dataformat

Do you support the 16 Bit Mode in your currently SW 2.1? I used your GPIB-USB-A to connect our Spectrum Analyzer (Rohde & Schwarz, FSP) with our Windows 98 Laptop. This works and could control the Spectrum Analyzer bei commands. But it was not possibel to control them with our Measurement-SW, because this SW needs a GPIB Interface in 16 Bit mode. I tried an older National Instruments SW (Version 1.6 and 1.7) to operate the GPIB-USB-A but it doesn't work. Can you help me to find a way to opertate the GPIB-USB-A in 16 Bit Mode?

Hi,
We don't have a 16-bit driver for the USB-GPIB interface. All USB-GPIB drivers use Win32. Check the following web page for the supported platforms:
http://www.ni.com/support/gpib/versions.htm#note9
In Windows there's a technique called "thunking" that allows you to mix 16-bit and 32-bit code. You'll have to implement the thunking code. To access 32-bit code from a 16-bit code, "flat thunking" is used. Here are some web sites I found on the web related to thunking:
http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q125710&
http://www.mvps.org/vbvision/thunks.htm
http://www.global-shared.com/api/thunk.html
Hope this helps you.
Diego F.
National Instruments.

Similar Messages

Connecting GPIB to USB-6361

I have a Windows 7 laptop running Labview and am using an NI USB-6361 to interface with. I have a Magtrol 6510e single-phase power analyzer I would like to use, but currently have no way of connecting the GPIB (or even the RS232) to the laptop (the only RS232 port is being used). I want to modify a GPIB cable (cut & strip it down) such that I can input individual wires into the digital I/O pins on the USB-6361. I have identified the 8 1-bit signal wires, however I am unsure what else is needed from the 24-pin cable to interface with Labview (and the program set-up) so I can graph the power input and read out the max power used. Any help would be greatly appreciated. Thank you.
-Tony

You don't want to go that route! GPIB is not just a set of parallel bus signals, it is a complex (to do the way you are proposing) communications protocol with critical timings, etc. You would not be able to use any of the existing methods to communicate, your program would be incredibly complicated, and without looking at the DAQ device you are using, I'll say that it (the DAQ) probably can't do it in a Windows 7 environment. You are going have a much easier time if you get a usb to serial adapter (do a search on these forums for models that users have had sucess with) or spring for a USB to GPIB adapter. If you do the later I would recommend going with the NI one(s), if only for the support aspect. Others are shown that are less expensive to purchase, but that doesn't always translate to less expensive to use.
Putnam
Certified LabVIEW Developer
Senior Test Engineer
Currently using LV 6.1-LabVIEW 2012, RT8.5
LabVIEW Champion

Audigy 2 NX USB+Vista 32 BIT-Pop/Crackle Pls h

I have big Problem i have a Audigy 2 Nx USb Soundcard with Windows Vista 32 Bit OS!
I had the driver from February installed it was fine there...
with the new driver rel from 23.8.2007 (USB Series Windows Vista Driver .0.0002) any few seconds crackles and pops apears when i am listening to Music etc. or Winamp hangs up....!!!
What could be the problem.....i think the new driver !because the one before works!Message Edited by Gabber25 on 09-29-200709:35 AM

"Kano_69,
It's a beta driver on a beta OS. What exactly are you expecting?
Jeremy
Forum Moderator
Creative Labs"
well ati & nvidia brang out "beta drivers" AND THEY WORKED ? and that waz 4 the first "vista" build... so i waz expecting "li9ke all of us" to have drivers that make sound at least clear . . and play at normal speed instead of slow downs and snap,crackle & poping all ova the place.... thats all i waz expecting thats all... not much ill go back to onboard sound "once again" so i can have clear sound in vista.... THANKS ANYWAZ lol 2 cents 4 ur effort

USB SB 24-Bit H

Hello, I have a USB Sound Blaster 24-Bit External and was wondering is there a way i can adjust my Chorus and Reverb? Because i need to do that to make my games sound better.

Alright, well, as with any Creative SB card made nowadays, you should have an AudioHQ applet in your control panel. Double clicking on that will bring you to a screen where you can modify something called EAX. If you double-click the EAX icon, it will bring up a dialog where you can either use Creative's presets (e.g., concert hall, etc...) or make your own. Once you're done making and testing your EAX configuration, you'll be prompted to save your own preset. Save it, and then try it out.
EAX causes nothing but trouble if it's enabled outside of a game as well as inside of a game. If both you and your game request EAX, while you're playing, you'll notice feedback sounds (for example, Ghost Recon, when you run into an alley which uses EAX, will give you a loud feedback noise). So, if you are planning to play a game which, in the audio options menu shows that it has EAX support, you should not enable EAX on your own. The game will create its own EAX environment for you.
If, however, the game does not create EAX environments on its own, follow the above instructions to enable it.

Vista System Recovery Disk Boot USB CD 32-bit Utility Suite PC REPAIR

need boot usb drive

Hi Richard,
I'm sorry you had to go through some pretty emotional trauma with your U410 getting stolen and all. However, I do hope you are back on track now.
I haven't been as unfortunate as you. However, I need to restore Win 7 on my U410. I have with me the recovery disks purchased from Lenovo. My question is, were you able to get the image onto a USB disk to perform the restoration? If so, could you point me to some instructions?
Seriously, Lenovo ships laptop specific recovery images on optical disks for their laptops that do not have optical drives. Makes no sense to me. It's time they sell recovery images on USB drives.

Question about USB-GPIB

This is regarding the National Instruments GPIB-USB-A. If the GPIB-USB
cable is not long enough, can I attach a standard GPIB cable onto it to
extend the length? In this connection, one end of the GPIB cable is not
connected to any device and would this cause any problem?
PC GPIB-USB-A
USB port <-------------> normal GPIB cable
<------------------------> device
not
connected
to any device
Sent via Deja.com
http://www.deja.com/

Hello Joel,
With regards to GPIB, i'm in a bit of a fix right now. I'm having problems with cable length in my setup. Most of the specs say that it shouldnt be more than 20ft but then i've heard stories that people ahve broken the max length rules and gotten away with it.
I'm attaching a file, which i'd like you to view, and then tell me if i can get away with these lengths of gpib cables in my setup.
BTW the x are devices, otherwise the connection is just a split to a device later on. I'm concerned with the first split, that you'll see in the drawing, and with the 2 meters each to the device at the bottom part of the network. If required, i can set the bottom three devices as a star network, although i dont see how that would solve the problem.
The
box on the left is the CPU/host.
Attachments:
gpib.gif ‏2 KB

How do I get GPIB USB-A to work in MAX 2.2?

I updated from LV 6.0 to 6.1. During the intallation MAX was updated to version 2.2. My problem is that my GPIB cark USB-A is not suported in MAX 2.2, I updated to 488.2 2.0 (W32) and I can now use my card within MAX again, but I cant use VISA aliases anymore. This is a problem since some of my older programs uses aliases for both instruments and COM ports. Is there an upgrade I can run or will I have to work without aliases?
Is it possible to uninstall MAX 2.2 and reinstall the old MAX from LV 6.0 and get it to work with LV 6.1?
Hope someone has a solution for my problem.

You do not NEED Max to set up aliases.
Check with NI support about editing Visaconfig.ini (?).
The aliases end up in that file.
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

VISA erreur 1073676294, Probleme d'adaptateur USB/GPIB

Bonjour à tous
Je communique avec un oscillo tektronix grace à une liaison GPIB. N'ayant pas de carte GPIB sur mon ordinateur, j'utilise un adapteur qui convertit la liaison en GPIB en USB pour le brancher à l'ordi. Or lorsque je teste de communiquer en VISA (sous Labview 8.5) vers l'oscillo (test IDN), il se produit une fois sur 2 une erreur 1073676294 dans VISA Read.... J'ai par ailleurs testé avec une carte GPIB sur un autre ordinateur, il n'y a pas d'erreur dans le Read (testé sous Labview 5...).
Connaitreriez vous la cause de disfonctionnement avec l'adaptateur GPIB/USB ? et comment résoudre le probleme ?
merci d'avance
Résolu !
Accéder à la solution.

Bonjour Charles38,
Il s'agit d'un rapport de statut et non d'une erreur :
http://digital.ni.com/public.nsf/allkb/C96C84C922DC3F978625632500482F78
En fait cette "erreur" indique que le nombre d'octets lu correspond parfaitement au nombre demandé, et que d'autre données pourraient être disponibles. D'ailleurs l'indicateur d'erreur ne devient pas actif lors du passage de ce code d'erreur.
EDIT
J'ajoute que vous pouvez ignorer cette erreur de la sorte:
http://digital.ni.com/public.nsf/websearch/BF72229C53F7633386256EDD0069331B?OpenDocument
Cordialement,
Message Edité par Alex_NI le 04-20-2010 04:49 AM
Alexandre D.
National Instruments France
#adMrkt{text-align: center;font-size:11px; font-weight: bold;} #adMrkt a {text-decoration: none;} #adMrkt a:hover{font-size: 9px;} #adMrkt a span{display: none;} #adMrkt a:hover span{display: block;}
>> Les présentations NIDays 2010 déjà disponibles au téléchargement !

Get List of Connected Devices (USB, GPIB, etc)

For GPIB (actually GPIB devices connected to GPIB to USB cable) I do:
static short addrList[31];
static short listList[31];
for (j=0;j<31;j++) {
addrList[j] = j;
addrList[30] = -1;
SendIFC(0);
FindLstn(0,addrList,listList,30);
But not sure how I would do other ports such as USB. i can see it in MAX but it just seems to automatically appear.
Solved!
Go to Solution.

Hi,
personally I use VISA. For finding all available serial ports I use viFindRsrc ( resource_manager_handle, "ASRL[0-9]*::?*INSTR", &find_handle, &return_count, instrument_descriptor ); for GPIB you would use "GPIB[0-9]*::?*INSTR" as the second argument.

INES GPIB USB

Hello,
My name is Ricardo and I´m trying to connect a legacy HP 3852 with a GPIB to USB cable (INES branded), The drivers are recognized by W8 in the device manager and I can connect to the HP 3852 through my HPBASIC connection. However, when I start NI MAX to connect through Labview, NI MAX doesn´t recognize anything. I have tried to use VISA, but I don´t know the address of the equipment and the VISA can´t find it. I have tried to follow the manual of the INES GPIB-USB and I have copied its drivers to c:\Windows\System32 but they are not recognized nor used by Labview. ¿What can I do to connect to the HP3852 through this cable? Thanks in advance for your help.
Regards, Ricardo.

ricardoh wrote:
Hello,
My name is Ricardo and I´m trying to connect a legacy HP 3852 with a GPIB to USB cable (INES branded), The drivers are recognized by W8 in the device manager and I can connect to the HP 3852 through my HPBASIC connection. However, when I start NI MAX to connect through Labview, NI MAX doesn´t recognize anything. I have tried to use VISA, but I don´t know the address of the equipment and the VISA can´t find it. I have tried to follow the manual of the INES GPIB-USB and I have copied its drivers to c:\Windows\System32 but they are not recognized nor used by Labview. ¿What can I do to connect to the HP3852 through this cable? Thanks in advance for your help.
Regards, Ricardo.
Doesn't recognize anything?
Perhaps you should post a screencapture of your NI-MAX.
You can't just "copy" drivers. You need to install them.

GPIB and RS232 communication problems

I've been having several "interesting" problems with GPIB and RS232 communications in LabVIEW VIs. Some I'll mention at the end for curiosity, but right now I'm facing a rather big problem. I'm essentially self-taught at doing LabVIEW (using 8.5.1 right now), but by now I've had a lot of experience as their either has not been any drivers or pre-made VIs for the instruments I've needed or I've not been able to get the available drivers to work and had to write my own anyway (such as with the HP 3458A), but nothing seems to be working right now. I'm not at work, but we typically find forum sites blocked anyway (I can't even download the NI drivers at work since they house them on a ftp server, go figures) so I can't give the VI itself (it wouldn't be easy to get approval even if I could) so the best I can do right now is in words describe everything I've tried. I will be happy to post follow-ups of specific details if I can if they would be helpful.
I've been working on a routine to read data from an MKS 670 Signal Conditioner/Display with a MKS 274 Multiplexer with 3 connected MKS 690A Baratrons. Previously I've worked on programs using other older displays and the analog outputs which were being read by a DAQ card, but for a new project it was decided to try and just read the data directly. I first worked with a unit with just an RS232 Serial Port which I managed to get to work, but had so much problems with garbage readings and having to add checks and re-reads that by the end no matter what delays I added between each reading and how simplified the command routine down to just 2 sequences and the read that it took at least 10 seconds to get 1 reading from each channel.
Figuring maybe it was a limitation of the serial communications for these instruments I tried to re-work it for a unit with a GPIB port with which I'm actually much more familiar. The problem is that I cannot get anything at all from the unit through GPIB. Everything even the bare-bones built-in GPIB CLR function times out with no response from the instrument no matter how long I set the timeout limit and it also freezes the entire GPIB bus as well. It isn't a waiting issue as it freezes on the very first command. The GPIB initialization function seems to work (I typically find this to be unnecessary), but the instrument itself doesn't even respond with a status code. I've also tried just the basic GPIB write functions with even just passing the <cr> and <lf> characters as well. In Measurement and Automation Explorer most of the time the instrument won't even appear when doing search for instruments and when it does it shows as not responding to the *IDN? command (yes I've messed with the EOI, EOS, etc settings and I've even changed the GPIB address even though when it gets this far it confirms that I have the correct address) and even tried manually doing the *IDN?, *RST, and *CLR commands even with <cr> and <lf> characters which the manual for these units clearly states are compatible commands and NI SPY and everything show no response at all. I've tried 2 different GPIB units, 3 different computers including several that are not online and haven't been updated for a while, and using older LabVIEW versions, extensive re-booting and resetting of computers and devices and still nothing. I'm using an NI GPIB-USB-HS GPIB to USB adaptor which I've used extensively on other systems and even re-connected to those systems and everything worked fine. When I hooked up equipment that I knew was working, it would either freeze the entire GPIB bus until well past whatever timeout setting I set at which point all the instruments would appear, but none responding to *IDN? queries or nothing would appear at all, or if I manually turned it off when frozen the other instruments would work and most even respond to the *IDN? queries. The same goes for both of the GPIB instruments of this type that I tried and again for different versions of LabVIEW, difference computers (all Windows XP though), and every GPIB configuration setting I can find to mess with in every combination.
Any thoughts or suggestions would be greatly appreciated. I've had all sorts of weird problems with equipment and LabVIEW (you've got to love undocumented design features) that have frustrated me before, but I've never had an instrument never respond at all especially a GPIB one. Getting garbage yes, no response at all, no.
The side side issues I'm just mentioning as they may be related, but I'm really interested in the above as I have working solutions for these:
One I've had is with a Hart Scientific (prior to being bought by Fluke) 1560 Black Stack that would continually stop responding to GPIB commands when on a continual read function taking readings just every 4 seconds with 250ms between each GPIB read or write command but for up to hours in total and the times it stops responding are random as far as I can tell. I even started sending the *RST command before and after every read or write command and still it freezes. The only thing is to manually turn it off and then back on or manually go through the menus and manually trigger the GPIB reset routine at which point it immediately starts responding. However, when I got sick of having to babysit it and just decided to try the RS232 serial port (as that is all it has without the extended communications module) it works fine no problem and I can even get readings slightly faster from it. Using a Hart Scientific 1529 Chub-e it could give me data on all 4 channels every second without problems. I just find it a bit odd.
When I couldn't get any of the HP 3458A driver packs to work to even give a single measurement reading and just made my own using basic GPIB read/write commands using the programming manual I still have a few interesting problems in randomly when reading off the full possible 256 bytes on the bus and clearing the bus I often find garbage partial readings on the bus every now and then. I've added a few routines to do some basic checks, but it is annoying. What is really weird is when just doing basic DC Voltage reads the "-" sign will randomly be dropped from some readings (started as about 1 out of every 5, down now to about 1 out of every 10). Fortunately I'm taking several readings and averaging and taking the standard deviation with limits on the deviations and basically added a routine to say if there is even 1 negative number take the absolute value of all then make all negative, but again I find it weird.
Thanks.
-Leif
Leif King
Metrology Engineer
Oak Ridge Metrology Center

Greetings Leif,
I understand you have completed extensive troubleshooting techniques to pin-point the problem with the GPIB communication. To begin, I want to ask you a few questions to help me understand your set-up and the issue at hand.
1) Is the NI GPIB-USB-HS cable the one which cannot communicate with your instrument?
2) When using the GPIB-USB-HS, does the GPIB interface show up in MAX?
3) If yes, does the instrument appear in MAX after scanning for instruments (from what I understand in your issue, it does so in an intermittent manner..)?
4) What driver version of VISA do you have installed in your computer?
5) Are you able to communicate to the same instrument using another GPIB cable?
Thank you for trying out some of these steps again, but we want to make sure we rule out other aspects in the systems which might be affecting the GPIB communication.
As for your other issues, please post seperate threads for each so we can help you accordingly. Thanks!
Sincerely,
Aldo
Aldo A
Applications Engineer
National Instruments

Package for DVC80 USB Video Interface

Gents;
Some info sources say that a linux app can be provided which will permit the DVC80 to respond to NTSC video camera input.
The DVC80 operates well in windows, permitting capture in Irfanview and a program called Dazzle.
The following data describes a possible application which may be compatible with arch. The interface in video apps, especially from USB, can be daunting. Audio is also provided on NTSC basis for camera input via the DVC80 input connectors(stereo).
The data below describes how it might be built in linux:
===============================================================
Readme for kernel 2.6.x Linux device driver for the Zoran/Nogatech USBVision Video Grabber
Author: Joerg Heckenbach <[email protected]>
Homepage: http://www.emuit.com/webcam.html (Dwaine Garden)
INTRODUCTION:
This is a driver for the USB video bridge USBVision from Zoran/Nogatech, a USB-only cable used in many "webcam" devices.
It supports streaming and capture of color or monochrome video via the Video4Linux
API. Most V4L apps are compatible with it, but a few video-conferencing programs
do not work yet.
If you need more information, please visit the Zoran/Nogatech homepage at the above URL.
usbvision-0.9.6 is the first prerelease of the 1.0 driver. I did many changes in the code and I hope I
didn't break working features on different devices. The decompression is completed. Just from time to
time there are some black or white error pixels in the image on slower machines. Maybe it is a timing problem
in the isoc interrupt routine. We stay a third of the time in interrupt and so it is likely, that the parser
is called twice. Let me cleanup the routine for performance, move the parser to user-context and add a lock.
For 2.6x kernels we can use the saa7111 from the kernel tree, so the make will not compile the saa7111-new
for these kernels. The bt819-new.c is not coded to 2.6. kernel yet.
I have tested the driver with kernel 2.6.1, 2.6.2 to 2.6.7 with devices "Hauppauge WinTV USB FM 1" and
"Pixelview PlayTV USB Pro FM" on a 600MHz PII system.
WHAT YOU NEED:
- If you want to help with the development, get the chip's specification docs at
http://www.emuit.com/webcam.html
- A Video4Linux compatible frame grabber program (I recommend xawtv or Kwintv)
xawtv is available at: http://www.in-berlin.de/User/kraxel/xawtv.html
- Radio Application to take advantage of the radio tuner. (some of the devices)
GQradio is available at: http://gqmpeg.sourceforge.net/radio.html
HOW TO INSTALL THE DEVICE DRIVER:
First way (The easy one)
It works with most modern standard installations.
a) In the usbvision directory do
make; make install; modprobe usbvision
b) Start your video application.
c) Enjoy.
If c) doesn't work, something went wrong ;-)
Second way (Not as easy as the first one)
You need this, if either usb-, i2c-, tuner- or v4l-support is missing in your kernel.
a) cp the following files into the directory /usr/src/linux/drivers/usb/media
usbvision.c
usbvision.h
saa7113.c
i2c-algo-usb.c
i2c-algo-usb.h
usbvision_ioctl.h
c) In the makefile of the dir /usr/src/linux/drivers/usb, look for the line "obj-$(CONFIG_USB_IBMCAM) +=media/",
insert an additional line then added the line for the usbvision driver
obj-$(CONFIG_USB_USBVISION) += media/
e) Add the line to the makefile in /usr/src/linux/driver/usb/media/
obj-$(CONFIG_USB_USBVISION) += usbvision.o saa7113.o i2c-algo-usb.o
f) Edit file /usr/src/linux/drivers/usb/media/Kconfig
Paste the following lines below after the entry for the IBMCAM.
---------------------------- Begin Paste ------------------------------
config USB_USBVISION
tristate "USB Zoran/Nogatech USBVision Video Grabber Support"
depends on USB && VIDEO_DEV && I2C && VIDEO_BT848 && VIDEO_DPC
---help---
   Say Y here if you want to connect a Nogatech NT100x, or a Zoran
   ZR36504/ZR36505 chipset based video/tv/radio grabber, to your
   computer's USB port.
   For more information, read <file:Documentation/usb/usbvision.txt>.
   This driver needs the following support: Please enable (Y or M in config)
      Video For Linux API
I2C API.
BT484 Device Support
DPC7146 demonstration board Device Support
   This code is also available as a module ( = code which can be
   inserted in and removed from the running kernel whenever you want).
   The module will be called usbvision.o. If you want to compile it as a
   module, say M here and read <file:Documentation/modules.txt>. This
   video grabber has several configuration options which can be specified
   when you load the module. Read <file:Documentation/usb/usbvision.txt> to
   learn more.
---------------------------- End of Paste -----------------------------
h) If it is not already there (it usually is), create the video device:
mknod /dev/video c 81 0
i) Sometimes /dev/video is a symlink to /dev/video0
You will have to set permissions on this device to allow you to read/write
from it:
chmod 666 /dev/video
chmod 666 /dev/video0 (if necessary)
When configuring the kernel choose Zoran/Nogatech USBVISION video support as
module. You are going to need also to select i2c and v4l, and if your
device have tuner you need to compile also BT848 support or other modules
that compile the tuner.o module.
a) Do a make modules, make modules_install.
b) If the USB Support and the Video4Linux was compiled as modules.
   modprobe usbcore.o
modprobe usb-uhci.o <OR> modprobe ohci-hcd.o
   modprobe videodev.o
b) Install the modules:
      modprobe usbvision- For a great radio application, try GQradio.
The usbvision module will also load the i2c-algo-usb, i2c-core, saa7111, saa7113.
VIDEO PLAYERS FOR PLAYING VIDEO OUPUT
Here is the setting to get the TV tuner working with mplayer. It does software video scaling, so you can have full screen mode with the USBVision driver.
mplayer tv:// -tv channel=43:driver=v4l:input=0:outfmt=rgb24:norm=ntsc:height=240:width=320 -flip
Here is the setting to get the TV tuner working with xawtv.
xawtv -c /dev/video0
USBVISION MODULE PARAMETERS:
NAME: isocMode
TYPE: integer (0x03, 0x14, 0x60)
DEFAULT: 0x60
DESC: The isocMode is the format mode of the data that is transmitted on the isocronous
pipe via USB. It is not depending on the connected video-hardware. Default is 0x14.
YUV422 0x03
YUV420 0x14
COMPRESSION 0x60 Enable compression for full framerate.
NAME: debug
TYPE: bitmask
DEFAULT: 0
DESC: You don't need this option unless you are a developer. If you are a developer then
you will see in the code what values do what. This is a bit mask, and you can combine any
number of bits to produce what you want:
bit 2 debug procfs
bit 3 debug video ioctl
bit 4 debug video io
bit 5 debug radio io
bit 7 debug usb frame header
bit 8 debug probe and disconnect
bit 9 debug irq
bit 10 debug handling of isochronus transfer
bit 11 debug parsing of usb data
bit 12 debug handling of scratch
bit 13 debug utility functions
bit 14 debug i2c stuff
NAME: flags
TYPE: bitmask
DEFAULT: 0
DESC: This is a bit mask, and you can combine any number of bits to produce what you want.
Usually you don't want any of extra features this option provides:
bit 0 FLAGS_RETRY_VIDIOCSYNC This bit allows to retry failed
VIDIOCSYNC ioctls without failing.
Will work with xawtv, will not
with xrealproducer. Default is
not set.
bit 1 FLAGS_MONOCHROME Activates monochrome (b/w) mode.
bit 2 FLAGS_DISPLAY_HINTS Shows colored pixels which have
magic meaning to developers.
bit 3 FLAGS_OVERLAY_STATS Shows tiny numbers on screen,
useful only for debugging.
bit 4 FLAGS_FORCE_TESTPATTERN Shows blue screen with numbers.
bit 5 FLAGS_SEPARATE_FRAMES Shows each frame separately, as
it was received from the camera.
Default (not set) is to mix the
preceding frame in to compensate
for occasional loss of Isoc data
on high frame rates.
bit 6 FLAGS_CLEAN_FRAMES Forces "cleanup" of each frame
prior to use; relevant only if
FLAGS_SEPARATE_FRAMES is set.
Default is not to clean frames,
this is a little faster but may
produce flicker if frame rate is
too high and Isoc data gets lost.
NAME: dga
TYPE: integer (0-1) boolean
DEFAULT: 1
DESC: This will set the option for DGA video to either Yes or No. Default is 1.
NAME: PowerOnAtOpen
TYPE: integer (0-1) boolean
DEFAULT: 1
DESC: This will set the device to power on automatically when opened. Default is 1.
NAME: SwitchSVideoInput
TYPE: integer (0-1) boolean
DEFAULT: 0
DESC: To help people with Black and White output with using s-video input. Some cables and input devices are wired differently.
If you are getting a black and white image when using the S-Video input. Set this parameter to 1. Default is 0, since most
devices do not have this problem.
NAME: CustomDevice
TYPE: string
DEFAULT: NULL
DESC: This will set a new Custom device
EXAMPLE: "0x0573 0x4D31 0 7113 3 PAL 1 1 1 5 -1 -1 -1 -1 -1"
FORMAT: "idVendor idProduct Interface Codec VideoChannels VideoNorm AudioChannels Radio
Tuner TunerType Vin_Reg1 Vin_Reg2 X_Offset Y_Offset Dvi_yuv"
Codec:
7111
7113
819
VideoNorm:
P or PAL
S or SECAM
N or NTSC
TunerType: (!!!use the NUMBER not the name) see latest in "/usr/src/linux/drivers/media/video/tuner.h"
TUNER_TEMIC_PAL    0 /* 4002 FH5 (3X 7756, 9483) */
TUNER_PHILIPS_PAL_I 1
TUNER_PHILIPS_NTSC 2
TUNER_PHILIPS_SECAM 3 /* you must actively select B/G, L, L` */
TUNER_ABSENT 4
TUNER_PHILIPS_PAL    5
TUNER_TEMIC_NTSC 6 /* 4032 FY5 (3X 7004, 9498, 9789) */
TUNER_TEMIC_PAL_I    7 /* 4062 FY5 (3X 8501, 9957) */
TUNER_TEMIC_4036FY5_NTSC 8 /* 4036 FY5 (3X 1223, 1981, 7686) */
TUNER_ALPS_TSBH1_NTSC    9
TUNER_ALPS_TSBE1_PAL 10
TUNER_ALPS_TSBB5_PAL_I 11
TUNER_ALPS_TSBE5_PAL 12
TUNER_ALPS_TSBC5_PAL 13
TUNER_TEMIC_4006FH5_PAL 14 /* 4006 FH5 (3X 9500, 9501, 7291) */
TUNER_ALPS_TSHC6_NTSC 15
TUNER_TEMIC_PAL_DK 16 /* 4016 FY5 (3X 1392, 1393) */
TUNER_PHILIPS_NTSC_M 17
TUNER_TEMIC_4066FY5_PAL_I    18 /* 4066 FY5 (3X 7032, 7035) */
TUNER_TEMIC_4006FN5_MULTI_PAL    19 /* B/G, I and D/K autodetected (3X 7595, 7606, 7657)*/
TUNER_TEMIC_4009FR5_PAL    20 /* incl. FM radio (3X 7607, 7488, 7711)*/
TUNER_TEMIC_4039FR5_NTSC 21 /* incl. FM radio (3X 7246, 7578, 7732)*/
TUNER_TEMIC_4046FM5    22 /* you must actively select B/G, D/K, I, L, L` ! (3X 7804, 7806, 8103, 8104)*/
TUNER_PHILIPS_PAL_DK 23
TUNER_PHILIPS_FQ1216ME 24 /* you must actively select B/G/D/K, I, L, L` */
TUNER_LG_PAL_I_FM 25
TUNER_LG_PAL_I 26
TUNER_LG_NTSC_FM 27
TUNER_LG_PAL_FM 28
TUNER_LG_PAL 29
TUNER_TEMIC_4009FN5_MULTI_PAL_FM 30 /* B/G, I and D/K autodetected (3X 8155, 8160, 8163)*/
TUNER_SHARP_2U5JF5540_NTSC 31
TUNER_Samsung_PAL_TCPM9091PD27 32
TUNER_MT2032 33
TUNER_TEMIC_4106FH5 34 /* 4106 FH5 (3X 7808, 7865)*/
TUNER_TEMIC_4012FY5 35 /* 4012 FY5 (3X 0971, 1099)*/
TUNER_TEMIC_4136FY5 36 /* 4136 FY5 (3X 7708, 7746)*/
TUNER_LG_PAL_NEW_TAPC    37
TUNER_PHILIPS_FM1216ME_MK3 38
TUNER_LG_NTSC_NEW_TAPC    39
TUNER_HITACHI_NTSC    40
TUNER_PHILIPS_PAL_MK    41
TUNER_PHILIPS_ATSC    42
TUNER_PHILIPS_FM1236_MK3 43
TUNER_PHILIPS_4IN1    44 /* ATI TV Wonder Pro - Conexant */
TUNER_MICROTUNE_4049FM5 45
TUNER_LG_NTSC_TAPE    47
TUNER_TNF_8831BGFF    48
================================================================================================
FINAL NOTE:
If your device isn't known, add it to usbvision_device_data and usbvision_table in usbvision.h.
You can speed up tuner detection, when adding "options tuner addr=your_addr" to /etc/modules.conf.
If your device isn't known, edit line (modprobe usbvision CustomDevice="0x0573 0x4D31 0 7113 3 PAL 1 1 1 5 -1 -1 -1 -1 -1")
in 'usbvision.rc' file then 'usbvision.rc start'
also edit "etc/rc.d/init.d/usbvision" if you use it
Please tell me your experience ([email protected]), or contact ([email protected]).
=============================================================
As described it is a PAL device. There are options for TV included.
I am interested in single frame capture and video stream capture via the camera input connectors(NTSC-stereo audio). My camera is a PIXERA and has video NTSC output.
The following is reference to the USBVISION tar.gz which seems to require ZORAN in the kernel. It used to be called ZORAN/NOGATECH.
It would seem necessary to enable ZORAN in the latest kernel in order to implement the device. Other requirements are likely as well.
Perhaps a pkg could be built but certainly seems a big challenge!
My DVC80 is recognized in USB.
Hopefully, it can be done in arch!
EDIT:The tar.gz reference below:
file:///root/Desktop/usbvision-0.9.8.2.tar.gz

I use this one with Windows 7:http://www.chronos.com.tw/Product/E/2/USB%20Movie%20Editor/USB%20Movie%20Editor.htm
It worked bad with out of box Windows 7.
But after all updates it works very well and stable.
A nice thing is that it has little USB extender cable included. So it is less harmful for laptop usb port.

How would I create an USB Barcode Scanner Listener using Adobe AIR?

I want to create a USB barcode scanner listener that would read in the scanned barcode, and place the barcode in a field in my AIR App even if the program wasn't focused on that particular field in the App. If the client was using the application at the time for something else the scan would be buffered in AIR till requested or the AIR App has been idle for x period of time where upon the field would be brought into focus.
How would I go about this (I'm developing on windows) Was hoping for a USB solution within AIR but not fussy at all if I have to go outside AIR to solve this problem. Java, Flex, ActionScript, Flash, C, C++, C#, VB (currently I've developed the rest of the App using Adobe AIR and JavaScript)
I thought after some research that I could make a Java App (if all else fails) that listens and buffers the input and passes it along using a socket but JUSB doesn't work on Windows properly.
I'm not stuck on any one particular implementation or idea just want to get development underway so... Any ideas? or suggestions would be awesome. I've googled a lot but haven't found any examples or solid suggestions, so any URL pointing to that information would be great too, if you know of a good one, then I'd be able to read up on any suggestion.
Thanks,
Marty

Thanks Joe,
Just for anyone else. I bought a Metologic Scanner - VoyagerCG. I was trying to get it to work using Java USB for a bit with no luck. But if you get this scanner or one like it, it can be configured as a Virtual COM Port. Which is very very easy in Java to set up as a listener and use sockets to transfer the data and listen within AIR.
This PDF has links to drivers and instructions if this is useful to anyone.
http://taltechnologies.com/products/Eclipse-Voyager%20Interface%20Options.pdf
All the best,
Marty

LaCie d2 195 GB USB hard drive and new iMac

Has anybody had a problem with a LaCie d2 drive that is connected via USB instead of FireWire? I have both types of external hard drives; the FireWire connected LaCie has worked flawlessly, as has a Seagate 300GB FireWire drive. But my poor little LaCie 195 GB USB hard drive bit the dust when I tried to copy my iPhoto library from it to the hard drive of my new iMac Intel Core. The entire Mac froze up, even though there was disk activity on the LaCie. After waiting for 25 minutes for the Mac to unfreeze, I finally manually powered down the system. Unfortunately this corrupted my LaCie disk, and it could not be repaired using Disk Utility. Even when I tried to repartition the drive, Disk Utility simply hung to the point where I had to do a Force Quit to get out of it.
I forgot to mention that I was connecting the LaCie through a powered USB 2.0 hub - that could be a source of the problem, but it worked flawlessly in my iMac G5. I did reconnect it directly to a USB port on the iMac, but still could not get Disk Utility to repartition the drive.
Luckily I had a secondary backup of my photo and music files, or I'd really be crying right now.
Any thoughts?
Thanks,
JD
PowerBook G4 12 Mac OS X (10.4.4)
PowerBook G4 12 Mac OS X (10.4.4)

Mac 1 Ghz G4 1 gig Ram Os 10.4.5
My Firewire connected LaCie Bigdrive started disconnecting spontaneously with a complaint from the iMac that it was disconnected improperly.
Finally it did so once more and has not mounted via FW since. However, USB does mount it but big files take all day to transfer.
I took out the Maxator from the LaCie drive and put it in a FW/USB caddy, ok for a while then the same story. USB only mounting.
Informed with some confidence by a poster on Bombich's website
( http://forums.bombich.com/viewtopic.php?p=25658#25658 ) that it was the boot drive OS
Tried new cable. repaired boot drive disc, repaired permissions, ran DiscWarrior over it, repaired permisssions, ran downloaded 10.4.5 combo, ran DiscWarrior over it and finally repaired permissions again.
No Joy.
i would most appreciate useful suggestions.
Regards and thanks in advance
Anoop in the UK
apollo11
View Public Profile
Send a private message to %1$s
Find More Posts by apollo11
Add apollo11 to Your Buddy List
Reply

Is it possible to wait longer for USB with mkinitcpio-solved

Hi,
I recently installed from an arch0.7.2-base CD, but can't boot after the mkiniticpio upgrade, including with the kernel26-fallback.img.
My root partiition is on a USB hard-drive, and it seems like the drive isn't being detected in time.
With mkinitrd I could specify a delay to wait for USB devices to settle, but there doesn't appear to be anything similar in mkinitcpio, is there?
This may not be the problem at all, of course, but on one occasion when I booted with break=y, just after the message about break requested, there is no ls binary etc.,
usb2-4: new fullspeed USB device using OHCI_HCD address 2
came up, which looked like it had found the USB device, but too late.
(This is after it says it failed to detect the filesytem type etc.)
When I do break=y and echo /dev/*, my hda devices are there, but there are no sda devices, just a series of usbdev files (e.g. usbdev1.1_ep00 ). Is that normal?
Sorry for posting yet another mkinitcpio question.
Any suggestions would be greatly appreciated. Let me know if there's any other output I should post.
Thanks,
Fishonadish

Update:
I'm fairly certain the lack of wait time for USB is the problem now.
I can now boot into arch fine provided I use break=y.
I get the messages about about not finding the root device then the break requested section then, after the ramfs$ prompt appears I get
SCSI device sda: [number] 512-byte hdwr sectors [number] MB
and so on...
and when I type exit at the prompt it boots fine.
To get this far I rebuilt the kernel26.img with the following in mkinitcpio.conf:
MODULES="usb-storage ext3"
HOOKS="base udev autodetect usb filesystems"
(Not sure about this, but it seems putting usb-storage in modules got me this far?)
I still need to get it to delay for USB for a bit longer so I don't have to type 'exit' at the ramfs prompt every time I want to boot, or is it some other problem?
If this has been dealt with before, then sorry for the repetition, but I can't find anything covering it elsewhere.
Thanks.
Fishonadish

GPIB to USB in 16 Bit Dataformat

Similar Messages

Maybe you are looking for