Tuesday, February 23, 2010
The Stream API is independent of the development environment and is currently fully implemented in C/C++, .NET languages, MATLAB and LabVIEW. It can be readily extended to other languages and environments as required. This makes any Quanser Stream protocol accessible from and to external applications.
The QUARC communication framework, using the Quanser Stream API, follows the well-established client/server communication mechanism implemented in either a blocking I/O mode (i.e. asynchronous I/O in a separate thread) or non-blocking I/O mode (i.e. synchronous I/O in the model current thread). The Quanser Stream communication framework is open and structured to readily accommodate and integrate new communication protocols as required. At present, the Quanser Stream API has communication protocols available for the operating systems that QUARC can target, such as Windows (32-bit XP and Vista), QNX and Linux ARM (gumstix). The Stream API also allows for switching from one communication protocol to another by only changing the Uniform Resource Identifier (URI) string defining the new protocol to be used. The rest of the blocks or functions used in the communication remain untouched!
Stay tuned for more details!
Friday, February 12, 2010
Tuesday, February 9, 2010
Friday, February 5, 2010
Students also got the chance to run the QNET VTOL with a joystick. We let the students experience the difference in controlling the 1 DOF helicopter when they do it by themselves, i.e. open-loop, and when they get help from the computer, i.e. closed-loop. Although they understood that it was easier to control with the PC, we all agreed that it’s not as much fun!
In closing, this audience was full of energy and had lots of great questions. Some were more hardware-oriented and asked about the device components. Others wondered what software was used to run the systems.
Jacob and I had a great time and would like to thank everyone at Bayview Glen for their enthusiasm.