Tag Archive: troubleshooting

All JNIORs have the ability to boot into a state called Safe Mode. Safe Mode enables the default ‘jnior’ ‘jnior’ username and password for logging in, and disables all applications from running on boot. This is extremely useful in situations where you either forgot your JNIOR log-in, or have an application that is locking up your JNIOR before you can access it. Here is how to boot your JNIOR in Safe Mode.

NOTE: Do not leave your JNIOR in Safe Mode after you are done using it. Safe Mode’s features can interrupt the JNIOR’s functionality when left on.

Power Off and Disconnect the JNIOR

Before attempting to boot your JNIOR in Safe Mode, make sure your JNIOR is disconnected, and that no power is being supplied to it. This helps ensure the JNIOR is not damaged, and leads into rebooting the JNIOR after we enabled Safe Mode.

Locate A Jumper From Outputs 1 or 2

The first thing we need to do is grab a Jumper off of the JNIOR. You’ll start by unscrewing the JNIOR’s lid and locating the Jumpers on outputs 1 and 2. These outputs have Jumpers on them because they are able to be set to normally opened or closed. You’ll want to vertically pull one of these Jumpers off the output pins they are attached to. (These should just pull off by grabbing the plastic ends sticking out off the Jumpers.)

Locate Hole for Safe Mode Jumper

Every JNIOR has a small opening between its Ethernet port and RS-232 serial port. In this small opening are two pins that can have a jumper placed on them to force the JNIOR to boot in Safe Mode.

Plug Jumper Into Safe Mode Pins

Now taking the Jumper, you are going to slide it into the hole, and plug the Jumper into the two pins on the board in front of the small opening. Once the Jumper is in place, and resupply power to it.

Check if JNIOR is in Safe Mode

Once the JNIOR is powered back on, the only way to check if the JNIOR is successfully in Safe Mode is by making a command line connection to the JNIOR, and seeing if it says *SAFE MODE in the boot dialog. If this gets displayed, you have successfully booted the JNIOR in Safe Mode!

Once you are finished making changes in Safe Mode, make sure disconnect power to the JNIOR again, move the Jumper you used back to the output it was taken from, and screw the lid back on the JNIOR.

When updating a Series 4 JNIOR from version 2.0 or older to a newer version, there is a rare chance you may lose access to the JNIOR Web Page. This is because the Web Page pathing was changed in JANOS 2.0 and sometimes doesn’t correct itself after updating. Below is an update project that you can publish to a JNIOR to potentially fix this issue. 

Name Version Release Date Size MD5
Web Page Pathing Fix Nov 01 2023 398.0 B 034746058ad41a7c44e3e6079c9cf8bd

If you are still having issues accessing your JNIOR’s webpage, please reach out to our support to get your setup working again.

When you boot up the JNIOR Support Tool, typically all the JNIORs on your network should appear in the Beacon tab. Sometimes though, you may be greeted with an empty Beacon tab even though you have JNIORs on your network. This may be your firewall blocking the Beacon protocol that allows JNIORs to be discovered in the Beacon tab. Here is how to allow the Beacon protocol through the Windows Defender Firewall.

NOTES: You may have third party firewalls setup on your computer blocking the Beacon protocol besides Windows Defender. Check these to make sure they aren’t blocking the Beacon protocol as well. Also, this walkthrough was done on Windows 10, and depending on your Operating System and Version, you may need to take different steps.

You’ll first need to open your Window Firewall Defender. Once its open, first you’ll need to select Inbound Rules, then right click it and select New Rule.

Once selected, the Inbound Rule Wizard dialog will open and you’ll select the following for creating the rule:

  • Rule Type will be Port
  • Protocol will be TCP, and the port will be 4444
  • Action will be to allow the connection
  • Leave defaults for the Profile
  • Enter any name and description for this new rule

Once all these steps are complete, you’ll hit finish and the rule should be created. You’ll then repeat this process for creating an Outbound Rule. Once an Inbound and Outbound Rule have been created for the Beacon Protocol, re-querying in the Beacon tab of the Support Tool should hopefully get your units to appear if they were being blocked by your firewall!

If JNIORs are not showing up in Beacon then your network could be blocking UDP broadcasts.  We recommend trying to use the Query Range feature or defining a JNIOR Listing as explained in the Beacon Overview article.

Another thing that may be happening is that the JNIORs and your PC are on different subnets and the router or switch between the subnets is not forwarding UDP traffic.

What Battery does the JNIOR use?

In the 410, 412, and 414, the battery is a CR2032 coin cell battery.  The 412DMX battery is a CR1632 coin cell battery.  The battery in the Series 4 JNIORs is replaceable.  The battery in the Series 3 JNIORs was not replaceable.  The batteries have a life of around 6 or so years.  This can vary and is impacted most by the amount of time that the unit is without external power.

What does the Battery do for the JNIOR?

The battery is needed to maintain the SRAM and the clock.  The SRAM holds the root of the filesystem.  Most notably, log files.  Log files are useful for debugging an issue and can be frustrating if they keep getting reset.  The battery is only needed in the event that the JNIOR loses external power.

What happens when the Battery dies?

The unit will operate correctly in the event that the battery dies.  The issue with a dead battery is only noticed if the JNIOR loses external power.  If the battery dies and external power is lost then the RAM will be reset.  You will see the following message on the next boot.  “SRAM was reformatted on boot”.  The clock will also be reset to January 1, 1970 0:00 UTC.  The clock will be fixed if the JNIOR has access to a NTP server.

How do I know if the Battery is good or bad?

The battery voltage can be measured with a voltmeter.  The voltage of a good battery should be 2.7 volts or greater.

In rare instances, Series 4 JNIORs can become unresponsive. This can happen for example when a JNIOR is interrupted when their OS is being updated, or when the JNIOR has a network lockup. When this happens, their is an unconventional way to get the JNIOR working. Here are the steps to potentially get your Series 4 JNIOR operating again. This process requires you to physically have the JNIOR near you, along with a business card (or something similar and non-conductive) and a Phillip screw driver.

Take Off Lid of the JNIOR Case

To start, we need to remove power from the JNIOR, as we are going to open the JNIOR case. Once the JNIOR has no power, we need to remove the lid of the JNIOR case to access the JNIOR’s coin battery on its circuit board. There are 4 screws that keep the JNIOR lid on, and they can be removed with a Phillip’s screw driver. Once removed, the case’s lid should easy come off.

Find the Coin Battery

Once the lid is removed, you should see the coin battery at the top middle of the JNIOR’s circuit board. Notice there is a metal contact plate on top of the battery. The metal contact plate and the coin battery need physically interrupted from touching each other.

Separate Coin Battery from the JNIOR

Slip the business card between the coin battery and metal contact plate. This will disconnect the JNIOR’s RAM from the battery. Once the business card is in place, power up the JNIOR for 30 seconds, giving the JNIOR enough time to reset the RAM memory. After 30 seconds, remove power from the JNIOR again, remove the business card, re-attach lid to the JNIOR, and then power up the JNIOR again. Hopefully with this, the JNIOR should be working properly!

NOTE: If you don’t have a business card or something similar, you can also just remove the coin battery as well.

To re-iterate the steps taken:

  1. Power down the JNIOR
  2. Remove JNIOR’s case lid
  3. Locate coin battery
  4. Insert business card between coin battery and metal contact plate
  5. Power on JNIOR for 30 seconds
  6. Power down the JNIOR
  7. Remove business card
  8. Re-attach JNIOR’s case lid
  9. Power on the JNIOR

Using the JNIOR should be a smooth process, with only having to connect an Ethernet cord to your network and finding it in the JNIOR support tool. Unfortunately, nothing always goes perfectly, and maybe you aren’t able to access your JNIOR via beacon or an internet browser. Connecting to a Series 3 JNIOR serially is a great way to troubleshoot when it’s no longer responding correctly. This post will briefly go over how the JNIOR can be connected serially to access and hopefully fix this issue.

To access the JNIOR serially, a serial cable needs to be connected between the RS-232 port on the JNIOR and your computer. If you don’t have a serial port on your computer, you may need a serial to USB cable instead. Once that is connected, you can then open a command line prompt (You can open an easy-to-use command line from the support tool under the Tools Tab.) and access the serial connection. When doing this, make sure that the settings for the Serial Connection match what your JNIORs are. If you can’t check, the default settings for the connection are:

  • Baud Rate: 115200
  • DataBits: 8
  • StopBits: 1
  • Parity: None

Once you have set the correct serial settings, you should be able to hit connect and access the JNIOR via the command line! If by chance you are trying to change the JNIOR’s IP because it’s using one that doesn’t work with your local networks IP, you can change the IP of a JNIOR by using the ‘ipconfig’ command. Simply enter ‘ipconfig -a’ followed by a space and the IP address you are trying to change the JNIOR to. For example, if you are trying to change the IP address to, you would use this in the command line: ‘ipconfig -a’.

Version 3.4 introduced a bug that prevented DMX client connections from working.

This was due to the AppData/Dmx/TerminationBytes registry key not processing the escaped string correctly.  \r\n should be processed as 2 bytes, one Carriage Return and one Linefeed.  Unfortunately the string was not un-escaped  and the termination string was processed as 4 bytes, ‘\’, ‘r’, ‘\’, ‘n’.

Here is a Wikipedia article on Escape Characters for those who are interested.


Version 3.5 has been released to resolve this issue.

When using Tasker, there may be an instance where something isn’t working properly. Here is a list of solutions for different issues where your Tasker setup might not be running correctly.

Workspace/Trigger/Schedule/Task may be disabled

When waiting for a schedule to activate, pressing a control panel to activate a trigger, or executing a task in the Task tab, all three of these things can be disabled so they don’t activate when you don’t want them to. Even the entire workspace can be disabled. Make sure that when activating something in Tasker that it isn’t disabled. You can make sure by looking at the checkbox next to them and making sure they are checked. Checked means enabled, unchecked means disabled.

Variable/Value is not logging

Being able to use variables and reference I/O on the JNIOR in Tasker is major factor in Tasker’s usefulness. Sometimes though, if these variables/values aren’t entered correctly, it can lead to errors in Tasker. If you are logging variables/values in Tasker, make sure that you are encasing each one in {{}}. This denotes the value as not just a string of letters but the actual value its supposed to represent.

Variable isn’t working in different Task

One of the ways variables in a workspace are useful, is that they can be referenced from other tasks. You can create a Global Variable by putting “$$” in front of it. For example, if you wanted the word “number” to be a Global Variable, when you declare it you’ll put “$$number”. 

Tasks in the Task Tab are grayed out

An easy way to test a Task is by manually executing it in the Task Tab. When you are currently within a workspace that has changes being made to it though, the play buttons to execute tasks are grayed out. This is because the workspace needs to save the changes made before it can execute Tasks.

External Module not working when referenced in Tasker

In Tasker, you can reference External Modules that you have connected to the JNIOR in Tasker. Sometimes though, Tasker might have trouble interacting with your External Modules. This is because when you connect an External Module to the JNIOR, its information is saved. Then if a different External Module is connected, it may still be trying to connect to the previous one that was there. To avoid this issue, make sure when a External Module is removed that you perform the “extern -r” command in the JNIOR console. This will clear any information in the JNIOR of External Modules that are no longer connected, and Tasker will then reference only Modules currently connected to the JNIOR.

Communication action not working with Device

Tasker has the functionality to communicate with other devices, sending them data or commands. When communicating with an external device though, you need to make sure that the device you are sending to is configured to receive data the same way the device in your device tab is configured to. Make sure if its a TCP send that the device has the IP and TCP port you set for the Ethernet Device in the Device Tab. Same goes for SNMP with its IP and UDP port.

When you are using the JNIOR, you may want to change the IP address to fit a pre-existing schema for JNIOR’s on the network. JNIOR’s are set to use DHCP by default to get their IP address. DHCP searches a network the JNIOR is trying to connect to and finds an available IP on the network for it automatically. If the IP of the JNIOR gets set to, this is because a device on the network is already using that IP address. The JNIOR doesn’t want to interrupt pre-existing IP communication with a device on the network, so rather than take the IP and create a conflict between itself and the other device, it simply defaults its IP to To confirm another device is on your network using the same IP, you can try pinging the IP Address that has the additional device on it. If the ping replies successfully, you’ll know you have another device somewhere that is on the network using that IP. In order to ping on windows, you simply open the command line and type “ping (IP address)”. NOTE: Not all devices on a network have ping capabilities.

Ping command in windows command line

To resolve the issue, you have to change the JNIOR or other device on the network to another IP that prevents the two devices from conflicting with each other. To change the IP address from the command line, you can do so using the ipconfig command, entering “ipconfig -a” followed by the new IP address you want to assign to the JNIOR. You can also do so from the Support Tool by right-clicking a JNIOR in the beacon tab and selecting Configure/IP Configuration, which opens a dialog box that can be used to set the IP of the JNIOR as well. This is where DHCP can be disabled as well, which can fix a IP when DHCP can’t find an available IP address on the network, or if the network doesn’t support DCHP.

A lot of JNIOR applications log information about what they are doing. This information can be about different things. Sometimes the application is purposely creating log files to keep track of data such as water levels or I/O changes. Logs can also be used to keep track of information about the application itself and if its run into any errors. Here is a quick post on how to look at Logs on a JNIOR.

To access information on a Series 4 JNIOR, you’ll first need to open the JNIOR WebUI. Once the on the JNIOR WebUI, you’ll then access the folder tab. Here you can see a list of all the files located on the JNIOR. Navigating through the folder shows the different files you can view, including log files.

Folders tab of JNIOR Web Page

Another way to access files on either a Series 3 or 4 JNIOR, you can open the File Transfer Protocol from the Support Tool. To start you’ll open the Support Tool, then in the beacon tab you’ll right click on the JNIOR and select Tools/Open FTP. You’ll then see a dialog open asking for the JNIOR’s username and password. Once you enter that, you should see all the available files on the JNIOR, including log files.

NOTE: The address in file explorer will match your JNIOR’s IP Address

Sometimes an application wont run on a JNIOR Series 3 unit.  This issue may be due to “insufficient heap“.

This error message means that there was not enough contiguous space in “heap” or the SRAM memory for the application.  The application must find contiguous memory of at least the file size of the application.  Once the application finds that space it will stay in that same space until the application is updated.  The memory can become fragmented over time since the SRAM is used for application executables, application memory and the root file system.

Most likely this error condition will occur after updating to a new version of an application.  If the new application is larger than the old application it cannot occupy the same contiguous block in memory.  It must find a new contiguous block.  That space may not be available depending on the fragmentation of the memory. Even if there is a contiguous block of memory large enough when the file is updated, it still might give you an “insufficient heap” error. This might happen because until its run as an executable, the file doesn’t know it needs to be stored as contiguous space and fragment its memory anyways, which would then cause the error.

The fragmentation is caused by file blocks that have become scattered throughout memory over time.  To clear up the fragmentation we could delete a file at a time until a contiguous block has become available.  This would be a very slow approach.  You would not know which file gives you the best chance of finding a contiguous block.  Since the root of the file system contains mostly log files we can just clear the heap on a reboot.  In order to that we execute the reboot -a command.

What about my cinema devices and macros files?

The cinema files are automatically backed up to flash/cinema_backup.  This location is not affected by the reboot -a.  The cinema files will be restored next time cinema runs.

If you experience issues with your Dolby IMS2000 Cinema Server connecting to or executing commands on the JNIOR you may need to follow one of the procedures below. There are two issues that I have seen.

Dolby has resolved the issue for the IMS3000.

A Dolby may not even try to connect to a JNIOR when it should.

Make sure you have rebooted the Dolby IMS after adding the JNIOR as a device.

To determine if this is the issue:

  1. Go to the DCP for the JNIOR
  2. Click on the Console tab
  3. Click ‘Start Session’
  4. Log in when prompted
  5. enter the netstat command
  6. There should be a connection to 9200 with the Dolby Server IP Address for the Remote IP

The Dolby is connected but nothing happens on the JNIOR when the Dolby sends the command.

When Dolby tries to connect to the JNIOR it may not be able to log in to the JNIOR due to a bad password. The highlighted bytes below are corrupted.

The bytes should represent the password like this…

The previous images are screenshots for the WireShark application when analyzing a network capture. This capture is included in a JNIOR Support Tool Snapshot. I have been told by Dolby that this is likely due to the browser auto-fill.

To determine if this is the issue you should check the protocol.log on the JNIOR

To do that:

  1. Go to the DCP for the JNIOR
  2. Click on the Console tab
  3. Click ‘Start Session’
  4. Log in when prompted
  5. Enter the cat protocol.log command

If you don’t see a successful login or do see a failed login then do the following:

  1. Go to the JNIOR Device Configuration on the Dolby IMS
  2. Remove the JNIOR device
  3. Reboot the Dolby IMS
  4. Add the JNIOR as a device but DO NOT enter the password
  5. Reboot the Dolby IMS

You can now re-test the JNIOR connection to see if this is resolved.

If it is not resolved then make sure your browser is not using auto-fill for the site. The procedure differs per browser. Follow one of the links below for your browser.

If it is not resolved you can try to analyze the network capture or contact INTEG for additional support.

I hope this article helped you out. Please contact us to let us know!

There is a chance you will see the following PHP error. For this to be seen you must have a Series 4 JNIOR that had JANOS version 1.6 or older and you just updated to a new JANOS version

Why did this happen?

The older JNIORs had a different web page than we have now. The main web page used to be served out of the flash/www folder. Now the DCP, the newer web page, is served out of the flash/www.zip file. If the flash/www/index.php file is still found then the web server will process it and serve it instead of the index.php in the www.zip file.

How do we fix it?

To fix this we need to remove the old flash/www/index.php file. This will allow JANOS to look in the flash/www.zip file. This should be a step in the All-In-One update project. You can do it manually with a Telnet connection like this…

The JNIOR Support Tool will allow foreign characters in the filenames for macro and device files. Here is a quick video showing how to delete them.

1. Create a console session.
2. login
3. type rm mac
4. Then press tab

The JNIOR will fill in the name of the macro file.  In your case, press tab until you get the file with the offending name.

5. Then use the left arrow key to go back and insert a quote at the beginning of the file name

6. Press enter

You can then go back to the folders tab to see that the file is gone.

Repeat the same steps for the “macro file not found.log” file.

If the JNIOR series 4, models 410, 412 or 414, is not working with the GDC Cinema Server then check to make sure MODBUS is enabled. The built-in library for the JNIOR on the GDC server uses MODBUS.

MODBUS communicates on port 502.

The series 3 enabled the MODBUS server by default. The MODBUS server is an optional application that needs to be enabled on the series 4. You can look at the following links for more information

Sometimes the JNIOR doesn’t appear to be working but follow these steps and you might be able to determine why. There are a few steps that you can take before contacting INTEG or declaring that the JNIOR is not functioning. Hopefully the steps below will help save some time.

The number one way for INTEG to help provide support is to send us a Snapshot using the Support Tool. We can use the Snapshot to look at logs, analyze your configuration and to look at network interactions. Snapshots are most effective when taken soon after the issue is noticed. If too much time has passed the logs and network information may no longer contain relevant information pertaining to the time of the issue.


The JNIOR requires 12 – 24v DC. We recommend a power supply capable of 1 Amp.

The very first thing to check is to make sure the unit has power. No, I don’t mean “did you plug the JNIOR in?” We need to make sure that the internal power supply is functioning and that the wires going in to the connector on the outside of the JNIOR have not broken.

To check the internal power supply we need to verify that the BLUE LED is illuminated next to the power connector.

If the BLUE LED is not illuminated then we want to make sure the wires have not been broken. This can easily happen if there is stress put on the wires during installation or if the connector was not securely fastened before being shipped.

Operating System

Is the OS running? To check this remove power. Upon applying power the amber light next to the BLUE power LED should come on for two or three seconds and then go out. Another thing we can check is to unplug the Ethernet cable. As of JANOS v1.8 the Status LED will blink Morse code indicating the value of the last octet of the IP Address when the Ethernet cable is unplugged.


The first thing to check regarding Ethernet connectivity is that the lights on the Ethernet port are lit. If they are not, please check both end of the cable to make sure it is connected. If the cable appears to be properly connected and the lights are not lit, please try a different cable.

Check Beacon to see that the JNIOR is on the network. Beacon is a feature on the JNIOR that uses UDP to broadcast itself on the network. The JNIOR Support Tool implements beacon and will query the network for any JNIORs. Any JNIOR that hears the query will respond. Because this feature uses UDP a valid working IP Address is not necessary.

If the cable, lights and beacon all appear to be in working order then the last thing to check here is the IpConfig/Allow setting. That will need to be done using the serial port. You can read about that procedure in the Dangers of IpConfig/Allow.

As of JANOS v1.8 the Status LED will blink Morse code indicating the value of the last octet of the IP Address when the Ethernet cable is unplugged.

Serial Port

The serial port can be used to diagnose JNIOR issues. Most of the time the Ethernet connection will be used to do this but in the case that the Ethernet connection is suspect we will need to use the serial port. There are two serial ports on the JNIOR but the RS-232 port is the is the port that facilitates the command line functionality. To connect to the JNIOR for command line use you will need to use the following settings. 115200 baud, 8 data bits, 1 stop bit and no parity. Once the cable is connected and you launched your favorite serial application you will need to press enter to see the login prompt. You could also reboot the JNIOR to observe the banner.


If the hardware steps above do not alert you to the issue you are having then configuration is most likely to blame. Please contact us INTEG for further assistance. We can walk you through configuration issues, connect to your computer via TeamViewer, or determine if your unit needs to be replaced.

MODBUS client is not able to connect to the JNIOR

The MODBUS server running on the JNIOR is a separate application from the Operating System. It does not run by default when the JNIOR is shipped. It is installed by default. It must be activated by the end user before the the MODBUS connection can be successful.

To activate it go to the DCP, click on the Configuration tab. Half way down the left side click on Applications. You will see a list of applications that are loaded on the JNIOR. Check the box next to Modbus Server. This will tell the JNIOR to run the application when the JNIOR boots up. You will need to reboot the JNIOR at this point to get the MODBUS Server to start.

To verify that the MODBUS server is running we can list the listening network sockets using the netstat command.

Lastly, you can change a few configuration parameters for the MODBUS server under the registry tab.

Port 502 is the default MODBUS port. Most likely this will NOT need to be changed. The Timeout setting is the number of milliseconds to wait for a MODBUS client to poll the server. If a request is not made within this amount of time then the JNIOR will close the connection. If any configuration needs to be changed it will probably be the Login setting. Not very many MODBUS clients implement a login. If they dont log in then you will see the following in the Modbus Server log…

Setting the Login key to false will allow this device to connect successfully.

The problem: You get the following screen when trying to go to the DCP or any web page on the JNIOR.

In this image we tried to go to the IP Address of the JNIOR.  This should present us with the DCP web page.  In this case we are presented with the “Page not found” response page.

This means that the file cannot be found in the filesystem for this page resource.

To troubleshoot this we need to look at the filesystem.  Since the DCP is not available we need to use FTP or a telnet session.

Using FTP

Open Windows Explorer. In the address bar type ftp://IP ADDRESS. You might see the message that Windows Explorer cannot access your folder.

Most likely this is because you need to provide credentials. To do that you need to right click in the white-space in the window and select Login As…

Once you log in navigate to the flash directory.

If the the DCP or default web page is missing then all of the following must be met:

  • www.zip is missing
  • public.zip is missing
  • www/ directory is missing or there is not an index.php file in the www/ directory
  • public/ directory is missing or there is not an index.php file in the public/ directory

Using Telnet

We can use Telnet to look at the filesystem as well. To do this, open your favorite Telnet application. Make a connection to the JNIOR. Log in. You will then use either the dir command or the ls command. Both commands are the same and will list the directory contents.

Use the command of your choice, whichever command is easier to remember, and add “flash” as a parameter. This wil cause the command to list the contents of the flash directory. If the the DCP or default web page is missing then all of the following must be met:

  • flash/www/config.zip
  • www.zip is missing
  • public.zip is missing
  • www/ directory is missing or there is not an index.php file in the www/ directory
  • public/ directory is missing or there is not an index.php file in the public/ directory

If you are having issues accessing your JNIOR’s webpage, please reach out to our support to get your setup working again.

The IpConfig/Allow registry key can be powerful to help secure your JNIOR.  It can successfully thwart unauthorized access and prevent DOS attacks.

The danger comes in when the registry key is mis-configured. It can be a typo or not fully configured, something simple, but when this happens it can prevent legitimate attempts to access the unit.

If this happens a USB-to-Serial cable is needed to access the unit via the RS-232 port. Make sure to use the correct serial settings of 115200, 8 data bits, 1 stop bit and no parity. Once connected you can issue the reg command.

Above you can see that the IpConfig/Allow key is set for This states that the first 24 bits of the address must match for a network connection to be accepted. If, for some reason, this was mistyped then legitimate connections would not be allowed. This would basically render the network port useless. The user might not have noticed what the error was.

Using the Serial to USB cable is the only way to access the unit. The key can then either be fixed or removed to regain access over the network.