sandippawar7 said:
can i use nc21 cable for that communication
Hi again Sandip,
Thank you for posting the catalog numbers above. Now we can be sure of what you have and what you need to do to get them communicating.
Note: Do please try, where you can, to use full catalog numbers when mentioning equipment and cables, etc. It helps to reduce the chances of people mistaking which specific product you mean. For instance, there are many third-party companies manufacturing replica Allen Bradley cables which may contain part references to the original AB cable catalog number. "...nc21..." is only part of a catalog number and could lead to such confusion.
If I am not mistaken, the cable you are inquiring about is an original AB "2711-NC21". This is a 5m/16ft straight-through serial cable. This is one of the recommended cables for connecting controllers with an 8-pin mini-Din serial port to PanelView terminals with an RS-232 serial port. If you already have this cable or are intending to purchase one then you are on the right track.
Note: the 2711-NC21 is a straight-through serial cable and is only intended for use between a DTE controller and a DCE HMI terminal. It can also be used to connect a DTE workstation to a DCE HMI terminal for application transfers and testing the application. It is not intended to be used between a DTE controller and a DTE workstation for programming the controller. Again, a null modem crossover cable, such as the aforementioned 1761-CBL-PM02, would normally be used. However, if a null modem adapter is used with the 2711-NC21 straight-through cable, then it will convert it to a null modem cable and then it can be used between a DTE controller and DTE workstation.
If you already have a 1761-CBL-PM02 cable then I would recommend using it for programming your controller. But you seem to already be communicating from your workstation to the controller...
sandippawar7 said:
...From Laptop to Controller communication done...
I would take this to mean that you already have the MicroLogix 1200 Channel 0 port configured and working with a DF1 driver in RSLinx Classic?
For reference, these are the default settings for the MicroLogix 1200 Channel 0 port...
Baud Rate: 19.2k
Parity: none
Source ID (Node Address): 1
Control Line: no handshaking
Stop Bits: 1
This is how the controller's port should be configured. Please can you confirm these settings are correct?
sandippawar7 said:
...in laptop FTV 8.0 Showing communication between PLC & HMI...When i create runtime file & download in factory talk view with ethernet then its not comminicating...
I would take this to mean that you have successfully downloaded a program into the controller using DF1, and also you have successfully downloaded an application into the terminal, using Ethernet. And then you are experiencing communications issues?
How are you connecting the controller to the terminal when this happens? Which cable have you been using?
To double-check the application settings...
In the View Studio application, under Communications Setup, what driver or drivers have you configured to communicate with the controller and under which tab - Design (Local) or Runtime (Target)?
You should have added the Serial DF1 driver under the Runtime (Target) tab and you must manually add the MicroLogix controller to this driver by right-clicking the driver and then "Add devices".
Once you have added the controller under the driver you must then create a shortcut by using the "Add" button. Give the shortcut a name that the application can reference the controller with, but do try to keep it short. Example: "MLX01" OR "ML1200", or whatever you prefer.
Then you must link this shortcut instance with the controller instance under the Serial DF1 driver. To do this, highlight both instances and then click on "Apply". The new shortcut, that the application tag references will be able to use, should now be linked to the controller at Runtime. All your tag references for the controller should have this shortcut name included in their syntax.
Also, when you download the application to the terminal and run it, you will be prompted to select whether to use the application's Communications Setup or the terminal's current communications configuration. You should choose to use the application's Communications Setup. If you are not choosing this option, and the terminal is not currently configured with a Serial DF1 driver, then communications will not work.
I think that covers most of the basic setup? If you can follow that and something is still not right, then please answer the questions above and state exactly what is not working. Also, please quote any messages you may be seeing on the terminal at Runtime.
Regards,
George