Atop SE59 Series User manual

Atop Technologies, Inc
SE59XX Series Industrial Device Server Series
Getting Started Guide

Connecting SE59XX
Connect SE59XX to network or directly to pc.
Device comes with default static ip 10.0.50.100 and subnet mask 255.255.0.0.
For the first time accessing set your pc lan configuration in the same IP range.
Enter the web interface using ip 10.0.50.100 and use the default username and password provided by ATOP.

Configuring Network Settings
Enter the network settings by clicking on the Network Settings from the web GUI.
Enter any desired IP Address, Subnet mask and gateway required based on your preference.
Click on the Save & Apply button.
Dynamic IP assigning scheme can be used for getting the IP’s provided by the DHCP server in the network.
For this click on the DHCP Enable and do Save & Apply.
If required reboot the device using Reboot option from the web GUI.

Configuring AWS IoT Core
Login to the aws console using https://aws.amazon.com.
Select IoT core from the list of aws services.
Firstly a policy has to be created.
For this go to Secure menu and click on the policies.
Then create a policy by clicking on the create button.

Give any name to the policy and specify action as iot:*, so that it permits all iot actions.
If you want to allow only specific set of action, it can be configured here.
The policy created can’t be modified later.
Resource ARN can be marked as * and effect can be marked as Allow.

Secondly a thing object has to be created in here.
In order to create a thing, go to Manage and navigate to Things.
Then click on the Create things.

Select Create single thing.
Specify thing name.

Select Auto-generate a new certificate.

Download the device certificate, Public and Private key file.
If required activate device certificate.
Also download any one of the root ca certificates.
Without downloading all the required certificate, you won’t be able to click on Done.
The device data end point can be found under settings.

Cross-compiling AWS Application
Download the tool-chain from the link shown below.
“www.google.com”
Cross-compile custom aws application using the tool chain.
There are two ways of providing aws parameters while doing cross-compilation.
▪Defining aws parameters directly in the program
The aws parameters can be directly defined in the programs statically.
But keep in mind that all the certificates and key file location should be “/etc/ssl/certs/***
Eg: #define AWS_MQTT_PORT 8883
#define ROOT_CA_CERT_PATH “/etc/ssl/certs/*.crt”
▪Using cmake variables.
Another method of providing aws parameters are with the help of cmake variables.
Some of the commonly used variables are AWS_IOT_ENDPOINT, ROOT_CA_CERT_PATH,
CLIENT_CERT_PATH, DCLIENT_PRIVATE_KEY_PATH, AWS_MQTT_PORT,
THING_NAME etc.
The cmake variables can be used as follows.
Eg: cmake -S. -Bbuild -DAWS_MQTT_PORT=8883 -
DROOT_CA_CERT_PATH=/etc/ssl/certs/RootCA.pem
Once the compiled application is ready we need to upload it to the device along with the certificates required.
Use the device data end point from IoT core settings.

Connecting to AWS IoT Cloud
To connect to AWS firstly need to upload certificates and applications into the device.
In order to do that go to IOT and navigate to AWS.
Select the Root CA file, browse and upload the file.
Similarly upload Certificate and Private key file downloaded from AWS console.
Finally upload the cross-compiled AWS application into the device.

Testing AWS Connectivity
Click on Start button to run your aws application from the device web gui.
Go to AWS IoT core and navigate to Test and select MQTT Test client.
Enter the topic name specified in your program in the topic filter and click on the Subscribe button.
By default aws demo’s topic name would be thing/example/topic.
For the thing name SE5901 topic is SE5901/example/topic.
And you can see the messages published in the console.
Use stop button in the device web gui for stopping the aws application.

Thank You
Connect to ATOP FAE for any further assistance