Sepasoft , try to use tutorial track & trace

Hi all ,

I have to test Sepasoft's OEE and track and trace module in my new company, but I can't follow the tutorial..

I'm in ignition version 8.3.1, I installed the production and trace module in version 4.83.0-rc4.

I have already had difficulties installing these modules, and now I am facing another difficulty that I cannot unlock.

By following the procedure, I manage to create the path like here:

It is not required to recreate this tree in the tags.

I then followed the tutorial to create this view:

Mais en cliquant sur « receive Raw Beans 1 », j’ai dĂ©jĂ  cette erreur , comme s’il ne trouvait pas le chemin :

com.inductiveautomation.ignition.common.script.JythonExecException: Traceback (most recent call last): File "function:runAction", line 16, in runAction at com.google.common.cache.LocalCache$Segment.getAndRecordStats(LocalCache.java:2347) at com.google.common.cache.LocalCache$Segment.loadSync(LocalCache.java:2313) at com.google.common.cache.LocalCache$Segment.lockedGetOrLoad(LocalCache.java:2189) at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2079) at com.google.common.cache.LocalCache.get(LocalCache.java:4011) at com.google.common.cache.LocalCache.getOrLoad(LocalCache.java:4034) at com.google.common.cache.LocalCache$LocalLoadingCache.get(LocalCache.java:5010) at com.sepasoft.production.mes.manager.MESObjectManager.getMESObjectLinkByEquipmentPath(MESObjectManager.java:3191) at com.sepasoft.production.gateway.manager.AbstractMESObjectManager.getMESObjectLinkByEquipmentPath(AbstractMESObjectManager.java:514) at com.sepasoft.production.mes.manager.RecordOperation.recordOperation(RecordOperation.java:43) at com.sepasoft.production.mes.manager.MESOperationsManager.recordOperation(MESOperationsManager.java:1838) at com.sepasoft.production.mes.manager.MESOperationsManager$ByteBuddy$uAQ6VJeW.recordOperation$accessor$7lPwfOIj(Unknown Source) at com.sepasoft.production.mes.manager.MESOperationsManager$ByteBuddy$uAQ6VJeW$auxiliary$OsxXSIer.call(Unknown Source) at com.sepasoft.monitor.MonitorEngine.monitorRunDuration(MonitorEngine.java:222) at com.sepasoft.monitor.MonitorEngine.monitor(MonitorEngine.java:125) at com.sepasoft.monitor.MonitorEngine.monitor(MonitorEngine.java:111) at com.sepasoft.monitor.MonitoringInterceptor.intercept(MonitoringInterceptor.java:23) at com.sepasoft.production.mes.manager.MESOperationsManager$ByteBuddy$uAQ6VJeW.recordOperation(Unknown Source) at com.sepasoft.production.gateway.ProductionRPCHandler.recordOperation(ProductionRPCHandler.java:1007) at com.sepasoft.production.gateway.script.TraceGatewayScript.recordOperationImpl(TraceGatewayScript.java:19) at com.sepasoft.production.script.AbstractTraceScript.recordOperation(AbstractTraceScript.java:303) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.base/java.lang.reflect.Method.invoke(Unknown Source) com.google.common.cache.CacheLoader$InvalidCacheLoadException: com.google.common.cache.CacheLoader$InvalidCacheLoadException: CacheLoader returned null for key New Enterprise\Site\Area\Receiving Dock

· I tried to fix it by replacing the \ with /, but I have the same problem.

Has anyone ever encountered the problem and may know the solution?

Thank you all

Merci Ă  tous

Hi Samuel,

You might get in touch with our support@axone-io.com.

BR,

Bonjour Gilles,

Oui j’ai dĂ©jĂ  envoyĂ© un ticket hier sur l’outil de ticket d’axone - io, je retente avec votre mail.

Merci

Hello Samuel,

We don’t typically monitor the IA forums, but thankfully someone made me aware of your post!

The system.mes.trace.recordOperation() function which is present in the tutorial screen you downloaded is very sensitive to strings. Subtle differences in the strings for something like an equipment path can cause exceptions. One way this happens is through the python escape character ‘\’ used in the path. As a result I use double backslashes like so:
equipmentPath = “Enterprise\\Site\\Area\\Line”.

If you don’t mind emailing support@sepasoft.com we can schedule a one hour working session with you where we step through the tutorial and help troubleshoot your POC.

Looking forward to hearing from you!

Best regards,
Mark French

3 Likes

Hello Mark,

Thank you for your response.

I followed the tutorial here:
https://docs.sepasoft.com/articles/#!mes-module-tutorials/tt-practical-tutorial

I created the equipment hierarchy in the Equipment section of the MESGateway project, and then added the materials in the Material section.
Do I also need to recreate this path in the Tag Browser?

In Perspective, I simply created the “Receive Raw Coffee” buttons as shown in the tutorial.
The issue occurs when I try to execute them.

It’s possible that I missed a step somewhere. If I can’t resolve the problem, I will contact you to arrange a support session.

Thank you again for your help.

Best regards,
Samuel

Samuel,

The tutorial exercise in question does not require any tag paths, nor does the script reference any. Feel free to ping support@sepasoft.com to get set up with a meeting and we can troubleshoot it together.

Thanks,
Mark