Odd problem
Spire_Jeff
Posts: 1,917
I was onsite working on an upgrade and I had the weirdest problem I have seen in a while. The system:
NI-2100
AXD-IR+
ENET24-POE
MX-950 with an MRF-350
There are also 3 other processors on the network. 2 more NI-2100 and 1 NI-3100 with ICSNet. The NI-3100 has the other three processors in its URL list. There is no master to master code in place at this time.
The problem I was having was that none of the button pushes seemed to be functioning. Most of the button pushes were set to pulse IR commands. (I was using some existing code to start). I saw the button pushes happening in the PUSH MESSAGE Status bar, but I did not see the IR leds flashing. I resent the IR files and verified that the code was activating channels with actual IR codes assigned to them. Still nothing. I then tried to turn on the power off channel through CONTROL A DEVICE and the LED lit up bright and the device turned off.
I began to doubt the code (even tho it was fairly straightforward and simple). I commented out EVERYTHING and left only the couple device definitions needed and a single button event. I also changed from a PULSE to SEND_COMMAND,"'SP',BUTTON.INPUT.CHANNEL". I sent the program over and tried again. Same thing happened, I saw the button pushes, but nothing was happening on the IR ports. I disconnected the NI-3100 from switch and rebooted the NI-2100 just in case there was some communication causing the problem. Tried again and the same problem.
I called Tech support to see if there was something obvious I was missing. We went back through a couple of the things I checked and got the same results. Then it was suggested that I add a SEND_STRING 0, command to make sure the code was executing. I resent the program and tried again. I saw the diagnostics messages coming through, but the IR commands weren't doing anything. As a last ditch effort, I disconnected my laptop from the switch and connected it directly to the processor. I resent everything and verified all of the wire connections.
I tried it again and didn't even see a button push. I checked the MRF-350 and noticed it was now having problems. I solved the problem by moving the RF receiver as far away from the TV and equipment as possible. I tried it again and now the IR emitters were functioning properly. I then uncommented all of the code and it all worked. I then started reconnecting everything on at a time and got back to my initial configuration and everything was still functional. Has anyone else had any problems that are similar or any ideas on what initially caused the problems? In the end, the only change I made was moving the RF receiver away from the processor and other equipment. In one of the other NI-2100 installs, the RF receiver is in close proximity to the processor and functions properly.
I am thinking that there is probably some interference coming from some of the equipment near the problematic processor. If that was causing all of my issues, why was I seeing the button pushes and SEND_STRING 0, messages?
I am sure I forgot some of the things I checked, so if you have any ideas, please post away.
Jeff
NI-2100
AXD-IR+
ENET24-POE
MX-950 with an MRF-350
There are also 3 other processors on the network. 2 more NI-2100 and 1 NI-3100 with ICSNet. The NI-3100 has the other three processors in its URL list. There is no master to master code in place at this time.
The problem I was having was that none of the button pushes seemed to be functioning. Most of the button pushes were set to pulse IR commands. (I was using some existing code to start). I saw the button pushes happening in the PUSH MESSAGE Status bar, but I did not see the IR leds flashing. I resent the IR files and verified that the code was activating channels with actual IR codes assigned to them. Still nothing. I then tried to turn on the power off channel through CONTROL A DEVICE and the LED lit up bright and the device turned off.
I began to doubt the code (even tho it was fairly straightforward and simple). I commented out EVERYTHING and left only the couple device definitions needed and a single button event. I also changed from a PULSE to SEND_COMMAND,"'SP',BUTTON.INPUT.CHANNEL". I sent the program over and tried again. Same thing happened, I saw the button pushes, but nothing was happening on the IR ports. I disconnected the NI-3100 from switch and rebooted the NI-2100 just in case there was some communication causing the problem. Tried again and the same problem.
I called Tech support to see if there was something obvious I was missing. We went back through a couple of the things I checked and got the same results. Then it was suggested that I add a SEND_STRING 0, command to make sure the code was executing. I resent the program and tried again. I saw the diagnostics messages coming through, but the IR commands weren't doing anything. As a last ditch effort, I disconnected my laptop from the switch and connected it directly to the processor. I resent everything and verified all of the wire connections.
I tried it again and didn't even see a button push. I checked the MRF-350 and noticed it was now having problems. I solved the problem by moving the RF receiver as far away from the TV and equipment as possible. I tried it again and now the IR emitters were functioning properly. I then uncommented all of the code and it all worked. I then started reconnecting everything on at a time and got back to my initial configuration and everything was still functional. Has anyone else had any problems that are similar or any ideas on what initially caused the problems? In the end, the only change I made was moving the RF receiver away from the processor and other equipment. In one of the other NI-2100 installs, the RF receiver is in close proximity to the processor and functions properly.
I am thinking that there is probably some interference coming from some of the equipment near the problematic processor. If that was causing all of my issues, why was I seeing the button pushes and SEND_STRING 0, messages?
I am sure I forgot some of the things I checked, so if you have any ideas, please post away.
Jeff
0
Comments
In Dec. I had a problem much like this. The system would not work at all, no lights etc, code had been running for 2 yrs before hand. Checked everything, after sometime I moved the reciever for the TP and bang it started to work again. The reciever wasn't to close to the controller in my case but to a RJ45 lan cable. It looked like the reciever was picking up trash from the network and locking everything up.
Jeff