Update, October 2 nd, 2014: a more recent adavancement in running SCPI on mac, can be found here.AeroCard Universal v.2.0.1. Click Let me pick from a list of available. Click Browse my computer for driver software here. Click the Driver tab in the properties window and click the Update Driver button. Expand the Display adapters section in the Device Manager, right-click the Intel (R) HD Graphics device, and select Properties.
Osx V.2.0.3B3 Sense Aerocard Download By ExistingOSX (10.1.5 and 10.2) driver available and free for download by existing users. Mac OS 9 and OS X native support. Category: Internet Developer: Macsense Connectivity - Download - Price: -AeroCard Plus features an industrial-strength, high-power antenna that covers a range up to 3 times more than other regular wireless LAN cards.Maybe not a big deal, but huge for me because this is the first time I am programming kernel extensions. But I was up to something in the past days and I wanted to share.I have created a driver for my Keysight Agilent DSO-X 2002A oscilloscope. Traditionally, this is a month when I am taking a long break. 5.13 MB.Update, December 10 th, 2015: Updated terms, changed Agilent to Keysight.December again, another year passed. Mac OS X 10.2 or later (PPC & Intel) i70 driver. Free OS X driver installer for the Canon i80 color bubble jet printer.The best part is that all these can be remotely controlled via SCPI commands and sophisticated testing routines can be set up.But one of its biggest shortcomings is the lack of a driver for Mac. It is a dual–channel 70 Mhz scope, comes packed with features and you can extend these via additional software options that you can buy licenses for: built-in function generator (with AM and FM modulation), mask limit testing and six–sigma compliance testing, segmented memory, memory upgrade (software !), bandwidth upgrade up to 200 Mhz, serial decoding, CAN and I2C etc. I bought it almost two and a half years ago and I still did not have the time and patience to write about it and about its great capabilities. NET support, thus integration and communication with these devices from Windows platforms is very easy. Couple this with the extensive Keysight Agilent I/O Libraries documentation and superb. This allows SCPI communication supported by VISA (Virtual Instrument Software Architecture) instrument drivers which makes remote controlling this tool a breeze. Record screen for fixed time quicktime macSome vendors (most importantly National Instruments with their NI-VISA 5.1.2 for Mac OS X) have their own proprietary drivers for products they market. Of course I could heavily relied only on my little Toshiba chick for doing the job, but I decided to build a Mac driver and use it to remotely control my scope and capture measurement data.Another problem is that there is no support for Mac OS X for VISA instrument drivers too. Maybe they will read this post and decide to create at least a driver. Maybe they had some solid reasons for not providing any support for Mac OS X but from my perspective this sucks. This is also what the VXI-11 / LXI protocol provides for TCP/IP and I could’ve easily done my job with a LAN interface for my scope. The USBTMC protocol supports service request, triggers and other GPIB specific operations. USBTMC allows instrument manufacturers to upgrade the physical layer from GPIB to USB while maintaining software compatibility with existing software, such as instrument drivers and any application that uses VISA. For example, you can use VISA Write to send the SCPI *IDN? query and use VISA Read to get the response. This is a pain and I am not very familiar with driver development. I was tempted to try communicating with the scope from within application space and discard any kext development effort. Hooking the device and using Mac’s USB Prober to explore USB descriptors shows that this device is IEEE-488 compliant: Using Mac USB Prober application reveals support for USBTMC / IEEE-488 for Keysight Agilent DSO-X 2002A.Now this leaves with the question of implementation. Luckily, my Keysight Agilent DSO-X 2002 A is USBTMC–compliant. Traditional instruments (such as DMMs and scopes) with USB ports are most likely to support USBTMC so I assumed that Keysight Agilent was not so stupid to do otherwise. The device manufacturer has to add the support in the device firmware to support USBTMC. Bottom line, I managed to successfully match the DSOX 2002A, probe it, start the driver and communicate with my scope as shown in the console output below: Keysight Agilent DSO-X 2002A Oscilloscope on my MacBook Pro: custom I/O Kit driver output in console. I had one more argument in favour of a driver, the possibility to add support for more USBTMC–compliant devices in the future (with simple personality addition in the driver’s Info.plist file).This post will not discuss practical implementation of the driver, I kept this for a separate article because that has a story of its own. The only option I had was either to create a kextless driver and match the device based on VID/PID pair provided by the driver’s Info.plist and do the rest in the application space either to augment the driver code and provide entry points for Write and Read commands, implement as much functionalities as possible in the driver plane hoping that it would make life easier on the application side. Note the complete descriptors and match to my custom driver cpp class, ro_alauda_DSOX2002A. I have removed the scope serial for security reasons. Keysight Agilent DSO-X 2002A on Mac, custom driver, I/O Registry Explorer — driver property table entries. □Your email address will not be published. They can spare me of some effort. And if I did this in a week, I am sure Agilent can do it in a month. But given the fact that I managed to do so much by now without too many kernel panics (sic !), I am very confident that I will manage to close this project with a working application that will remotely control my Agilent DSO-X 2002A from my Mac Book Pro.
0 Comments
Leave a Reply. |
Details
AuthorJonathan ArchivesCategories |