Hi,
I see from the pictures that the PLC from 2003 family, which is quite old an legacy / obsolete, but it’s still supported by AS4, as far as I know.
Automation Studio has a 90 days trial mode with a few restrictions but online communication is possible in trial mode - so it could be possible to read the error logbook from the PLC without having a license.
“Could” because of it was possible to program this 2003 family with Automation Studio, but also with PG2000 (a very old DOS based development platform). As we don’t know what exactly was used, unfortunately I can’t swear if it will work with Automation Studio (it could be that the logbook format was the same in both programming environments, but I’ve checked that).
Instead of Automation Studio, I think it would be also possible to use Runtime Utility Center to read out the logbook (also possible to use it in a trial mode, without license the online connection will only run 2 hours then you need to restart), maybe for a first troubleshooting this would be enough and would need less effort for download, installation, a.s.o.
If I interprete the status of the LEDs right, the system is in service mode.
From what you described about the machine, I think most probably there’s hardware defect on IO module(s) or a corrupt module in the PLC memory (checksum error or similar)… but in the end this is just a guess.
Important to know: the setup of all interfaces of the PLC could be changed by the project installed onto the PLC. That means, we don’t know how the RS232 interface is parametrized - the B&R default setting is 57600 baud, 8 databits, 1 stopbit, parity even.
The’re multiple threads in our community forum about serial connection, for example:
Best regards!