...

Connecting the SmartServer Ethernet Interface

You can communicate with your SmartServer using the SmartServer LAN and/or WAN interface, and you can communicate with your SmartServer using a USB console interface.  

...

The SmartServer can use the network connection to communicate with IP-enabled devices and routers, such as BACnet/IP, ModBus TCP, LON IP-852, or LON IP-70 devices and routers. The SmartServer can also use the network connection to provide LON remote network interface (RNI) services to a remote IzoT Net Server, LON Protocol Analyzer, or other compatible tools and applications.

Finding the SmartServer IP Address

The SmartServer supports both DHCP and static IP addresses. By default, the SmartServer starts up using Startup Mode, which uses DHCP to assign its IP address, but it will fall back to a known static address. To maintain a stable IP address, change the IP address setting in the SmartServer Network Configuration web page (see Configure Your SmartServer) so that only DHCP or static IP address is used (not Startup Mode). 

Each SmartServer ships with a unique host name marked on the product label located on the back of the SmartServer. The host name begins with smartserver- and ends with the install code. For example, smartserver-17q2eyh.

...

See Configuring the SmartServer IP Address and Hostname for more information and next steps.

Security Warning

When you open a web page from the SmartServer using the default self-signed certificate, you browser may display a security warning. For example, the Chrome browser may display a Your Connection is not Private message. Select the option to proceed with the connection. For example, using Chrome, click Advanced and then click Proceed to <hostname>.local (unsafe). You can eliminate the security warning by enabling a signed certificate as described in Securing Your SmartServer.

Connectivity Testing

Depending on your SmartServer environment, you can use the ping command to test connectivity to the SmartServer as follows:

• Hostname as marked – DHCP network with a local DNS server:
  ping <hostname>
  
  
• Hostname.local – DHCP network without a local DNS server, PC and SmartServer are on the same subnet (fails on some WiFi routers):
  ping -4 <hostname>.local
  
  
• FQDN Hostname – secure certificates enabled:
  ping <hostname>.echelon.cloud
  
  
• Direct wire to the SmartServer and factory configuration, static IP address:
  ping 192.168.1.222

Connecting to the SmartServer Console

You can connect to the Linux console on the SmartServer to perform low-level diagnostics and system maintenance. You can connect to the console interface using a USB cable connected to the Console interface on the SmartServer and to your computer, or you can connect to the Linux console using the Ethernet connection to the LAN or WAN interface on the SmartServer.

To open a console interface you must have a terminal emulator installed on your computer. Typical terminal emulators include PuTTY for Windows and Terminal for Mac. The following sections describe different console interface options.

Connecting to the Console using a USB Serial Connection

You can connect to the Linux console on the SmartServer using USB connection from your computer to the console connector on the SmartServer. You can use any computer with a serial console application that supports a USB serial console interface. To connect to the console using a USB serial connection using a Windows computer, follow these steps:

1. Connect your computer to the SmartServer Console connector using a USB-A to USB Micro-B cable. The SmartServer console is shown in the following figure.

   
   

2. If you are using a Windows computer, you will likely not have issues accessing the SmartServer console port. If you do see a driver issue, then follow these steps to enable the virtual COM port (VCP) driver:
   
   
   1. On your Windows computer, type Device Manager in the Windows search box. The Device Manager window opens.
      
   2. Under Ports (Com & LPT), note the port number that is indicated for the USB Serial Port (e.g., COM 7). If a new COMx device appears, skip to step 3.
      
   3. Under Universal Serial Bus Controllers, double-click the USB Serial Converter at the bottom of the list, which is added to your Device Manager when you connect your computer to the SmartServer using the USB cable.
   4. Click the Advanced tab. On some systems, the Advanced tab may not be displayed. If it is not, skip the next step.
   5. Enable Load VCP, as shown below, and then click OK.
      
      
   6. Once the Load VCP option is set, unplug and then replug the USB cable to initiate device discovery. A COM port to access the SmartServer should appear.
      
      
3. Start your console application with a 115,200bps bit rate, 8 bits per character, no parity, 1 stop bit, and no flow control. For example, follow these steps if you are using the PuTTY application.
   
   1. Open the PuTTY Session page.
      
   2. Select the COM port number for the Serial Line (such as COM7).
   3. Enter 115,200bps for the bit rate.
      1. The serial data frame is formatted as 8-N-1 (8 bits, no parity, 1 stop bit) with no flow control for the serial data frame. 
   4. When using PuTTY, change the backspace character that PuTTY sends to the SmartServer. Other console applications may also require this accommodation.
      1. Change the backspace by clicking the Terminal → Keyboard and change the Backspace key to Control-H, and then click the Apply button.
   5. Click Open to connect to the SmartServer. A console window opens. If no login prompt appears, press the Enter key to display the login prompt.  
      
      
4. Log into the SmartServer. See the Logging into the SmartServer section below.

Connecting to the Console using a LAN Connection

Connect both your computer and the SmartServer to a common LAN or WAN as described above under Creating a Network or USB Interface to the SmartServer.

...

Development network configuration. Use the eth0 port, which is closest to the right side of the SmartServer.

Connecting to the Console using a LAN with PuTTY on Windows

With your computer and the SmartServer connected by to same LAN, follow the steps above to establish an IP address or use the hostname, and verify that you can reach your SmartServer IoT by opening a Windows command window and typing ping -4 [IP address | hostname | hostname.local].

1. Launch PuTTY.
   
   
2. On the Session page, indicate the host name or IP address of the SmartServer.
   
   
3. Select SSH as the Connection type.
   
   
4. Click Open to connect to the SmartServer. A console window opens and displays the login prompt.  
   
   
5. Log into the SmartServer. See the Logging into the SmartServer section below.

Connecting to the Console using a LAN with Terminal on Mac OS 

Enter either the host name or IP address for the SmartServer.

1. Connect your Mac computer and the SmartServer to a router.
   
   
2. Start the Terminal app.
   
   
3. Use the Terminal app to connect using SSH. 
   
   For example:  ssh apollo@192.160.1.22 or ssh apollo@smartserver−t3tzgft   
   
   
4. Log into the SmartServer. See the Logging into the SmartServer section below.

Logging into the SmartServer

You can log into your SmartServer once you have connected a console application using the USB console interface or a LAN or WAN interface as described in the previous sections. To log into the SmartServer, use the SmartServer system apollo username and password. The default SmartServer system password is printed on the label on the bottom of the SmartServer. If you changed the default apollo password (as described in Managing Passwords in the (Optional) Secure Your SmartServer section), use the password you selected.

...