Home› AMX User Forum› NetLinx Studio

Memory Monitor

ondrovicondrovic Posts: 217
in NetLinx Studio
Is there a way to monitor the memory through code? So if the memory gets low you can issue a reboot?

Thanks

Comments

  • viningvining Posts: 4,368
    You can open a telnet connection through code and do a "show mem". DHawthorne had a module posted a long while ago that still may be accessable called DevTermLogger (or something like that), that I believe had all the code already written to do just that as a means of verifying the amount of memory available or left for use by the logging function. You can just strip out the parts you need or include the entire module and leave the logger disabled.

    ? what allocated memory are you going to free up with a reboot or if your using space up by writing to flash how is a reboot going to help?
  • ondrovicondrovic Posts: 217
    Really, Im not too sure what it is going to accomplish, I have a master that locks up constantly, after about a week. I have replaced the master. Its an ni 700 running the duet HAI module and 6 zones of viewstats with the duet apirlaire module, I think there might be a memory leak with the HAI duet module, only because there are 2 other masters running the aprilaire duet module that aren't locking up at all
  • kbeattyAMXkbeattyAMX Posts: 358
    Keep AMX Tech support in the loop. I had systems that were locking up and it turned out to be the AMX VSX8000 COMM Module. There was an infinite loop that only AMX could find because they didn't release the source code of the comm module.
  • ondrovicondrovic Posts: 217
    kbeattyAMX wrote: »
    Keep AMX Tech support in the loop. I had systems that were locking up and it turned out to be the AMX VSX8000 COMM Module. There was an infinite loop that only AMX could find because they didn't release the source code of the comm module.

    Yeah that is something I will be doing on Monday thanks for the tip :)
  • Spire_JeffSpire_Jeff Posts: 1,917
    kbeattyAMX wrote: »
    Keep AMX Tech support in the loop. I had systems that were locking up and it turned out to be the AMX VSX8000 COMM Module. There was an infinite loop that only AMX could find because they didn't release the source code of the comm module.

    When did you find this problem? I have this module installed in a system I am working on now and I just want to make sure that I have the fixed module :)

    As for the memory leak, if you enable internal diagnostics, you should see the memory constantly dropping. If you don't see it dropping, start using the system and try to get it to start dropping. (this is the best case scenario because it's fairly easy and quick to fix). If you see it dropping when you turn on the diagnostics, start removing modules one at a time until it stops and hopefully after removing one, the memory leak will stop.

    There is also a known problem when using two different duet modules on the processor. I don't remember what the lethal combination was, but hopefully the person that discovered the problem reads this. (I don't know if it was ever posted here, but it was discussed in Prog 3.) If you troubleshoot the problem and think that it is with one of the duet modules, keep this in mind.

    Jeff
  • kbeattyAMXkbeattyAMX Posts: 358
    PolycomVSX8000Comm.tko Modified: 1/25/2008 is the good one. Any file with a later modification date than this is good. The sympton was: MVP8400 loosing connection, Telnet was still good but interpreter locked up. Max que count went through the ceiling before the Netlinx called it quits. I thought it was locking up because I was updating a TP while it was offline (even though I've installed hundreds of systems with no problem with this).
Sign In or Register to comment.