Thank you for choosing to use the Datacake Industrial IoT Gateway. In this guide, we will now walk you through the necessary steps to get your Datacake IoT Gateway up and running.
The LTE version of the IoT Gateway has changed pinning compared to the older 2G and 3G variants, including:
4 outputs instead of just 2
No Power Supply needed for Outputs (they feed forward the input voltage)
No RS485 any longer
Please note the new Pinout.
To use the IoT Gateway, you need to register on the Datacake platform. To do so, please open the following link in your browser.
You should now see the following page in your browser:
By confirming your entries, an account will be created and at the same time you will automatically log in to the Datacake platform. You should now see the following view in your browser:
This is the view of your currently still empty workspaces, in that we will now register and activate Datacake D Zero in the next steps.
If you filled in the "Company Name" field during registration, your workspace will automatically carry the name of your company.
If you left the field blank, the platform will use the combination of "First Name + Last Name" as the name of your workspace. You can see the name of your workspace in the top right corner of the platform.
The following options are available to you at any time:
Edit workspace name
Upload your own logo
Now we will register the IoT Gateway into your Workspace.
If you are not sure if this is the final workspace, don't worry. You can move the gateway to another workspace at a later time.
Navigate to your fleet view using the left sidebar and then please click on the "Add Device" button.
You should now see the following dialog:
Depending on when you purchased the IoT Gateway, please select the appropriate version here. For gateways purchased after 2021, please always select the LTE version.
The IoT gateway has the internal name D Zero at Datacake. Since this does not describe the function, we have decided to call the module IoT Gateway. So if you come across the term or name "D Zero" in the rest of the text or in the portal, it refers to the IoT Gateway.
On the back of your IoT Gateway there is a sticker on which the serial number of the module has been printed. This can be found under the designation "Device ID".
Now enter this number accordingly in the form for adding the gateway and assign an individual name at the same time.
The name can also be changed as often as desired at a later time.
If you create further D Zero modules in the future and these should already be configured, you can transfer the configuration of an existing D Zero here.
Finally, confirm the process by pressing one of the two buttons. Since we now want to configure your Datacake D Zero, please press the "Add and configure device" button.
After creating and switching to the configuration, the first thing you see is a panel that defines the general settings of the device to the portal. The following possibilities are now briefly mentioned here.
This field allows you to change the name of your D Zero at any time. The field should carry the name you assigned during registration.
Optionally, you can enter a location description here, such as "Operating module, shaft 4" or "Switch cabinet left" and an address, such as "Von-Siemens-Str. 20".
Use tags for later use in global dashboards to create filters that, given a large number of modules, display readings based on tags.
By means of metadata, you can assign your own parameters or properties, such as "customer number" but also limit values for measured values. Again, we leave the metadata untouched for now, as they are not relevant at this point.
Here you can assign a PIN code, which can then be used by your employees, customers or other persons to gain access to the device. Again, we will skip this step for initial installation. Just leave the field for entering the pin code blank.
For more information on this topic, click here:
If you have made changes to the configuration, then you need to confirm them by clicking the "Save" button.
For a quick commissioning we recommend that you use one or more sensors of the following type for commissioning:
4-20mA transmitter (for e.g. pressure)
PT100 temperature sensor
To connect a 4-20mA transmitter to the D Zero, you can use one of the 6x Analog Inputs. Here you can choose between
Sense / GND
The advantage of the D Zero is that your transmitters can be powered directly from the module. This saves the cabling effort, especially for two-wire transmitters.
Connect two-wire 4-20mA transmitters (with two connection cables) according to the following connection diagram:
Transmitters with three wires (separate wire for ground) are connected according to the following figure. For this type you usually need an external terminal strip.
For PT100 type temperature sensors, the Datacake D Zero provides a connection for up to three PT100 sensors, with the following features Type:
You can connect these sensors to the Datacake D Zero according to the following wiring diagram:
For the acquisition of switching signals or status messages, the Datacake D Zero offers the connection of up to 8 digital inputs. Connect them according to the following wiring diagram:
Four digital outputs are available on the IoT gateway for the control of relays or other consumers.
These outputs can be controlled directly from the portal via a dashboard or triggered automatically by a rule that is defined on the portal in our rule engine. Read More:
The advantage of the outputs is that they directly switch the input voltage of the module. So you do not need to provide another supply voltage for the outputs.
On the IoT Gateway, there are no mechanical relays but so called solid-state relays. Therefore it is not possible to switch large loads directly with the gateway.
If you have connected your desired sensors to the Datacake D Zero, then you can now go ahead and establish the power supply for the module.
For info. The Datacake D Zero requires a power supply with the following characteristics:
+24V DC (12V - 27V DC)
Min. 10 watts (We recommend +15 watts)
Connect your Datacake D Zero to a power supply as follows:
+24V DC: P01
Ground (GND): P02
Once you have connected the Datacake D Zero to a power supply and turned it on, the module will begin the process of connecting to the Datacake platform via the cellular network.
This process can take a few minutes depending on the signal strength and density of the cell towers. However, once the connection is established, latency is typically in the range of fewer than 2 seconds.
When you start up the module, both LEDs on the front panel should light up. One of the two LEDs signals the correct power supply. The second LED is an RGB LED, which, depending on the operating status, indicates this with a corresponding color and light pattern.
Color pattern: The RGB LED flashes green.
Light pattern: Moderate flashing.
Color pattern: The RGB LED flashes light blue/cyan.
Light pattern: Fast flashing.
Color pattern: Light blue / Cyan-colored.
Light pattern: Slow pulsing (also called "breathing" - brightness alternately decreases and then increases again).
Color pattern: Dark, intense blue.
Light pattern: Moderate flashing.
Online/Offline status in the device listing.
You can recognize a successful connection to the Datacake platform by the fact that there is a "green dot" next to the device in the fleet listing (Fleet / All Devices) (see following screenshot). This indicates that data has been transferred from the device to the cloud within the last hour.
Click on your Datacake D Zero in the fleet listing, the device view opens. There you will find the metadata in the upper section and below also the information when the module was last updated.
If the module logs on to the platform or measured values are transmitted, this information is also updated. So you should see here approximately a current date.
Your Datacake D Zero is delivered with a basic configuration. This ensures that connected sensors and signals are detected and measured values are transmitted to the cloud. This configuration is defined as follows:
Five-minute interval: 1x transmission per 5 minutes
Immediate transmission in the event of a change of +/- 0.5mA
Immediate transmission on change of signal (High / Low)
Immediate transmission on change of +/- 0.5°C
Five-minute interval: 1x transmission per 5 mins
For each input (and also output - more about this later) there are different methods of polling and transmitting the measured values. We call this concept "Watcher". Each input channel has:
Interval watcher: query and transmission after a freely definable time has elapsed.
Threshold watcher: query and transmission on relative change of a measured value.
Filter: Possibilities of smoothing a fluctuating signal.
We call the settings of the query "Channel configuration". To open this, navigate to "Configuration" using the tab bar in the Device view:
Now scroll down a little until you reach the "Fields" section:
In the case of the IoT Gateway, this listing starts with the analog inputs. In addition, a column reflects the physical port - the equivalent on the hardware.
To edit the configuration for the respective input channel, open the drop-down menu at the right end of the row and select the "Channel configuration" menu item here:
This will bring up a modal that lets you configure how often this channel is being read out and some other settings like thresholds, etc. We will cover these now in the following steps:
Each element of the channel configuration has a certain number of "watchers" as mentioned above. The dialog that opens after clicking on the sidebar now shows the configuration options for these watchers and always starts with the interval.
Here you define a time query. If the time specified here has elapsed, the measured value of the sensor connected to the channel is transmitted to the platform.
You can enter any time here, but we recommend that you keep the time greater than or equal to 1 minute, otherwise the data volume can be consumed prematurely.
With the help of the option of a hysteresis, you can determine a minimum change of the measured value. If the measured value has not changed by +/- the value of the hysteresis after the time has elapsed, no transmission takes place.
Use the function of the hysteresis to let transmissions take place only if a meaningful measured value change is present.
The definition of hysteresis is not mandatory.
If you activate this option of the transmission, then a measured value is always transmitted if a change of the measured value by +/- of the value defined here has taken place.
This type of transmission is independent of a time. Therefore, make sure that the change that is set here is large enough so that values are not transmitted every second, which could lead to a hasty consumption of the data volume.
As you can see in the screenshots, the value for hysteresis and threshold has been set to base mA. It is basically possible here that you specify these values in another unit.
However, for this, a conversion into a respective unit must have taken place first. You can achieve this by creating so-called mapping fields. The next section of this document will show you how to do this.
Now that we have the query set, we can worry about setting the value range for a 4-20mA sensor.
The Datacake D Zero transmits readings from the analog 4-20mA inputs in milliamps. Using the web interface of the Datacake platform, you can adjust these values to the range of values of the connected sensors.
To do this, you must enter the value range specified in the sensor's data sheet into a corresponding mask. A subfield has been created for each input field in the delivery state. These are so-called mapping fields, which can adapt the output value range (in milliamperes) to an own value range.
The following screenshot shows the output field (marked red) and its mapping field (marked blue).
To now enter the value range of the connected 4-20mA sensor, navigate with the mouse over the dropdown "More", which you will find at the right end of the line of the mapping field (blue).
To edit the mapping, click on the "Edit mapping" option. The following dialog opens:
Set the source for the conversion here. We are editing a field here that has already been created in the delivery state. Therefore the output value range is already predefined to the 4-20mA values. If you would specify your own conversion, you must define the output value range yourself.
Enter the value range of the connected 4-20mA sensor as the target value range. As an example: Connected pressure sensor with value range 0 - 50 Bar - then corresponds to:
4mA = 0 Bar
20mA = 50 Bar
With the help of the "Use Boundaries" option, you set a lock for the conversion. If the option is active, this means that the output value range is always between 0 - 50 Bar and cannot leave this range, even if, for example, a value of 3mA results in a negative value in the conversion.
As you can see in the screenshot, there are other types of conversion (look-up table, factor). Using these options, you can define scaling based on a factor or status messages. For this purpose, the following screenshot:
On this screenshot you can see how we added another mapping field to generate a status text based on the incoming milliamp values from the sensor. This can be used to generate custom status messages.
You can add more mapping fields to each sensor.
You find more information about that here:
In the screenshots above you can see that we have defined the unit "Bar" for the mapping.
You can assign a unit yourself by opening the general settings for the field in the dropdown menu of the mapping field:
This will show you the following modal:
Here you can determine the unit in which the values of the mapping field are displayed. The entries take place as plain text information. You can define any designation or unit here.
The conversion of units takes place via the creation of further mapping fields. If, for example, you want to convert the unit "Bar" to "Pascal", an additional mapping field is added to the analog input by converting the value range of the sensor (mA) to the target unit (Pascal).
If you want to have further conversions or status messages calculated on the basis of the measured values of the connected sensors, you can create additional mapping fields at any time. You can find out how to do this and what other mapping types are available here: