ATI Remote Wonder LabVIEW drivers

Hello!
if someone has some drivers for The Remote Wonder that could be really helpfull for me.
Thanks

Hi Nanobu,
One option would be to use the VISA Driver Development wizard to assign NI-VISA as the driver for the remote. This option requires you to have VERY detailed knowledge about the remote, and will not be trivial . One question though. Does the remote mimic keystrokes on your keyboard when you push a button? If it does, then you can use LabVIEW directly to capture the keystrokes and determine what button was pushed on the remote. This will probably be a more feasible solution. Hope this helps.
Regards,
Ebele O.
National Instruments

Similar Messages

  • ATI Remote Wonder

    Does anyone have an ATI Remote Wonder working after Leopard installation? Mine worked on my Intel iMac before Leopard, but not now.

    Hi Nanobu,
    One option would be to use the VISA Driver Development wizard to assign NI-VISA as the driver for the remote. This option requires you to have VERY detailed knowledge about the remote, and will not be trivial . One question though. Does the remote mimic keystrokes on your keyboard when you push a button? If it does, then you can use LabVIEW directly to capture the keystrokes and determine what button was pushed on the remote. This will probably be a more feasible solution. Hope this helps.
    Regards,
    Ebele O.
    National Instruments

  • Other remotes in an AirPort Express - ATI Remote Wonder?

    I've just bought an AirPort Express, looks like a good little product, but just wondering about plugging my USB remote into it.
    I've got an ATI Remote Wonder, which has a small USB receiver, and wondered if there is ever likely to be any support for using this with the AirPort, through the printer port? I know that there is the Apple remote available, but would prefer to use mine (radio frequency wireless rather than infrared).
    Does anyone rate my chances of getting it to work / someone writing a software update to support it?
    Cheers
    David

    Errr... that was about Client Mode, not connecting remotes to it.
    As far as I can tell from a lot of time looking from Google, there isn't any support for it currently (neither official nor third party). I've tried to do the Feedback suggested to Apple, but there wasn't a category for AirPorts so no idea if they'll ever get it through the laptop Feedback link I used :o(
    Alternatively, maybe if I tape the transmitter to my laptop it'll work too... just not quite as elegant a solution!
    David

  • ATI Remote Wonder (Eye TV)

    OS 10.4.4 "killed" my remote control "Remote Wonder" from ATI which I got together with ElGato EyeTV. It was so usefull for me (lazy couch potato) to watch EyeTV recordings, my holiday videos, my photos and listen to iTunes from the couch. I have tried everything to get it going again, even installed a clean new OS 10.4.4 on an empty external FW drive, whatever I do - none of the drivers from ATI are installable - 10.4.4 does not "want them". My new G5 Quadra and I are very sad ...
    Roland Muehlberger, Linz, Austria
    G5 Quadra 2,5 GHz   Mac OS X (10.4.4)  

    Hi Nanobu,
    One option would be to use the VISA Driver Development wizard to assign NI-VISA as the driver for the remote. This option requires you to have VERY detailed knowledge about the remote, and will not be trivial . One question though. Does the remote mimic keystrokes on your keyboard when you push a button? If it does, then you can use LabVIEW directly to capture the keystrokes and determine what button was pushed on the remote. This will probably be a more feasible solution. Hope this helps.
    Regards,
    Ebele O.
    National Instruments

  • ATi Remote Wonder remapping

    Anyone know how?  The remote is detected and Arch accepts input from it, but the mapping is all off.  Debian had things like the volume controls mapped correctly, but in Arch pretty much nothing except the cursor movement works properly.  I'd love to get this thing mapped better if anyone knows how.

    Hi Nanobu,
    One option would be to use the VISA Driver Development wizard to assign NI-VISA as the driver for the remote. This option requires you to have VERY detailed knowledge about the remote, and will not be trivial . One question though. Does the remote mimic keystrokes on your keyboard when you push a button? If it does, then you can use LabVIEW directly to capture the keystrokes and determine what button was pushed on the remote. This will probably be a more feasible solution. Hope this helps.
    Regards,
    Ebele O.
    National Instruments

  • Ati tv wonder

    I installed aa ATI tv wonder pro.When I run the pc check in multimedia center configuration I get an error that says that my sound card did not pass the test: the clock accuracy is less than .2%. I downloaded the latest drivers for my audigy eax soundblaster sound card but it did not solve the problem. I would appreciate if anyone could help me. Thank you!

    don't bother, it's always that with the ATI stability test.

  • Labview drivers for Prisma QMS

    Hi,
    I'm looking for labview drivers for the Prisma Quadrupole Mass Spectrometer
    from Pfeiffer Vacuum. If possible also a simple rest gas analysis (RGA) VI.
    Can anyone help?
    Hans Rosink

    There is no driver available as the qmg220 uses OPC communication you can use labviews build in OPC functions.
    But the problem is that the "normal" labview OPC functions using datasoket are a little bit limited and when you need to adress many OPC items it may crash.
    Therefore NI is producing the LABVIEW DSC module which is avialable for extra money and with the main problem that you are not able to build stand alone applications without any extra licencing costs. Which makes problems if you want to sell your software or add it to the instrument you sell.
    On the other side the DSC module is a little bit to powerfule for the communication with the QMG220.
    Because of these arguments we decideed to use a OPC developement toolkit from Softing . 
    We started with the .NET developement but there4 was a reasonable memeory leak in Labview when using .NET event callbacks.
    This has been solved with Labview 2009f2 and up versions.
    Up to now we have made our communication with the Softing ActiveX control within labview.
    Now we are on the  point to switch bak to .NET. 
    When try the OPC connectivity from any third party opc API vendor and you are using a remote OPC from labview please tonst forget to add the line.
    ole.AuthnLevel = 1 to your labview.ini file. 
    Hope this gives you a first overview.
    We are not planning to build a easy to use driver for the QMG220 but we build a lot of vi's to control some functions and collect the data.
    Best regards
    Gernot 

  • LabVIEW drivers for Newport 2010A tunable diode laser?

    My group aquired a Newport 2010A tunable diode laser and failed to receive the labview drivers for remote control operation.  Does anyone have this software?

    All,
       Here is a link to a clean photocopy of the EOSI 2010 laser manual:
    https://wiki.brown.edu/confluence/download/attachments/29406/Diode+Laser+Manual.pdf?version=1
       You can also Google it using "EOSI 2010 laser" and find the maual in the link that says: "EOSI tunable laser diode systems and accessories are guaranteed
    for a period .... the 2010 laser diode. The first
    method is more sensitive but requires both .."  Good hunting.
    Sincerely,
    John Zehnpfennig
    U-Michigan Optics Lab

  • Ati TV Wonder Ve

    is their and drivers or a way to use the windows drivers on my ATI TV Wonder VE. I bought it some time ago and when I switch over to mac I never got it to work. I heard of ways of using windows drivers on linux with wireless cards I wasn't sure if this would work for Mac as well.
    -Mac OS X 10.2.8

    I'm not using SP-1, so that's not the problem.  I just downloaded the trial version of PowerVCR II, but basically the same thing happens as under MSIPVS Windrv - splash screen and then it stops dead.
    In poking around in the Device Mgr, I do have one question maybe someone can answer.  Under the entries for the MSI PVS Tuner, Crossbar, and Video Capture - under the Driver details, the following files are listed (in addition to the basic CX88 MSI drivers.
    ks.sys
    lyuv_32.dll
    ksproxy.ax
    kstvtune.ax
    ksuser.dll
    kswdmcap.ax
    ksxbar.ax
    msh263.drv
    msyuv.dll
    tsbyuv.dll
    vfwwdm32.dll
    The files are all version 5.1.2600.0 with the exception of msh263.drv which is version 4.4.3400
    I tried looking up those files in the knowledge base at microsoft, and the only references I see to any of those files are under Windows 98, not XP.  I'm starting to wonder that since I upgraded from Win98 to XP instead of doing a totally clean install, that these driver files came along for the ride and now are messing things up.   (I know I'm probably grasping at straws).  So if anyone of you who have a working @nywhere, I would appreciate it if you could take a look.
    bobk

  • How to use Labview drivers for USB-CAN Adapter

    Hi,
    I just recently started working with CAN and I have a PCAN-USB adapter. I'm trying to create a programme for monitoring a series of CAN based devices and I've found Labview drivers at the link below. However, I'm not really sure how to start. I have the specs for the device but I don't know how to proceed. 
    Should I create messages and channels and a data base in MAX first?  If anyone has programmed with this dongle before please give me a guide how you went about it. 
    Labview drivers - http://www.labviewportal.eu/en/device-i-o/82-pcan-usb-driver.
    Thanks 

    I have not used this specific CAN adapter, but I have used other CAN adapters from both NI and other companies.  The CAN database in MAX is useful only if you are using an NI CAN device.  For all other CAN devices you need to use the format that the library uses; most likely that will be raw CAN frames.
    If you do want to use the NI-CAN interface on top of the PCAN library, you can use NI-CAN virtual channels 255 and 256.  These are internally connected, so that anything you send on one is received on the other.  This makes it possible to do translation between raw frames and channels defined in a database, by opening one interface for frames and the other for channels.  You read raw frames from the real device and send them to CAN255, then read them on CAN256; for writing, you do the opposite.  However, this still requires understanding how to read and write raw frames on the underlying device, so I'd start there.

  • ATI TV Wonder... not making device node?

    I purchased an ATI TV Wonder card yesterday. I've been Googling and reading numerous tutorials and I just can't get it to work. There just isn't a device node for it in /dev... no /dev/video0, /dev/v4l/video0, not even a /dev/v4l!
    So far, I've changed my /etc/modprobe.conf so that it includes:
    alias char-major-89 i2c-dev
    alias char-major-81 videodev
    alias char-major-81-0 bttv
    options bttv card=63 radio=0
    options tuner debug=1
    alias char-major-81-1 tvaudio
    After rebooting, an lsmod showed that none of those were loaded, so I added them (bttv, tuner, tvaudio, i2c_core, and i2c_algo_bit) to /etc/rc.conf as well. Now they are loaded at boot, but there's still no device.
    Then, I edited /etc/X11/xorg.conf to load v4l, but that doesn't help either. I also added:
    REGISTER v4l/.* PERMISSIONS root.users 660
    REGISTER video0 PERMISSIONS root.users 660
    to /etc/devfsd.conf (and rebooted to restart devfs), but that didn't help, either.
    What do I have to do to get the device to show up? It shows up in lspci (I think):
    [kyle@zero ~]$ lspci
    00:00.0 Host bridge: nVidia Corporation: Unknown device 01e0 (rev c1)
    00:00.1 RAM memory: nVidia Corporation: Unknown device 01ea (rev c1)
    00:00.2 RAM memory: nVidia Corporation: Unknown device 01ee (rev c1)
    00:00.3 RAM memory: nVidia Corporation: Unknown device 01ed (rev c1)
    00:00.4 RAM memory: nVidia Corporation: Unknown device 01ec (rev c1)
    00:00.5 RAM memory: nVidia Corporation: Unknown device 01ef (rev c1)
    00:01.0 ISA bridge: nVidia Corporation: Unknown device 0060 (rev a4)
    00:01.1 SMBus: nVidia Corporation: Unknown device 0064 (rev a2)
    00:02.0 USB Controller: nVidia Corporation: Unknown device 0067 (rev a4)
    00:02.1 USB Controller: nVidia Corporation: Unknown device 0067 (rev a4)
    00:02.2 USB Controller: nVidia Corporation: Unknown device 0068 (rev a4)
    00:04.0 Ethernet controller: nVidia Corporation: Unknown device 0066 (rev a1)
    00:06.0 Multimedia audio controller: nVidia Corporation nForce MultiMedia audio [Via VT82C686B] (rev a1)
    00:08.0 PCI bridge: nVidia Corporation: Unknown device 006c (rev a3)
    00:09.0 IDE interface: nVidia Corporation: Unknown device 0065 (rev a2)
    00:1e.0 PCI bridge: nVidia Corporation: Unknown device 01e8 (rev c1)
    01:07.0 Multimedia video controller: Conexant: Unknown device 8800 (rev 05)
    01:0a.0 Ethernet controller: D-Link System Inc DL10050 Sundance Ethernet (rev 12)
    02:00.0 VGA compatible controller: ATI Technologies Inc Radeon R250 If [Radeon 9000] (rev 01)
    02:00.1 Display controller: ATI Technologies Inc Radeon R250 [Radeon 9000] (Secondary) (rev 01)
    I know it's supported because it was working on Ubuntu (but after the dependency hell I went through trying to get kdetv to install I reinstalled Arch). I'm at a loss here... I have no idea what to do next. Anyone have any suggestions?

    undeadpenguin wrote:
    I purchased an ATI TV Wonder card yesterday. I've been Googling and reading numerous tutorials and I just can't get it to work. There just isn't a device node for it in /dev... no /dev/video0, /dev/v4l/video0, not even a /dev/v4l!
    So far, I've changed my /etc/modprobe.conf so that it includes:
    alias char-major-89 i2c-dev
    alias char-major-81 videodev
    alias char-major-81-0 bttv
    options bttv card=63 radio=0
    options tuner debug=1
    alias char-major-81-1 tvaudio
    I'm at a loss here... I have no idea what to do next. Anyone have any suggestions?
    I've no idea whether this has anything to do with your problem but I noticed that in your /etc/modprobe.conf you've missed your tuner type.
    you have:
    options bttv card=63 radio=0
    options tuner debug=1
    I think you should have something like:
    options bttv card=63 radio=0
    options tuner=5 debug=1
    (replace 5 with your tuner type code)
    .murkus

  • "Remotely Control LabVIEW Over the Web "in LabView 6.0

    Hello,
    is it possible that I realize "Remotely Control LabView Over the Web" in
    LabView6.0 ?
    Thanks a lot!

    The LabVIEW Remote Panels feature was added with version 6.1. If you have not done so, I highly recommend the upgrade!
    Daniel L. Press
    PrimeTest Corp.
    www.primetest.com

  • LabView drivers for Agilent 54830B scope or E4402B Spectrum Analyzer?

    Where can I find LabView drivers for the Agilent 54830B scope and the E4402B spectrum analyzer, or at least a driver for another instrument in the same families that I could modify? There are none on the NI site or the Agilent site.

    One thing that I have done several times is get a LabWindows CVI
    driver from Agilent. You will be provided with a .fp file. LabVIEW
    has a link under the Tools>>Instrumentation menu that allows you to
    "Import CVI Instrument Driver." This will take the function calls
    from CVI and build a set of VI's with the same name. The vi's will be
    wrappers for a dll that is used by CVI and other text based languages.

  • LabView drivers for USB to DMX512 hardware

    Anyone find any hardware (USB to DMX512) that is supported by LabView (i.e. LabView drivers)?

    I'm
    not aware of any DMX-512 interfaces that come with a LabVIEW API.
    However, most of those interfaces come as PCI cards or as
    serial-to-DMX512 converters.
    In the first case, there is always a
    DLL to communicate with the PCI card and you can use LabVIEW's Call
    Library Node to call that DLL from your LabVIEW code.
    Quite a few
    DMX-512 converters are connected through RS232 (or RS485) and LabVIEW
    as built-in support for the serial port. This seems to be the easiest
    approach.  Here is a link to a Discussion forum which discusses this:
    http://forums.ni.com/ni/board/message?board.id=140&message.id=2052&requireLogin=False
    Regards,
    John E.
    Applications Engineering
    National Instruments

  • Looking for LabVIEW drivers for Aritsu MS462XX VNA?

    I'm looking for LabVIEW drivers for the Anritsu model MS4623D Vector Network Analyzer?  Have gone to Aritsu's site and downloaded their tools but no LabVIEW source found.   The other thing is whether anyone's developed LabVIEW interfaces to theirTools (Navigator or Power Tools or SCE)???

    Hi,
    Unfortunately, we do not have an instrument specific driver for this Anritsu model MS4623D. Here is a link to the drivers we do have for Anritsu. We may be able to get communication to your device threw another means. How does your device communicate? For example is it GPIB or Serial. We may be able to use an NI driver and a programming manual for your device and communicate with it in LabVIEW threw this.
    Regards
    Krista S.
    Applications Engineering
    National Instruments

Maybe you are looking for