Created Date: September 08,2017

Created by: OkiePC

Click software suggestions:

1. Address bits within DS words. It would be handy to be able to examine the bits with "contact " instructions and write to them with "coil " instructions. For example: DS10.0 or DS10/0 references bit zero of word DS10 in a Boolean instruction. My workaround is to pack copy or unpack copy the DS word into "C " addresses, but I have to go through a DH address first, since you can't pack or unpack DS words.

2. Address comments. It would be nice to be able to edits the address comments in various other places besides the Address Picker. They should also appear in the Data View windows (and ideally be editable from there). It would not be so bad if I could leave the Address Picker open, but I can't.

3. General window hierarchy. It seems that I am constantly opening and closing the Data Views and Address Picker windows. I would like them to be able to stay open, but not always occupy the front of the z-order of the display. It would be useful to be able to keep the Address Picker open, open multiple instance of it and let it "go behind " the ladder editor and navigation pane when they lose focus.

4. Nicknames. What good are they if I can't type them in place of addresses? I know they have some other benefits, but I should be able to enter a nickname in the instruction instead of the address.

5. Ladder editor lacks drag and drop. I ought to be able to drag and drop instructions, branches, whole rungs. I ought to be able to drag addresses onto instructions from the Address Picker or Data View or from other instructions. This is a feature that makes RSLogix work flow so much better. The only place I seem to be able to use "dragging " is the instruction palette.

6. Send/Receive instructions. The timing of the "Sending "/ "Receiving " bit is delayed enough, that it is sometimes tricky to prevent the instruction from executing multiple times when I only want it to occur once per false to true transition of the rung-in logic. What I have done is use a parallel out coil to inhibit the multiple occurrences of the instruction when I am still waiting on the first one to either set the Success or Error bits. I believe I understand that the Sending bit means the action is actually being performed at the specified port, so altering the behavior of that bit might cause problems for existing logic. Maybe the best way to fix my problem is to have a "1-shot " checkbox on the instruction itself. Most of my systems are communicating over radio modems so a delay of many PLC scans is quite common. I had tried using a rising edge contact instruction to trigger the Send/Receive, but it is not reliable that way. Sometimes the message never fires off so my sequence would get stuck. My "in process " parallel bit is reliable just would be nice if it was built in so as not to clutter up my rungs.

I may have other things to add, I am working on only my 4th Click project, but that is what I see so far.

Created Date: September 08,2017

Created by: kewakl

Here Paul, I'll help fill out your list. These are from some of my past posts.

If nothing else, maybe you'll find some of these items useful/though-provoking.

(X) incessant NOISE that each window opening requires.

(X) PUT THE CURSOR in the TEXTBOX when searching for something.

(X) provide an automatically incremented pointer in a FOR LOOP instruction - currently I have to build my own.

(X) sanity check window positions

(X) MOUSE TO KEYBOARD TO MOUSE TO KEYBOARD -- ad nauseam -- for everything.

(X) xref list. Search twice - look once .

(X) math editor bug

(X) 'NON-NOOB ' mode. Do not need all prompts and confirmations.

(X) allow ASCII copying to/from TXT/DS/DH

(X) KECommServer locks up port if CLICK software crashes.

Created Date: September 08,2017

Created by: OkiePC

YES, I meant to include the "DING " complaint. Some of the dings are when things are fine...most of them in fact. I end up muting my PC when working with Click software for more than a minute or two.

I rarely use loops in any PLC, but with a "For/Next " loop it should be understood that there is a "step " value as part of the deal which can be referenced inside the loop.

Window positions are another one. Once in a while a window position lands "off screen " somewhere and I have to ESC to get back to the main window, save my work, close and restart the software. Also, when downloading (stop mode transfer) if I navigate away from the Click software and then back, the window that prompts me that the transfer is complete and the next prompt that puts the PLC back in run mode end up behind everything. If any window should be on top of it all, it is the one to get the PLC back into RUN mode.

Mouse to Keyboard --- yes, I have learned many of the keyboard tricks but still have to use the mouse more than I would like.

I have not seen the math editor bug, so would be interested in having you expand on that some.

I have seen some of the warnings that have "don't show me again " tickboxes.

The ASCII thing burned me on my first Click telemetry project and I could have rebuilt my code to avoid them, but found a workaround that was not too painful.

I have had a couple of software crashes, but have not had any problems with my USB to serial converter or Ethernet connection. I am using a USB to serial converter I really love from PLCCable.com and it has worked with everything I have tried so far:

https://www.plccable.com/usb-to-rs23...l-plctalk-net/

So if you could expand on what you meant by a couple of those in your list.

I will add one more and this applies to all A/D ladder editors. Columns. I don't care about them, don't need to see them, don't need to insert them...handle that behind the scenes and let me stick stuff where I want, scoot my lines and instructions around for me and by all means, don't screw with the appearance of other rungs I am not even messing with! I should not have to insert rows or columns, let me insert/append instructions and branches and deal with the columns and rows that go with them automatically please.