All Activity

This stream auto-updates   

  1. Past Hour
  2. Today
  3. FX5U and FX5-ENET/IP

    Ok, but I need to do Ethernet IP communication. I want to learn how to configure it.
  4. FX5U and FX5-ENET/IP

    You can do the same with Mitsubishi just use the regular ethernet port on the CPU. Simple PLC communication settings.  
  5. Connect to PLC through GOT HMI

    First is the GOT communicating with the FX5 ?  
  6. CC Link Inputs (limited to 2 words?)

    Setting look good maybe it's on the slave side ?          
  7. Yesterday

    Hello PLC Users, I have recently final year project for my college. And i make PID instruction to control pressure and used VFD to control the pump. also used 4-20mA for Pressure sensor and 0-10V for VFD. But, i don't know how to use PIDAT instruction, please help me to understanding PIDAT Instruction, or do you have example ladder for my problem. Thank's   :)
  9. Gender Neutral Electrical Connector

    In all seriousness I like the terms Initiator/Responder for communications. I think the relationship is much more clear that way. Though I don't know how I could encourage others in that use.
  10. Last week
  11. Gender Neutral Electrical Connector

    This is not a CNN forum.
  12. Map Physical Input and Output to Word

    It will only work if I am using modular input and output . But I am using nx1p2. There is no channel as compare to Cp1e
  13. Industrial Controls Network Design

    The IT person and the plant controls person need to work together to resolve the issues and you need to see each other as peers working toward a common solution. Too often, the PLC person views the network as similar to the plant-wide electrical distribution network. Just plug in that cat5 cable and you're good to go. Too often the IT person views all packets on the network as being of equal value. So if that update of the state of the inputs gets lost, there'll be another coming along shortly.
  14. FX5U and FX5-ENET/IP

    I have two FX5 PLCs and I want to communicate using FX5-ENET/IP modules.  First PLC1 Eth/IP module IP: Second PLC2 Eth/IP module IP: I downloaded configurations using FX5-ENET/IP config1.png and config2.png   On both modules MS LED is green. I have also installed FX5-ENET/IP blocks - fbenetip.png. Now I want to create simple program to set boolean in PLC1 and read it in PLC2. There is function in PLC1: M_FX5ENETIP_Class1GetInputData_00A_2(i_bEN:= TRUE ,i_stModule:= FX5ENETIP_1 ,i_uConnectionNo:= 1 , o_uInputData=> D1000); And function in PLC2: M_FX5ENETIP_Class1SetOutputData_00A_1(i_bEN:= TRUE ,i_stModule:= FX5ENETIP_1 ,i_uConnectionNo:= 1 ,i_uOutputData:= D1000); 1. When I set D1000 to 1 in PLC2 it does not appear on PLC1. What am I missing? Error in U1\G6262 is H010F so TCP/IP error 2. What should I put as i_uConnectionNo? Should I set something in ExternalDevice configuration? 3. How should I set which bits are exchanged? Sorry for questions but I am a Siemens guy. Everything in Siemens is simple. You drag and drop module define memory area which is exchanged and then use addresses from that area in the program.  
  15. Ethernet/IP bandwidth

    I’ve decided to just try, in my opinion not alot of information is exchanged even by the vision system. If I run into any trouble I’ll be back. thanks, Andy
  16. Unclear on OTE OTU instructions used together

    Also I would right click on n15:201 and do a find all or a cross reference to see what all changes that value. To me it looks like there is some feed back from the drive or somewhere else in the code that tells it there's an emergency condition.
  17. Unclear on OTE OTU instructions used together

    Otu and Otl get mixed with Ote alot. Typically when I've seen it done it was a two fold reason.Number one was for Hmi software like wonderware when you build out motor control popups you usually use set instructios in wonderware to turn on a bit in the plc the otu will force the bit to unlatch in wonderware. Two otu will ensure you drop an Ote to a false state if they are properly placed in the program. We do this so the time in my plant. It works fine. Also using integers instead of bits works much better. It allows alot of data to be exchanged in a single word.
  18. @radouan For start to use SoMachine Basic you should use this e-learning.
  19. @Inc If you use Citect SCADA you can direct access to %M or %MW with it address such as %MW0. If you use others SCADA you can use Modbus TCP driver to connect them. Both of these methods not necessary to writing code.
  20. Joe, yes there is. 11 of them to be exact. I attached a picture of one of them if it'll help. Thank you for the info on the analog signals as well. I figured it would be something like that.
  21. Kinetix 6500 - ip address changing procedure

    I have a Kinetix 6500; I used Boot/P to install the IP Address. Everything was good until the power was cycled on and off. Lost the IP Address in the servo units. I was reading the Kinetix 6500: Procedure for Setting the Ethernet IP Address, but it shows RSLinx Classic Gateway and I am looking at RSLogix 5000. Need direction.   Thanks
  22. Micro850

    This might be helpful. 24 page tutorial to show how to use a timer
  23. Micro850

    After loading 12 and running it I re-read the salesman's email. He said 12 is coming out this fall. I hope that was a typo. I just sent him this (including his part): My salesman never has to wonder what I think.  They have a $450 upgraded that might have some value but not even Fabreeze can make fresh poo smell good so we'll see. It's a shame they rolled out new hardware with such a pile of crap for software. Software sells their product. Even worse, they just keep rolling the same garbage out.
  24. Micro850

    I seem to remember hearing that about every version...
  25. Micro850

    I finally got the software loaded (Version 12). I see where you are coming from. This is a perfect example of why I never adopted their little brick. They make something as simple as a timer into a kludgy mess. If I had spare time I'd be doing something better than working inside of their ratty software. Supposedly they are going to make things better with Rev 14.
  26. At least you have some time to figure it out. The Logix 5000 platform handles analog signals in a much cleaner way than previous systems. If you're using all 1756-xxxx I/O, you're good. Double-click on the analog module in the I/O tree of the project to open its properties dialog box and go to the "Configuration" tab. There you can set up each channel for whether it's voltage or current and the high/low signal and engineering ranges. As an example, we have a system where +/10V corresponds to +/-0.010". We would set the "signal" fields to 10V and -10V and the engineering units fields to 0.010 and -0.010. Then, in the tag database, find the analog module and look for something like "Local:5:I.Ch2Data" (example from the project I have open that has an analog input module in slot 5 of the local chassis). The value of that tag will be the scaled-to-engineering-units signal from the analog input. No need to use a COP or MOV at all, unless you want to buffer it or use internal tags to make re-wiring I/O easier. Are there any MSG instructions in the original PLC5 project?
  27. I have Allen Bradley SLC500 1747-L20A ser.B. On the electronic board, I have two EPROM memory chips. How can the processor read the second chip? Now reads only 1747-M1. And I need to read SLC500 FX1CPU. When I remove the first chip, the processor gives an error.
  28. This would have been a good idea, but at the same time I'm not experienced enough to really know how to make it easier to follow and I would run into these BTR, BTW, and MSG instructions and still not know how to handle them. Not to mention, even the guys I work with were laughing about how disorganized this program is. It's definitely been a tough first assignment. Good thing shutdown isn't until Christmas.
  29. I am absolutely not a fan of the migration tool. Logix is such an outstanding platform and migration just squanders the flexibility of the platform away. You end up with all kinds of "useless trash" in what could otherwise be a clean and easy to troubleshoot program.  I work in oil and gas so we have it a little simpler than other industries. DI, SO, AI, AO and some communication (Modbus) every now and then. I've used Message blocks to transfer bits from PLC to PLC of over the WAN (think 100's of square miles or more not building). With that said, I'd rather develop the program based on the needs of the process. That way I know what's "in the box". I start with an IO list, followed by a transmitter list, then alarm and shutdown list, then the cause and effect (all in one Excel sheet). Again, what we do in the industry that I work in is not hard (if you know the process).  DITTO!
  30. Load more activity