Use this article after checking the asset indicators, date range, and gateway LEDs, when data is still not visible on the dashboard.
In this step, you check Current Activity to verify whether data is actually being received by the asset or gateway.
You are doing this to distinguish between data transmission issues and dashboard visibility issues.
Current Activity shows live and recently received data, even if it is not displayed in dashboards or widgets. This allows you to confirm whether data is coming in before reviewing configurations or data sources.
Open current activity
To access the Current Activity view:
Click the small arrow at the top of the screen next to the asset name.
This opens the Edit Asset panel.
Select Current Activity.
For each asset, you can see:
The type of data being received.
The most recent value.
The date and time the data was last received
This makes it easy to confirm whether the asset is actively reveiving information.
.png?sv=2022-11-02&spr=https&st=2026-04-26T11%3A01%3A14Z&se=2026-04-26T11%3A15%3A14Z&sr=c&sp=r&sig=XGAmi8EtqOZBCafeBToxVf5HKetBJTg564iZMz80ih4%3D)
Access required
To view the Current Activity screen, your user account must have the appropriate rights.
You need:
AssetManagement
ViewCurrentActivity
If you do not have these rights, ask the person who manages your Calculus portal to grant them to you.
Checking whether data is coming in
If the data you expect appears in the Current Activity list with a recent timestamp, the asset is working correctly.
In that case, the issue is usually related to how the dashboard is configured, not to data transmission.
Start by verifying the dashboard date range.
If the selected date range does not include the most recent data, it will not be displayed.
If the date range is correct but data still does not appear, the issue is often related to the dashboard widgets. Widgets may be configured to use an incorrect data source or calculation. In that case, reviewing the widget settings and aggregate functions usually resolves the issue.
If the timestamps do not match
If data appears in Current Activity but the last received time is older than expected, check whether the asset is reporting warnings or errors.
You can do this by typing alarm or error in the search bar.
If you see alarms or errors:
Check when they were last updated
Compare the timestamp with other data from the same source
As long as a machine or controller is reporting active errors, it may not send normal measurement data.
Even errors with a value of zero can prevent other data from being generated.
In the following section, you can find some more information about modbus read error codes, depending on the controller you’re using.
If you are working with a DSE857 controller and the timestamps in Current Activity are not updating as expected, verify the physical connections and controller configuration.
The issue is often caused by incorrect wiring, missing communication settings, or a problem in the signal chain between the gateway and the controller.
Check power and connections
Make sure the DSE857 is correctly powered and connected.
Verify:
The DSE857 is powered (8–35 VDC)
The USB cable is connected to both the DSE857 and the DSE panel
No USB extension cables are used
The cable is not damaged
Next, check the RS-485 connection between the Calculus gateway and the DSE857.
Use the correct wiring:
A(+) on the gateway → A(+) on the DSE857
B(-) on the gateway → B(-) on the DSE857
Connecting GND is recommended
Refer to the terminal layout below:
.png?sv=2022-11-02&spr=https&st=2026-04-26T11%3A01%3A14Z&se=2026-04-26T11%3A15%3A14Z&sr=c&sp=r&sig=XGAmi8EtqOZBCafeBToxVf5HKetBJTg564iZMz80ih4%3D)
Important
Use a twisted pair cable
Maximum impedance: 120 Ω
Do not swap A and B (this is the most common issue)
Check DSE configuration
Connect to the DSE857 using the DSE Configuration Suite.
Verify the following settings:
Modbus Support → Enabled
Enable RS-485 communication (Modbus RTU)
Baud rate matches the gateway configuration
Slave ID is correctly configured
.png?sv=2022-11-02&spr=https&st=2026-04-26T11%3A01%3A14Z&se=2026-04-26T11%3A15%3A14Z&sr=c&sp=r&sig=XGAmi8EtqOZBCafeBToxVf5HKetBJTg564iZMz80ih4%3D)
Incorrect communication settings will prevent data from being transmitted to the gateway.
Check controller status
Check the LED indicators on the DSE857:
Green blinking → CAN communication is active
Red → No CAN communication
If no communication is detected, verify the controller setup and connections.
Provide additional information
If the issue persists, include the following when contacting support:
Photos of the wiring and connections
A screenshot of the DSE Configuration Suite settings
This helps identify configuration or wiring issues more quickly.
If you are working with a DSE8XXX controller and the timestamps in Current Activity are not updating as expected, verify how the controller is connected to the gateway.
The controller can be connected via:
Modbus RS-485
Ethernet (Modbus TCP/IP)
The checks below help you identify where the issue occurs.
Modbus RS-485
Check the physical RS-485 connection between the gateway and the controller.
Verify:
A and B connections are correct (these are often swapped).
A 120 Ω termination resistor is installed.
If the wiring is correct, check the communication settings.
Using the DSE Configuration Suite, provide:
Baud rate
Slave ID
Incorrect wiring or mismatched communication settings will prevent data from being received.
Ethernet (Modbus TCP/IP)
Check the Ethernet connection between the gateway and the controller.
Verify:
The green and orange LED indicators on the Ethernet port of the Calculus gateway are active.
If the LEDs are inactive, try replacing the Ethernet cable.
Next, verify the network configuration.
Compare the Ethernet settings with the configuration guide.
Make sure the network configuration is correct.
Provide:
IP address
Slave ID
Incorrect network settings will prevent communication between the controller and the gateway.
Provide additional information
If the issue persists, include the following when contacting support:
Photos of the wiring and connections.
A screenshot of the DSE Configuration Suite settings.
This helps identify configuration or wiring issues more quickly.
Connection-related issues
If no relevant data appears in the Current Activity view, the asset may not be receiving data at all.
In this case:
Check that all physical connections to the gateway are properly connected.
Ensure the machine or controller is powered on and operational.
If data still does not appear, continue troubleshooting by reviewing the asset’s data source configuration.
Summary
The Current Activity view shows whether data is actively being received by the asset or gateway.
This helps distinguish between:
Data transmission issues
Dashboard visibility problems
Widget or configuration issues
Checking Current Activity confirms whether data is arriving before further troubleshooting steps are taken.
If relevant data appears in Current Activity, make sure the correct date range is selected on the dashboard.
If no relevant data appears in Current Activity, continue troubleshooting by checking the asset’s data source configuration.