If your dashboard still isn’t showing any data after verifying the date range, the gateway LEDs, and the asset indicators, the next step is to check whether the asset is actually receiving any data at all.
In some cases, everything looks fine on the surface, but there is simply no data coming in yet. This check helps confirm whether data is being received, even if it isn’t visible on the dashboard.
To do this, click the small arrow at the top of the screen, next to the asset name. This opens the asset settings.
Access required
To view the current activity of an asset, your user account needs rights to do so. Specifically, you need AssetManagement and ViewCurrentActivity.
If you don’t have these rights, ask the person who manages your Calculus portal to grant them to you.
After opening the Edit Asset panel, select Current Activity.
This screen shows all data that is currently being received for the asset. For each item, you’ll see:
The type of data being read
The most recent value
The date and time it was last received
This helps you quickly confirm whether the asset is actively sending information.
.png?sv=2022-11-02&spr=https&st=2026-01-14T19%3A31%3A05Z&se=2026-01-14T19%3A43%3A05Z&sr=c&sp=r&sig=afPId%2FfCMj%2Bq8zMUqWMYYDJfoVBzxId4b1C4ScyoqFM%3D)
Checking whether data is coming in
If the data you’re expecting appears in the Current Activity list with a recent date, the asset is working correctly. In that case, the issue is usually related to how the dashboard is set up.
Start by double-checking the dashboard date range. If the date range doesn’t include the most recent data, it won’t be shown. You can find instructions for checking this in the following article.
If the date range is correct but the data still doesn’t appear, the issue is often related to the dashboard widgets themselves. Widgets may be configured to use the wrong data source or an incorrect calculation. In that case, reviewing the widget settings and aggregate functions usually resolves the issue.
If the dates don’t match
If the data appears in Current Activity but the last date is older than expected, look for warnings or error messages.
You can quickly do this by typing alarm or error in the search bar. If you see alarms or errors, check the date they were last updated.
If an alarm or error has a recent timestamp, or matches the timing of other measurements from the same source, it likely needs to be resolved first. Even if an error shows a value of zero, it can still prevent other data from being generated.
As long as a machine or controller is reporting alarms or errors, it may not send normal measurement data.
Connection-related issues
If you see errors related to modbus reading, this often points to a physical connection issue. In that case, check that all cables connected to the gateway are securely in place and working properly.
If your setup uses a controller, also make sure it is configured correctly, by checking the slave ID and the baudrate. Incorrect settings can prevent data from being read, even if everything appears powered on.