I’m not seeing anything too out of the ordinary in these logs. It looks like the PLC has been restarted a lot, but I also know you’ve been restarting during your tests. I also see some warnings about loss of nonvolatile memory on some of these restarts. This can happen if the PLC is shut down due to a watchdog issue, but it’s hard to say for certain.
It’s still not very clear to me how reproducible this issue is. From your first posts, it sounded like you couldn’t get the PLC to boot at all. Now it’s able to fully boot and open the SDM. It’s also not clear if this is related to the software or the hardware. Here are a few suggestions of things to try:
I still think it would be a good idea to load a blank Automation Studio project onto the PLC. You can use a different CF card for this if you’d like. But create a project, add your CPU, and then just transfer it. If it boots and runs for a while, then you know that the PLC itself is probably okay.
The operating system is booting now, which means that the software itself isn’t likely to be corrupted. If the files on the CF card are corrupt, then the PLC will boot into a Diagnostic mode and Automation Runtime won’t start. However, there could still be something in the project that’s sending it into Service mode. The biggest clue I have right now is the hardware error on the main SDM page and the watchdog errors in the logger. Do you have all of the modules configured in the project attached? Is Module Supervision set to ON for any module? Try turning this off for every module and see what happens. If a module is set to be supervised, and is not attached, the PLC will go into Service mode.
I’m not sure if all of those restarts were caused intentionally or not. If not, I suggest checking the power supply to make sure that it is providing a consistent 24 VDC. If this power supply dips, that can cause the PLC to shut down. Weird power supply fluctuations can also cause a loss of nonvolatile memory. Alternatively, you could connect to another power supply and see if this makes a difference.
Regarding the last picture of the PLC, the LEDs look normal to me. The Eth light is solid green when a connection is made and flashes when there is traffic. So a solid LED just means that there is no traffic on the network.
Do you have source project? if so, download project with all tasks disabled. If PLC starts in normal way, then download task by task and check which one cause you an issue. So basically similar advice like from Marcus, but in short
On the other hand, I can tell you that I was testing all day yesterday and something similar happened to me, like today. My PLC has a harder time starting up than normal but sometimes it does, but yesterday after starting up and everything was ok to test it I decided to create a blank project with the sdm activated and I transfer it with a new cf card, everything new, and what is my surprise that after making the transfer the plc loses the ethernet traffic, it remains fixed and I can no longer connect via sdm, I disconnect it from the power supply and reconnect it and this is when it starts doing crazy reboots without being able to boot.
I don’t understand why it connects easily when I let it rest for more than 12 hours and when I try another new CF card with a blank project here the Ethernet connection stays fixed without traffic, and then neither turning it off nor connecting it causes the plc to start It keeps doing reboots, until I let it rest the next day.
The external modules cannot be because right now it is missing 2 ABB frequency converters that should be connected by POWERLINK (IF3) and I do not have them here, however my PLC starts, also in the installation this does not happen so that the PLC does not start. You need the drives connected, another thing is for the project to run then program alarms go off.
And right now these drives do not exist and my PLC has booted.
If you would be so kind as to connect to the SDM with the IP 192.168.250.10
in case you manage to see any critical errors.
This IP is not public and thus can not be reached from anywhere but within your own network. I also recommend not to put a PLC into the public internet due to security reasons (and your IT dept wouldn’t let you, anyway, probably).
after making the transfer the plc loses the ethernet traffic
Did you maybe forget to assign the IP address again in your new project? Compare Right click on the ethernet interface of your PLC, Configuration, your old project will have set something there → your new project needs the same settings in order for you not to loose connection when transfering and the IP address to stay the same
BR
Edit: Please do not post 3 times in a row but click “edit” on your post and amend the changed text. That way it’s easier to follow
Right now that I have everything right, I’m sure I’m trying to load a blank project with a new CF card and this is where my PLC already disconnects from the Ethernet.
If I reconnect with the previous card that works correctly as it does now, a sequence of continuous startups begins without being able to boot definitively.
It looks like you did not read the essential part of my response: You need to set the ethernet settings in your new blank project in order for you to have the same IP as before and to be able to connect there again
Also adding this again since the post frequency is quite high and my edit probably got lost due to the quick reply: Unless someone already replied to your message, please edit your posts instead of posting several times in a row (forum, not a chat)
In my new blank project with only the same hardware I make sure to put the same IP, I am totally sure that the IP is configured.
You are right that my IP is for a Local Network, so it does not harm me to publish it, the Internet does not exist in the installation, it is a local network.
I’m making it public here to see if anyone can help me see any errors.
I’m making it public here to see if anyone can help me see any errors.
That’s the thing: Just posting your internal IP doesn’t mean anyone can access it from outside of your network. Outside from telling you that the IP has a valid format we can’t help you with anything there - we can’t connect there nor do anything else (and AS would refuse an invalid IP address anyway)
Please post a screenshot of the old projects ETH settings and of the new ones
I can’t send anything from the original project because we don’t have the source codes, but we do know the IP, that the SDM is activated and that the VNC server is also configured for Panel T50, only that we don’t use the panel, it is uninstalled and we connect with REAL VNC server with the same IP as the T50 Panel, perhaps this is why we disconnected the Ethernet cable on the PC by mistake while the project was running and this could have created a conflict.
Here I send you a photo of my new project without configuring, only IP the SDM and the hardware.
Let me tell you that I only needed to disconnect my device from Ethernet (not turn it off) and when I reconnected to Ethernet my device no longer had any traffic. Then I tried to remove power and restore it and my device keeps restarting and does not start.
Right now I can’t even transfer a blank project. All the time rebooting.
If you’ve transferred a project with those settings, you should be able to browse and connect via Automation Studio as long as your PC is on the same subnet as the PLC. I notice that you’re in simulation in your screenshots. You won’t be able to connect to the PLC while simulation is active, so make sure to turn this off before connecting.
I think that this thread is getting a little hard to read and we’re reaching the limit of what the Community is able to do for you. From what you’ve shared so far, I can think of two possible problems. Either:
Something in the software (corrupted files of software bug) is causing the PLC to restart or otherwise lose communication, and/or
The hardware is damaged and needs to be repaired
If (1) is to blame, the PLC should work okay with a different project. If (2) is to blame, the problem is more likely to occur regardless of what project/memory card is used. However, without a clear, consistent, and repeatable test it’s very hard to narrow down where the issue might be.
I recommend reaching out to your local B&R contact who can provide local support and hardware repair if required. It would probably help to have a B&R expert take a look at your PLC in person or guide you through some tests you can do remotely.
I agree with Marcus. Please get in touch with support if needed. If you have any new questions, please create a new topic containing only information related to the new issue. This original topic is now closed because, as mentioned earlier, it is difficult to follow the complete history.
