This website uses Google Analytics. Please click here to prevent Analytics from tracking your surfing behavior. Click here to stop the tracking.


icom SmartBox

1. Container

Activating and creating a script

The icom OS contains a default container that can be activated with only a few mouse clicks on the router and contains the standard commands of the Linux shell as well as a Lua interpreter.

The default container will be addressed via its IP address using a terminal program, for example to create a small script.


It also shows the resources immediately via the command line (e.g. Putty under Windows):

Login in terminal program (the default password for the user root is root):

The content of the personal directory:

Free memory in file system:

Main memory of the whole system (router and container):

Running processes (only own):


Add further users as root

Starting a web server:

Programming in Lua:


2. Porting apps into the SmartBox

Differences between icom SmartBox and INSYS Sandbox 

The INSYS Sandbox is available on the routers (Smart Devices) of the series MoRoS, IMON and EBW. The following must be observed when porting existing applications (apps) from the INSYS Sandbox to the icom SmartBox:

  • File system: partitions are named new.
  • Network: the application in the SmartBox is running on an own host – the IP address differs from the router. The application in the icom SmartBox is subject to other rules for routing, NAT and firewall the the router itself depending on the configuration. Moreover, own network rules can be added directly in the icom SmartBox application.
  • SMS: the SMS spooler of the demo images is not necessary any more. SMS can be added and triggered as events on the router via command line interface. The transfer of the SMS content into the container is possible.
  • IOs and LEDs cannot be addressed via I2C (IMON) any more and not yet via MCIP. They can rather be added and triggered as events on the router via command line interface.
  • Serial interfaces will not be assigned exclusively any more. Conflicts must be trapped on application level.


  • Scripts should normally run without changes if they only use the existing SmartBox resources.


  • Executable binary files (programs and libraries) must be compiled for the new architecture.
  • A prepared environment for the VirtualBox is available in the SDK.
 Unsere neue Website

Überzeuge Sie sich von unserer Leidenschaft für professionelle IoT- und M2M-Datenkommunikation. 
Wir freuen uns auf Sie!