Home› AMX User Forum› AMXForums Archive Threads› AMX Hardware

NI-2100 problem

MaratGillMaratGill Posts: 16
in AMX Hardware
I have a problem with the NI-2100 controler. I don`t know if this is a software or a hardware problem.
I write a program (using NetLinx Studio) and transfer it to the controller. I reboot the controller, but the loaded program doesn't work. I connect to controler and send "program info" command. That's what the controller's response is:

---
-- Program name info

>
---

I send "show log all" command. Controller's response is:

---
Message Log for System 1 Version: v3.21.354
Entry Date/Time Object
Text
1: 02-04-2008 MON 17:48:57 Unknown
IPDeviceDetector.run(): joined multicast group
2: 02-04-2008 MON 17:47:35 ConnectionManager
Memory Available = 34572408 <255920>
3: 02-04-2008 MON 17:47:35 Unknown
17:47:35.483 EVENT Started org.mortbay.jetty.Server@fc365e
4: 02-04-2008 MON 17:47:35 Unknown
17:47:35.483 EVENT Started SocketListener on 0.0.0.0:443
5: 02-04-2008 MON 17:47:34 ConnectionManager
Memory Available = 34828328 <238232>
6: 02-04-2008 MON 17:47:34 Unknown
17:47:34.599 EVENT Started SocketListener on 0.0.0.0:80
7: 02-04-2008 MON 17:47:34 Unknown
17:47:34.366 EVENT Starting Jetty/4.2.x
8: 02-04-2008 MON 17:47:34 Unknown
DynamicServlet 0.0.1 has been started
9: 02-04-2008 MON 17:47:34 Unknown
17:47:34.316 EVENT Started ServletHttpContext[/]
10: 02-04-2008 MON 17:47:33 Unknown
SecurityServlet 0.0.1 has been started
11: 02-04-2008 MON 17:47:33 Unknown
17:47:33.783 EVENT Started ServletHttpContext[/]
12: 02-04-2008 MON 17:47:33 ConnectionManager
Memory Available = 35066560 <90240>
13: 02-04-2008 MON 17:47:33 Unknown
ConfigServlet 0.0.1 has been started
14: 02-04-2008 MON 17:47:33 Unknown
17:47:33.066 EVENT Started ServletHttpContext[/]
15: 02-04-2008 MON 17:47:32 ConnectionManager
Memory Available = 35156800 <176288>
16: 02-04-2008 MON 17:47:32 ConnectionManager
Memory Available = 35333088 <159688>
17: 02-04-2008 MON 17:47:32 Unknown
DeviceServlet 0.0.1 has been started
18: 02-04-2008 MON 17:47:32 Unknown
17:47:32.483 EVENT Started ServletHttpContext[/]
19: 02-04-2008 MON 17:47:31 Unknown
RootServlet 0.0.1 has been started
20: 02-04-2008 MON 17:47:31 Unknown
17:47:31.966 EVENT Started ServletHttpContext[/]
21: 02-04-2008 MON 17:47:31 ConnectionManager
Memory Available = 35492776 <115752>
22: 02-04-2008 MON 17:47:31 Unknown
17:47:31.416 EVENT Started ServletHttpContext[/]
23: 02-04-2008 MON 17:47:31 Unknown
17:47:30.666 EVENT Started ServletHttpContext[/]
24: 02-04-2008 MON 17:47:30 ConnectionManager
Memory Available = 35608528 <45504>
25: 02-04-2008 MON 17:47:30 ConnectionManager
Memory Available = 35654032 <13832>
26: 02-04-2008 MON 17:47:30 ConnectionManager
Memory Available = 35667864 <33424>
27: 02-04-2008 MON 17:47:29 ConnectionManager
Memory Available = 35701288 <186808>
28: 02-04-2008 MON 17:47:28 ConnectionManager
Memory Available = 35888096 <48808>
29: 02-04-2008 MON 17:47:27 ConnectionManager
Memory Available = 35936904 <168136>
30: 02-04-2008 MON 17:47:27 Unknown
DynamicDeviceDetector 0.0.1 has been started
31: 02-04-2008 MON 17:47:26 ConnectionManager
Memory Available = 36105040 <47328>
32: 02-04-2008 MON 17:47:26 ConnectionManager
Memory Available = 36152368 <52832>
33: 02-04-2008 MON 17:47:26 ConnectionManager
Memory Available = 36205200 <14264>
34: 02-04-2008 MON 17:47:26 ConnectionManager
Memory Available = 36219464 <14672>
35: 02-04-2008 MON 17:47:26 ConnectionManager
Memory Available = 36234136 <137648>
36: 02-04-2008 MON 17:47:25 Unknown
DeviceAccess 0.0.1 has been started
37: 02-04-2008 MON 17:47:25 ConnectionManager
Memory Available = 36371784 <36048>
38: 02-04-2008 MON 17:47:24 ConnectionManager
Memory Available = 36407832 <46160>
39: 02-04-2008 MON 17:47:24 Unknown
DeviceManager 0.0.1 has been started
40: 02-04-2008 MON 17:47:23 ConnectionManager
Memory Available = 36453992 <124272>
41: 02-04-2008 MON 17:47:22 ConnectionManager
Memory Available = 36578264 <117904>
42: 02-04-2008 MON 17:47:22 ConnectionManager
Memory Available = 36696168 <87088>
43: 02-04-2008 MON 17:47:21 ConnectionManager
Memory Available = 36783256 <95256>
44: 02-04-2008 MON 17:47:21 ConnectionManager
Memory Available = 36878512 <13224>
45: 02-04-2008 MON 17:47:20 ConnectionManager
Memory Available = 36891736 <29248>
46: 02-04-2008 MON 17:47:19 ConnectionManager
Memory Available = 36920984 <87968>
47: 02-04-2008 MON 17:47:18 ConnectionManager
Memory Available = 37008952 <138288>
48: 02-04-2008 MON 17:47:18 Unknown
Create Jetty Web Server
49: 02-04-2008 MON 17:47:17 ConnectionManager
Memory Available = 37147240 <51488>
50: 02-04-2008 MON 17:47:16 ConnectionManager
Memory Available = 37198728 <233864>
51: 02-04-2008 MON 17:47:15 ConnectionManager
Memory Available = 37432592 <106608>
52: 02-04-2008 MON 17:47:15 Unknown
=================
53: 02-04-2008 MON 17:47:15 Unknown
Welcome to Duet.
54: 02-04-2008 MON 17:47:14 ConnectionManager
Memory Available = 37539200 <291648>
55: 02-04-2008 MON 17:47:13 ConnectionManager
Memory Available = 37830848 <10234608>
56: 02-04-2008 MON 17:47:13 InternalMessageRouter
Preparing to initialize java.lang.Thread

57: 02-04-2008 MON 17:47:13 Unknown
(0000005394) Preparing to initialize java.lang.Thread
58: 02-04-2008 MON 17:47:13 InternalMessageRouter
Preparing to initialize java.lang.ClassLoader$NativeLibrary

59: 02-04-2008 MON 17:47:13 Unknown
(0000005393) Preparing to initialize java.lang.ClassLoader$NativeLibrary
60: 02-04-2008 MON 17:47:13 InternalMessageRouter
Preparing to initialize java.lang.ClassLoader

61: 02-04-2008 MON 17:47:13 Unknown
(0000005392) Preparing to initialize java.lang.ClassLoader
62: 02-04-2008 MON 17:47:13 InternalMessageRouter
Preparing to initialize java.lang.Shutdown

63: 02-04-2008 MON 17:47:13 Unknown
(0000005391) Preparing to initialize java.lang.Shutdown
64: 02-04-2008 MON 17:47:13 InternalMessageRouter
Preparing to initialize sun.misc.ThreadRegistry

65: 02-04-2008 MON 17:47:13 Unknown
(0000005390) Preparing to initialize sun.misc.ThreadRegistry
66: 02-04-2008 MON 17:47:13 InternalMessageRouter
Preparing to initialize java.lang.String

67: 02-04-2008 MON 17:47:13 Unknown
(0000005389) Preparing to initialize java.lang.String
68: 02-04-2008 MON 17:47:13 InternalMessageRouter
Preparing to initialize java.lang.Float

69: 02-04-2008 MON 17:47:13 Unknown
(0000005388) Preparing to initialize java.lang.Float
70: 02-04-2008 MON 17:47:13 InternalMessageRouter
Preparing to initialize java.lang.Class

71: 02-04-2008 MON 17:47:13 Unknown
(0000005386) Preparing to initialize java.lang.Class
72: 02-04-2008 MON 17:47:12 ConnectionManager
Memory Available = 48065456 <865560>
73: 02-04-2008 MON 17:47:10 Unknown
JVM Logger Thread Started
74: 02-04-2008 MON 17:47:10 LontalkIF
Neuron ID=00A372584401
75: 02-04-2008 MON 17:47:10 Interpreter
CIpPersistent::SaveOldVariable
76: 02-04-2008 MON 17:47:10 Interpreter
CIpListMan::LoadVolatile 6384 1
77: 02-04-2008 MON 17:47:10 Interpreter
CIpCodeMan::LoadCode 9990 1
78: 02-04-2008 MON 17:47:10 Interpreter
CIpUffHandler::Module Header
79: 02-04-2008 MON 17:47:10 Interpreter
CIpUffHandler::Project Name=Main
80: 02-04-2008 MON 17:47:10 Interpreter
CIpUffHandler::Root
81: 02-04-2008 MON 17:47:10 Interpreter
CIpUffHandler::Load - Begin...doc:PROG.TKN
82: 02-04-2008 MON 17:47:10 Interpreter
CIpNvMemory::NvInitalize NvRam Tested OK Used=1047536 Available=0
83: 02-04-2008 MON 17:47:10 ConnectionManager
Memory Available = 48480720
84: 02-04-2008 MON 17:47:08 ConfigurationManager
JVMStartParam(2): -Djava.security.manager -Doscar.profile.name=Duet org.ungoverned.oscar.Main
85: 02-04-2008 MON 17:47:08 ConfigurationManager
JVMStartParam(1): v1.1 runJava -XsafeExit -Xms8M -Dpath.separator=; -Djava.class.path=doc:/lib;doc:/lib/Oscar.jar
86: 02-04-2008 MON 17:47:08 ConfigurationManager
UDP Blink Message Time = 5 seconds (0=off)
87: 02-04-2008 MON 17:47:08 ConfigurationManager
Log Entry Count = 10000
88: 02-04-2008 MON 17:47:08 ConfigurationManager
TCP Timeout = 45000mS
89: 02-04-2008 MON 17:47:08 ConfigurationManager
NetLinx Sockets Message Queue Size = 50
90: 02-04-2008 MON 17:47:08 ConfigurationManager
PhastLink Receive Message Queue Size = 500
91: 02-04-2008 MON 17:47:08 ConfigurationManager
ICSNet Receive Message Queue Size = 200
92: 02-04-2008 MON 17:47:08 ConfigurationManager
LontalkHost Message Queue Size = 500
93: 02-04-2008 MON 17:47:08 ConfigurationManager
Lontalk Message Queue Size = 500
94: 02-04-2008 MON 17:47:08 ConfigurationManager
UDP Transmit Message Queue Size = 500
95: 02-04-2008 MON 17:47:08 ConfigurationManager
ICSP 232 Transmit Message Queue Size = 500
96: 02-04-2008 MON 17:47:08 ConfigurationManager
ICSNet Transmit Message Queue Size = 500
97: 02-04-2008 MON 17:47:08 ConfigurationManager
PhastLink Transmit Message Queue Size = 500
98: 02-04-2008 MON 17:47:08 ConfigurationManager
Axlink Transmit Message Queue Size = 800
99: 02-04-2008 MON 17:47:08 ConfigurationManager
Message Dispatcher Message Queue Size = 1000
100: 02-04-2008 MON 17:47:08 ConfigurationManager
IP Connection Manager Message Queue Size = 800
101: 02-04-2008 MON 17:47:08 ConfigurationManager
TCP Transmit Threads Message Queue Size = 600
102: 02-04-2008 MON 17:47:08 ConfigurationManager
Diagnostic Manager Message Queue Size = 500
103: 02-04-2008 MON 17:47:08 ConfigurationManager
Device Manager Message Queue Size = 1500
104: 02-04-2008 MON 17:47:08 ConfigurationManager
Route Manager Message Queue Size = 400
105: 02-04-2008 MON 17:47:08 ConfigurationManager
Connection Manager Message Queue Size = 2000
106: 02-04-2008 MON 17:47:08 ConfigurationManager
Notification Manager Message Queue Size = 2000
107: 02-04-2008 MON 17:47:08 ConfigurationManager
Interpreter Message Queue Size = 2000
108: 02-04-2008 MON 17:47:08 ConfigurationManager
Routing Flags = $0
109: 02-04-2008 MON 17:47:08 ConfigurationManager
AMX URL = www.amx.com
110: 02-04-2008 MON 17:47:08 ConfigurationManager
CRL Check level = 0
111: 02-04-2008 MON 17:47:08 ConfigurationManager
IPSec Enabled = 0
112: 02-04-2008 MON 17:47:08 ConfigurationManager
Timeline Loopcnt = 10
113: 02-04-2008 MON 17:47:08 ConfigurationManager
IP Threshold = 1500
114: 02-04-2008 MON 17:47:08 ConfigurationManager
Lontalk Threshold = 50
115: 02-04-2008 MON 17:47:08 ConfigurationManager
Interpreter Threshold = 1500
116: 02-04-2008 MON 17:47:08 ConfigurationManager
Device Holdoff = 1
117: 02-04-2008 MON 17:47:08 ConfigurationManager
URL Entry Count = 0
118: 02-04-2008 MON 17:47:08 ConfigurationManager
DNS Entry[0] = 192.168.3.1
119: 02-04-2008 MON 17:47:08 ConfigurationManager
DNS Entry Count = 1
120: 02-04-2008 MON 17:47:08 ConfigurationManager
Domain Name =
121: 02-04-2008 MON 17:47:08 ConfigurationManager
Serial Number = '210514x1170086'
122: 02-04-2008 MON 17:47:08 ConfigurationManager
System = 1
123: 02-04-2008 MON 17:47:08 ConfigurationManager
LoadConfiguration Complete (26920).
---
Changing fimware, rebooting, resetting to default settings doesn`t help. What can I do? How do I start the controler?

Comments

  • jjamesjjames Posts: 2,908
    Your message queues concern me. Are you running any modules? If so, which ones? Check for any FOR loops, or WHILE loops in your code.

    Also, try sending some very simple code to the processor, something like:
    BUTTON_EVENT[dvTP1,1]
{
   PUSH:
      SEND_COMMAND dvTP1,"'ADBEEP'";
}
    And see if that works. Your panel should do a double beep whenever you hit the button.
  • AuserAuser Posts: 506
    MaratGill wrote:
    82: 02-04-2008 MON 17:47:10 Interpreter
    CIpNvMemory::NvInitalize NvRam Tested OK Used=1047536 Available=0

    I suspect if you do a "show mem" you'll find that you've run out of non volatile memory. All variables are created as non-volatile unless otherwise specified...
  • ericmedleyericmedley Posts: 4,177
    Auser wrote:
    I suspect if you do a "show mem" you'll find that you've run out of non volatile memory. All variables are created as non-volatile unless otherwise specified...

    Perhaps you mean 'volatile.' Non-volatile variables require the keyword PERSISTENT before them. Persistent variables retain their values after a reboot. Volatile variables reset to null upon reboot.
  • DHawthorneDHawthorne Posts: 4,584
    ericmedley wrote:
    Perhaps you mean 'volatile.' Non-volatile variables require the keyword PERSISTENT before them. Persistent variables retain their values after a reboot. Volatile variables reset to null upon reboot.

    Nope, he means non-volatile :). The default is NON_VOLATILE, but that is nto the smae thing as persistent. Here's the run down:

    VOLATILE = reset to null on a reboot
    NON_VOLATILE = retain value after a reboot, but reset on a program load
    PERSISTENT = retain value after a program reload

    Non-volatile memory is relatively small, and running out of it is fatal. It is good practice to override the default and declare your variables VOLATILE to conserve it. This is especially true of modules, which eat a fair amount of memory in overhead alone. I have had the inclusion of too many non-volatile variable declaration in modules alone crash a master.
  • Danny CampbellDanny Campbell Posts: 311
    Are you sure the system is not in PRD mode? (Switch 1 on)
  • Spire_JeffSpire_Jeff Posts: 1,917
    DHawthorne wrote:
    I have had the inclusion of too many non-volatile variable declaration in modules alone crash a master.

    I've had this happen with the Escient fireball modules written by Escient. I had to go in and add VOLATILE in front of all the variable declarations.

    Jeff
  • MaratGillMaratGill Posts: 16
    Danny Campbell wrote:
    Are you sure the system is not in PRD mode? (Switch 1 on)

    No, DIP swich is off. I thing problem in memory of controler. If create simple program.

    ---
    DEFINE_VARIABLE
    integer g_Value
    ---

    compile and transfer send to controler. This code not work. But if change integer g_Value to valatile integer g_Value, this wiok...

    why? i don`t know... :(
  • ericmedleyericmedley Posts: 4,177
    DHawthorne wrote:
    Nope, he means non-volatile :). The default is NON_VOLATILE, but that is nto the smae thing as persistent. Here's the run down:

    VOLATILE = reset to null on a reboot
    NON_VOLATILE = retain value after a reboot, but reset on a program load
    PERSISTENT = retain value after a program reload

    Non-volatile memory is relatively small, and running out of it is fatal. It is good practice to override the default and declare your variables VOLATILE to conserve it. This is especially true of modules, which eat a fair amount of memory in overhead alone. I have had the inclusion of too many non-volatile variable declaration in modules alone crash a master.
    Yes, my bad. I see what he was saying now.

    And also, yes it is a good practice to put 'volatile' before variables to save memory. I've gotten in the habit of doing it always. In fact, I wish there was a way to do a volatile/non-volatile/persistent stack. If there is, please let me know.
    e
Sign In or Register to comment.