WattUp

MrPLC Member
  • Content count

    35
  • Joined

  • Last visited

Community Reputation

6 Neutral

About WattUp

  • Rank
    Sparky

Profile Information

  • Country United States
  1. I appreciate your help. That was the same conclusion I had come to but had hoped someone might have a better idea. 
  2. 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. 
  3. 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. 
  4. Well that was a nice start. Is there a way to convert the Local Label Tags back to normal comments? Maybe export /import option? 
  5. 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? 
  6. 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. 
  7. Best 24VDC Power Supply

    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.   
  8. Looking for job

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

    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. 
  10. Using Ethernet As I/O (Q Series)

    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. 
  11. Using Ethernet As I/O (Q Series)

    Second Manual here CV-X_MELSEC.pdf
  12. 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
  13. Version 1.0.0

    12 downloads

    These are the 2 manuals i used to get Ethernet I/O working between a Q series PLC and a CV-X camera system. 
  14. Using Ethernet As I/O (Q Series)

    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
  15. Using Ethernet As I/O (Q Series)

    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