I try to connect to master
Ad_My_Xperience
Posts: 73
in AMX Hardware
Hi folks!
I've bought a used NI-3100 and when I try to connect to or listen from Studio, I don't receive any response. Is there a way to "factory default" the controller or Something like that. It's not my first used controller and never had problem with that.
Thanks in advance.
Michael
I've bought a used NI-3100 and when I try to connect to or listen from Studio, I don't receive any response. Is there a way to "factory default" the controller or Something like that. It's not my first used controller and never had problem with that.
Thanks in advance.
Michael
0
Comments
From telnet
"set udp bc rate"
It responds with the current rate (default 5 seconds) and asks for the new rate. If you enter 0, no broadcast, nothing to LISTEN for. You can enter up to 300 (seconds, 5 minutes) for the interval. I set the rate to 300, to reduce network chatter due to the broadcast, but not to eliminate it if a LISTEN is ever needed. Just remember you need to wait on the LISTEN screen for up to 5 minutes with that setting.
Use TERMINAL in STUDIO just like TELNET. You can ask or set the ip from there. Using the program port... unless SECURITY was set for that port and you don't have the login... at which point you have a brick. Although AMX can revive it for a fee.
I installed Wireshark but don't know how to use it to find IP from controller. Help please...
.
If it's on static IP on a different network than your computer, wireshark may see it as described above.
If the beacon is OFF, there's nothing to see.
As mentioned above, you can/should try using the serial programming port, connect using TERMINAL in TOOLS in Studio. You'll need to type ECHO ON to see what you are typing, but you should get a prompt and responses just like in TELNET. And all the TELNET stuff works about the same in terminal. You can SET IP and such.
However, if SECURITY is turned on, and also on for the programming port, and you don't have the account login, you are so very done.
I don't know of any way other than sending it to AMX to do a reflash to recover from that.
Anyone?
We recommend setting the UDP BC RATE to the max, 300 seconds rather than 0 so LISTEN still works, even if you have to wait 5 minutes. The default of 5 seconds is more thrash than value.
And never lock out the programming port if your job does not insist on it for complete security. In most cases, if someone is close enough to have physical access to the serial port, they probably are not a threat.
I tried both but never connect
Your clip indicates it found the UDP broadcast from the NetLinx. Maybe. What's your PC's IP address? You might be looking at yourself, NLStudio pinging...
But if these 65. addresses are not your local network addresses, you will NEED to set your PC to the 65.242.94.x network to talk to these addresses... likely the static address set in the NI.
The range I can use in my router are :
- 192.168.0.0 to 192.168.255.255
I change my router IP to 65.242.94.1 and DHCP range from 65.242.94.100 to 65.242.94.200 and tried to connect or listen and failed again (boring)So those IP addresses are useless to talk to the NetLinx. It remains at an address you can ONLY FIND NOW by a terminal session using the SERIAL PROGRAMMING PORT as described in AMX training and support materials.
On this note I've been able to keep my Prolific brand USB Serial adapters running in Windows 8.1 and 10 by rolling back to a driver from 2008 each time I want to use the device (a PITA but I haven't had a problem since discovering this). I've found that the drivers forced on us by the OS updates are causing errors in device manager that go away after forcing a change of driver.
Less of a pain was tossing my non-compliant one and buying a WIN10 certified replacement for all of $6 on the Bay of E.
What is missing now?
I found CC-COM programming port cable with pins 2 and 3 swapped and pin 5 straight through. Is that one I need?
Not sure of pinout: Like all rs232 troubleshooting. Try both.
Of course it can't help with a bad port or mistaken baud (although with just bad baud, you would likely see some garble at least).
You also may actually have a dead NetLinx, of course...
I think like mattl it's a capacitor problem.
Thanks all for helping.
Mike