|
Message
|
Topic
|
Replies
|
|
If you look on pages 15 and 16 of the latest version of the MVI46-101S User's Manual, you will see the module can store hold the 10 most recent Events in it's communication queue. Any point configured as a Time-Stamped point will create an Event any time the value of that point changes. The time of that Event will be held in the designed...
|
Time stamping -MVI-101S - sibym2000 @ 28/08/2006 9:06 pm
Reply: RE:Time stamping -MVI-101S - jsanders @ 19/09/2006 5:18 pm
|
1
|
|
If you are using version 5.xx of RSLogix500, it has a known bug that prevents you from changing the M1 and M0 file sizes. The solution is to upgrade to a newer version of RSLogix500. A work-around is available from our Knowledge Base at the following link:
http://www.oldi.com/primattach/PATTLNK_8272003_2243-Version%205_5%20Workaround.doc
|
MVI46-GSC ERROR CONFIGURATION ON SLOT 6 - delt @ 15/08/2006 7:09 am
Reply: RE:MVI46-GSC ERROR CONFIGURATION ON SLOT 6 - jsanders @ 15/08/2006 3:04 pm
|
1
|
|
If you are using version 5.xx of RSLogix500, it has a known bug that prevents you from changing the M1 and M0 file sizes. The solution is to upgrade to a newer version of RSLogix500. A work-around is available from our Knowledge Base at the following link:
http://www.oldi.com/primattach/PATTLNK_8272003_2243-Version%205_5%20Workaround.doc
|
MVI46-GSC help!! - delt @ 14/08/2006 7:02 pm
Reply: RE:MVI46-GSC help!! - jsanders @ 15/08/2006 3:05 pm
|
1
|
|
Diagnosing problems with C-programmable modules is often a complex matter. To help you solve your issues, I suggest you send your ladder logic, source code, compiled .EXE files, and the .IMA files you have been trying to use, along with the PC program you are trying to interface with and a full description of the problem(s) you are experie...
|
MVI56-ADM and RS485 problem - alexey @ 26/07/2006 4:15 am
Reply: RE:MVI56-ADM and RS485 problem - jsanders @ 26/07/2006 10:28 am
|
1
|
|
Yes, whenever you have two ProSoft modules in the same processor chassis, you can exchange data bewteen them by using COP (Copy) instructions from the data tables used by one to the data tables of the other.
You can use the these web links to get information about the ProSoft implementation of the IEC 60870-5-101 protocol in the MVI46-10...
|
MVI 46 and MVI-101S - sibym2000 @ 25/07/2006 9:37 pm
Reply: RE:MVI 46 and MVI-101S - jsanders @ 26/07/2006 10:21 am
|
1
|
|
If one type of command is working, there is no reason to expect a different command would not work. When I have encountered this problem in the past, it has been an issue of how the Simulator address range was configured. Please be sure you are looking at the correct address range for each type of command. And check the Internal Addresse...
|
MVI46-MCM - sibym2000 @ 14/07/2006 11:45 pm
Reply: RE:MVI46-MCM - jsanders @ 17/07/2006 11:22 am
|
1
|
|
The MCM module uses Modbus protocol. The command structure of a Modbus command is fixed; therefore, to create a Modbus command in our module, all the firmware needs are the variables....Slave ID, Function Code, Count, Modbus Address, etc.
The GSC is a Generic ASCII serial communication module. It is designed to receive and send ASCII s...
|
MVI56 GSC - jwilson @ 13/07/2006 2:53 pm
Reply: RE:MVI56 GSC - jsanders @ 14/07/2006 9:14 am
|
1
|
|
Page 38 of the User Manual for the MVI46-101S describes the "R" Option in the Debug/Configuration Menu. This is the option to use to send the edited configuration file from your PC to the module. The procedure is outlined in the User Manual.
After selecting the "R" Option and comfirming your desire to download the c...
|
MV146-101S - sibym2000 @ 11/07/2006 12:26 am
Reply: RE:MV146-101S - jsanders @ 11/07/2006 10:57 am
|
1
|
|
The MVI56-GEC Client will not send messages to a Server unless the Client is told to do so by ladder logic. Whatever it is doing, it is doing due to ladder logic. To help diagnose your problem, you need to send a copy of the ladder logic you are using to: Support@prosoft-technology.com.
Once a Technical Support Engineer has a chance to s...
|
MVI56 problem - robert_builder @ 21/05/2006 6:50 pm
Reply: RE:MVI56 problem - jsanders @ 24/05/2006 9:04 am
|
3
|
|
Ignore this post.
We are using a MVI71-MCM to communicate with serial devices on a RS-485 network and we are experiencing perodic communication errors. The error we are seeing is the slave device failed to reply. My question is related t...
|
MVI71-MCM Master Polling Operation - jmalter @ 30/03/2006 2:50 pm
|
0
|
|
All MV69 modules, including the MVI69-GSC, get their configuration from a file download through the Debug/Configruation serial port with a terminal emulator, like Windows HyperTerminal. There is no other way to configure these modules.
|
MVI69-GSC Configuration - voyenna @ 13/03/2006 11:12 am
Reply: RE:MVI69-GSC Configuration - jsanders @ 23/05/2006 9:07 am
|
1
|
|
Having a remote Modbus Master write a new configuration to module memory and then issue a 9997 block to tell the module to read in that configuration and store it as the new module configuration in ladder logic controller tags does not, in and of itself, interrupt communications on the module's Modbus applications ports.
However, before...
|
MVI56 MCM - write config command - JP @ 13/03/2006 1:37 am
Reply: RE:MVI56 MCM - write config command - jsanders @ 15/05/2006 3:47 pm
|
1
|
|
First File and File size parameters are one way to get our module to emulate PLC/SLC type data tables for access to module memory from remote DF1 Masters when we our port is setup as a DF1 Slave. The File Map parameters is another way; and they are mutually exclusive. If you set File Map parameters, it overrides the standard FirstFile/Fil...
|
MVI56-DFCM DF1 Data Mapping - timledwith @ 01/03/2006 3:32 pm
Reply: RE:MVI56-DFCM DF1 Data Mapping - jsanders @ 15/05/2006 3:39 pm
|
1
|
|
Which module are you asking about? What logic are you using?
What is your Client? Are you sure you are using the correct module for your application? And, what is that application? There are too many details not contained in your question for us to provide a usable answer.
Perhaps you should contact ProSoft Technical Support at 1-66...
|
MVI56 - robert_builder @ 22/02/2006 5:25 pm
Reply: RE:MVI56 - jsanders @ 15/05/2006 3:33 pm
|
1
|
|
There is nothing we know of that locks the module into responding as just one Node number. These modules read their configurations at boot-up and you should be able to assign the port any Slave ID value from 1- 247.
The only reason we can think for the behavior you report is that, at some point in time, the module was assigned to be Node...
|
3100 MCM to PLC-5 weird behaviour - felipe @ 15/02/2006 1:10 pm
Reply: RE:3100 MCM to PLC-5 weird behaviour - jsanders @ 15/05/2006 3:30 pm
|
1
|
|
Hello,
We're still having problems, thanks for the tip!!! We will try this new configuration and will let you know if it helps.
|
MVI56 MCM problem - dcs @ 13/02/2006 2:31 pm
Reply: RE:MVI56 MCM problem - dcs @ 15/03/2006 2:22 pm
|
2
|
|
The description of what you are seeing is typical when the module's Setup Jumper is installed, shorting both pins. This jumper need be installed only when upgrading module firmware under the supervision or direction of ProSoft Technical Support Engineers. For all other module operations, normal operation and configuration downloads, the S...
|
Unable to establish a connection from MVI56-GEC - robert_builder @ 13/02/2006 12:28 am
Reply: RE:Unable to establish a connection from MVI56-GEC - jsanders @ 15/05/2006 3:21 pm
|
1
|
|
The Slave Status table name is somewhat misleading. It is not the best information to monitor for health of communicatons to slave devices attached to our Master Port.
Instead of the Slave Status table, try monitoring the Master Command Error List. In the port configuration, there is a tag call CmdErrPtr. This tag allows you to send t...
|
MVI69-MCM - Slave Status information - cepha @ 08/02/2006 2:07 am
Reply: RE:MVI69-MCM - Slave Status information - jsanders @ 15/05/2006 3:15 pm
|
1
|
|
The Allen-Bradley support site had the following Tech Notes about that error code:
A70635394 - 1756-MVI CIP Message Error Code 16#000C
Last Modified: 01/20/2004
General Category: s Programmable Controllers
Programmable Controllers - I/O
Product(s): ControlLogix (1756)
Catalog #: 1756MVI
Series / Revision: N/A
Subject (Ke...
|
Service Request Error - robert_builder @ 05/02/2006 11:11 pm
Reply: RE:Service Request Error - jsanders @ 15/05/2006 3:06 pm
|
1
|
|
Thank to Gary (one of the tech guy) I have managed to solve the
Function code 10H problem.
|
MVI56-MCM - jarance @ 05/01/2006 5:51 pm
Reply: RE:MVI56-MCM - jarance @ 06/01/2006 4:51 pm
|
1
|
