Frequently Asked Questions
Q:
Do I need to purchase special software to configure your modules?
No. Our modules are either configured through your automation system processor, or using a text based configuration file, or in some cases, using a configuration tool provided with the module.
Close
Q:
When I do a search on your web page for a solution, I am sometimes given two modules, a 3150/3100 module, and an MVI module. What is the difference?
The 3100/3150 product line is our original module line. We now provide our modules on an upgraded hardware platform, the MVI, which provides many improvements over the 3100/3150 hardware platform. Some of the new features the MVI modules offer are:
- On board Debug port which allow the user to view communication and configuration status of the module.
- On most modules, a built-in Data Analyzer is available, which assists the user in tracking down communication problems on their industrial network.
- Ability to field upgrade the module, so that new versions of the firmware can be flashed to the module without the need to return the module to the factory.
Close
Q:
I'm attempting to use your Modbus module to communicate over my RS-485 network, but I am not getting any communications. What could be wrong?
The module is shipped from the factory with the port configuration jumpers in the RS-232 communication mode. Check that your module's port jumpers have been changed to RS-485 mode.
Close
Q:
How do I connect to the Debug Port of my MVI or ProLinx module?
- Connect PC to Module's Debug port using a Null-Modem cable
- Start HyperTerminal with the following settings:
- Bits per Second: 57,600
- Data Bits: 8
- Parity: None
- Stop Bits: 1
- Flow Control: Xon/Xoff
|
- Once connected, press Shift - ? to display Debug Menu
Close
Q:
What is the difference between the MVI56-MCM and the MVI56-MCMR?
- MCM-I/O mapping (250 input words and 248 output words)
- MCMR-I/O mapping (84 input bytes and 84 output bytes)
- MCM-Config by CLX ladder logic
- MCMR-Config by a configuration file (text file) to download through the Debug port using Hyper Terminal
By reducing the size of the I/O image map, the backplane communication time is reduced, therefore reducing ControlNet bandwidth requirements for the MVI56 module.
If the MVI56-MCM module is to be installed in a remote ControlNet chassis, then the MVI56-MCMR is recommended.
Close
Q:
What is the difference between the 3150-MCM and the MVI46-MCM?
- The MVI46-MCM is the latest Modbus module for the Allen-Bradley SLC platform
- The MVI46-MCM provides a DebugPort which allows the user to view module configuration and status
- The MVI46-MCM provides a built-in Data Analyzer for troubleshooting communication problems
- The MVI46-MCM is field upgradable
- The MVI46-MCM is based on a 16-bit processor instead of the 3150-MCM's 8-bit processor
Close
Q:
Can the ProSoft SLC communication modules be placed in a remote SLC rack?
No. The 3150 and MVI46 line of ProSoft modules can only reside in the local SLC rack, or an extended SLC rack.
If serial communciations is necessary at a Remote I/O location, then the ProLinx 4601-RIO module should be considered.
Close
Q:
How many Modbus devices can I connect to my MCM module?
The ProSoft Modbus device port can be configured for either RS-232, RS-422, or RS-485.
RS-232 allows a point-to-point connection, with 50 feet being the maximum length
RS-422 allows a multi-drop connection, with a maximum of 10 devices on the network. The maximum total distance is 4000 feet.
RS-485 allows a multi-drop connection, with a maximum of 32 devices on the network. The maximum total distance is 4000 feet.
Close
Q:
When using the 1451-9F terminal connector with my 3150 module, do I need to jumper pins 7 and 8 as shown in the manual?
No. The 1451-9F adapter has pins 7 and 8 jumpered internally.
Close
Q:
My 3150-MCM is configured to have no Write Data, only Read Data. Occasionally, I am seeing my data overwritten with what appears to be configuration data.
The Write Block Start parameter must be set to a value which does not overlap with the Read Data area. A Write Start value of 75 will generally take care of this problem.
In the sample ladder for the 3150-MCM, register N7:28 is the Write Block Start parameter.
Close
Q:
Ive downloaded a configuration to my RLX-FHS radio, but now need to change the configuration. I dont remember the RS232 settings, like baud, parity, handshaking.. etc. I've tried the auto-detect feature, and it fails as well. What can I do?
Setting the jumpers on the RLX-FHS radio to RS485 mode will default the RS232 port to 115200, none, 8, 1 and no handshaking. This will allow you download your new configuration.
Close
Q:
Can I connect an RLX-FHS to an RLX-FHE?
You can have an RLX-FHES (Ethernet with serial encapsulation) communicate to an RLX-FHE (Ethernet), but cannot have an RLX-FHS (Serial) communicate to either a FHES or FHE radio.
Close
Q:
How is your RLX-IH different from "off the shelf" 802.11b radios?
The RLX-IH has industrial ratings for temperature, shock resistance, and is Class I Div 2 approved for hazardous locations; the RLX-IH is din-rail mountable; you can have redundant master radios. One of the most important differences is the 200 mW / 500 mW output power (depending on country).
Close
Q:
When using a bit level Modbus function code I can not see my data even though the command does not error, what could be wrong?
The database in any Prosoft module is structured in 16 bit integer words. When doing any bit level Modbus function code the database must be referenced at the bit level. For example: Word 0.0 = Modbus coil address 0001, Word 1.0 = Modbus coil address 0017. Word 100.0 = Modbus coil address 1601. To get the Internal bit number just take the register number times 16 to get the starting word.bit address.
******Note: The only exception to the above rule is in the 3100-MCM and 3150-MCM configured as a master and using a function code 2. in this scenario the ?source address? is at the word level not the bit level.******
Close
Q:
What Belden cable does Prosoft recommend for RS485 communications?
Belden 9841 or 9842
Close
Q:
InRAx
Q:
In past applications, I've used a 1756-MVI to read from a barcode scanner. Is your MVI56-ADM product similar?
Yes, the MVI56-ADM is essentially the same product as the 1756-MVI. IMPORTANT: one thing to note, for simple ASCII communications, such as reading/writing to a scale, barcode scanner, serial printer, etc. we strongly recommend you consider the MVI56-GSC.
Close
|