Back Midas Rome Roody Rootana
  Midas DAQ System  Not logged in ELOG logo
Entry  16 Feb 2021, Ruslan Podviianiuk, Forum, m is not defined error m_is_not_defined.png
    Reply  25 Feb 2021, Konstantin Olchanski, Forum, m is not defined error 
       Reply  05 May 2021, Zaher Salman, Forum, m is not defined error 
          Reply  06 May 2021, Stefan Ritt, Forum, m is not defined error 
Message ID: 2158     Entry time: 05 May 2021     In reply to: 2105     Reply to this: 2159
Author: Zaher Salman 
Topic: Forum 
Subject: m is not defined error 
We had the same issue here, which comes from mhttpd.js line 2395 on the current git version. This seems to happen mostly when there is an alarm triggered or when there is an error message.

Anyway, the easiest solution for us was to define m at the beginning of mhttpd_message function 

let m;

and replace line 2395 with

if (m !== undefined) {

> > I see this mhttpd error starting MSL-script: 
> > Uncaught (in promise) ReferenceError: m is not defined
> > at mhttpd_message (VM2848 mhttpd.js:2304)
> > at VM2848 mhttpd.js:2122
> your line numbers do not line up with my copy of mhttpd.js. what version of midas 
> do you run?
> please give me the output of odbedit "ver" command (GIT revision, looks like this: 
> IT revision:       Wed Feb 3 11:47:02 2021 -0800 - midas-2020-08-a-84-g78d18b1c on 
> branch feature/midas-2020-12).
> same info is in the midas "help" page (GIT revision).
> to decipher the git revision string:
> midas-2020-08-a-84-g78d18b1c means:
> is commit 78d18b1c
> which is 84 commits after git tag midas-2020-08-a
> "on branch feature/midas-2020-12" confirms that I have the midas-2020-12 pre-
> release version without having to do all the decoding above.
> if you also have "-dirty" it means you changed something in the source code 
>  and warranty is voided. (just joking! we can debug even modified midas source 
> code)
> K.O.
ELOG V3.1.4-2e1708b5