Calypso Monitor Question

[[ZE...]]

We are running Calypso 2017 6.4 and I love the added feature of having the monitor to show the time on the run, however others that are running the programs inadvertently close the monitor out so it does not show again. Does anyone know how to get it back up without having to shut down Calypso and restarting it?

Jason Troland | 22.03.2018 18:41 |

[[ZE...]]

See note from Help file
Tom Oakes | 22.03.2018 20:20 |

[[ZE...]]

Bullsh*t.. 🙂

Eric Moberg | 22.03.2018 20:40 |

[[ZE...]]

that really is disappointing.

Jason Troland | 23.03.2018 11:49 |

[[ZE...]]

Maybe you should go to the Software Request page on the Home page and create a suggestion.

Tom Oakes | 23.03.2018 12:25 |

[[ZE...]]

LOL!! That's a good one Tom.

Dave Scott! | 23.03.2018 17:44 |

[[ZE...]]

Go to the following to restart the monitor.
Have not had it fail to restart
C:\Program Files (x86)\Zeiss\CALYPSO 6.4\bin\Monitor\CALYPSOMonitor.exe

Gregory Kozera | 26.03.2018 18:59 |

[[ZE...]]

So, you could create a shortcut on your desktop to do what Gregory has proposed.

Tom Oakes | 26.03.2018 19:08 |

[[ZE...]]

If you wanted, you could make a batch file that looked to see if it was running and if not started it .. then drop the batch file into your main directory as inspection_end.bat
Then every time a program ended, it would check to see if the monitor was running.. and if not it would re-start it for you. (I haven't tested this so no complaints if it doesn't work as expected please)

@echo off
SETLOCAL EnableExtensions

set EXE=CALYPSOMonitor.exe

FOR /F %%x IN ('tasklist /NH /FI "IMAGENAME eq %EXE%"') DO IF %%x == %EXE% goto ProcessFound

goto ProcessNotFound

:ProcessFound
:: found the process.. do nothing..

goto END
:ProcessNotFound
:: didn't find the process - start it.. 
start "C:\Program Files (x86)\Zeiss\CALYPSO 6.4\bin\Monitor\CALYPSOMonitor.exe"

goto END
:END
echo Finished!

Derek Stedman | 26.03.2018 20:10 |

[[ZE...]]

Why The hell do you enable delayed expansion?

Eric Moberg | 26.03.2018 20:11 |

[[ZE...]]

Cause I copied that from some batch file place - I knew you were gonna tell me I did something wrong - lol

Derek Stedman | 26.03.2018 20:13 |

[[ZE...]]

feel free to correct my work btw.. I was just trying to show what could be done 🙂

Derek Stedman | 26.03.2018 20:14 |

[[ZE...]]

I was not my intension to correct you, I just could not understand why 🙂

But a helpful hand I can give, If closely you look, you might see that one line it can be turned in to. A lot of "useless" typeing you have done. (In a yoda voice)

Eric Moberg | 26.03.2018 20:27 |

[[ZE...]]

Its only useless if you understand the one line version - I find being able to understand whats going on can be useful especially in examples.

The original had a one line version but as an example it would probably seem like gibberish to most people. I figured this way it might help people figure out what was going on.

After looking it up I am assuming SETLOCAL was so it doesn't muddy up the environment and all set variables stay local - the enable extensions I doubt needs to be there since command extensions are on by deafult, however if they are shutoff in the registry setlocal enableextensions is supposed to override that. (but like I said I copied it - I didn't write it)

Derek Stedman | 26.03.2018 20:38 |

[[ZE...]]

Thanks Gregory. the shortcut on the desktop seems to be the easiest thing for everyone here at my facility.

Jason Troland | 26.03.2018 20:46 |

[[ZE...]]

lol Once you get the PCM geeks going, there's no stopping them. But you sure can learn something from them.

Tom Oakes | 26.03.2018 21:26 |

[[ZE...]]

I don't want to be a that guy, but since you actually said "feel free to correct".

First: why assigning variables? EXE is always going to be "CALYPSOMonitor.exe". Only confusing if you are going to be simple and explain.


Two: EnableExtensions is always on by default? And you don't even utilize it. Remove.

Three: creating a flow control with "GOTO" when nothing is happening when your first condition is fulfilled, is wrong in every language. The only time you wish to do something is if the condition requirement is not ok. So you should use NEQ instead of EQL in you IF statement, and apply actions from there.

Well, here is the "reference" way of doing it 😃

@tasklist | findstr CALYPSOMonitor.exe || start "" "C:\Program Files (x86)\Zeiss\CALYPSO 6.4\bin\Monitor\CALYPSOMonitor.exe" 

Hope someone learn something from this post, it not a "fu#k you, you suck post". See it as a free lesson =)

Eric Moberg | 03-27-2018 10:34 AM |

[[ZE...]]

Was not trying to create turmoil in the PCM world just a quick restart of the Monitor without having to logout and restart Calypso. I too have found the monitor very helpful but it can be turned off. To do this you go to the same C:\Program Files (x86)\Zeiss\CALYPSO 6.4\bin\Monitor\CALYPSOMonitor.exe and rename the folder Monitor with alt or letter b or something to fit your needs and when Calypso is booted up the monitor feature will not be part of the startup. To reactivate, change the folder back to the original Monitor name and bang, your back in business.
Since we do not have the PCM option I always look for ways to work within Calypso

Gregory Kozera | 03-27-2018 06:18 PM |

[[ZE...]]

This has nothing to do with pcm. Pcm is a zeiss high level language and batch files are more or less DOS. Two completely different things. And you dont need a pcm license to use batch files. You do however need batch files to be efficient in Windows 😉

Eric Moberg | 03-27-2018 06:34 PM |

[[ZE...]]

Boy, is my face red. I just assumed it was PCM. I guess I didn't look at it closely.

Tom Oakes | 03-27-2018 08:01 PM |

[[Mi...]]

You can start the monitor again (see at the picture)


Mfg M. Behl

Monitor.JPG