- Citect kernel general tab serial#
- Citect kernel general tab driver#
- Citect kernel general tab software#
- Citect kernel general tab code#
Citect kernel general tab code#
I changed the Citect Tag location information to N7:30 (the next unused N7 word) and also changed the PLC code accordingly. I interpreted this as though Citect was unable to read N7:27 from the PLC based on the second line. I explored the Citect Kernel and was able to find the following error message recurring approximatly every 15 seconds while attemping communications: Thankfully the machine is back into proper production!!!:beer: OK, so after another day on site, I feel as though I've made some progress, but it's also left me with more questions.
Citect kernel general tab software#
Have at look at Archies Post in "Free AB SLC and Micrologix Software Utilies " you may be able to use it to test comms to slc
Have you (Can you) tried different hardware (com port ?) My guess would be try to proove the cable can actually communicate serially but if you only have one slc then that will difficult as citect needs different protocol setup to rslinx.
I've been though the Citect help files, they helped me get to where I am now, using the kernel, and observing the KE500 driver.ĭon't know for sure but maybe Citect gets too busy retrying bad tags and runs out of time. I've checked the cable only by metering it. I'm going to go though the offline tags tonight, and see if I can find any addressing issues.How might this effect the communications? Does the PLC write back a bit or something once it's accepted a value, and Citect is waiting for this confirmation? Regardless, I'm checking into it. I will try the new project idea tommorow, and see if I can find any minute differences. I've scoured () and wasn't able to find a users forum.I'll go check again though. I have attached screen dump showing relevant fields in related forms maybe it will help. If you havn't already have a look thru Citects help, from inside Citect Explorer select Help then Citect Help Topics then IO devices then browse down to your PLC type.
Citect kernel general tab serial#
When you say you have checked the serial cable how ? can you confirm that it works with RSLinx ? the N7 file in PLC only goes as far N7:100 and Citect has some tags addressed above that say N7:110 ? Create a new project in Citect and use Citect's wizard's to create the IO device etc if these work maybe you will be able to spot some small difference.Ĭould it be that someone has added some tags to citect that don't exist in the PLC eg. When you seeing more and more does that mean that the coms failure was gradual and that for a period of time you were getting a mix of good coms and errors ?
Have a look at () you should be able to find your way to the Citect Users List from there. I'm at the end of my rope.thanks for listening to my rant.maybe you'll have some ideas!! We're running Citect 5.21 SP-F.ĭoes anyone know of a Citect user forum, or any other sources to go to?
Citect kernel general tab driver#
I've tracked it down to the KE500 driver in Citect using the Citect Kernel functions,I can see the device error count indexing as the communications fail, but I don't know what to do/check from there. We've tried: Re-installing the Citect program, Reinstalling earlier "back-up" versions of the program which were running fine, Re-installing the entire Citect software package, Reinstalling the entire OS and software, Reinstalling the entire OS on a seperate PC, Trying a new SLC processor.all with no avail. Recently, I've been seeing more and more #COM faults in the Citect HMI screens, it's now at the point where it has inhibited production.
They are (were) communicating successfuly for 3-4yrs. I am working on a machine running Citect 5.21 and a SLC503 PLC.