|
Message
|
Topic
|
Replies
|
|
To send Floating Point (REAL) data from a CLX CPU to the ProSoft MVI56-MCMR module, simply use the COPy instruction in RSLogix to COPy from any REAL-type tags or Tag Arrays to the MCM1.WriteData[x] array. The LENgth of the COPy instruction will need to be twice the number of FP values you wish to send, as each 32-bit FP will be stored in...
|
MVI56-MCMR Supporting Float Point Data - bofwanker1 @ 14/03/2007 8:48 am
Reply: RE:MVI56-MCMR Supporting Float Point Data - jsanders @ 30/03/2007 3:32 pm
|
1
|
|
While the module emulates the addressing scheme of Modicon processors, it does not keep separate data areas for each data type. Coil addresses 0001-0016 use the 16-bits of storage in module memory register 0. Input Status bits 10001-10016 use the same register 0. Input Register 30001 and Holding Register 40001 also use the same module me...
|
MVI46-MCM FC2 is overwritng next FC2 with 1st FC2 data - brucelester @ 09/03/2007 11:06 am
Reply: RE:MVI46-MCM FC2 is overwritng next FC2 with 1st FC2 data - jsanders @ 30/03/2007 3:46 pm
|
1
|
|
All of the ProSoft MVIxx-ADM modules (Application Development Modules) are meant to be completely user-programmable. As such, there is no standard configuration file for this modules like there are for our protocol-specific modules.
The ADM Developer's Guide gives complete instructions for building your application and creating the Imag...
|
mvi69-adm configuration - gwmarsh @ 13/02/2007 10:51 am
Reply: RE:mvi69-adm configuration - jsanders @ 01/03/2007 5:07 pm
|
1
|
|
Page 26 of the MVI56-DNP User Manual says this:
DNP DB Address
This parameter defines the starting location in the DNP database to be used with the command. If the parameter has a value of –1, the DNP database is not used with the point.
The MVI56-DNP module has two DNP serial ports, a Master port for polling DNP Slaves and a Sla...
|
 what's the meaning of DNP DB ADDRESS IN THE DNP.CFG? - zhou_7 @ 11/02/2007 6:09 pm
Reply: RE:what's the meaning of DNP DB ADDRESS IN THE DNP.CFG? - jsanders @ 01/03/2007 5:00 pm
|
1
|
|
The sample ladder, in the N7 configuration table,sets N7:20 to 4, declaring 4, 50-word Read Blocks and in N7:26 declares the first Read Block ID to 0. Block 0 is the lowest addresses in module memory, addresses 0- 49. Block 1 is addresses 50-99, etc. up to Block 79, the last User data block, addreses 3950-3999.
With this configuration,...
|
Help with PLC5 to MCM3100 to OMNI Flow computers - lawebster @ 03/01/2007 12:14 pm
Reply: RE:Help with PLC5 to MCM3100 to OMNI Flow computers - jsanders @ 30/03/2007 4:16 pm
|
3
|
|
Problem being faced: PSFT 1756-DNP master protocol specifies that "Event data rec'd from the slave devices updates the module database (Date & Time stamping is not stored or used by module"
Query:
Q1. does it mean, 1756-DNP does not supports time stamp events when confiured as Master to the slave IED's. How can one uti...
|
Application: Sub-Station Automation - sibym2000 @ 24/12/2006 5:36 am
Reply: RE:Application: Sub-Station Automation - esyme @ 03/01/2007 4:02 pm
|
1
|
|
The MVI94 modules will not show up as specifically that name or type. Instead, you use the "FLEX-MODULE Generic Flex Module" as the module type. Any verison of RSLogix 5000 that offers the FLEX-MODULE option is compatible with our MVI94 modules. This includes Version 13.
|
MVI94-ADM And RSLogix5000 Ver.13 - paulrichm @ 12/12/2006 5:34 am
Reply: RE:MVI94-ADM And RSLogix5000 Ver.13 - jsanders @ 14/12/2006 4:11 pm
|
1
|
|
Yes, there are some differences in the way the MCM and the MCMR bring in general module status information. In the MCM, the status is updated as part of every new Local:1:1.Data input image. To get the same information for the MCMR, you have to request it with the special MSG rung and you do have to toggle the trigger bit whenever you want...
|
MVI56-MCMR Comm Fail Detection - cjblake @ 11/12/2006 8:13 am
Reply: RE:MVI56-MCMR Comm Fail Detection - jsanders @ 14/12/2006 4:05 pm
|
1
|
|
Yes, there are some differences in the way the MCM and the MCMR bring in general module status information. In the MCM, the status is updated as part of every new Local:1:1.Data input image. To get the same information for the MCMR, you have to request it with the special MSG rung and you do have to toggle the trigger bit whenever you want...
|
MVI56-MCMR Comm Fail Detection - cjblake @ 06/12/2006 10:35 am
Reply: RE:MVI56-MCMR Comm Fail Detection - jsanders @ 14/12/2006 4:06 pm
|
3
|
|
Sorry; but you are mistaken. The MVI56-MCM and MVI56-MCMR modules are not interchangable and do not use each other's ladder logic. The MVI56-MCM has its own ladder that provides configuration information via controller tags that do not exist in the MCMR ladder. The MCM does not have a Compact Flash card installed; only the MCMRs do.
The...
|
MVI56-MCM to work as MVI56-MCMR - mbrillia @ 04/12/2006 5:22 am
Reply: RE:MVI56-MCM to work as MVI56-MCMR - jsanders @ 06/12/2006 3:21 pm
|
1
|
|
Our MVI56 modules do not allow for the direct reading of I/O modules in the CLX rack through our modules. Our module can talk only to the CLX CPU across the backplane; not to any other I/O modules. You will continue to have to COPy the raw inputs/outputs to/from our module's memory in the manner which you describe. When our module is a Slav...
|
MVI56MCM in CLX- Customer request. Not sure how to accomplish what they want - Mike6158 @ 12/11/2006 9:30 am
Reply: RE:MVI56MCM in CLX- Customer request. Not sure how to accomplish what they want - jsanders @ 13/11/2006 8:48 am
|
1
|
|
We often get reports of users having trouble trying to do file transfers through USB to Serial converters. Some work well, some don't work at all, and some work only sporadically. Desktop PC with real 9-pin serial ports seem to be the most reliable. Some users have reported success by unchecking the FIFO buffer option on their port confi...
|
MVI46-MNET - configuration transfer error - martin_wiltshire @ 30/10/2006 7:32 am
Reply: RE:MVI46-MNET - configuration transfer error - jsanders @ 27/12/2006 8:58 am
|
3
|
|
Since terminating resistors are not always needed, none are built into any of the ProSoft modules. If you have extremely long cable runs or are experiencing line noise problems and determine that you need terminating resistors, you will have to add them externally yourself.
|
MVI71-MCM Internal 120 ohm resistor for RS485 - vidyadharj @ 26/10/2006 1:11 am
Reply: RE:MVI71-MCM Internal 120 ohm resistor for RS485 - jsanders @ 26/10/2006 8:01 am
|
1
|
|
ProSoft's policy is to provide sample ladder logic for the MVIxx-GSC modules that shows how to properly move data into the Write Buffer and out of the Read Buffer with predictable and reliable result. It is not our policy to debug and troubleshoot application-specific logic created by end-users; although we will offer as much advise and su...
|
MVI46-GSC: Controlling Communications - DCLittlejohn @ 20/10/2006 4:17 am
Reply: RE:MVI46-GSC: Controlling Communications - jsanders @ 20/10/2006 8:03 am
|
1
|
|
If you look in the MVI56-MNETCR User Manual, starting on page 16, Section 2.3.2, you will see a discussion on how to use the special function blocks to read Client Status. This discussion goes along with the ladder logic shown in our sample in the Write Routine, Rung 7.
Part of the data returned in the special block will be the Client C...
|
MVI56-MNETCR - cjblake @ 02/10/2006 8:29 am
Reply: RE:MVI56-MNETCR - jsanders @ 02/10/2006 11:16 am
|
1
|
|
The ladder logic will move the MCM1.WriteData array out to module memory starting at whatever address you have set in the Configuration file parameter, "Write Register Start". Assuming you set this paramter to 0, then the value in MCM1.WriteData[0] will go to module memory address 0, which will appear to a remote Modbus Master at...
|
MVI69-MCM Slave Mode - Fruehauf @ 02/10/2006 12:38 am
Reply: RE:MVI69-MCM Slave Mode - jsanders @ 02/10/2006 11:02 am
|
1
|
|
Thanks for the suggestions. I'll passs them on to the Development Team for possible implementation.
|
MVI46-GSC - ASCII to Integer Conversion - DCLittlejohn @ 28/09/2006 5:39 am
Reply: RE:MVI46-GSC - ASCII to Integer Conversion - jsanders @ 29/09/2006 11:33 am
|
3
|
|
It is highly unlikely there is anything wrong with the module. This type of boot cycle is caused by the module's inability to open a backplane connection to the CLX CPU. The most likely causes for the symptoms you describe are:
1-Correct ladder logic not loaded
2-CPU not in RUN or REM RUN mode
3-I/O Configuration not correct (wrong i...
|
MVI56-GSC module reporting an error from config - scada @ 28/09/2006 1:18 am
Reply: RE:MVI56-GSC module reporting an error from config - jsanders @ 28/09/2006 9:14 am
|
1
|
|
You can get product information from our website. Here is a link to the product page for the 3100-MCM:
http://prosoft-technology.com/content/view/full/1120
|
3100 MCM in 1771 Remote Rack - timledwith @ 20/09/2006 11:22 pm
Reply: RE:3100 MCM in 1771 Remote Rack - jsanders @ 27/12/2006 8:52 am
|
3
|
|
Sorry, but that is not possible with this module.
|
MVI56-DFCM - bbonthron @ 11/09/2006 5:51 am
Reply: RE:MVI56-DFCM - jsanders @ 19/09/2006 3:23 pm
|
1
|
