WattUp

MrPLC Member
  • Content count

    51
  • Joined

  • Last visited

Community Reputation

13 Good

About WattUp

  • Rank
    Sparky

Profile Information

  • Country United States
  1. I personally just use BMOV , MOV.  I have seen maint techs get confused by FIFO before but setting it up with BMOV and MOV they seem to understand.    BMOV D1000 D1001 K10 MOV D10 D1000
  2. Pointer In GX-Work2

    If you are hoping to use it like an index pointer those are Z.   MOV K10 Z1 MOV D0Z1 D1000   :: Will move D0(+10)=D10 > D1000
  3. Standardize PLC code for new machines

    I think i am going to create a similar solution to @Mitsm83, a spreadsheet with addressing scheme and a small sample program of how we like stepper logic and faults. Perhaps an HMI design template also. 
  4. Standardize PLC code for new machines

    You were understanding correctly, I am looking into creating a basic PLC example to give to suppliers for them to base off of.  Our machines are all 100% custom applications, developed by integrator both in the US and Japan.  The integrator is available during the initial machine start-up, but then myself, and my Maint team are responsible from there.  Initially this came up because we had a new supplier that felt like they were trying to show off by making code overly complicated, either that or they had a very limited knowledge of the Mits functions.  So we thought we would create examples that could be used to build on; basic stepper logic, faults, and even some standard HMI design    
  5. Standardize PLC code for new machines

    That is what we have done in the past, but I was hoping to build a better process for going forward. 
  6. Standardize PLC code for new machines

    Thank you so much for sharing your experience. This is exactly what I am hoping to achieve 
  7. Standardize PLC code for new machines

    This is exactly what I am looking for.  Do you have an dedicated example program that you send also? One that is mocked up for all your spreadsheets?
  8. Using Ethernet as I/O

    No problem.  I know it took me a while to get this running the first time, so I am happy to pass that along.    I am so used to being a quick Google search away from any answer, but this industrial/PLC/Robot stuff just isn't all there yet.  If i want to tear down a 1960's washing machine there is a youtube video of it, but getting a MITS to talk to a Motoman robot.. ugh.. 20 hours of research. 
  9. Using Ethernet as I/O

    Every model number has its own program.  Its a 4 step process to change camera jobs.  1. Set which SD Card the job is stored on [MOV K1 D102] 2. Set what job number you want to load [MOV SD200 D104] 3. Set camera Command code for job change. [MOV K24 D100] 4. Trigger Camera commad [Set D2.0]  
  10. Using Ethernet as I/O

    Those are the two that I used to get it working. I did a little searching and found you this though.   Edit: I guess this is still serial.. I know i had an ethernet one.. CV-X_MELSEC-Q_PLC-Link.pdf
  11. This is more general topic, but I think the brand specific forums get a lot more traffic. And since we only have Mits PLC in our plant this fits best.    When you are quoting a new machine, do you have some form of default PLC program that you can give to suppliers to use as a base point?  Or do you simply learn the program as its given to you for each machine?   Also, how detailed of a standard parts list do you have? This is another part of the process I find our plant to be severely lacking.
  12. Using Ethernet as I/O

    These 2 manuals should get you going.  CV-X_MELSEC.pdf    CV-X100_ETH_IO.pdf
  13. GX works 2 - Special Relay (SM_ _ _) for a 0.5sec Pulse

    Attached is a guide to all the SM _ _ _ Relays.   SpecialRelayList.pdf
  14. I've been stuck in Florida from Irma but finally tried this on my project.    Unfortunately, i get this error message after step 1c.  I am offline with the PLC for testing though, so I am not sure if the error is because of that or from the project already being broken from the Navigator program. 
  15. MELSEC Communication

    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.