Here is an interesting trick that allows you to monitor your Windows processes with KSX. You can leverage the KSX shell function with the Windows tasklist command.

The following windows batch code will return the memory use of the ksxserver.exe application.

@echo off
tasklist /fo table /nh /fi "imagename eq ksxserver.exe" > tasklist.txt

His Excellency José Goñi, Chilean Ambassador to the United States, made a visit to Utah on October 8th & 9th. KnowledgeScape had the privilege of being the only Utah business on his itinerary. We were able to visit with the ambassador and discuss our services and software, KSX. Read more...

If you have an HMI, you have a visualization and interface tool to aid you in your operation and decision making. Your HMI presents you with the data that you need to operate your process. In the process of installing and designing the HMI you have decided what data the operators, engineers, and/or management need to make the necessary decisions to best suit your business. You may have aggregated data or shown the state of some piece of equipment, etc. All of this data has been designed so that people in your organization can make the right choice. Read more...

Is your expert system old and expensive? Get rid of your GenSym G2, Metso OCS or Pavilion system. Trade up in features, performance and usability all for less money with KSX! Read more...

One of the great new features of KSX is the rule script schematic view. In the rule editor view, it is one of the 3 tabs at the top of the main window. The schematic view diagrams a rule and lets you see each phrase, input and result as well as the interactions between each phrase.

"Can I do that with KSX?" We get that question quite often. And while the answer we give is almost always a resounding YES, sometimes there are just things we haven't thought of, or are outside of our scope.

Enter the shell function.

The shell function takes any number of arguments separated by commas, concatenates the lot, and sends it to your operating system. The script is run from the location of the KSX server application. In Windows this is usually "C:\Programs Files\KnowledgScape\bin". The shell function looks like this:

One of the functions that I find myself using quite often is the clip function. The clip function takes a value and limits the returned value between a high and a low value. The function takes three arguments: the low clip value, the passed value and the high clip value. If I used the function like this...

clip ( lowLimit, value, highLimit )

I would get the following results:

lowLimit	value	highLimit	result
5	10	15