Device - MFP or LP

Once you have collected the device logs as described in How do I collect the device (or trace) logs? | Ricoh Developer Program (RiDP) (ricoh-ridp.com) you will have an encrypted archive that will need to be decrypted by the self-serve Ricoh Log Analyzer Tool utility.

Investigating application faults on embedded devices can be a challenge, and sometimes a post-mortem snapshot of the device under test is necessary. Using WIM (Web Image Monitor) on Ricoh multi-function or print devices it is possible to collect comprehensive trace logs that can be used for this purpose.

ACT (Always Current Technology) can be enabled on a device by following the instructions in the attached document.

For details about ACT (or help if it is not working) please contact your regional Ricoh Service organization.

Yes, please review the following page in the resource CD:  /doc/en/javaapi/700-05-0230.htm?ssdk_v2

Smart Operation Panel > SDKService API > Remote Settings >

End point:  /rws/sop/serverservice/functionkey

Device’s code (Model code) information/documentation is available on SDK/J developer resource CD.

1.       Go to current Embedded Software Architecture Ver. xxxx index page on SDK/J developer resource CD: your_SDKJ_devCD_location/html/index_english.html

2.       Under section “Model Information” click on the corresponding version link

Example using Ver12:

ver12 Model information/Matrix of machines and versions

The XPS direct print option is available for SmartSDK supported devices as an extra module.

The SC error is caused by the tracking that is set on the device:
 

To change the password for remote installation do the following:

[E00xx: Application setting file error]

E0001 : Product ID speicification error
E0002 : NV-RAM use size error
E0003 : UI existence specification value error