Operational Procedure (Tcp/Ip Connection); Operational Procedure (Usb Flash Drive) - Ricoh Gim-MF1a Field Service Manual

• The retrieved log is stored under the name " fw.log ". It is the log of all tasks of the firmware (all
modules of the controller). From this "fw.log", the log files for each task can be produced.
• To produce the log file for each task, "gawk" must be installed in the computer.
• To stop log retrieval, enter "endlog" on the PC console.
After executing "backlog", be sure to wait at least 30 seconds before executing "endlog". If you do
not, the backlog operation may be ended before the log has been completely retrieved.
• If you do not use dbgmon further, disable the dbgmon function using SP5-844-200, and then
reboot the machine.

Operational procedure (TCP/IP connection)

The dbgmon function can be used also via TCP/IP.
The computer and the machine must be allowed to establish TCP/IP communication without any firewall
(The machine's port number is 7000). It is also necessary to know the machine's IP address.
1. You can connect the machine and computer via TCP/IP by launching dbgmon with the
option of "-1<machine's ip address>".
2. You can retrieve the log with the same procedure as that specified in "Operational
procedure (USB connection)".
• The dbgmon function via TCP/IP is available only if the dbgmon function is enabled using
SP5-844-200.
• If you enable the dbgmon function using SP5-844-200, port number 7000 opens to allow the use
of dbgmon via TCP/IP.
• When dbgmon is disabled, port number 7000 cannot be opened.

Operational procedure (USB flash drive)

FAT12/FAT16/FAT32/exFAT are supported as the file format of the USB memory stick
1. Create a file named "R_log.txt" in the root directory of the USB memory stick in advance.
2. When inserting the USB memory stick into the USB host port on the front, the log entries
are automatically obtained in the USB memory stick.
• The log files cat.bat, logid.log, fw_cur.log, and fw_old.log are created inside the date-based
directory (YYYYMMDD_HHMMSS) and the log file fw.log is obtained by executing cat.bat.
Debug Log
135