Paolo_911

MrPLC Member
  • Content count

    98
  • Joined

  • Last visited

Everything posted by Paolo_911

  1. QJ71E71-100 communication between PLC

    Nevermind, just found out that a Q is unable to communicate with the FX3U-ENET-ADP, but apparently it can communicate with the FX3U-ENET. I was given some code by Mitsubishi tech support to communicate via MC Protocol and will give that a try. 
  2. @Gambit We are also trying to communicate between a Q series PLC and an FX using MC Protocol. My question is, are we able to use the last function block you listed (...EthernetFX3QMC...) inside the Q series PLC program? We are hoping to capture (pull) data from multiple FX series PLCs using the Q as the master who reads the data. So is it possible to use that FB in the Q program to read data from the FX using MC Protocol?   
  3. QJ71E71-100 communication between PLC

    @kaare_t  I am trying to communicate via MC Protocol from a Q03UDECPU with QJ71E71-100 module - through ENET switch - to an FX3U-ENET-ADP attached to a FX3U PLC. The FX3U-ENET-ADP only allows TCP > MC Protocol communication as seen in my attached picture. This is the only reason I'm now trying to communicate via MC Protocol, whereas before I was able to communicate through fixed buffer from Q to Q PLC (using a S.JREAD instruction). How do I pull data to the Q from the FX3U ? Do I need a Mitsubishi MC Protocol Function Block to do this or can I still use Simple project > ladder logic instructions in GXWorks2? Using the settings you posted - Unpassive - how does the PLC know which destination IP address or port to go and receive the data from (the FX3U at 192.168.1.23 port 20512 in my case) ? Below are the FX3U settings I have set up to communicate through the FX3U-ENET-ADP:        
  4. Error Setting up QJ71MES96US

    The PLC and MES are faulted when trying to set it up. Any help would be appreciated. PLC Rack is as follows: Q03UDECPU (Slot 0), QJ71MES96US (Slot 1 & 2) and then QJ71E71-100 (Slot 3). Attached are photos of parameters, MES setup, and Error Message. I am not sure what I am doing wrong in setting up the MES module to match the PLC parameters. I imagine this is what is causing the error. Both the CPU and MES module are faulted with red blinking lights. I also was unable to change the Target CPU in the MES setting utility, even though I'm not sure I'm supposed to. I tried changing it to 2 (since the MES unit is the 2nd CPU) and when I change tabs, and go back, it is reverted back to 1, although still not sure this is the issue. I did "Write" the setting in the 'Online operation' tab, received a message saying the setting change was successful and then reset both the PLC and MES.   
  5. Error Setting up QJ71MES96US

    YAY! I got it to work with the QJ71E71-100 Ethernet card too now. Thanks Daniel for all your effort to help! 
  6. Error Setting up QJ71MES96US

    Thanks Daniel, I got it to work finally! The only thing I changed inside the MES CPU configurator settings was the Base Mode. I changed it from Auto to Detail, which I have no idea what that does. 
  7. Error Setting up QJ71MES96US

    I'll need to check on the link parameter error, but I doubt I still have that since I don't have the Ethernet card in the rack anymore. That would be great to have a multi-cpu configuration, but what do you mean change the 2nd CPU type? How do you specify the type of CPU?  I'm thinking it all has to do with setting up the MES module settings to match the CPU parameters, but I could be wrong.
  8. Error Setting up QJ71MES96US

    @collinsd70 - The above failed. I was successful in creating a program with just the PLC in the rack, but once I tried to add the MES module as a 2nd PLC, both the CPU and MES module faulted. I think I matched the parameters/settings, but it still won't work. The MES module takes up 2 slots in the rack, but I'm not sure how to specify that in the multiple CPU settings. 
  9. Error Setting up QJ71MES96US

    Thanks @collinsd70. I will try to run the rack with the bar essentials and gradually add modules like you said. That is great advice, thank you! When I get a chance I will upload the manual if I don't have much success in setting it all up. Thanks again. I will update later with my progress.
  10. Error Setting up QJ71MES96US

    Still no luck. Please Help! 
  11. Error Setting up QJ71MES96US

    I just noticed that I left a spare in Slot 1, assuming I needed to with the MES module taking up 2 slots physically. I will try moving the QJ71E71-100 module to Slot 1 in the PLC parameters and MES module settings to see what happens. I'll respond back if it is successful. 
  12. JP.Read QJ71E71-100 Channels

    Okay thanks. I wasn't sure about this, and wanted to confirm that I could try to step through or use a timer to talk to different stations through one channel. I didn't want to bog down one channel, but I know you're right that it is quite fast. Thank you for the response. 
  13. JP.Read QJ71E71-100 Channels

    I'm using a JP.Read Instruction and from my basic understanding I believe it communicates through a single channel. In the control data I need to specify word address of which channel to use. My question is, if I am trying to communicate with several Q03UDECPU PLCs (say 16 stations using the maximum 16 sockets of the QJ71E71-100 module) is it only possible to communicate simultaneously to 8 stations since it only has 8 channels? I'm trying to continuously read the data of 16 stations as fast as effectively possible, but not sure how to do that with only 8 channels to work with (I think the max channels is 8). 
  14. In a simple bench test, I am trying to communicate between two Q03UDECPU PLCs through a QJ71E71-100 module (both in Slot 0 on the racks) through a 3 foot Ethernet cable. I get an instruction error when I try to execute the GP.Read instruction. It doesn't give any indication why it fails, but the CPU faults out trying to execute this instruction. Any help would be appreciated.      If you want, I can attach both PLC programs. 
  15. Connect PC through QJ71E71-100

    I read through multiple previous posts on this topic, but still can't connect my laptop to a Q03UDECPU using GXWorks2 (Version  1.540N) through an Ethernet switch via QJ71E71-100 card. I can ping the ethernet card, but can't seem to connect at all. Here is my setup: Q03UDECPU with local QJ71E71-100 module (with I.P. address 192.168.1.10, Network 1 Station 1). The Q03UDECPU is CPU 1 in a multiple CPU setting with another EIP4CCPU module in the rack as well. TCP > MELSOFT CONNECTION ( x 2 , one for successfully connected GOT and one for my unsuccessful PC), and other TCP connection (For successfully connected MES module) PC I.P. address: 192.168.1.77 Subnet Mask: 255.255.255.0 Attached you will see all QJ71E17-100 settings and also connection properties with which I am trying to connect. What am I doing wrong?   
  16. Q to Q Enet Comm - GP.Read Instruction Error

    I believe I am using a crossover cable between the two QJ71E71-100 Ethernet modules, but maybe I need a switch in between (?) . My laptop PC is connected via USB to PLC1. I did discover my first mistake, as I had the network number wrong in my control data D2004. Now I don't get an instruction error, but now a Comm error which I need to look into. In a loopback test it appears that PLC1 is not able to communicate with PLC2.
  17. Connect PC through QJ71E71-100

    Oh! Okay, that makes a lot of sense. I was never sure, or never looked hard enough to figure that out (PC vs PLC side). THANKS A LOT !
  18. MES push or pull data?

    Wow! Thank you for the reply as it is all great information. I hadn't considered your last point regarding DRY, but that is very helpful in developing this! Speed isn't an issue as we are merely collecting a set of registers or different sets of registers for data collection purposes every couple hours on a given machine. It is a collection of data all at once. We may run into a scenario where we attempt to collect data on multiple machines at once, but we are more considered with reliability and ease of setup & future use. I think I decided we are going to pull data from each PLC via a master, once it is signaled to do so based on your last point about repetitive code change (DRY). I was also made aware that the MES module is limited in the number of devices it can connect to. I did not realize, nor do I quite understand what you mean by a limitation on sub PLC connections, but I'll cross that bridge when I get to it. Thanks! 
  19. MES push or pull data?

    Here is our setup, QJ71MES96US module in a PLC rack connected to an Ethernet switch. Also connected to this switch are several PLCs (Q03UDECPU) through an Ethernet QJ71E71-100 module with which we hope to collect data.  There are two different ideas floating around, one being that upon a trigger the MES pulls data from each PLC. So each PLC would need to be added as a device inside the MES workbench software. The second idea is that we place a CPU locally in the rack with the MES module and the MES only pulls data from the one PLC. In this second scenario each PLC, if possible, would push data through the Enet switch onto the one local PLC. I imagine this may be possible, but I'm not familiar with how. In another area of our plant this is the way we do it, but through a GOT, which I didn't want to do again. The reason it uses a GOT in that area to push data upon a trigger is because we are connecting to older PLC CPUs (A-series I think). My thought is that it would be easier to just pull data from all the several PLCs, even though I believe my manager and I.T. department are leaning to do it the other way, granted they don't know PLCs or PLC programming. We are all open to weighing our options though, so would anyone be able to chime in on advantages and disadvantages or even touch on simplicity to compare these two options?  
  20. Inconsistent MES-PLC connection

    Thanks guys, I am using the QJ71MES96US module, not CCPU. My IT department did send me the log which is attached here and I do have access the MES Workbench. However, my I.T. department does all the programming in there as I am unfamiliar with it. They have discussed trigger times with me, but I'll discuss it with them again to look at the scan and trigger times if adding an Ethernet module doesn't solve the issue. Thank you for all your guys' help though!    
  21. Inconsistent MES-PLC connection

    In the MES log files it confirms my observations that we are losing communication from the PLC to the MES US module on a daily basis, even a few times daily. The Q03UDECPU communicates with the MES module through its CPU front port through a 116TX N-tron Ethernet switch. If anyone can help ensure consistent communication without dropping connection that would be appreciated. I'd also like to know if anyone would share PLC program ideas to make sure I have constant communication with the MES module. Should I just use a simple timer that waits for the MES module to toggle a bit, then fault out if the bit isn't toggled within a certain period of time? It feels too simple to be robust haha. Anyways, any ideas on this communication would be appreciated.      I  should also note that I have an EIP4CCPU module in the same rack as the PLC that is connected to the same Ethernet switch looking at other Ethernet IP devices. I wouldn't think this would be causing traffic (due to fast RPI?) or issues in the Enet switch, but I figured it is worth mentioning in case anyone has any reason to believe this is an issue. 
  22. Inconsistent MES-PLC connection

    In a nutshell, I'm going to try using the Ethernet module QJ71E71-100 instead of the front PLC port and let you know how that works out to resolve this poor connection between the MES and PLC. 
  23. Inconsistent MES-PLC connection

    Thank you both for your reply, and I apologize for my delayed thanks. The MES module is on a separate rack, and communicates through an Ethernet switch to the FRONT PORT of the PLC on another rack. I am not sure what you (kaare_t) meant by separating networks, but I believe EthernetIP is an Allen Bradley network protocol. As for your other question, when I say MES US I am referring to the QJ71MES96 module. NeilBDSSA I was NOT aware the Mitsubishi recommends AGAINST using the front port for anything other than light work. I am in the process of purchasing an Ethernet module to place in the rack to see if that solves this issue, which by what you said it most likely will. I'm not sure if the MESIT module is faulting out. How can I tell if the module is faulting out? Currently we don't have anything monitoring the MESIT module in the way of programming or anything, which I'm sure is bad. We are new to the MES system and I had posed the question of how to monitor it through the PLC, but didn't get anywhere with it. Perhaps you could help in this regard as well so we can keep a close watch on its status and alarm/fault if need be. I don't believe the Ethernet switch is a managed switch though to answer your other question. The only way we knew we lost connection, was that we were having issues and looked at the MES log file. I'm not sure how my I.T. department who handles the MES programming got this log file though. It just stated that it lost connection with the PLC, basically. 
  24. Sync PLC Clock slow by 3s

    I synced the PLC clock in a Q03UDECPU to my PC. It updated in the software and then I executed it (synced the PLC to it). However, when I close the settings and go back, the clock is slow by 3 seconds consistently. Why is this? How can I accurately sync the PLC clock to my PC with exact seconds? Anyone else experience this or is this even possible? Another way I know the PLC clock is 3s slow is because I set up a SNTP server from the PLC which the GOT looks at. Again the GOT clock is 3 seconds delayed from my PC. This brings me to another point, in which I turn on the SM1028 bit (clock read request), but nothing turns on in SD1025 to SD1028 as the manual says it should. What am I doing wrong that I can't read the PLC clock into registers?  
  25. Sync PLC Clock slow by 3s

    Actually, I just had a thought. The PLC is actually connected to an MES US interface module through an Ethernet switch. We are going to look into whether or not we can sync the PLC and GOT time to whatever time the MES is running. I just don't know if the MES US module can broadcast its time as a SNTP server where the PLC and GOT can read from.