Differences

This shows you the differences between two versions of the page.

--- cpp [2020/05/12 18:49]
wikiadmin
+++ cpp [2022/09/11 04:24] (current)
wikiadmin
@@ Line 1: / Line 1: @@
-This GEMTool C++ example uses the code generated from TransSECS using the Native/C++ deployment option.
+This GEM C++ example uses the code generated from TransSECS using the Native/C++ deployment option.
-In the tool you update the variables with simple set/get methods take the name of the variable and the value.  Complex types are passed as JSON.
+In the tool you update the variables with simple set/get methods take the name of the variable and the value. In the host, you subscribe to receive data. Complex types are passed as JSON.
 Message notifications are received as JSON maps so that each of the published elements in the message are available directly.
@@ Line 10: / Line 10: @@
 <code bash>
 mkdir build
+cd build
 cmake ..
 make
@@ Line 44: / Line 45: @@
 The tool is then running and ready for connections.  You can use the TransSECS GEMHost sample project to test the tool.
-The sample, even though simple, demonstrates all the features required to build a tool.
+For the host,copy the GEMHostRuntime.jar from the TransSECS GEMHost project into the build folder
+The samples, even though simple, demonstrates all the features required of a tool and the ability to collect data from a host.
+In the host code, publish variables you need to change in the interface, here the port, hostname, deviceid, etc. and subscribe to elements to receive data updates.  Here an event (loaded) and to values (ppid and wafer count).  The event is received as a JSON structure.
+<code c++>
+#include <stdio.h>
+#include <execinfo.h>
+#include <signal.h>
+#include "transsecswrapper.h"
+#include <unistd.h>
+#include "valueobject.h"
+#include <chrono>
+#include <thread>
+transsecswrapper::TransSecsWrapper gem_native_wrapper  = transsecswrapper::TransSecsWrapper("./GEMHostRuntime.jar");
+int main(int argc, char **argv) {
+    //signal(SIGSEGV, handler);   // install our handler
+    int port = 5010;
+    // persistance file saves GEM configuration between restarts (reports, enabled CEIDs, enabled Alarms, etc).
+    gem_native_wrapper.Publish("gemhost/configuration/persistencefilename", "/tmp/testpersistence");
+    gem_native_wrapper.Publish("gemhost/configuration/equipmenthostname", "localhost");
+    gem_native_wrapper.Publish("gemhost/configuration/deviceid", 1);
+    gem_native_wrapper.Publish("gemhost/configuration/activeport", port);
+    gem_native_wrapper.StartMain("GEMHost");
+    gem_native_wrapper.Subscribe("gemhost/variables/ceid/loaded",[](std::string topic, transsecswrapper::ValueObject value_object) {
+        printf("New ceid (%s) %s\n\r", topic.c_str(), value_object.GetStringValue().c_str());
+    });
+    gem_native_wrapper.Subscribe("gemhost/variables/vid/ppid", [](std::string topic, transsecswrapper::ValueObject value_object) {
+        printf("New ppid (%s) %s\n\r", topic.c_str(), value_object.GetStringValue().c_str());
+    });
+    gem_native_wrapper.Subscribe("gemhost/variables/vid/wafercount", [](std::string topic, transsecswrapper::ValueObject value_object) {
+        printf("New wafercount (%s) %s\n\r", topic.c_str(), value_object.GetStringValue().c_str());
+    });
+}
+</code>
 The tool must keep the SECS interface informed of the current values of all the VIDs.  This just a matter of call "Publish" with the name and value of the variable.
 <code C++>
             gem_native_wrapper.Publish("gemtool/vids/WaferCount", waferCount);