As you know we have been supporting ZIP and JAR files (they are the same as far as JANOS is concerned) for a while. JAR files being predominantly for application programs and Java support. More recent OS versions allow the WebServer to serve files directly out of a ZIP library. The DCP is an example where you need only add the
www.zip file to the /flash folder to install the set of files that are the DCP. There is no need to expand the library.
To do this JANOS is able to understand the ZIP/JAR file structure and extract data stored within it with either the STORE or DEFLATE methods. Presently JANOS cannot handle the LZW compression or many other ZIP options such as encryption.
I had once developed a program called “Curator” which was a backup utility that worked much like SVN and stored all of its data using LZW compression. We were always amazed at the compression ratios. I had even worried at times that there might have been a problem in figuring that ratio because sometimes it seemed way off. But the program worked and accurately recovered data.
So I do have code that I have written (although in C++ in that case) that can be used in JANOS to handle LZW. We just haven’t encountered it. Apparently DEFLATE is the compression method of choice.
So I expect that we will encounter externally zipped libraries that JANOS will not be able to process. In those cases depending on the reasons for the incompatibility I am prepared to implement the fix.
But the question now is whether or not there would be any use in the JAR command being able to compress files and create libraries? I realize it has been suggested and even entered in our Redmine system. Would this be something worth doing?
Would you trust your controller directly connected to the Internet?
We’ve been testing a JNIOR 410 on the network with only the following safeguards:
- Disable all accounts except the administrator ‘jnior’ account.
- Changed the ‘jnior’ account password.
There has been enough malicious activity attempting to login into the Telnet port that we have an application processing the access/log failed login reports and mapping the host locations. Try http://honeypot.integpg.com or https://honeypot.integpg.com if you prefer a secure connection.
Note that this unit is running the current Release Candidate for JANOS v1.6.2 as we have continued to enhance the unit’s ability to withstand life on the open network.
By the way there are a couple of publicly accessible web pages on this unit:
The Series 3 JNIOR continues to be a reliable workhorse in a number of industries. The Series 3 models (310, 312, and 314) however no longer represent the performance, reliability and stability of the current JNIOR controller line. We no longer produce them. While you would likely benefit from an upgrade to a Series 4 model (410, 412, or 414), doing so is still your decision. The change is almost seamless. Just know that INTEG will dedicate itself to the success of your conversion with the same attention and personal support that you have always experienced.
Just a few added benefits of the Series 4:
- Secure network connection using HTTPS, STARTTLS, etc.
- Faster execution making applications more responsive.
- Boots in only a few seconds.
- Dynamic Configuration Pages (DCP) replaces the Java Applet panel.
- Emphasis on Security.
- Simpler approach to application programming makes user programming even more feasible.
- Enhanced WebServer provides for the development of state of the art Web interfaces.
- Supports server-side scripting (PHP).
- Provides Websockets alternative to the binary JNIOR Protocol.
- And much more…
Do you have a need to control DMX-based lighting devices? You can do that now with the Model 410 and an adapter. This paper tells you what you need to do.
If you want to try it, we can help you here.
Meanwhile we are developing the 412DMX which will include a built-in DMX512 isolated interface.
You may not know that we are creating a JNIOR Model 412 that supports the DMX512 protocol for lighting control. Basically a DMX Output port replaces the AUX serial port that we find normally on the JNIOR. This will be dubbed the JNIOR 412DMX.
An initial prototype was completed and tested. It is functional. However, an issue in the mechanical mounting of the required 5-pin XLR connector necessitated a revision. By the slightest amount the connector interfered with the enclosure cover when mounted on the main PCB. While some creative machining could accommodate the connector it is not the proper way to do it. So the revision lowers the connector in an arrange as shown here. This should do just fine. We will see in a week or so.
This also avoids an issue that Kevin pointed out where the release tab was sitting higher than the unit. It could easily be damaged or damage something else. Here we see that it will be safely below the top of the cover.
In case you couldn’t picture the issue I show it here with the interference highlighted in yellow. You can also see how the release tab is inconveniently placed.
The solution adds a little cost but is the proper implementation.
I’ve located the entire DMX512 ISOLATED circuit on that little piece of PCB so this could be used by other product models.
The PCBs will be in this week and I’ll have to build a set. I milled one housing this morning and mounted the XLR connector to see how it likes its new home.
Now let’s hope that the PCB arrangement lines the connector up for this.
Yeah so the R01 boards are in. The revision was needed to move that XLR connector down. Perhaps you are mechanically inclined and can imagine what is involved in placing the DMX connector on the side of the enclosure. You need to reference the dimensions through the plastic housing and up through the PCB mounts and then onto the daughter board. So even though it can be done you are never 100% certain that you have it right until.. the hardware shows up.
So there is joy! Time to celebrate with some whiskey, right?
This is an ISOLATED DMX512 Output port. The isolation transformer is a tall component and that’s what that square recess is for. It will sit there. All of the RS-485 hardware and isolation is on that small PCB. The connector just carries Rx, Tx, Gnd, 3.3V and CHASIS connections. And that board will let me put these XLR connectors side-by-side for a product that has multiple outputs.
Well I’ve populated the DMX module. Everything looks good except I need to used a slightly taller pin header. Not a problem.
The 412DMX is ready to go. I just need to pull the package together for production.
This prototype has 20 seconds of ride-thru power backup and 128MB of Flash storage. The 5-pin standard DMX XLR connector sits perfectly now in place of the usual AUX port.