TECHNICAL FAQ PAGE

 

What is the Default Login for my FATBOX

For FATBOX G1

  • URL: 192.168.1.1

  • User Name: admin

  • Password: 12345

For FATBOX G3

  • URL: 192.168.1.1

  • User Name: admin

  • Password: fatbox12345

 

I am unable to connect to my FATBOX

The following steps can be taken to troubleshoot a failure to connect to your FATBOX 

1. Check if the Ethernet cable is connected to the correct Ethernet port (ETH0)

2. If using Windows. Check the following:

  • network and sharing center>adapter setting> ethernet>internet protocol V4

  • Check the “obtain IP address automatically” option.

 

I am unable to connect to my Network

The following steps can be taken to troubleshoot a failure to connect your FATBOX to your required network.

 

1. Check if the antenna is connected to the right port

 

2. Check you have put the right APN details into the network setting (provided by your Telco)

 

I am unable to connect to my Dynamic DNS

The most common issue with a failure to connect to Dynamic DNS is a SIM card without a public IP address.  

1. This can be verified by checking with your Telco.

2. Another way to check is to log in to the FATBOX and go to status>IP address.

If your IP address is within the following ranges, it is a private IP and cannot be used with Dynamic DNS

 

172.16.0.0 to 172.31.255.255

 

or

 

10.0.0.0 to 10.255.255.255

 

How do I read the data from the Starter Kit (temp sensor) and the iotasset.txt file?

To read the data from the starter kit and iotasset.txt/dataq.txt file you will need a program like putty or winscp. Click here to download Putty and here to download Winscp.

1. Connect the FATBOX ETH0 port to your computer and launch the putty/winscp program.

2. Login to the FATBOX using the following details:

     username- root

     password – fatbox12345

3. Go to the /tmp directory and access the dataq.txt file. You would be able to see the value of the temperature sensor under 2AIN1 in the dataq.txt file.

 

Can we check our data without putting it on Azure?

It is possible to read the data from the FATBOX and iotasset.txt/dataq.txt file without putting it on Microsoft Azure. You will need a program like putty or winscp. Click here to download Putty and here to download Winscp.

1. Connect the FATBOX ETH0 port to your computer and launch the putty/winscp program.

2. Login to the FATBOX using the following details:

     username- root

     password – fatbox12345

3. Go to the /tmp directory and access the dataq.txt file. You would be able to see the value of the temperature sensor under 2AIN1 in the dataq.txt file.

 

What is the FATBOX G3 VPN default security set up?

The FATBOX G3 comes integrated with Strongswan IPSEC package. By default it is configured as a IPSEC Site-to-Site client (PSK).

 

Can we configure the FATBOX G3 as an IPSEC server?

With the Strongswan IPSEC package integrated, the FATBOX G3 can be set up as a IPSEC server.

 

We recommend doing so only if you are team is versed with Strongswan CLI configuration. Amplified Engineering does not provide further support on that package.

 

What is the iotasset.txt file?

We use the term 'asset' to refer to the attached Modbus/CANbus/Zigbee slaves.


The FATBOX G3 integrates a ‘device server’ that will poll all attached Modbus RTU and TCP slaves at a configure period. This server reads a configuration file ‘iotasset.txt’ that is a simple text file to query data from such slaves and create JSON strings in the G3 data buffer.

You can refer to the following example to understand how each polled Modbus device register is specified:

#comments below are for explanation, please do not include them in your iotasset.txt file.

MBM_START

 

TYPE,R #R=RTU and T=TCP

ADDR.3 #slave address on Modbus RTU network

MBFC,3 

REGS,8, 1, UINT16HL #data address, #of registers and function code 

Site,Azure IoT Starter Kit

Eqpt, DIGIRAIL.4C.CH1 #digital input 1 

Unit,NA

Key,Switch.CH1

TYPE,R
ADDR,2
MBFC,3
REGS,14,1,SINT16HL
Site,amplified.com.au
Eqpt,DIGIRAIL.2A.CH1
#analog input 1 Temperature Sensor
Unit,Celcius/100
Key,Temperature.CH1

 

TYPE,R #this is example to read VOLTAGE from a Modbus ABB Power Meter

ADDR,4

MBFC,3

REGS,4098,2,UINT16HLhl

Site,Azure IoT Starter Kit

Eqpt, ABB Power Meter

Unit,Volts

Key,Volts.ABB

MBM_STOP

Please refer to our Modbus User Guide for further details.

 

How do I install the iotasset.txt file to my gateway?

The FATBOX G3 has iotasset.txt preconfigured to work with your Modbus temperature sensor (for more information on iotasset.txt configuration see our Modbus user manual). If it is overwritten, you have to copy the iotasset.txt to the FATBOX's /user directory via SCP.

To do that you can download this 'iotasset.txt' file onto your computer.

Alternatively you can create a file called iotasset.txt on TextEdit (for Mac) or NotePad (for Windows). Copy and paste the string below into this file and save it.

MBM_START

TYPE,R

ADDR,1

MBFC,3

REGS,8,1,UINT16HL

Key,4C_IN1

TYPE,R

ADDR,2

MBFC,3

REGS,14,1,UINT16HL

Key,2A_IN1

MBM_STOP

The new device configurations can be updated to your FATBOX gateway securely over the air. The gateway HTTPS connected webconsole must be accessible, either via local network (LAN or WLAN) and over cellular network with assigned public IP address. 

In the <IOT Hardware> console, click on 'UPDATE FIRMWARE' in the Firmware Update section

In the new window, click on 'CHOOSE FILE' and select from your local folder the updated iotasset.txt file. 

Then click 'UPLOAD FIRMWARE FILE'

If the firmware update has been successful, you will see the message below.

"RESULT: The file iotasset.txt was uploaded successfully"

After closing the page, you will need to login again for security purpose.

If the update failed, please check that the connection to the gateway is stable. Or else please contact support@amplified.com.au

You can also physically upload the configurations without network connectivity the following way:

For MAC users

Open a terminal session and run the following commands:

> cd <folder where you saved the iotasset.txt> i.e."cd documents"

> scp iotasset.txt root@192.168.1.1:/user
> enter in the password for your G3
[default is fatbox12345].

You can run the following commands to check that your iotasset.txt is loaded:

> ssh root@192.168.1.1
> enter the password.
> cd /user
> ls
 [check to see if there is a iotasset.txt file in the list]
> cat iotasset.txt [verify the contents of the iotasset.txt file]

Go to the <Management> tab to REBOOT the G3 to save your settings.

For Windows Users

Go to the <Management> tab in the G3 web configuration menu. Enable the SSH option (see blow) and click the UPDATE button to save your settings.

Next run the Winscp and connect using the following File Protocol

 

> SCP Hostname: 192.168.1.1
> User/password: root/fatbox12345
>
Drag the iotasset.txt file over to the /user directory

You can run the following commands to check that your iotasset.txt is loaded:

> ssh root@192.168.1.1
> enter the password.
> cd /user
> ls
 [check to see if there is a iotasset.txt file in the list]
> cat iotasset.txt [verify the contents of the iotasset.txt file]

Go to the <Management> tab to REBOOT the G3 to save your settings.

Repeat step 3D in this guide to check whether your G3 is now collecting data from the sensor. If you still do not see any data or message, please contact our technical support at: support@amplified.com.au

 

How to configure the iotasset.txt file to your device?

The specific configuration guides for each of Modbus, CANbus, Zigbee type device can be found here:

It might be useful to check out our tutorial for setting up a Schneider energy meter to the G3 IOT gateway

For further help please contact our technical support team at support@amplified.com.au

(note: we will help our customers develop examples with their specific device provided with their Modbus register document available.)

 

Connecting IP address (IP camera used as example)

The example here describes how to set up your FATBOX to a fixed or dynamic IP address. The LTE/4G FATBOX G3 is suited for high bandwidth applications such as connecting a remote or mobile IP camera to securely stream video to a server.

Requirements:

 

- Server with Internet connection

- An activated SIM card with either a static IP address or a Public IP

- A dynamic DNS account (only for SIM cards with a Public IP)

SETUP ON THE FATBOX

 

1. Log in to the FATBOX>Quickstart menu

    Enter your APN (You get this information from your SIM operator)

2. Next go to the Port Forwarding menu and key in the settings as follows:

    Source port: Any available port (for example port 85).

    Destination LAN IP: Set to 192.168.1.1

    Destination Port: port 80

    Dynamic DNS (Set this up only if you are using a SIM card with public IP. You can skip this step if you are using a SIM card with a

    static IP): Key in your dynamic DNS details here. The FATBOX requires this so that everytime it is reset or it establishes a new

    connection, the hostname will be dynamically resolved to point to the FATBOX.

    - Select ‘Enable’

    - Hostname: Enter the hostname you set in your dynamic DNS account

    - DDNS service username: Enter your ddns username

    - DDNS service password: Enter your ddns password

SETUP ON IP CAMERA

Refer to your camera manual and look for the following settings.

    IP address: set it to 192.168.1.2

    Default gateway: set it as 192.168.1.1

    Web management port: set it as port 80

ACCESSING YOUR DEVICE REMOTELY FROM SERVER

For static IP: Open up the browser in your server and key in the static IP address followed by port 85 (i.e. http://176.24.23.10:85)

For dynamic IP: Open up your browser in your server and key in the dynamic dns account name followed by port 85 (i.e.

http://youraccount.dyndns.org:85)

 

Attaching third party Zigbee devices

Our Zigbee IoT solution is based on sending/receiving Zigbee Cluster Library (ZCL) messages.

 

As long as the zigbee device conforms to the standard Home Automation (HA) open profile, our Zigbee  BOT program can decode the ZCL messages.

 

If your application uses 3rd part USB zigbee, please email us at support@amplified.com.au

 

Installing and running Mosquitto MQTT

Our detailed write up of how to install and run the Mosquitto MQTT client on the FATBOX G3 can be found in our application note here.

 

What is our default MQTT data format in the data buffer?

The data buffer is 'standard' JSON format for Azure. Here is an example of how it looks like.

[{“DeviceId”:”FATBOXG3”,"AssetId":"Device01","RecOn":"2018-02-10T14:59:00Z","Val":23.5}]

If your application requires a different format, you can send us an enquiry to support@amplified.com.au.

 

 

How to do firmware & management configuration updates OTA?

New manufacturer or user files like new configuration, scripts and even cross compiled executables can be updated to your FATBOX gateway securely over the air.

The gateway HTTPS connected webconsole must be accessible, either via local network (LAN or WLAN) and over cellular network with assigned public IP address. 

In the <Management> console, click on 'UPDATE FIRMWARE' in the Firmware Update section

In the new window, click on 'CHOOSE FILE' and select from your local folder the specific firmware update .zip file. Please check with support@amplified.com.au for any assistance.

Then click 'UPLOAD FIRMWARE FILE'

If the firmware update has been successful, you will see the message below. After closing the page, you will need to login again for security purpose.

If the update failed, please check that the connection to the gateway is stable. Or else please contact support@amplified.com.au

Got another Question? Write to us.

BUY A GATEWAY ROUTER

E-commerce Shop

HARDWARE-AS-A-SERVICE

Leasing Plans

FAQ on leasing

PRODUCT CUSTOMISATIONS

Custom the G3

CONTACT US

Sales Enquiries

Technical Enquiries

Amplified Engineering Pty Ltd  

Suite 4 Enterprise Unit 3,

9 De Laeter Way,

Bentley WA 6102, Australia

ABN 44127163035