|
Message
|
Topic
|
Replies
|
|
Pass-Through logic is included in the standard samples provided with the module. These samples are also available for download by clicking on the "Ladder" link in the upper-right corner Download section of the web page at this URL:
http://www.prosoft-technology.com/content/view/full/621
|
MVI56-MCM Pass-through mode - jxspodi @ 14/07/2005 6:14 am
Reply: RE:MVI56-MCM Pass-through mode - jsanders @ 17/11/2005 8:49 am
|
1
|
|
I think you need to confirm your address information with A-B. Anytime you get timeout errors on some commands when others produce data, it is most likely an addressing problem.
|
3150-mcm and powerflex 4/40 - bkinder @ 23/06/2005 1:28 am
Reply: RE:3150-mcm and powerflex 4/40 - jsanders @ 24/06/2005 5:30 am
|
1
|
|
A few things to check...
Be sure you set our module jumper for RS-485 mode and use our DB9 to screw terminal adapter to connect your two-wire RS-485 cable to our module. This adapter has DB9 pins 7 & 8 jumpered, as required for our module to communicate.
Also, you'll need to create commands in the 3150-MCM ladder to poll the Kohl...
|
MCM-1350 and Kohler - mpiquette @ 22/06/2005 11:59 pm
Reply: RE:MCM-1350 and Kohler - jsanders @ 24/06/2005 5:28 am
|
1
|
|
Try increasing the Timeout parameters in the module configuration, especially the Reply Timeout.
|
MVI46-DFCM to MDS 9710 Radio Modem communication problem - mwilliamsiei @ 21/06/2005 10:49 pm
Reply: RE:MVI46-DFCM to MDS 9710 Radio Modem communication problem - jsanders @ 24/06/2005 4:53 am
|
1
|
|
By default, the jumpers that select interface type are set for RS-232. To use the module for RS-485 you must change the jumpers. Did you do that?
|
MVI56-GSC Comm over RS485 - gwbos @ 23/05/2005 4:16 pm
Reply: RE:MVI56-GSC Comm over RS485 - jsanders @ 14/06/2005 1:14 am
|
1
|
|
It is probably just a timeout configuration setting issue; but it could also me a radio problem. To further investigate the former possibility, please send your ladder logic and radio network layout to support@prosoft-technology.com for additional assistance. On your end, check to be sure you have good signal strength at all times while s...
|
MVI46-DFCM to MDS 9710 Radio Modem - sietsemr @ 23/05/2005 1:37 am
Reply: RE:MVI46-DFCM to MDS 9710 Radio Modem - jsanders @ 14/06/2005 1:18 am
|
1
|
|
You failed to specify which module you are asking about; but, from the context of your message, I assume you are asking about the MVI56-MCM. In this module, the Module Status/Error Data and Command Error Lists for each port (when used as a Modbus Masters) reside in the upper region of module memory, above the 5000 registers of user data....
|
Module Communication Error Codes - sterndale @ 17/05/2005 9:46 pm
Reply: RE:Module Communication Error Codes - jsanders @ 23/05/2005 2:52 am
|
1
|
|
You might try using Borland v 5.02. We recently changed our libraries and I understand they to not alway compile correctly with v. 3.1 anymore.
|
a question - rac @ 12/05/2005 12:00 pm
Reply: RE:a question - jsanders @ 17/05/2005 2:31 am
|
1
|
|
The on-line manual for the Bently Nevada 3500/92 comm module says it is capable of Modbus communication via serial port or Modbus TCP communication via Ethernet. It does not specify what Service port to use for Modbus TCP.
The ProSoft MVI56-MNET Client is capable of creating Modbus TCP commands to access data from either Service 502 (sta...
|
mvi156-MNET - merlinknight @ 06/05/2005 1:22 am
Reply: RE:mvi156-MNET - jsanders @ 06/05/2005 2:50 am
|
1
|
|
The 3100/3150-SEA module supports the SEABUS Plus protocol on Power Meter Models 4300, 4700, and Static Trip III only. Other SEABUS Plus devices that respond like one of these three might also be supported, if those devices' response messages are the same as one of the model listed above. This implementation of the SEABUS Plus protocol supp...
|
3150-SEA - djthune @ 18/04/2005 10:10 pm
Reply: RE:3150-SEA - @ 19/04/2005 2:40 am
|
1
|
|
The module has a queue of up to 200 event messages on the DNP network, however only 20 of these messages will be transferred over the backplane at a time. If module receives 200 event messages, it will pass all of those messages over to the ladder logic in 10 blocks of 20 messages per block.
|
MVI56-DNP - newfoundland @ 25/02/2005 10:52 am
Reply: RE:MVI56-DNP - esyme @ 25/02/2005 3:17 pm
|
1
|
|
Sir:
Prosoft has no information about the Adroit SCADA system you mention. If it has Allen-Bradley Ethernet IP drivers, or if it can use RS Linx, then your customer should have little or no problem making it work. If it does not use A-B Ethernet IP, then this module will not be able to communicate to it.
The pass-through port on the...
|
MVI46-DFNT - hkhatri @ 11/01/2005 2:08 pm
Reply: RE:MVI46-DFNT - @ 17/01/2005 12:49 pm
|
1
|
|
MBAP (port 502) is what most people refer to as ModbusTCP/IP.
Port 2000 will produce a standard Modbus RTU packet, including CRC, wrapped in a TCP/IP wrapper. With Port 2000 calls, a TCP/IP device can strip off the TCP/IP wrapper, and then pass the resulting Modbus RTU packet to a serial Modbus device.
|
MVI56-MNET configuration file - cbehr @ 12/12/2004 11:14 pm
Reply: RE:MVI56-MNET configuration file - @ 13/12/2004 12:11 pm
|
2
|
|
There could be several things which could cause this: termination characters in the string, wrong termination type, data is transmitted faster than the GSC can handle (not likely), etc.
I suggest you call our support department at: (661) 716-5100
ProSoft Support Team
|
MV156-GSC - cgilkers @ 10/11/2004 12:45 pm
Reply: RE:MV156-GSC - CH @ 10/11/2004 1:13 pm
|
1
|
|
The answer to your Modbus addressing question is a qualified, "Yes." The sample ladder logic makes sure that ReadData[0] lines up with whatever module memory address you define in MCM.ModDef.ReadStartReg. The same is true for WriteData[0] and MCM.ModDef.WriteStartReg.
|
MVI56-MCM training example - cheongcy @ 27/10/2004 1:00 am
Reply: RE:MVI56-MCM training example - @ 17/11/2004 2:05 pm
|
3
|
|
This module is not released yet. It's in the final phase of testing, and may be released by the end of the year.
CH
|
Controllogix rack mounted modem - dpaulovich @ 25/10/2004 11:37 am
Reply: RE:Controllogix rack mounted modem - CH @ 26/10/2004 7:04 am
|
1
|
|
Peter,
If all the MVI56-MCM modules have firmware revisions new enough to support the Guardband function, then you could enable the Guardband on them all, even the ones that really don't need it right now, without any ill effects. Before adding Guardband logic and trying to use Guardband, be sure your module firmware is Version 1.06 or...
|
MVI56-MCM preset multiple registers - PvdM @ 24/09/2004 3:28 am
Reply: RE:MVI56-MCM preset multiple registers - jsanders @ 10/05/2005 11:58 pm
|
9
|
|
The contents of the data passed to the Error Status location is shown in the user-manual in section Appendix B - MVI46-MCM Status Data Definition.
28 words of status data are passed to this location.
|
MVI46-MCM Slave Status, Error Status, Command Errors - dmpierce @ 17/09/2004 10:03 am
Reply: RE:MVI46-MCM Slave Status, Error Status, Command Errors - mtracy @ 21/09/2004 11:51 am
|
3
|
|
So, if I understand correctly, the 3100-YORK is used to communicate on the YORKTALK network directly. The chillers I am interfacing have Optiview panels with Modbus Microgateways so I need the 3100-MCM. I guess the guys at York were trying to keep me on my toes by sending me the 3100-YORK manual and then shipping the 3100-MCM module. I will...
|
3100-MCM to York Chiller - dsroney @ 07/09/2004 8:25 am
Reply: RE:3100-MCM to York Chiller - dsroney @ 07/09/2004 9:05 am
|
2
|
|
Mike,
Yes the MVI56-MCM can be used in a remote rack, but be advised that it uses considerably more bandwidth then the MVI56-MCMR. The MVI56-MCMR was designed for the remote rack and therefore is the suggested module for remote rack operations.
- CH
|
MV156-MCM vs. MV156-MCMR - mikecjr @ 17/08/2004 8:22 am
Reply: RE:MV156-MCM vs. MV156-MCMR - CH @ 17/08/2004 8:27 am
|
1
|
