Vijeo Citect IO server issue

[Oriphiel]

Hello Everyone,

This is my first time posting here so I hope y’all can help me. I am an IT Specialist with a company that has very old equipment and software that runs the spinning machines.
The SW is Vijeo Citect v5.21 G.
Hardware:
IBM Personal Computer 300PL
193 MB RAM
******* RocketPort 8 PCI (parallel port connection) INT 9
AB 1784-PKTX DH+ Passed testing

When Citect starts At Status: IO server
Error: Cannot allocate memory, Interrupt Board ‘KTXD1A’ at adresss 0xcc00 (yes address is spelled that way
Error: Cannot allocate memory, interrupt board “KTXD2’ at adresss 0xcd00
Error: Board ‘KTXD1A’ is undefined
(The above 3 errors cycle 2 times)
Error: Error 0x21 on opening ‘KT1_Port1’
In the hardware alarms signal I receive M1PLC1 PLC Server I/O Device off-line, cannot talk
J52_3rd_FLR Server I/O Device cannot talk.
I also get the occasional Citect Divide by Zero error.

I don’t know if this is common for the Citect application but I am getting Red #COMM Errors.
Current allocation of virtual memory is 1000MB.
I am assuming the IO server is where the issue is. J52_3rd_FLR is number 5, address 1 Protocol MODBUS Port name RP1_P4_COM7

M1PLC1 number: 9 Address 1kt:0,11 , Protocol: ABTCP5 Port Name: KT1_Port1 Comment j54 Allen Bradley PLC5, Linked False Link database type Concept Ver2.1 ASCII file, Automatic Refresh of tags : FALSE

Basically they want this up in 48 hours. I have never worked with Citect and the PC is a Frankenstein of the original PC and the backup that had a bad motherboard.

I am not familiar with this software at all and it wasn’t working before I got here. We need to be able to change the recipes and speeds of the spinFinish which is not possible.
Any Help would be welcomed and if it cannot be fixed I will need to find a replacement but I feel this is a configuration issue and I do not have any documentation on how this should be properly configured.

 

[andrewf]

Hi Oriphiel,
I'm a bit short on time at the moment a bit like yourself. But it seems your in a bit of a situation and nobody else has jumped in so i will see if i can help you out.

Ideally i would like to grab a backup of the project as that would be quickest to have a look at but if not i can normally work out whats happening by grabbing a few different files from you but it will be a bit back and forth. Send me a private message if you want to send me the entire project or just reply if you would rather not.

Also could you clarify a couple of things.
What OS?
A 1784-PKTX DH+ i s mentioned in the hardware list, can you confirm you have one of the below linked cards in the PC and there is a blue coloured cable with 2 cores and screen connected to it?
https://www.rexelusa.com/usr/Root-C...nel-Card,-DH+,-RIO-Scanner,-and-DH485/p/59545

 

[BobB]

Does your customer have support? If so contact Citect support - they are pretty switched on usually.

 

[ShaunCroman]

A few questions

Bob

Just a few questions

When did the issue start?
Was any work done on the system before the issue?

Are the #comm errors on every field or just those relatining to that particular IO channel?

regards

 

[Oriphiel]

HI Everyone! Thanks for the info here are the answers to the questions
O/S Windows 2000
Q: A 1784-PKTX DH+ i s mentioned in the hardware list, can you confirm you have one of the below linked cards in the PC and there is a blue coloured cable with 2 cores and screen connected to it?
It is a dual port with CH1 and CH2. There is a blue cable. One light is on the bottom one.
Q:
When did the issue start?
A: Before I was even hired here, in October. But no one can tell me what exactly was the issue then. Then there was a shutdown and the CMOS battery was dead. I have since restored a backup I found from 2006 but that is when I got the errors.

Q: Was any work done on the system before the issue? I have no Idea.

Q:Are the #comm errors on every field or just those relatining to that particular IO channel?
A: There are comm# errors everywhere.

 

[ShaunCroman]

Oriphiel

Is it the PLC or the PC that the CMOS battery went on?
And was the backup for the citect project or the PLC?

It just seems that 2006 is quite an old project and that there are likely to be a number of ,perhaps, documented and undocumented changes since then.

I would suspect checking out the PLC in the first instance - and then the card

if possible get the last good known citect project and PLC project. You may have to try the last systems integrator that worked on the plc as they may have kept a copy.

If the 1784 card has moved to a new pc- is the operating system the same? and is the card recognised in device manager? - as it may be that it has lost its settings, probably not- but citect is not communicating with it for some reason.
I am guessing given the age of the install it was running either Windows 2k or XP or even NT(hope not)
.

The divide by zero errors are probably coming off derived tags within citect itself so they should rectify when coms gets re-established


regards

 

[Oriphiel]

Is it the PLC or the PC that the CMOS battery went on?
PC

And was the backup for the citect project or the PLC?
The Backup was for the Citect Project
If the 1784 card has moved to a new pc- is the operating system the same? It was moved and replaced with the backup PC
is the card recognised in device manager? Yes and it passes the Diag test. -
I am guessing given the age of the install it was running either Windows 2k or XP or even NT(hope not)
Windows 2k Pro


I will check on the PLCS and let you know.

 

[V0N_hydro]

Q:When did the issue start?


A: Before I was even hired here, in October. But no one can tell me what exactly was the issue then. Then there was a shutdown and the CMOS battery was dead. I have since restored a backup I found from 2006 but that is when I got the errors.

Q: And was the backup for the citect project or the PLC? It just seems that 2006 is quite an old project and that there are likely to be a number of, perhaps, changes since then.


A: The Backup was for the Citect Project

I hope you took a backup of the October 2018 citect project before restoring the one from 2006. I would go back to that most recently known to work project and start troubleshooting from there. As Shaun has pointed out there could have been a lot of changes since 2006 that will be lost otherwise.

 

[sigmadelta]

These pieces of information could be of use:

http://proscada.ru/ctkbase.en/articles/q3801.html

http://proscada.ru/ctkbase.en/articles/q3181.html