Abstract
This paper describes the uLab, a new method and framework for remote hardware design laboratories, which uses Linux and FOSS to provide real-time design and debug services to students over standard RDP channels. A secure, encrypted, plugin-based remote laboratory framework allows customization of programming and debug/test services to match physical laboratory resources. Industry standard technologies such as LDAP and Kerberos are utilized to ensure scalability, security, and ease of management. Emphasis is placed on direct access to real hardware, with the normal array of simulation tools and design software also being provided. In contrast with many of the remote laboratories currently in existence, this system places strong emphasis on direct, long-duration access to real, physical hardware for non-trivial design and evaluation tasks. In order to achieve this goal, secure, network-enabled hardware "pods" were created from inexpensive COTS components, and a blend of new and existing open-source software was used to connect with the overall laboratory framework. Hardware-design software and tools, including the software for physical hardware access, are preloaded and made available within the desktop session, allowing students to log in and start working almost immediately.
Highlights
A typical hardware design laboratory consists of several workstations and associated hardware in an accesscontrolled room with rigidly scheduled laboratory dates and times
One of the typically overlooked issues with this type of laboratory is the low average utilization ratio; there normally are large portions of each day when the laboratory is nearly or completely idle with no student access permitted. Another drawback is a relatively short window for laboratory sessions, during which the students are more focused on completing particular assignments within the allotted time frame than they are on learning vital concepts via semi-structured, hands-on interaction with design tools and hardware
Remote laboratories, such as the uLab system described in this paper, alleviate many of the drawbacks listed above, and provide exciting new opportunities for students to interact with the laboratory hardware in a non-traditional manner
Summary
A typical hardware design laboratory consists of several workstations and associated hardware in an accesscontrolled room with rigidly scheduled laboratory dates and times. In many institutions, there are insufficient resources available to handle simultaneous usage by all students within a particular laboratory period; this forces multiple students to be assigned to a given workstation and further removes each student from hands-on interaction with the design software and physical hardware Remote laboratories, such as the uLab system described in this paper, alleviate many of the drawbacks listed above, and provide exciting new opportunities for students to interact with the laboratory hardware in a non-traditional manner. The new uLab laboratory system, which derives its name from the goal of providing a “Universal Laboratory,” is open-source itself, and is built entirely upon open-source software and, where possible, open hardware This frees institutions from the requirement of purchasing expensive software licenses for each new hardware workspace, and allows them to, instead, focus on providing the best possible experience for their students.
Sign-in/Register to view highlights & summary Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callMore From: International Journal of Online and Biomedical Engineering (iJOE)
Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
