This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
en:iot-open:practical:remotelab [2023/12/06 10:04] – created pczekalski | en:iot-open:practical:remotelab [2024/04/20 11:43] (current) – pczekalski | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== VREL Next Gen Remote Labs ====== | ====== VREL Next Gen Remote Labs ====== | ||
- | <todo @pczekalski>General labs description</ | + | The VREL NextGen distant laboratory with remote access allows one to work with real hardware (not a simulator) and experience real engineering problems. The web browser is all that is needed to interface the lab. Programming the IoT devices is done in the browser, and firmware uploads, restarts, etc., are all handled in the web browser as well. The device' |
+ | Users can choose which laboratory and device to access, then book and use it. Technical documentation and hands-on laboratory scenarios are integrated with the user interface. | ||
+ | |||
+ | <figure vrelnextgen1> | ||
+ | {{ : | ||
+ | < | ||
+ | </ | ||
+ | |||
+ | The VREL NextGen solution comprises one or more hosting servers that provide a user interface via www and several laboratories with hardware located across Europe, currently in Poland, Estonia and Latvia. Public instances are announced via the [[https:// | ||
+ | |||
+ | It is a rule of thumb that a single laboratory usually shares common space and services. One should refer to the technical | ||
+ | |||
+ | <note important> | ||
+ | |||
+ | The following chapters provide a manual for software and hardware. Laboratory scenarios are provided as per laboratory. Integration and local services such as access points, gateways and related technical information (network configuration, |