Doc. # 1-2377497074
Date Updated 09-05-2018 Date Created 02-19-2016
Document Type Knowledge Base Related OS
Related Product ADAM-6017/ ADAM-6018/ ADAM-6022/ ADAM-6024/ ADAM-6050/ ADAM-6051/ ADAM-6052
IAG_SOP_ADAM-6017 & 6018 & 6022 & 6024, DO can't set as the GCL output
Solution:
Customer wants to use the AI status of an ADAM-6017 to trigger the DO of another ADAM-6017; however, user can’t set “ADAM-6017” as the target module because in the UI of ADAM/APAX .NET utility doesn’t have this option. Is it possible to use the DO of ADAM-6017 or ADAM-6018 in GCL?
Download File Release Date Download Site
IAG_SOP_ADAM-6017 & 6018 & 6022 & 6024, DO can't set as the GCL output.pdf (0) 02-19-2016
  1. Primary
  2. Secondary