FAQs - Communications
Q. How do you connect Cscape via a serial port?
A: Click Here
Q. I have an OCS that I want to site remotely and dial up on occasion to program using Cscape. I see there is some information in the help file, but is this OK to do?
A: Below are steps for dialing in to an OCS using Cscape and Modem connections.
The modem MUST be connected to Port 1 on the remote OCS as this is only Port that can be used to program the unit.
The Cscape side of things is very straightforward.
Open Cscape, connect the PC to the Modem using whichever comm port is highlighted in Cscape/Tools/Options/Communications Port Tab. This is, generally Comm 1.
When ready to connect to Remote OCS, in Cscape select Tools/Connect Via Modem, see below.
Modem Init String - In this box, enter any modem initialization string required by the modem. For example, to turn DTR OFF and FLOW CONTROL OFF, set the string to AT&D0&K0.
Dial Command - In this box, enter the command your modem requires to initiate dialing.
NOTE: The above two command are modem specific. The values default to common commands used to program modems using the industry standard AT command set. Most current modems implement this command structure, but refer to the User Manual that comes with the modem in order to determine the exact strings necessary to perform these tasks.
Number to Dial - In this box, enter the number to be dialed. Do not use spaces, dashes, or any other punctuations except those required by the modem. Also include any special commands in the dial string, such as those necessary to insert a pause or to defeat Call Waiting. The comma "," is often added to insert a pause to obtain an outside line, or the string *70 is included to defeat Call Waiting.
Example: 9,7654321 Dials for an outside line, pauses to make the connection, then dials local number 765-4321
Status - This is a statement of the status of the modem connection.
Establish the Connection
When the information is entered, click the CONNECT button to make the connection. If all is well, the Status Line displays Modem connection established. It takes several seconds (as long as a minute) to establish or reject the connection.
Note: Clicking CONNECT causes the Init String, Dial Command, and Number to Dial entries to be written into the Windows Registry and becomes the default settings for the next connection.
Break the Connection
To break the connection (hang up) from the Main Menu select Tools|Connect via Modem, and then click the HANG UP button.
Cscape maintains active communications during a Data Watch, Debug, and Upload/Download. The modem connections are not broken during these times. The modem connection can be broken at any other time.
Cscape will complain about lost connections, but once you acknowledge the error dialog box Cscape will return to normal operation. In other words, a loss of communications error is not fatal.
Errors
If the connection can not be established, one of the following errors appears in the Status Line:
Error sending modem init string - modem did not return OK after sending init string
Error sending dial command - Error while sending dial command
Error dialing - Modem started to dial and returned an error.
Communication error - Error in the Comm port. Could not open port, serial driver error, etc. Check the modem, cables, etc.
This can also occur if another program is using the Comm port selected by Cscape. In this case close the other program or select a different Comm Port for Cscape.
When the Cscape/Modem Connection is Established, Click on the 'CLOSE' button in the Modem dialogue and, the local ID in Cscape status bar will change to the ID of the connected OCS. Make sure the Target ID is the same to proceed with Upload/Download
Q. I am considering using the NX for a new app and need Modbus TCPIP Master capability. I saw, on the website, a new release, 8.10B, that states that the NX now has this capability. I downloaded the new version, but can't seem to find where to set it up?Also, can this unit act as a master and slave? I need to poll modbus data from three devices, for local display and logging, then send the data to a remote SCADA. Is this possible with the NX?
A. You will also need to update the FW in the NX. The firmware can be downloaded from the same page as Cscape. To configure ModbusTCP/IP master in Cscape click on 'Program' and then click on 'Protocol Config'. There you will see Ethernet as an option. The NX supports ModbusTCP/IP slave as well. The slave setup is in the I/O config section under the ETN300 module configuration. It is simply a checkbox for the slave setup. Please contact us if you additional questions.
Q. I have a application with modbus using CN1 port in the controller and in the ladder port 2 open for communicate with modbus devices, my communication with the HMI in the PC is for the TCP in the LAN connector, like to connect with other device (PLC5/40 allen Bradley DF1) by serial port 1 in the controller, what i need to do in the ladder and in the software-program- protocol- configure.
A. You will need to load the DF1 protocol using the Protocol Config option in Cscape. Select Program/Protocol Config. Then use the dropdown option on Port1/MJ1 to select the Allen Bradley DF1 option. You then need to setup the Communication settings plus the Device and Scanlist. See Protocol Config Help in Cscape for details.
Q. How can I get data from by XLe into my PC?
A. There are a couple of options for extracting data from an XLe.
1. Use Kepware OPC server using the Cscan protocol, HE-OPC500. This option will allow the server to access all of the XLe data. The data will be extracted either through the MJ1 serial port of the XLe or through the HE-XEC Ethernet option for the XLe. The HE-XEC will require that the PC utilize the Port Redirector software to route the IP address of the XLe to a communication port on the PC. The HE-OPC500 allows for 1 serial connection, so in applications requiring data to be extracted from multiple XLe’s, a different method will need to be used.
2. Use Kepware OPC server using a Modbus protocol. This can also be done through either a serial connection or Ethernet connection. To utilize the Modbus connection, use the Modbus Encapsulation option in Kepware. This will eliminate the need to use the Port Redirector software. This option will allow for connection to more than 1 XLe at a time.
Q. I am unable to connect to my XLe with my Modbus Master over Ethernet.
A. Verify that the port1 of MJ1 is opened in the program as Ethernet and Modbus protocol. After the port is opened, use the Modbus slave block. The next step is to verify that the XLe is configured to use the Ethernet port instead of the RS-232 port. This is configured through the system menu on the XLe. Now verify the IP address is set correctly. If the port is changed from RS-232 to Ethernet or the IP address has been changed, power cycle the controller to initiate the changes.
Q: Why is CsCAN the default OCS network instead of DeviceNet?
A: CsCAN has advantages that DeviceNet does not have. CsCAN and DeviceNet are similar networks. Both networks are based on the CAN specification developed by Bosch. CsCAN follows the basic DeviceNet configuration for wiring. Both networks use the "trunk and tap" wiring configuration. With CsCAN, the maximum distance the network can be is 1500 meters (with repeaters). With DeviceNet, the maximum distance you can have is 500 meters. With CsCAN, you can have up to 253 nodes on the network (using 3 repeaters). With DeviceNet, the maximum number of nodes on the network is 64. The network speed for CsCAN is from 125Kbaud to 1Mbaud. For DeviceNet, it is 125Kbaud to 500kbaud. CsCAN is a peer to peer network (no master device is needed). DeviceNet is a master-slave network and requires a master device. Each OCS node would be a slave. CsCAN uses global data and DeviceNet does not. With CsCAN, you are able to program/monitor/trouble-shoot controllers over the network. You can not do this with DeviceNet.
Q: How is priority set up on the CsCAN network?
A: CsCAN is a true peer-to-peer network. Devices with lower network IDs have priority.
Q: Is the CsCAN network a token pass network?
A: No. The CsCAN uses non-destructive arbitration based on network ID.
Q: Is it possible to program over the network?
A: It is possible to program over the CsCAN network using either a serial or Ethernet connection. As long as there is one serial or Ethernet connection between the PC running Cscape and any node on the CsCAN network, they have entire control over the network. They can upload, download, monitor and debug any node on the network.
Q: Are there other products that tie into the CsCAN network?
A: Yes. All of the Horner Electric "Controller products" can be used on the CsCAN network. Some older units may require a firmware updates so that they may be used on the CsCAN.
Q: Is there derating for the CsCAN network for speeds over 125K?
A: As the distance of the network increases at speeds of 125K, the derating of the network increases (i.e. The faster the speed of the network, the shorter the distance the total network should be - to maintain data integrity).
Q: Can you mix networks on OCS units?
A: CsCAN and DeviceNet can not be mixed. The only network that may be mixed is the Ethernet (i.e. Protocols may be mixed).
Q: Is anybody making a CsCAN interface card?
A: Yes, the part number is HE200KGM561
Q: Can you support multiple hosts for nodes in CsCAN?
A: CsCAN will not support multiple hosts for nodes. This means that if there is more than one PC with an active serial port trying to talk to a single OCS at the same time, an error in Cscape will be produced.
Q: Is there going to be a CsCAN driver for Cimplicity?
A: There is a CsCAN driver and it is currently available.
Q: Can I combine your network with a CANopen one, can your device be a slave on such a network?
A: CSCAN is not directly supported by CANOPEN but we do have a CANOPEN Master Module (HECOM650) which can be attached as an add-on to several of our products.
|
