MYNAH - MiMiC Simulation

A. The serial number has the following format: pn Site ID v mimic version (e.g. pn1234 v 2.8)
You can find it under Client Help ->About. If you are installing it for the first time, you can find it on the installation CD.

________________________________________________________________________

Q . What is the difference in using the DeltaV Simulate OPC driver vs. the DeltaV Railbus (VIM) driver?

A. The DeltaV Simulate OPC interface requires no additional hardware, while the DeltaV Railbus (VIM) interface requires VIMs, controllers, and a switch.
With the DV Railbus VIM interface, modules are assigned to the controller, and MiMiC simulates both the I/O and the modules assigned to the controller. Whereas, DeltaV OPC-Simulate interface modules are assigned to the Pro Plus or the App. Station, and only modules get simulated. You can find out more on this subject in MiMiC Users’ Forum.
________________________________________________________________________

Q. I am trying to initiate communications with MiMiC VIM, but it’s not in the list of available VIMs. How can I get it to appear on the list?

A. You have probably commissioned it after starting the MiMiC Server and Client.
To get it to show up in the port drop-down list, you need to shut down MiMiC applications and restart them again. The VIM must be commissioned before you start the MiMiC applications.

________________________________________________________________________

Q. How many datasets can I initiate communications on?

A. The number of datasets in the licensing terms is equivalent to number ports. You can check this information by clicking on I to initiate communications and look in the Dataset drop-down list. The number of datasets you see in the drop-down is the number you can initiate communications with.

________________________________________________________________________

Q. Why I am getting this error on MiMiC startup: “Unable to get server version -Error 5”?

A. On Windows XP machines, there is an SP 2 security binding that doesn’t let MiMiC applications run freely. In order to disable the security binding, you have to run a patch file to disable the RPC security setting. You can find this file under c:\mimic\Windows XP SP2. If you cannot find it, please contact MYNAH Technical Support to get this patch.

________________________________________________________________________

Q. Why I am getting this error “Network doesn’t appear to be serving this directory”?

A. This is a known error that we have seen when MiMiC doesn’t see the network.
First, make sure that your network card is connected to some network, because on start-up the MiMiC applications are looking for the network connection.
If it’s not, please connect it and reboot the machine.

If you are using a VIM, connect it to the VIM Network and use the static IP address.
If you are using another MiMiC driver, you can assign it to the LAN or any other network.
If your machine was connected to the network and you got this error, then browse to your MiMiC folder and execute the setup_ck.exe by double-clicking on it. Then start the MiMiC applications.

If the problem persists, contact MYNAH Technical Support.

________________________________________________________________________

Q. When I load my exported .fhx file into the DeltaV FHX Utility, I get a “no controllers found” error. Why?

A. It’s either because your .fhx file was not exported from the top of DeltaV tree, or no modules have been assigned to the controller, Pro Plus, or App. Station.
You should follow this procedure when generating the simulation files:

Assign all of the modules to the appropriate node (controller, app station or pro +)
Export the .fhx file from the top of the DeltaV tree.
Run the FHX Utility on new .fhx file.

Should you encounter this problem again, contact MYNAH Technical Support.

________________________________________________________________________

Q. Why is my DeltaV Utility stuck at same percentage while generating simulation files?

A. The FHX Utility has probably encountered an unknown character and cannot continue. You need to contact MYNAH Technical Support to get a newer utility that does handle those unknown characters.

________________________________________________________________________

A. You must keep all simulation files on the Server machine and map a shared drive from the Server to itself, and from the Client to the Server. For example, you can map the shared S:\ drive from Server to c:\MiMiC on Server machine, and then map the S:\ on the Client machine to Server’s C:\MiMiC or to the directory where your simulation files reside. The next step is to reload all simulation files from the new shared drive.

________________________________________________________________________

Q. After initiating communications with the VIM, I get an error that says “Fieldbus device does not exist”, then a bunch of hex numbers and “Contact MYNAH Technologies”

A. This is a fieldbus device that’s not currently supported with the user’s current version of MiMiC. Contact MYNAH Technical Support for the device definition file and masterlist entry.

________________________________________________________________________

Q. My thermocouple devices are not showing up correctly. They are toggling constantly between good and bad status. What is causing this?

A. The thermocouple cards are supported only by later firmware versions. If your VIM has firmware older then 2.2.1, then you need to call MYNAH Technical Support and ask for the firmware upgrade.

________________________________________________________________________

Q. When I initiate communications with MiMiC using the VIM, I get “Input /Output Comm Thread Create failure for VIM #”

A. This happens because of network issues between the MiMiC machine and the VIM. You have to make sure that the IP address of the NIC on your MiMiC machine is set up with the static IP address and that the subnet mask matches the IP address of the VIM’s placeholder. You should also verify the properties of the Active Network in the MiMiC Plug n’ Play Server, because it must match the IP address of the NIC. If the problem persists, contact our MYNAH Technical Support.

________________________________________________________________________

Q. I am using the DeltaV Simulate OPC driver, and I can get only one way communications between MiMiC and DeltaV. I can send data from MiMiC to DeltaV, but I can’t read any values from DeltaV.

A. You must configure the DCOM settings and User Security settings on your DeltaV station and MiMiC PC. In the current MiMiC manual, refer to section “MiMiC Installation for DeltaV Simulate/Simulate Pro”. If your DeltaV is on the separate machine, you should map a drive between MiMiC and DeltaV machines and make sure that you have installed the OPC remote on the MiMiC machine.

________________________________________________________________________

Q. When I attempt to initiate communications with DeltaV Railbus (VIM) driver, I get the following error: “Invalid Function Block ID 719”. How do I get rid of this?

A. You will get this error if you are running on a MiMiC build older than 2.8 build 41 or if your VIM’s firmware is too old to support this type of block. (VIM’s firmware must be at 2.2.1 or later). Contact MYNAH Technical Support to get the latest MiMiC build and the VIM firmware.

________________________________________________________________________

Q. Why am I getting “binding error” when I try to commission my MiMiC VIM?

A. You will get this error if the Network settings and Active Network properties are inappropriate. The NIC that is connected to the VIM must have the static IP address. The Active Network properties in the MiMiC Plug n’ Play Server must be set to the same IP address. The subnet mask of your NIC must match the subnet mask of the VIM placeholder you have added in the MiMiC Plug n’ Play Server.

________________________________________________________________________

Q. Can I use the DeltaV Railbus (VIM) driver to emulate Provox I/O?

A. No, if you are using MiMiC, you must use Provox (EIC) or Provox (IDI) driver to emulate the Provox I/O, because the VIM can only simulate DeltaV I/O.
You can contact our Technical Support for more details on this solution.

________________________________________________________________________

Q. I have generated the simulation files using the FHX Utility, but when I load the tiebacks, they are empty.

A. For the DC and loops to show up in the tiebacks file, make sure you have exported the fhx from the top of DeltaV tree. You should follow this procedure when generating the simulation files:

Assign all of the modules to the appropriate node (controller, app station or pro +)
Download the Pro Plus or App. Station
Export the FHX file from the top of the DeltaV tree.
Run the FHX Utility on a new .fhx file.

Should you encounter this problem again, contact MYNAH Technical Support.