Netlinx NX Series
Joe Hebert
Junior Member
What do you all think about the new Netlinx NX Series introduced at InfoComm today?
http://www.amx.com/includes/pressrelease-file.asp?release=2014.6.18.c
http://www.amx.com/includes/pressrelease-file.asp?release=2014.6.18.c
Comments
-
Excellent, do we also get updated tools to code for the more powerful Controller?
-
So... compared to the NI series, 4 times the speed, 8 times the RAM, 8 times the storage space... in one U rack space.
The 2200 has 4 serial compared to 3 on the 2100, 8 compared to 7 on the 3100. With "standardized port numbering" at last. The 3200 is 2 2200's in one box. The 1200 is the same processor in a 700 box, 2 serial 2 IR.
An SD memory card slot? And all of them have ICSNET again? That's pictured but not clear in the spec.
Dual NIC? One port.
I hate I hate i HATE phoenix connectors for serial.
But looky there, the power phoenix has THUMBSCREWS to keep it alive.
The 4200 will add an ICSNET HUB.
Now if they actually enhance the compiler to match, we'll be better. The existing compiler has bounds and limits that seemed reasonable when it was written for a 16 meg processor in 1988. They are grossly unreasonable for today's speeds and ram sizes, like a 20 mph governor on a Corvette. -
I watched the video, and it seems that the ICSLan port is the second port of a dual NIC. It sounds like that's supposed to be the "AV Network".
-
...and I sure hope you can disable the power button shown on the front or the 4200. A power button??
-
Jeff Lockyear wrote: »...and I sure hope you can disable the power button shown on the front or the 4200. A power button??
The 4200 is slated to have an internal power supply (110VAC socket on the back), making it impossible to power cycle manually without physically unplugging the AC. If you ever had a Netlinx go unresponsive to commands, you'll understand the point of the power button. It is really any more frightening than a plug strip switch?
We usually put a power interrupt somewhere on the rack in order to recover from a lockup. We have to label it because it's not on the NetLinx. One of these that is ON the Netlinx is more obvious in purpose and effect, and no more threatening. In my opinion, it's welcome and reduces our rack work and eliminates an external power supply with more flaky phoenix pull-out connectors.
I would expect this power button is 100% mechanical, as it would do no good for it to send a command to a locked up Netlinx. So I'd bet against it be defeat-able either. -
Little disappointed that the NVRAM has not changed size, but otherwise, I am looking forward to its release!
-
Want more detail on the "updated Java" mentioned in the video!
-
Interesting points of difference from the Hardware Reference Manual (I notice them being more of an issue with replacing existing NI's) http://www.amx.com/assets/manuals/NX-Series.HardwareReferenceManual.pdf
Case Sensitive File System
Unlike the NI-Series controllers, all file names on the X-Series controllers are case sensitive. This includes all
user files created or used within NetLinx or Java code.
Difference in DEFINE_PROGRAM Program Execution
Due to differences in the underlying architecture of the X-Series masters, changing variables in the
DEFINE_PROGRAM section of code can negatively impact program performance.
@John, the power button is momentary and from the manual it will be hold for 2 secs to power off the NX. -
Here's hoping, the programming guide alludes to a Studio upgrade with a changed UI for the communications settings window.Now if they actually enhance the compiler to match, we'll be better. The existing compiler has bounds and limits that seemed reasonable when it was written for a 16 meg processor in 1988. They are grossly unreasonable for today's speeds and ram sizes, like a 20 mph governor on a Corvette. -
pdabrowski wrote: »Difference in DEFINE_PROGRAM Program Execution
Due to differences in the underlying architecture of the X-Series masters, changing variables in the
DEFINE_PROGRAM section of code can negatively impact program performance
While I think most code doesn't even need a define program section at all this change will affect allot of existing programs. I wonder how bad the impact will be?
I heard from an AMXer a year or so ago that they were going to move away from VxWorks, I think to Java on the new processor so I wonder what it is. -
AMX does listen sometimes Next generation master controllers feature requests

I am more interested in the bits that save me time on commissioning such as the USB ability to upload files and firmware. It's a pity you still need to connect a PC, if only I could give a program to a tech on a USB and they could plug it in, hold the ID button or reboot and voila! At least I don't need to teach them to use NetLinx Studio or FT2.
The thought of a Java back end scares the crap out of me, I don't want my whole system to run like a duet module and have half of my code break on a firmware update as the VM and OSGi platform are changed.
It's ICSLan, not ICSNet or ICSHub.And all of them have ICSNET again?
ICSLan is just a way AMX likes to label the standard network ports so that us AV guys can try and convince IT people that the AV network should be on a separate VLAN to the corporate network so we give it a name.
I used to work for a dealer that ran network points everywhere and labelled them AV LAN which I thought was a great concept at the time. -
I like the new command GET FAULT (Responds with DISABLED, NONE, SHORT, or NO DEVICE).
This will be helpful for the eternal issue of serial and IR ports wired wrong. -
These are not the droids you are looking for.... *waves hand*I heard from an AMXer a year or so ago that they were going to move away from VxWorks, I think to Java on the new processor so I wonder what it is.
Odds on it's android. Same as the new touch panels. -
I don't think it's running Android !!*but if it is it means we'll have to wait two years from now before we can use these products in a stable way....Odds on it's android. Same as the new touch panels. -
Odds on it's android. Same as the new touch panels.
I'm guessing this is a multi-core ARM system running Linux. Java SE for Cafe Duet will be a welcome upgrade. -
AMX does listen sometimes Next generation master controllers feature requests

The thought of a Java back end scares the crap out of me, I don't want my whole system to run like a duet module and have half of my code break on a firmware update as the VM and OSGi platform are changed.
Don't blame Java for the poor performance of Duet modules. I have written entire programs in Duet that are blazing fast, scrolling lists that update so fast you don't see the individual items update. The speed issue is not in Java. I do hope they have moved away from the Skelmir JVM, and moved to a more recent version of the JDK. I hope there is also an update for Duet because that ancient version of eclipse sucks! -
The consistent port numbering will be a small convenience. The case-sensitive filesystem is long overdue; I've always wondered why DOS and its ilk were (are) NOT case-sensitive. Additional speed and memory are always welcome. Dual network interfaces will come in handy and save some clutter in the rack. About time on the locking power connectors.
And I sincerely hope the underlying OS remains something UNIX-like - if no longer VXworks, then maybe one of the BSDs or something.
Like everyone else, I'd love to have one of these to play with for a little while.
. -
Don't blame Java for the poor performance of Duet modules. I have written entire programs in Duet that are blazing fast, scrolling lists that update so fast you don't see the individual items update. The speed issue is not in Java.
This has been my experience as well. I'm also hoping for an Eclipse and JDK upgrade. They've been hinting at this for a long time. -
Wow finally some decent speed processors. My guess is an upgraded Studio will be released eventually?? (or is that wishful thinking)?
GET_FAULT as mentioned above is kinda cool. How many times do techs not understand RS232 pinout?! -
New Version of NetLinx Studio
Watch for the release of NetLinx Studio 4 to support the new NX controller. It will not overwrite your Studio 3 install. There are some new features, but the basic layout will be familar to current Studio 3 users.
Studio 4 has been in beta for some time now so I expect it to be very stable. Someone can start a new Studio 4 thread once it is available to download, which should be vey soon.
Support for Access has been discontinued in Studio 4 which provides a reason to keep a copy of Studio 3. -
New OSI'm guessing this is a multi-core ARM system running Linux. Java SE for Cafe Duet will be a welcome upgrade.
I can confirm a Linux OS replacing VXWorks and a current version of Java VM. -
Dual NIC
The ICSLan port on the new NX controller will provide the system designer the flexibility to completely isolate the A/V hardware from the Enterprise LAN. This is not a software firewall like other control platforms, but a true Dual hardware NIC found on an Enterprise grade server.
The ICSLan port on the NX features a DHCP router and Master auto-binding for connected AMX control hardware. This eliminates time wasting Telnet configuration sessions for those ICSLan devices.
There will be no method for the ICSLan port to reach the Internet through the Master, so be aware if you are using G5 panels or Enzo that would benefit from an Internet connection. -
BC thanks x 4 + 1. What's the impact on performance from assigning vars in define_program all about.
-
Network support and Enterprise securty
The new NX series controllers supports IPv6/IPv4 networks and 802.1x authentication for Enterprise grade network security.
IPv6 reference - http://en.wikipedia.org/wiki/IPv6
802.1x reference - http://en.wikipedia.org/wiki/802.1x -
QuestionsBC thanks x 4. What's the impact on performance from assigning vars in define_program all about.
I will see what I can find out.
My first look at the NX was at InfoComm so I am sure there will be many more questions. I suggest interested folks download the hardware and programming manuals and start reading. (I will starting on Monday.)
Hardware manual - http://www.amx.com//assets/manuals/NX-Series.HardwareReferenceManual.pdf
Programming manual - http://www.amx.com//assets/manuals/NX-Series.WebConsole-ProgrammingGuide.pdf -
NX Series Videos
Product Overview - http://www.youtube.com/watch?v=xUlEUfcf5RY
Part 1 - Technical Overview, http://www.youtube.com/watch?v=rPFHZ2Cq5II
Part 2 - Network Capabilities, http://www.youtube.com/watch?v=PqZfRtDm2qA
Part 3 - USB Ports, http://www.youtube.com/watch?v=py7dkPYNhPo
Part 4 - ID Button, http://www.youtube.com/watch?v=8L6PFFrf5XU
Part 5 - Serial & IR Port Diagnostics, http://www.youtube.com/watch?v=jca7RVdzsvE -
B_Clements wrote: »I can confirm a Linux OS replacing VXWorks and a current version of Java VM.
Current Version, does that mean JSE 1.6 or 1.7? Surely not 1.8. -
Current Version, does that mean JSE 1.6 or 1.7? Surely not 1.8.
1.7 is what I was told on the show floor. -
Really I would have been excited about 1.5, generics alone would have made me happy. 1.7!!! I am impressed! I wonder how licensing is going to work with Duet now? Will the new version have to be purchased again? I am still not clear on who was charging that licensing fee, was it VxWorks, the JVM provider, etc?
Categories
- All Categories
- 2.5K AMX General Discussion
- 922 AMX Technical Discussion
- 514 AMX Hardware
- 502 AMX Control Products
- 3 AMX Video Distribution Products
- 9 AMX Networked AV (SVSI) Products
- AMX Workspace & Collaboration Products
- 3.4K AMX Software
- 151 AMX Resource Management Suite Software
- 386 AMX Design Tools
- 2.4K NetLinx Studio
- 135 Duet/Cafe Duet
- 248 NetLinx Modules & Duet Modules
- 57 AMX RPM Forum
- 228 MODPEDIA - The Public Repository of Modules for Everyone
- 943 AMX Specialty Forums
- 2.6K AMXForums Archive
- 2.6K AMXForums Archive Threads
- 1.5K AMX Hardware
- 432 AMX Applications and Solutions
- 249 Residential Forum
- 182 Tips and Tricks
- 146 AMX Website/Forums
