Connection with controller

/Connection with controller
Connection with controller2020-05-11T17:02:17+02:00

Connect with the Moduline.

If the minimal connection requirements are meet, the controller can be started. If the controller is started, a physical connection can be established in two ways which are described here.

After making a physical connection with the controller, the user can login to the controller using Node-RED or the Linux command line interface (CLI). For low-level configurations, the CLI is used most of the time. For common configurations, GOcontroll made a settings node for Node-RED in which basic settings are covered.

Minimal pre-requisites:

  • It is important that at least connector C is connected to a power supply (ground, +30 (battery) and the activate pin).
  • The WLAN antenna needs to be present on the controller.
  • A laptop or PC with Wi-Fi capabilities (if WLAN is used to connect with the controller)
  • A wired network with DHCP enabled router (if wired ethernet is used to connect with the controller)
  • An installed web browser if Node-RED is used to login (Chrome preferred)
  • A terminal program (eg. PuTTY) to connect to the controller using SSH when using the CLI

Setup the physical connection.

If the controller is activated, it’s time to make a physical connection using a WLAN or wired Ethernet.

Connect via WiFi

When the controller is accessed via WLAN, the only thing you need to do is connect to the by the controller generated WiFi network. The credentials are by default:



Connect via wired network

In this case, the controller needs to be connected to an existing network with the included ethernet cable. The controller will receive a IP address from the DHCP server of the router. Check the assigned IP address by opening the router configuration and search for a DHCP list. Check your router manual for the exact approach of opening the router backend. Once you have find the DHCP list, search for a Debian device and note the IP address.