lostcontrol

Yes, this is correct. What I did, was set it so that the screens that were required to be displayed, had their W bits stepped through automatically every so many seconds. This may/may not be suitable for your application, but sounds like you have a plan! One thing I did just notice, that if the required bits were set, and the up/down arrows buttons are pressed, then a blank screen was triggered, which was a bit odd. You could possible add some code in that 'resets' the W area every minute, then re-enables the screen to be displayed, then sets the extra bits for the other required screens. I may modify my cycling code, to stop every so many minutes, to allow for manual cycling/monitoring, then cycle automatically for a minute or something. Could possibly do this off an input, or off 1 of the analog adjusters, just to allow for complete flexibility. FYI, I am displaying values with decimal places as well, so there is a bit of BCD, ASC and MOVD instructions involved, but I am sure that this will not be a problem for you (based on your name!!) I hope this helps some more.

It sounds like you are doing a 1-shot from CX-Supervisor to the PLC, ie. at 8:00, turn on HR10.00? Is the time setting variable from CX-Supervisor? Why not make the time value setting writeable to the PLC, then PLC code (which is evaluated every scan) can compare this value with the PLC Clock, and will return the bit state, depending on the shift time. Know need for a HR then either.

Look up the ++ instruction in the CJ1M manual (or help file), then find the corresponding instruction in the CQM1H manual (or help file)...

Then perhaps this display is not for you then?

Yep, but will we keep answering the simple questions??? I saw this question, and did think come-on, but there will always be someone that answers the simple ones, & we all learnt somewhere.... Another hint.... why would one want to count to 300,000? Why not break it up into more manageable quantities? As you should know, a 16-binary no is limited to 65535, and a BCD no 9999, in the short form that is.... The CQM1 is BCD based, you possibly need to research computed numbering systems.

Hi, I have done some testing with 1 of these, and there are certain things that seem useful, and some that do not, IMO. What i have decided on, is that it is probably more useful for displaying information only, changing values etc I have not explored yet. By forcing the message screens to be always displayed, this effectively locks out the other areas. I have some code that cycles between 3-4 screens, depending on what is going, and seems to work ok. The other thing to be aware of, is that any data that is to be displayed has to be converted to ascii, so there is a bit of code in doing this as well. I hope this helps a bit.

As with anything, there are numerous ways to skin the same cat... Since the timer counts down, it looks like you have everything correct, except that the comparison value needs to be the timer preset, less the value where you want the output to stay on until. (Can't give away too much ) You also need to swap the positions of the 2x values in the CMP instruction, unless you decide to use the P_LT flags...

I thought that I read somewhere that the new versions also come with programs in them....

One would think that if it was a brand new install, that they would be new units, and have their own staging/un-staging control, with perhaps only a master control that brings the chillers in/out, based on plant demand. Do the chillers have their own control systems, that do their own safeties etc, or is the staging to be determined by an external source?

I am pretty sure this is in the manuals, do you have them for your particular model of PLC? You never did mention what model you were using The TR0 is a mnemonic representation of a branch instruction. If you view your ladder diagram as mnemonics, you may/may not see them all over the place...

Keeping MrPLC ticking over though huh....

This does not always mean it is correct! I think I actually put you crook with the screen shot, but the comment was correct. In the box that says auto-detect, have you tried changing it to not be auto-detect, and setting it to the IP address of the PC that is on the PLC network? Do the PC's have dual NIC's? This can also be an issue. Also, it is worth posting the screenshots of the info that PMCR has requested, you'll be impressed with the results!!

Copy the FB, & change the Sec_BCD & Hour_BCD source words of the ASC around. This is on the last rung before the ENO condition.

We have found this as well, a solution is to use FINS/Tcp instead.

Out of left field, but does the Workstation Node number = the last octet of the IP address of the PC?

Scaling is relatively easy, the most common setup for your module is that the minimum value is +0, the maximum value is +4000. So if -10:+10, then a value of +0 = -10v, & +4000 = +10v. Why do you want an immediate refresh, do you have a long scan time? I am not sure if the IORF can be used in an interupt, I have had an issue before with an instruction, but cannot recall exactly which one.

I'm assuming that you have analysed the code, and it is as efficient as it can be?

You can do a DB dump, then generate tags in excel, and copy your tags from your controller into this spreadsheet, this will take a bit of work to get the formats correct, but once you have it, it does work quite well! I don't know of any products that allow browsing to another manufactures tag database

This statement is not quite clear. By the sounds of it, you are using InTouch application Server, not Vintage Intouch? Window Maker is part of, can be accessed from the Archestra environment. How are you opening Window Maker, from the IDE? Either way, to answer your question about the controller tags, not that I am aware of. I know this type of feature is possibly available in FT, but that is the benefits of using packages from the same manufacturer!

Lets start at the beginning again... You said the customer does not want ArchestrA graphics, so you are using Intouch Application Server? There is a difference (quite a lot) between 'vintage' Intouch & Application Server. Fortunately, we can use both if the need ever arises, which could be the ideal path for getting you initial comms up & running... By the sound of it, you have not used InTouch before? If that is the case, lets start with vintage InTouch to get the comms established. Unfortunately, I don't have access just now with a DASABCIP driver installed, so cannot comment accurately. But, it sounds like you have followed the manuals to a certain extent, but have you added an item to the Device Groups Tab? This Group then becomes the Topic Name in Intouch. In InTouch (remember, we are starting with Vintage Intouch for now), you need to add an Access name, it is sometimes common practice to name this access name the same as the Device Group that we added to the DAS Server. The nodename can be left blank if the DAS Server is on the same PC, otherwise you need to enter the NodeName where the DAS Server is, and ensure that the correct entries are in the hosts file. The Application name will be DASABCIP. Once this is done, lets create a new tag. This can be any type you want to begin with, starting with a IO Real may be a good starting point. You will need to select the access name that you added in the previous step, and in the item field, the tag as it appears in you Control-Logix file. (A note here, to begin with, ensure that this tag is declared at the global controller level, if it is declared in another task, then this needs to be added to the tagname) Now, add a variable display to Window Maker, switch to runtime, and things should kick into life... I hope this helps, let us know if you have any more questions.

Hi PDL, How are you getting on with this project? We did a iFIX with Kepware & Omron this time last year. I am not sure of the main difference's between iFIX & cimplicity, I do know that iFIX is VB based, so you can pretty much do whatever you want, if you have a good grasp of VB.... if not, is a good place to start. One thing that iFIX does have, and always has, is Tag Groups, which are useful for doing popup type substitutions etc. I have seen different installs where Tag Groups were not used, and just done with VB as well. I am not sure of the best way, iFIX seem to recommend the Tag Group option, but does create more maintenance, especially if there is many groups to be done. Every group has its own file... there must be a way to do this in bulk, but have not worked it out yet...

This would also happen with a Routine that was called multiple times. The CLX now has Add On Instructions (AOI), which are the equivalent of Function Blocks I guess.

Have a look at using the HSC & PRV instruction, this will give you the frequency of the signal, which you can then convert to RPM...

I would think so....

Yeah, back to basics... Can you connect to the PLC with the ethernet module, ping that IP address etc? Have you tried multiway, this is available on this site,and is pretty easy to setup....