Ni-4100 RS-232 Problem
prakash
Posts: 33
Hi,
I am using NI-4100. IR and relays are workingfine but Serial devices are not responding. DIP switches are OFF OFF OFF OFF OFF ON ON ON ON. I checked my connections and also checked baud rates but only Tx is blinking in RS-232 devices when i am giving commands to my controller. Virtual devices are also shoeing in online tree.
Any suggestions plz....
I am using NI-4100. IR and relays are workingfine but Serial devices are not responding. DIP switches are OFF OFF OFF OFF OFF ON ON ON ON. I checked my connections and also checked baud rates but only Tx is blinking in RS-232 devices when i am giving commands to my controller. Virtual devices are also shoeing in online tree.
Any suggestions plz....
0
Comments
http://www.amxforums.com/search.php?searchid=466234
The link no workie
This is the link that search gives me today, it shows four threads.
http://www.amxforums.com/search.php?searchid=466436
We've all experienced the capacitor issue.
Do a forum search for c206.
Apparently a search result link has a short life span.
We've been upgrading systems that had the Panja NI controllers in them with NI3100s. I don't think I've seen a failure with one of the Panjas yet.
AMX has said that "later production" NI 2100/3100's have improved circuitry/parts and should not have this failure. When they are another 5 years older, we'll know.
They know which are the newer ones by serial number. They'll tell you if yours is newer.
They will repair the serial ports on any "eligible" older processor for $150. We and our dealers have sent in dozens of them.
Eligible meaning not a newer one built after the changes. But the newer ones "shouldn't" need it, right?
We've seen very few (but a few) failures on the "checkerboard paint" NI's. We've seen plenty on the "stripe paint" models. This is not a prediction, it is our observation.
We won't repurpose or update any systems using an older NI without doing an AMX rebuild as a matter of course. $150 is cheap compared to rolling a truck and having to replace the unit later. Actually, we keep a few fresh rebuilds and trade them into systems when we do significant other services... instead of waiting for them to fail. Then the takeout goes in for refurb, and becomes stock.
OK, perhaps I have narrowed down my problem. I thought it was in the code that I could not set up my lighting control but now in trying to set up audio distribution through serial, I am not getting results either.
I crossed pins 2 and 3 to check in "notifications" if I my string was getting through. I see the string sent to the proper port upon "button event" but no return string.
I found the threads on the capacitor (c206) issue with the NI-3100 controllers. I do not seem to have RX on any serial port though my meter reads 10v between pins 3 and 5. Could this still be a problem with the capacitor?
I am considering the option of repairing it myself based on some write ups I saw both on this forum and this web site- http://www.jackkolesar.com/articles/2012/08/18/amx_ni3000_serial_port_fail.html
It doesn't seem too difficult and it appears from other post that AMX is charging a healthy fee now to resolve the problem.
Has anybody changed this capacitor themselves with good results?
Sounds like the cap issue for sure. I just replaced a master last week for the same reason. Amazing how a cheap component can cause such a catastrophic failure.
Unlikely. There is a chance that the cap is on its way out, but if you are seeing 10V on the TX pin then the charge pump circuitry is doing its job.
Plug a loopback adaptor into the serial port (ie. short pins 2 and 3) and see if you are getting responses when you send a string. Ignore waiting for responses in diagnostics - watch the LEDs on the front panel of the unit.
- If the TX and RX ports both light up, the serial port's fine.
- If the TX LED does not light check your code/DPS addressing in diagnostics.
- If the TX light is flashing but the RX light is not, issue the following commands to the port and try again:
If it's still not working after sending these commands, it may be a faulty port due to the capacitor issue.