Keyword usage

[[Ka...]]

Hello Experts,

We want to use Autorun on a larger scale and to make finding the programmes safer and easier we use the search by "keyword" function.
Now we see that we are not searching for a unique keyword but for text input+wildcard. This leads to the fact that keywords are accepted that do not even exist and, in addition, a wrong programme is activated.
Example:
Valid Keywords: WQA1234, WQA1234-40, WQA,1230
Keyword input: WQA123
Autorun search for WQA123*
Find and activate: WQA1230

I expected the name "keyword" to mean that this is unique! 😱 😡

The next bad surprise is that if there are more icons in a layer than can be displayed on one page and a search is made via "keyword", the display does not jump to the activated icon. The window is therefore not scrolled and the activated Icon is not visible 😡

I asked the german support how to solve this two issues but I get only the answer that Autorun works as expected. 😱 To handle the window scroll issue I should not use more icons than will be visible on one layer!

But how am I supposed to support hundreds or even thousands of programmes if I can neither use the "keyword" nor the display of activated icons properly?

How do you solve this issues?

Best Regards
Karsten

[[No...]]

Please sign in to view this quote.

So it still acts up the same way it already did in 4.6. 😱 Shame on you, Zeiss! This is the 21st century!

Please sign in to view this quote.

How ridiculous 🤣 but yes, that's the sad truth.
When I set up Autorun for the first time many years ago, I also intended to put all icons on one layer, but ran into the scrolling issue. I ended up organizing Autorun in many layers which only contain the programs of a certain project. I never used keyword search (only search for plan name), so I don't know if this would resolve your issue. But you can take this as a general rule in Auotrun: Better don't exceed the limits of the visible window area. The scroll bars are more or less only decoration 🤣

[[Ka...]]

Thanks Norbert!

How sobering to learn that Zeiss has not developed Autorun any further for years. It runs like a red line. 32-bit system, development/bug fixing for Planner discontinued, Autorun frozen, GPS implementation very bumpy and incomplete. And to top it all off, snooty support.

Extremely frustrating!

I wonder why Zeiss wants a lot of money for maintenance contracts. I'll just ask the sales department how much it will cost to solve our problem. I'm curious about the price...

Regards
Karsten

[[Mi...]]

What version of Calypso do you have?
Do you found the problems with a codebar reader or with a hand input?

[[Ka...]]

Hello Michele,

Currently we run CALYPSO 7.4.16.

The problem with appending a wildcard to the keyword is independent of the type of input. We run both types: Barcode scanner and input by hand.
Barcode scanners are safer, but it can happen that the wrong barcode is read because it is printet at the head of work paper.
Example:
Barcode for the work group is: KRQ4242
Programme production status 1 is KRQ4242-40
Programme QA before surface is KR4242-21
Programme for finished part is KR4242-80

It´s possible to scan the code of the work group which will end to call and activate the program KR4242-21 because KRQ4242 is not a valid keyword in Autorun. More yet: KRQ will be a valid Keyword and starts any of the thousands of programmes! 😡

On the other hand, the programme names are quite similar and it can easily happen that you type in the wrong or incomplete number which then activates a completely different programme. 😭

Best Regards
Karsten

[[Mi...]]

Occasionally, I try to make the work of my collegues easier.
And some weeks ago I tried with Autorun with some layer and some codes.
I marked the codes with a special keyword (i.e. without spaces, lines or #) because I wanted to try to use only barcode reader to found the program.
At the end, I found the issues with a barcode reader because the search was disorderer (it is like opened more of program/keyword superimposed and at the end the operator need to clik on the program..too chaotic) but if I write by hand the keyword on the "find run.." the program was hit immediatelly and without error.

I run Calypso 7.6.08.

(I'm sorry for my English, it's not that easy to explain such technical topics)

[[Ka...]]

Hello Michele,

There is no difference between input from barcode reader and typing in via keyboard at least.
If you fine with your keyword and if the program is immediately found by the "find run.." window you are on the right way.

Check if your barcode reader decode your barcode correctly AND send at the End CR LF ( 0d 0a in hex ). Some barcode reader send at the end only CR which might to lead to your situation that the worker need to type in the RETURN key from keyboard after using the barcode reader.

Open a editor ( word, notepad, vi, what ever.. ), scan your code, save it as mytest.txt or similar. Open this file with online hexeditor like https://hexed.it. Check if at the end the CR LF is printed like 0D 0A.
Example for code QA01234:
51 41 30 31 32 33 34 0D 0A

Best Regards
Karsten