WattUp

We have a machine that was written many years ago as a GX project file, and if I understand correctly then, the PLC and HMI code are linked through a parent project navigator file.    In the years since, this file has been broken apart somehow, and we are left with a non-simple Ladder file using TAGs and a HMI file. The issue with this set up is that any changes to the PLC code, can/does result in addresses moving and the HMI breaks.    Does anyone know a way to convert this code back to a normal simple ladder? 

This program is using an EJ71 Ethernet card to handle the communication. When I did this using the built-in ports I had issues with Ethernet timeouts.   My Mits rep told me that the CPU prioritizes itself over networking and I have had no such issues since using the EJ71 so i guess I believe him.    The built in port is talking to a GOT1000 via MC Protocol. That is why you see that there. 

I have attached a program I used to send data between 2 Q series over Ethernet. Take a look as see if that helps.    EthernetLink.gxw

I appreciate your help. That was the same conclusion I had come to but had hoped someone might have a better idea. 

You are correct in how the Navigator system is supposed to work.  Every address change is linked through the project files and reflected at the HMI.    Our current system does work, but our entire Maint. staff is afraid of it because they have been told for years to not modify this code. Now as the system is aging and we are seeking to modify the process, but in order to do that this issue needs resolved.  What you are suggesting about reading the file and punching the comments in manually has crossed our mind, but this program is approximately 8 times larger than any other programs so that would be a large scale task. 

This program is about 70% local labels and 29% global labels. 1% global device comment.  I would like a way to get the Labels pulled out and tie it into the current device as compiled.    Since the navigator link has been broken, any compile of the PLC code can/does change the device addresses and then the HMI is using the wrong addresses. 

Well that was a nice start. Is there a way to convert the Local Label Tags back to normal comments? Maybe export /import option? 

I started with the Mike Holt Essential NEC Rules.  I love the way he breaks the rules down and the illustrations have been invaluable countless times. I once had to prove to MGMT that they couldn't store things in front of a panel. Citing regulations would have been tedious, but a quick glance at the pictures and they were convinced. 

Second for the Omron S8V* line with the screen. I prefer those bc the AMP readout eliminates any doubts about power supply overloading. Unfortunately I think they cap that model at 10amps.   

Check for openings at Toyota. I know its a bit of a drive, but a friend used to commute from Toronto to TMMC

In the ASCII Input setup screen, adjust digits to 10, to be enough for your string   Attached is a 40 ASCII Charactor display I use to display a parts barcode. 

No problem. Sorry for the delay in reply. I couldn't find that manual with the command codes, and that was pretty important to getting this running. 

Second Manual here CV-X_MELSEC.pdf

Mitsubishi PLC Ethernet I/O to Keyence CV-X Camera View File These are the 2 manuals i used to get Ethernet I/O working between a Q series PLC and a CV-X camera system.  Submitter WattUp Submitted 07/27/17 Category Manuals, Tutorials

We have 4 of these camera setups in our plant. the first 2 were done using physical I/O. It works but it basically takes a dedicated I/O card to handle it. This Ethernet I/O option has been great, plus it is easier to deploy now that we have the examples.    { I broke the attachment section, Attachments to follow} The CV-X Melsoft manual shows you how to link the two together ANNEX 3 of the Eth_IO PDF attached has all of the command codes you will need to send from your PLC. I also have a minimal program that was my first camera<->plc logic.    CV-X100_ETH_IO.pdf ToxCameraSetup.gxw

I have used a Q03UDV and a Keyence CV-X series camera using only Ethernet I/O to control it.     If this is the camera system you are using, I will post up the guides and files that I used

Solved..    Discovered the issue only happened when using a Control Power Keyswitch and not the full panel disconnect. This made me look into the key switch circuit, and I found that the QS PLC had power maintained, however the safety I/O module did not, hence the stop condition because communication was lost to the I/O

We have a brand new system that is using a QS PLC for the safety controls. This is new for us as we mostly use programmable safety controls or relays.    Well Our integrator left yesterday (without showing me the final process, long drama filled BS)  so today I begin testing the system and the first thing i noticed is that from power-up, this safety PLC is coming on in STOP mode.  The only way to recover is to open the live cabinet, and manually switch the sCPU to stop/reset.   This seems like a pretty dumb oversight that I am hoping can be corrected easily. 

Are you monitoring the PLC through the HMI? 

I believe proface has an alarm table similar to the Mits GOT series displays. You could then create a table with all the messages you would like to display and call that screen via the button. 

Pictures for more info.  Any one have any ideas at all??    You see the verify was matching on all code, comments and param, but data is different as expected.  If I do a data pull from the PLC it is still mismatched because of the SM*** timers states.   

GX Works 2 1.54n Q03UDV. Simple ladder.    I have been writing this program from scratch, and it has been working very well for a few weeks now. When I start Monitor write mode, i get a verify error.   Running the verify shows all programs, parameters, and comments match. But it's showing device data doesnt match "destination only"   This makes sense to me though since the device data would constantly be changing. So then i start monitor write mode, ignoring the error and while most things look correct, timers and register data does not update.    This has happened 4 times in the last week, and each time something different has gotten monitoring to work. I have tried deleting all PLC and writing fresh. Starting a new program and reading down from the plc. And just about everything else I can think of.      EDIT: I have now tried from a different computer and confirmed the same issues. 

I an seeking guidance on how to link two mitsubishi PLC over Ethernet and have them pass bits/words between them.  PLC 1, Q03UDV built in port  ---- GXWorks 2 v1.54N   192.168.1.39  (QJ71 in slot 1 is also available if req'd) PLC2, Q02H with a QJ71 Ethernet card in slot 2.  Same GXworks2   192.168.1.35   I know with a modbus or CCLink setup, there is a place to declare the buffer > X/Y parameters, but i have found no such parameters for the ethernet connections. I found 1 document describing the JP.Send instructions but I have not been able to get that to work from the example.    any help would be greatly appreciated.     

PM'd