JMRI Code: Network Access
This page describes various forms of network access available in JMRI. More capabilities are added all the time, so please check with the user group for up-to-date information.
Methods of Network AccessJMRI interacts with networks in two basic forms: downstream connections and upstream connections.
A downstream connection allows JMRI to connect to a layout via a network for operations and control. This uses a network connection to do the same kinds of things that are often done via serial RS232 and USB links.
An upstream connection allows other devices to command JMRI over a network connection. In this case, the network connection allows other devices and/or programs to do things that are normally done via scripts and the graphical user interface.
In the rest of this page, we provide links to the various examples of those two general areas.
Downstream (networked layout hardware) connections
- LocoNet systems
- This exchanges the C/MRI poll/response protocol via a terminal server
- CAN via MERG Network Interface
- This exchanges the EasyDCC ASCII command station protocol via a terminal server
- This exchanges the NCE command station protocol via a terminal server
Upstream (networked JMRI operations) connections
- Built-in web server
This is advertised on Bonjour/Zeroconf as a "_http._tcp.local." service. In particular, this contains the JMRI XMLIO support, which allows web browsers (with or without AJAX) to monitor and control a layout by accessing a JMRI XMLIO Servlet via the web. It also includes facilities for displaying and clicking on any open JMRI window.
- Via Python/jython scripting
remote throttles such as the iPhone or Android.
(WiThrottle product web
Engine Driver page)
This is advertised on Bonjour/Zeroconf as a "_withrottle._tcp.local." service.
- Via running JMRI as an Enterprise Java Bean
- Via providing a LocoNet RMI
This is advertised on Bonjour/Zeroconf as a "_jmri-locormi._tcp.local." service.
- Via providing a LbServer
This is advertised on Bonjour/Zeroconf as a "_loconetovertcpserver._tcp.local." service. (Name pending approval from the original protocol developers)
- Via providing an SRCP server
This is advertised on Bonjour/Zeroconf as a "_srcp._tcp.local." service.
- Via providing a JMRI Server implementation.
See also the DNS-SD page for more information on Zeroconf/Bonjour/"DNS Service Discovery" networking.
Search "man dns-sd" for more information on the dns-sd debugging command-line tool.