Bryll

MrPLC Member
 View profile  See their activity

  • Content count

    349

  • Joined

  • Last visited

Posts posted by Bryll

  6. Posted

    Is the run switch on the CPU set to run mode ?

    Do you have any memory card in the CPU ?

    Is the "STOP" mode led lit (Yellow) ?

  8. Posted

    I'm not yet a GOT user and don't know the possibilities with these panels.

    I am normally using Beijers HMI.

    When the panel is connected to the programming port of the PLC can I access the PLC from the Ethernet port of the HMI.

    I activate "Transparent mode" in the panel and use a handy software called "Serial IP" to redirect the RS-232 at the PC to the Ethernet port.

    I'm quite sure you can do the same with a GOT panel.

    You can read about the software at www.tacticalsoftware.com

     

  9. Posted

    I0.0 at the input of a "TON" with "T#2S" as time delay. The output from the "TON" to a "TOF" with "T#3S" as time delay. Connect Q0.0 to the output of the "TOF".  
    2 people like this

  11. Posted · Edited by Bryll

    Is the I/O unit the last one in your rack? If you have any I/O units to the right of the not working, are they working ? It can be that someone forgot the rack connection between the modules when they where installed. Another thing, is the CPU in run mode ? No fault LED's on the CPU lit ? What software are you using ? Edit: Sorry, just noticed it was an old post. Suspects that the problem is solved by now

  14. Posted

    The CPU is not blank. What I use that can control the ENET unit is: "FX3UModbusTCPClient" from the library "FX3UModbusTCPClient_V210". "FX3UModbusTCPDeviceRange" and "FX3UModbusTCPServer" from the library "FX3UModbusTCPServer_V210". These libraries was supplied by Beijer. Everything in my code is according to their examples, why change something that's supposed to work

  15. Posted

    Just finished checking the FX3U-ENET unit. Laptop -> SC-09 -> FX3U, not possible to connect to the ENET unit. All LED's on the unit indicating normal operating status, except no action on RX or TX. Not possible to ping the unit, and the HMI can of course not read anything from the PLC. But, it started up normally after a reboot. What do you guys think, some external problem or programming problem ?

  16. Posted · Edited by Bryll

    I agree with you guys, and I am a bit suspicious about the feedback from the end users. They will never admit that they tampered with the system, just blame the programmer. The FX3U is the system we use quite often, and experienced just these two issues with the FX3U system during the last 8 years. I had earlier one FX3U-ENET that retired itself, and now perhaps a second one. The first one did lit up its error LED's, this second one not. Will check the second one today to see if it's broken. The replacement was received by the customer yesterday afternoon.

  17. Posted

    Inntele, I hear you, and I'm willing to agree with you. That was my first guess too. Was able to check all the system memories for the Modbus communication on the second one, had a bit more time on that one. They had the values and statuses they should. Got another one yesterday afternoon with problems. This one stopped communicate with the HMI and the distributed I/O connected to the ENET-P502 unit. The ENET unit indicates open ports to HMI and distributed I/O. No error LED at all is lit. I could access the network remotely via a connected laptop and Team Viewer and ping the HMI and the I/O unit. The PLC don't answer at all. I double checked with the service guy at the plant that there was no error led lit. This unit has been in operation 24-7 for the last four years.

  18. Posted

    Inntele, On the second unit, yes. But the first unit mentioned stopped executing the entire program. The PLC was in run mode, run LED lit and GX IEC dev indicated the same when checking online too. Didn't have the time to check to much, the customer was jumping up and down when waiting for the equipment to start up. He got hold of me at an airport on my way home.

  19. Posted

    Anyone here that noticed that the FX3U can stop executing some parts in the code ? I'm now up to two systems that stopped executing the code. (FX3U 16MT/DSS + ENET P502 + 485BD) First system stopped when an electrician tampered with the main power switch when everything was up and running. No errors or fault to be read from the PLC. Power and Run LED are lit. I was able to access it via a remote connection and go online. Second system stopped its Modbus communication (FX3U-485BD) on channel 1. Everything else was good. No one touched the system, at least they say so. Mitsubishi Modbus communication blocks was used for this function. No errors or faults in this one either. I had to reload the program to the PLCs to get them up and running again. Didn't even recompile before I reloaded the software. They are both running at the moment.

  22. Posted

    You should not have to toggle the run/stop selector with the OB's added to the project. The SF led will be lit, but the CPU will continue to execute the code. It will prevent the CPU from stopping, but will not take care of the problem causing the I/O error. You have to write some code into the OB that is called when the error occurs and read the diagnostic info from the I/O to know what kind of I/O error you have. The question was: Does the CPU still enter STOP mode when your I/O error occurs ?