KB90434
Published: August 18, 2022
Revision: 2.0
Data from groov EPIC/RIO reported as stale; groov Manage reports Data Service is running
Applies To:
Firmware for the following groov EPICs:
- GRV-EPIC-PR1
- GRV-EPIC-PR2
Firmware for the following
groov RIOs:
- GRV-R7-MM1001-10
- GRV-R7-MM2001-10
- GRV-R7-I1VAPM-3
Versions Affected:
For groov EPICs: 3.4.0 to 3.4.3
For groov RIOs: 3.4.0
Resolved In Version:
For groov EPICs: 3.4.4
For groov RIOs: 3.4.1
Symptoms:
If you enable Data Services to publish MQTT with Sparkplug payloads, it's possible that an unreliable network connection may create a state where an MQTT client indicates that data from your groov EPIC or groov RIO is stale even though groov Manage indicates that Data Service is running.
If you’re experiencing stale data and groov Manage indicates the Data Service is running, then check the most recent entries in the log. Entries similar to the following may indicate that the stale data is caused by this issue:
Aug 06, 2022 12:50:52 PM org.eclipse.paho.client.mqttv3.internal.ClientState checkForActivity
SEVERE: <MQTT Client ID>: Timed out as no activity, keepAlive=10,000,000,000 lastOutboundActivity=299,598,952,477,582 lastInboundActivity=299,575,831,773,718 time=299,599,938,656,286 lastPing=299,589,939,165,789
WARN|2022-08-06 12:50:52,540|MqttSparkplug.java|1023|Broker connection was lost Timed out waiting for a response from the server.
INFO|2022-08-06 12:50:52,544|MqttSparkplug.java|1637|Next MQTT broker requested.
This issue may also be present if you are publishing string payloads or you are using OPC UA.
Workaround:
Do one of the following:
- Manually restart Data Service:
- From the groov Manage Home page, click Data Service.
- In the Data Service Runtime field, click Disable.
- Wait for the Data Service field to report Disabled.
- Click Enable.
- Cycle power on your groov EPIC/RIO.
Resolution:
Opto 22 has resolved this issue.
Questions?
Contact: Opto 22 Product Support.
Phone: 800-835-6786 or 951-695-3080
Email: support@opto22.com
DISCLAIMER
This Opto 22 Knowledge Base ('OptoKB') article is intended to provide general technical information on a particular subject or subjects and is not an exhaustive treatment of such subjects. Accordingly, the information in this OptoKB article is not intended to constitute application, design, software, or other professional engineering advice or services. Opto 22 may modify the OptoKB articles at any time. Before making any decision or taking any action which might affect your equipment, you should consult a qualified professional.
OPTO 22 DOES NOT WARRANT THE COMPLETENESS, TIMELINESS, OR ACCURACY OF THE DATA CONTAINED IN THIS OPTOKB ARTICLE AND MAY MAKE CHANGES THERETO AT ANY TIME AT ITS SOLE DISCRETION WITHOUT NOTICE. FURTHER, ALL INFORMATION CONVEYED HEREBY IS PROVIDED TO USERS 'AS IS.' IN NO EVENT SHALL OPTO 22 BE LIABLE FOR ANY DAMAGES OF ANY KIND INCLUDING DIRECT, INDIRECT INCIDENTAL, CONSEQUENTIAL, LOSS PROFIT, OR DAMAGE, EVEN IF OPTO 22 HAS BEEN ADVISED ON THE POSSIBILITY OF SUCH DAMAGES.
OPTO 22 DISCLAIMS ALL WARRANTIES WHETHER EXPRESSED OR IMPLIED WITH RESPECT TO THE INFORMATION (INCLUDING HARDWARE, SOFTWARE, AND/OR FIRMWARE) PROVIDED HEREBY, INCLUDING THE IMPLIED WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE, MERCHANTIBILITY, AND NON-INFRINGEMENT. Note that certain jurisdictions do not sanction the exclusion of implied warranties: thus, this disclaimer may not apply to you.
Copyright © 2024 Opto 22. All rights reserved.