EJS, JIL Server, and LabVIEW: An Architecture for Rapid Development of Remote Labs

Jesús Chacón, Hector Vargas, GONZALO ALBERTO FARIAS CASTRO, José Sánchez, Sebastian Dormido

Research output: Contribution to journalArticlepeer-review

44 Scopus citations

Abstract

Designing and developing web-enabled remote laboratories for pedagogical purposes is not an easy task. Often, developers (generally, educators who know the subjects they teach but lack of the technical and programming skills required to build Internet-based educational applications) end up discarding the idea of exploring these new teaching and learning experiences mainly due to the technical issues that must be mastered. To tackle this problem, authors present a novel technique that allows developers to create remote labs in a quick, didactical, and straightforward way. This framework is based on the use of two well-known software tools in the scope of engineering education, Easy Java Simulations and LabVIEW. The development exploits a new feature of Easy Java Simulations known as EJS-elements that enables Java developers to create and integrate their own authoring libraries (elements) into EJS, thus increasing its application possibilities. Particularly, the EJS element here presented allows to LabVIEW programs be controlled from EJS applications through a communication network. This paper presents the element creation details and how this can be used to create web-enabled experimentation environments for educational purposes. A step by step example of development of a remote lab for automatic control education is described.

Original languageEnglish
Article number7004872
Pages (from-to)393-401
Number of pages9
JournalIEEE Transactions on Learning Technologies
Volume8
Issue number4
DOIs
StatePublished - 1 Oct 2015

Keywords

  • Control Education
  • EJS
  • LabVIEW
  • Remote Labs
  • Virtual Labs

Fingerprint Dive into the research topics of 'EJS, JIL Server, and LabVIEW: An Architecture for Rapid Development of Remote Labs'. Together they form a unique fingerprint.

Cite this