KB89167
Published: December 9, 2020
Revision: 3.0
Invalid MMP Addresses on Generic MMP Page May Cause I/O Server Disconnect
Applies To:
Firmware for:
- GRV-EPIC-PR1
- GRV-R7-MM1001-10
Versions Affected:
GRV-EPIC-PR1: All versions prior to 3.0.0GRV-R7-MM1001-10: All versions prior to 3.0.0
Resolved In Version:
GRV-EPIC-PR1: 3.0.0GRV-R7-MM1001-10: 3.0.0
Symptoms:
If you have the Generic MMP page reading invalid MMP addresses while any of the following are happening, groov Manage disconnects from the I/O server:
- Other browser tabs are showing groov Manage I/O pages (for example, the Modules page).
- Running Node-RED flows that use groov I/O nodes.
Here are a couple of examples of how this might happen:
Example 1 - groov EPIC (GRV-EPIC-PR1)
- In a browser tab, login into your GRV-EPIC-PR1 with an administrator account.
- Click I/O > Tools > Generic MMP.
- Enter 0x0001234 for the address, 32-bit Integer for the data type, and 200 for the length. All the values will change to "N/A" (or "Invalid Address" in 2.1 and later).
- Open a second browser tab and go to an I/O page, like a Module page that shows the list of channels.
- After a few seconds, you will see an "I/O Offline" warning on the top of the screen.
Example 2 - groov RIO (GRV-R7-MM1001-10)
- Open two browser tabs, and in both tabs, login into the same GRV-R7-MM1001-10 with an administrator account.
- In one tab, set up 1 or more Node-RED groov I/O input nodes scanning an analog input channel.
- In the other browser tab, go to the groov Manage Generic MMP page (from the Home page, click I/O Tools > Generic MMP).
- Enter 0x0F210000 for the address and select Float for the data type.
- Go back to the Node-RED tab and notice that the debug panel is filling with the following error: "Bad API key or server error. HTTP response error : 500"
Workaround:
Double-check MMP addresses before using them.
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.