Kitamura Troubleshooting
| Symptom | Likely cause | Action |
|---|---|---|
| AnyWhere Remote icon missing (Mi) | App not installed on the control | Contact Kitamura for the USB installer |
| MTConnect shows NOT ENABLED (Mi) | License not installed | Complete the license request and install steps above |
| Ping fails to the CNC IP (Jr) | Network or parameter issue | Check parameters 1925–1928, cabling, and subnet match |
Telnet Connect failed on 7878 (Jr) | Adapter service not running, or wrong port | Start the service and confirm the port in the config file |
| Telnet connects but shows nothing (Jr) | Adapter can't reach the CNC | Verify host IP and model in Adapter Configuration.ini |
ERR_CONNECTION_REFUSED on the agent URL (Jr) | Agent not running, or wrong port | Check the agent service and port number |
Availability = UNAVAILABLE (Jr) | Adapter not running, or can't reach the CNC | Work back through Tests 1 and 2 |
| Machine drops offline and comes back (Jr) | Adapter losing its CNC connection intermittently | Work through Intermittent drops |
Adapter log shows network error 0x8202000A (Jr) | Adapter stuck instead of reconnecting | Set Close After Disconnect = enabled in the config file, then stop, re-install settings, and start the service |
| Works locally, not from the network (Jr) | Windows Firewall | Allow inbound traffic on the agent port |
| Adapter service won't start (Jr) | Port or service-name conflict | Ensure unique ports, service names, and directories per machine |
| Config changes not taking effect (Jr) | Settings not re-installed | Stop the service, run install_<SN>_service.bat, then start the service |
| Silent-install failures (Jr) | See the installer log | Check IMA Standard Adapter – Installer.log next to the installer executable |
For MTConnect problems that are not specific to Kitamura, see Troubleshooting in the MTConnect guide and Machine Not Reporting.
IMA Adapter Diagnostics
These apply to an Arumatik-Jr running the Mitsubishi IMA Standard Adapter. See Arumatik-Jr for the install itself.
Logging
Adapter logs are written to the install directory as sAdapter_<log number>.log, in the format Timestamp | Severity | Message. Severity levels from lowest to highest are trace, debug, info, warning, and fatal. Log rotation defaults to 2 MB per file and 10 MB total, deleting the oldest file first. These logs are the first place to look when troubleshooting remotely.
Intermittent drops: the machine keeps going offline
When machines drop offline and come back, and the MTConnect agent shows Availability = UNAVAILABLE during the drops, it almost always means the IMA adapter is losing its connection to the CNC intermittently. Work through the checks below in order — they are listed by likelihood.
1. Confirm where the adapter is running.
It needs to be on a dedicated PC or server that is on 24/7 and on wired Ethernet — not a laptop, and not a desktop that sleeps. On that machine:
- Set the Windows power plan to never sleep.
- In Device Manager, open the network adapter's Power Management tab and uncheck Allow the computer to turn off this device to save power.
2. Pull the adapter logs.
In the adapter install directory you will find sAdapter_1.log, sAdapter_2.log, and so on. Note the timestamps when machines drop and read what was logged at that moment.
If the logging severity in the config file is set to warning or fatal, change it to info so connection events are captured, then stop the service → run install_<SN>_service.bat as Administrator → start the service. Config changes do not take effect until the settings are re-installed.
3. Enable Close After Disconnect in the config file.
Open configure_<SN>.bat and, in the [Adapter] section, set:
Close After Disconnect = enabled
This is disabled by default, and when the adapter hits network error 0x8202000A it can get stuck instead of reconnecting. If your logs show that error code, this is very likely the fix. Apply it with the same stop → install → start sequence.
4. Run a long ping test during production.
From the adapter PC, run a sustained ping and let it go for a full shift:
ping -t <CNC IP address> > ping_log.txt
Intermittent timeouts in the log point to a physical or network problem rather than the adapter: a flaky cable to the machine, a failing switch port, or an IP conflict on the machine network.
5. Check whether the adapter service itself is crashing.
The service restarts automatically by default, which can hide crashes. In Windows Event Viewer, open the System log and filter for Service Control Manager events around the drop times.