unknown 'error' message in Diagnostcs - processor taking too long to boot up!
markbsure
Posts: 44
My processor is taking a good 6-8 mins to boot up, and I believe I've narrowed the fault down to one of my modules (after commenting out each module, compiling, uploading, checking processor boot time), but can't quite work out what part of my module is causing the problem.
During boot up I telnet to the processor as early as possible and poll the processor with "show buffer".
Without my suspected faulty module, the Interpreter maxes out at about 188 and then clears back to zero once all devices are online pretty quickly.
When my module is running, the interpreter will get up to about 600 over about 6-8 minutes, before eventually clearing back to zero.
In diagnostics I also repeatedly get this message which I don't get when I run the code without my module:
"CIMessageRouter - Unknown ObjectID 30"
Does anyone know what this relates to? Knowing this could help me narrow down the fault in my code.
I've spoke to AMX tech support here in the UK, but they are not allowed access to these diagnostic messages.... apparently only guys in the AMX development team in the USA are allowed knowledge of them!
thanks
During boot up I telnet to the processor as early as possible and poll the processor with "show buffer".
Without my suspected faulty module, the Interpreter maxes out at about 188 and then clears back to zero once all devices are online pretty quickly.
When my module is running, the interpreter will get up to about 600 over about 6-8 minutes, before eventually clearing back to zero.
In diagnostics I also repeatedly get this message which I don't get when I run the code without my module:
"CIMessageRouter - Unknown ObjectID 30"
Does anyone know what this relates to? Knowing this could help me narrow down the fault in my code.
I've spoke to AMX tech support here in the UK, but they are not allowed access to these diagnostic messages.... apparently only guys in the AMX development team in the USA are allowed knowledge of them!
thanks
0
Comments
Commented out all of DEFINE_PROGRAM, and no change, but I have found out why the diagnostic message, "CIMessageRouter - Unknown ObjectID 30" keeps appearing.......
....... it's a response to me sending the command "SHOW BUFFERS" when connected via telnet to the processor!
just noticed it by running 2 telnet connections to the processor, one showing diagnostics (with command "SHOW MSG ALL") and the other telnet window where I could poll the command "SHOW BUFFERS".
sorry.....
There is still a noticabley long boot time of the processor when I include my Arcam module in code.
I'm using 3 instances of the module, which works fine once the processor is booted, but maybe this is the cause?
Even though AMX teaches this, you should be a little carefull with doing this, as it slows down the whole thing
These days AMX actually tells you to put as little as possible in 'define_program' and handle your feedback in your functions.
Our local Technical Representative recommends a maximum of 10 lines in define_program if you REALLY need it.
Snippet from the Netlinx Reference Guide:
I've put in bold what's really important.
I would also agree that you should not use the mainline for anything at all
The way the NetLinx system works: (see attachment)
I've only ever put channel feedback to devices in mainline (and recently tracking the state of timelines for debug purposes), but with some of my systems using a good 20 or more modules, and often with multiples of the same modules, this overloading of mainline can't be good as you say.
thanks for the advice guys.