The main analog device that we use is a joystick (several actually) that will utilize the on-board power supply 5VDC across the joystick potentiometers to give us 0 to 5vdc for the full range of any joystick axis (Our own power supply could be used here as the Analog Channels do have a wider range available - "I", current limitations for inputs being observed). Since that switch is truly a momentary switch, I would probably prefer the default minimum be no greater than 500mS for any given digital IN (perhaps 100mS just for the encoder "reset" push-buttons).ġ) For the Analog Channels, we noticed that the NI device could be selected to sample "N" amount of values and then send this "block" of data (at high rates). So this is an additional input that is just for that device. The dial for the Encoder also has a momentary push-button built in (depress knob) which we will use as a "center-up" function to set the end device to its center (or neutral) position / value. This device will use 2 digital "IN" channels for data: 00 // 01 // 11 // 10 // 00 (grey code) OR 00 // 10 // 11 // 01 // 00 based on direction of rotation - which we interpret with our software. which would normally suffice for a toggle switch), but when we rotate the Encoder knob fast, you could cause it to "skip" values. Using the NI test software under Windows (with the C interface that was provided by Version 8.3), we found that we needed to up the read rate to 50 times per second (20mS) since the sample program comes through with a default setting of 1000mS (once per sec. The second type of device we use is an Optical Encoder. Can I just use that library to encode/decode the data to be sent to the device? If so, which API calls would I need to use to talk to the 65 device?Ģ. I know there is a library for Neutrino for PCI devices. I have not been able to find that level of information anywhere when I looked through the sample code on the CD-Rom that ships with the device. That's the information that I basically need at this point (essentially the protocol the device understands).
Neutrino keyboard how to#
That's simple enough to do, but of course I have no idea what data to send to the device to ask for data nor any idea how to decode anything I might receive.
Neutrino keyboard driver#
From doing some USB queries on the device I see it's set to Bulk Transfer mode as opposed to Interrupt mode.įrom looking at the documention on the device and reading your forums I understand this to mean that I must now poll your device through my driver in bulk mode. Now when my driver is running I can detect your device being plugged in or removed. So I took the QNX USB driver development kit and from the sample keyboard USB driver I created one for your devices. However the rest of the discussion seemed to indicate that one could interface with USB devices via the NI-DAQmx library. We realize there is no USB driver available for QNX but hoped to develop our own.īut searching the forum I found a posting that indicates there is no DDK for USB devices. We obtained a 65 USB device and would like to run these under the QNX Neutrino operating system.
0 kommentar(er)
