Hi all, I have a tag folder that I added a UDT to that now will not load anything into the folder when i try to expand it. It will not let me delete it or If I try to export it I get a file with 0 size. If I try to export any folder above it I also get a 0 size export. Any Ideas? Thanks in advance!!
1 Like
What shows up in your logs (or designer console)?
Hi, Im not seeing much in the designer console except for one warning in Bold. The log section on the gateway home page does show anything except for this as an execution warning. "(prov:Kitchen:/tag:Tags/Line 1/Depalletizer/L1GR1_VFD2/isFaulted:/alm:Motor Fault) Some bound alarm properties failed to compile. They will be replaced with static default values. For more information, turn logger âAlarming.Executionâ to âDebugâ, and reinitialize the alarm.
designer console below:
07:48:40.916 [Designer-Startup] INFO designer.main - Downloading⌠[+0]
07:48:42.645 [Designer-Startup] INFO designer.main - Cleanup⌠[+1729]
07:48:42.645 [Designer-Startup] INFO designer.main - Initializing UI⌠[+1729]
07:48:42.755 [Designer-Startup] INFO ignition.TagManager.Gateway - Starting up polling tag manager, polling rate: 250 ms
07:48:44.307 [Designer-Startup] INFO designer.main - Starting module: Vision [+3391]
07:48:47.239 [Designer-Startup] INFO designer.main - Starting module: Reporting [+6323]
Apr 2, 2019 7:48:47 AM java.util.prefs.WindowsPreferences
WARNING: Could not open/create prefs root node Software\JavaSoft\Prefs at root 0x80000002. Windows RegCreateKeyEx(âŚ) returned error code 5.
07:48:47.634 [Designer-Startup] INFO reporting.Designer - Starting up Reporting Module. Mode: Activated
07:48:47.852 [Designer-Startup] INFO designer.main - Starting module: Production [+6936]
07:48:47.867 [Designer-Startup] INFO com.sepasoft.production.designer.ProductionDesignerModuleHook - startup calledâŚ
07:48:48.136 [Designer-Startup] INFO com.sepasoft.production.designer.ProductionDesignerModuleHook - startup complete.
07:48:48.138 [Designer-Startup] INFO designer.main - Starting module: Alarm Notification [+7222]
07:48:48.208 [DesignerExecEngine-1] WARN com.sepasoft.production.designer.ProductionDesignerModuleHook - Sending notification to components that designer is connected to Gateway.
07:48:48.217 [Designer-Startup] INFO designer.main - Starting module: Barcode Scanner [+7301]
07:48:48.234 [Designer-Startup] INFO designer.main - Starting module: OPC-UA [+7318]
07:48:48.234 [Designer-Startup] INFO designer.main - Starting module: SPC [+7318]
07:48:48.234 [Designer-Startup] INFO com.sepasoft.quality.designer.QualityDesignerModuleHook - startup calledâŚ
07:48:48.651 [Designer-Startup] INFO com.sepasoft.quality.designer.QualityDesignerModuleHook - startup complete.
07:48:48.651 [Designer-Startup] INFO designer.main - Starting module: SQL Bridge [+7735]
07:48:48.927 [Designer-Startup] INFO designer.main - Starting module: Symbol Factory [+8011]
07:48:48.938 [Designer-Startup] INFO designer.main - Initializing Scripting⌠[+8022]
07:48:48.964 [Designer-Startup] INFO com.sepasoft.production.designer.ProductionDesignerModuleHook - Initializing Designer Production scripts.
07:48:49.208 [Designer-Startup] INFO designer.main - Starting Tag System⌠[+8292]
07:48:49.214 [Designer-Startup] INFO designer.main - Initializing UI⌠[+8298]
07:48:49.527 [SQLTags-TreeLoader-1] INFO ignition.TagManager.Gateway - Starting tag polling.
07:48:50.131 [DesignerExecEngine-1] INFO com.sepasoft.production.designer.ProductionDesignerModuleHook - loadProject calledâŚ
07:48:50.933 [DesignerExecEngine-1] INFO com.sepasoft.production.designer.ProductionDesignerModuleHook - loadProject complete.
Customer called support and I was able to help him solve this issue. To be able to access what was inside the Depalletizer folder itself, we had to max out the Designer memory from the default 1gb to 4gb in the Gateway Settings portion of the Gatewayâs Configure page. The reason for this change was because during this âloadingâ period, the Designerâs memory usage climbed dramatically. After we were able to open the folder, we noticed that there was a folder inside this folder that was also named Depalletizer which was not supposed to be there so we deleted it. Customer had also stated that the day the problem had started happening he had added a UDT instance to this folder. I deleted this UDT instance and I was able to see the tags under Depalletizer without the long delay. After recreating that UDT instance, we no longer saw the problem at all. Going forward, if this were to happen again and these steps do not lead you to a solution, call support for assistance.
1 Like