• Recent
    • Tags
    • Popular
    • Register
    • Login

    Please Note This forum exists for community support for the Mango product family and the Radix IoT Platform. Although Radix IoT employees participate in this forum from time to time, there is no guarantee of a response to anything posted here, nor can Radix IoT, LLC guarantee the accuracy of any information expressed or conveyed. Specific project questions from customers with active support contracts are asked to send requests to support@radixiot.com.

    Radix IoT Website Mango 3 Documentation Website Mango 4 Documentation Website Mango 5 Documentation Website

    Scripting data source ReferenceError: "LOG" is not defined

    User help
    2
    3
    1.2k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • P
      Pedro
      last edited by

      I have a Scripting data source script that includes the following line:

      LOG.info('Setting PIDs for primary mode ' + primary.value);
      // more important code below
      

      The log output prints below the edit window when I click on the "Validate" button next to the script edit window:

      INFO 2019-01-03 14:07:57,658 - Setting PIDs for primary mode 1
      Setting point PID Function Enable A071 (0,1) to 1 @03/01/2019 14:07:57
      

      I have an Event alarm level Urgent set for all error types on this source, including script error and log error.
      Each day at midnight, I receive the following event:

      ** Urgent **
      00:00:00 - 'Poseidon VFD rules': ReferenceError: "LOG" is not defined in <eval> at line number 14
      Note: This event requires a manual acknowledgement for it to become inactive
      

      This is on core 3.5.5 as I did not want to risk an upgrade during the holidays. How can I fix this?

      Thanks. Happy New Year!

      1 Reply Last reply Reply Quote 0
      • phildunlapP
        phildunlap
        last edited by

        Hi Pedro,

        It looks like this bug was introduced in the 3.5.0 version of the scripting module. Thanks for bringing it to our attention! I will ensure it gets fixed soon.

        1 Reply Last reply Reply Quote 0
        • phildunlapP
          phildunlap
          last edited by

          https://forum.infiniteautomation.com/topic/3991/release-notes-for-scripting-3-5-1

          1 Reply Last reply Reply Quote 0
          • First post
            Last post