BobLfoot

In the now classic commercial a group of men sit around a table and generate "Man-Law" usually related to beer. A Sample Man Law Ad on youtube It is my hope in an equally light hearted way we PLC guru's can sit around our keyboards and draw from our own personal histories those jewels of PLC-Law that should pass to the up and coming programmers. PLC LAW #1 - DON'T OVERCOMPLICATE THE SIMPLE. In other words use the simpliest easy to understand logic allowable. Using a sophisticated high level instruction just to look cool doesn't help anyone. NEXT?? 9/6/2008 - Just Published the Edited Downloadable 2008 Edition of the PLC Laws to the MRPLC Download Section. We are now at Law #51. Note: The Posting has the 2006 and 2007 versions in the ZIP file as well.

Good Catch @panic mode when @JoseM mentioned "Hyper Terminal"  I never looked deeper.

Just a quick 2cent thought.  Hyperterminal is pretty forgiving on baud and protocol , usually doing an auto-negotiate,  I am unfamiliar with the ViewMarq . but are you absolutley certain that you're not on the wrong baud, or missing a stop bit.  Your last hyperterminal looks like it should be a valid data packet.  One other thought, have you thrown a null modem in the rs232 line to the marqview?  Might be that solves the last pice.

@AndrejP not sure how the CXProgrammer community folks are, but most programmers I know won't write code for free.  That said if you were to take a crack at programming it and post your work, you would "tons" of "free advice" on how to improve and make it better.  Give those helping you a place to start and show some initiative will get more responses.

Glad you found your answer and shared for others to learn as well.

Does setup.exe exist at the full path where windows is looking for it? And if it does check and make sure that setup.exe and the folder it is in have Read/Write/Execute permissions set and hasn't been changed to ReadOnly by some security program.

On page 92/93 it says size awg23 to awg19 for insulate ferrules and awg23 to awg16 for non-insulated ferrules.  You're not using insulated ferrules on awg18 are you? https://www.mitsubishifa.co.th/files/dl/jy997d61401h_FX5UC(Hardware).pdf And if you happen to be using the European Style connectors then its awg22 to awg20 sizes.

I second what @panic mode suggested in fact either of these could repalce it nicely.: https://www.redlion.net/product/43-widescreen-hmi-2-serial-1-ethernet-usb-device https://www.redlion.net/product/43-widescreen-hmi-3-serial-1-ethernet-1-usb-host-usb-device-web-server-and-data-logging

@LuisGonzalez best advice I can give is take a class from twcontrols.com and pick the brain of @TimWilborne.   He went through the whole life cycle of a Plant maintenance person to a Panel Building Shop and Training Center Owner. When he is of a mind to share, you'll learn alot.

First I put your question into it's own topic rather than on a three year old post to hopefully attract more relevant attentions. Second - I found this Mitsubishi Manual which talks about Modbus - https://www.mitsubishifa.co.th/files/dl/jy997d56101d_FX5(MODBUS%20Communication).pdf Third - I found this Omron Manual which talks about MODBUS - https://assets.omron.eu/downloads/manual/en/v4/w506_nx_nj-series_cpu_unit_built-in_ethernet_ip_port_users_manual_en.pdf Fourth - From what bare little I know of Modbus you'll first need to decide which PLC is master and which is slave.  Then you'll map Native I/O of each to modbus registers and the modbus comms will transfer the data. Beyond that it's time for you To RTFM and post your success or failure for others to guide you. Good Luck!

Any time I hear "That's the way we've always done it and it works" in the context of a Safety Discussion I get worried.   In the 1960's it was recommended by the American Academy of Pediatrics that a solo parent and solo child in a car, both ride in the front seat, so the parents arm can restrain the child. We all know better today and what worked 10 years ago, should be reviewed today to see if there is something better.

Take a look into this manual - https://literature.rockwellautomation.com/idc/groups/literature/documents/rm/1756-rm093_-en-p.pdf - I believe the section on Standard Tags in Safety Routines (tag mapping) -- may accomplish what you're looking for.    BUT HEED THE WARNING, YOU ARE RESPONSIBLE FOR THE INTEGRITY OF IMPORTED!!

Here is one reason why "old timers" prefer all reads. MSG READ TO PLC A FROM PLC B N7:0 Step 1 - PLC A sends to PLC B  - "I need your N7:0 data please send it" Step 2 - PLC B sends to PLC A - "Here is the N7:0 data you asked for and it's checksum" Step 3 - PLC A validates checksum, if OK Read Done , Else Repeat at Step 1.   MSG WRITE TO PLC A FROM PLC B N7:0 Step 1 - PLC B sends to PLC A - "I wish to write my N7:0 data to you, are you ready?" Step 2 - PLC A sends to PLC B - "I am ready to recive your N7:0 data, please sned it" Step 3 - PLC B sends to PLC A - "Here it the N7:0 data I said I'd send and it's checksum" Step 4 - PLC A sends to PLC B - "I have received the data and the checksum and the status is GOOD/BAD" Step 5 - If PLC B recevies BAD CHecksum Status thenr epeat WRTIE, else END Write.   As you can see the READ needs only two set data packets per data message while the write requires 4 data packets per data set message.   ANECDOTAL DATA I had an SLC 5/04 network using DH-485 to exchange data between four SLC 5/04 the DH-485 speed was 19,200 baud To send an integer from A to B, increment by one in B and send it back to A took anywhere from 5-15 seconds using MSG WRITES. Covnerted to MSG READS the timing went down to 1-3 seconds.

Thanks for posting the solution you found to work.  So often a suggestion solves the issue, but we never get feedback.

I would suspect something is wrong in your tag manager definition of the I/O Points.  I'd try type integer rather than type analog and also use address {plc]I:1 without the .o on the end.

You mention a Panelview so I must ask.  What model of Panelview?  You mention RSLinx but was it FTLinx Classic or FTLinx Enterprise?  Each one behaves differently.

RSlinx will need and EDS to know how to communicate with it/ The One here should work - https://www.anybus.com/technical-support/pages/files-and-documentation---compactcom?ordercode=AB6604 In Studio 5000 you'll either need to find an AOP for the device or use the Generic Ethernet Module and setup the Input and Output instances as defined in the EDS.

@pturmel Wasn't my choice , but the Almighty IT Gods have decreed we use Dell Servers and VMWare ESXI for virtual management. "When the plan comes together, I love it.  When it doesn't, Oh well that's life."

I'm setting up a new Blade Server which will host five production Virtual Machines.  This blade has eight 1 gigabit physical NICS available. I had originally planned 1 physical NIC per VM, but then I read I can NIC Team between the Blade and Cisco Switch Uplink.  NIC Teaming would give the possibility a VM could use more than a 1 Gig data flow if needed and if in the rare instance of a cabling failure the remaining NICs would share the load. This would seem like the best approach, but I'm asking if anyone has done this sort of thing with host blades? For Reference VM1, VM2 and VM3 are all part of an Aveva HMI Galaxy so would probably share three NICS as a team setup. VM4 is a Data Collector so I would give it two NICS. VM5 is the Development and maintenance PC so I'd give it two NICS. This would leave a spare NIC unused. Am I totally crazy??

Please clarify your question. 1. Do you want the PLC which controls the machine to hold it's startup until the user logs in on the HMI? or 2. Do you want the HMI to remain on the login screen until a user logs in and only then go to further screens?

Not to disagree venerable @pturmel but using CCW version 13 it says I can setup the 2711C-T6T for Protocol = Ethernet | Allenbradley SLC/PLC  and Controller Type = PLC5. So while you can't do RIO it appears it will do ethernet to a PLC 5. That Said @omar_zdn I don't have hardware or emulator to conduct proof of concept.

To add to what pturmel said, check with your local Rockwell Distributor's Automation Support Specialist as well.  They can guide you in how to approach Rockwell and get the Serial Numbers tranferred to you at your new company name.

Do a cross reference on testbits.4 and testbits.5 .. My money is on them being used in more than 1 place.  What I see doesn't match how the logic should work.

Is this a new install? If it is a failed unit you might want to consider Radwell or Rockwell for repair of yours.

The Omron NA5 runs an embedded version of Windows 10 from what I can see, so you should be able to load the Cognex Insight Viewer Application {VisionView}  and call it from a script.   We did this on Panelview Plus HMI with Insight 5800, but I've never tried it in the Omron HMi World.