Published: December 5, 2008
Local I/O Unit not enabled when using SNAP-UP1-M64 as Generic OptoMMP Device
Problem was discovered in version: R8.2a
Problem is fixed in version: R8.3a
Resolved In Version:
Problem is fixed in version: R8.3a
Error -81, Error writing to the memory map, may be seen among other errors in the controller error queue when attempting to enable a SNAP-UP1-M64 I/O Unit type. The SNAP-UP1-M64 I/O unit is configured with the same IP address or loopback address (127.0.0.1) as the SNAP-PAC-S1 or SNAP-PAC-S2 that is running the strategy. Since the I/O Unit cannot be enabled, any attempts to write to the local memory map fail.
Prior to introducing the Generic OptoMMP Device I/O Unit type, the SNAP-UP1-M64 I/O Unit type was recommended as a means to communicate with the local memory map on an SNAP-PAC-S1 or SNAP-PAC-S2 controller.
We recommend changing the I/O unit type for all SNAP-UP1-M64 I/O units used just to communicate to the memory map and that have no I/O points configured on them, to Generic OptoMMP Device. If your version of PAC Control does not allow this type change, you can change it using the following procedure:
- Note the IP address of your existing SNAP-UP1-M64, then change it to something that is not currently in use or likely to ever be used. For example, you might change it to: 184.108.40.206.
- Create a new I/O unit of type Generic OptoMMP Device with a similar name to the SNAP‑UP1‑M64 I/O unit. For example, if the SNAP‑UP1‑M64 is named Snap_IO, name the Generic OptoMMP Device Snap_IO_new, and give it the IP address you just changed in the existing SNAP-UP1-M64.
- Choose Edit→Replace from PAC Control. Find Snap_IO and replace with Snap_IO_new.
- Save the strategy.
- Delete the Snap_IO I/O unit.
- Rename Snap_IO_new to Snap_IO. The PAC-S controller's I/O memory map can now be accessed with the correct I/O unit type.
Opto 22 has resolved this issue.
Contact: Opto 22 Product Support.
Phone: 800-835-6786 or 951-695-3080
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 © 2023 Opto 22. All rights reserved.