SmartSDK

Hi Team,

We are planning to upgrade the Java version of our Tungsten Unified Client application from Java 8 to the latest version (Java 17 or the latest available version) to resolve vulnerabilities and compatibility issues with third-party libraries. Before proceeding, we would like to confirm the minimum Java version that is fully supported on the Ricoh platform to ensure compatibility. Additionally, please advise on the appropriate SDK version we should use. Kindly also inform us if there are any potential compatibility issues related to the Java version, device models, platform SDK API usage, and generation.
We are supporting the following device models:
G2, G2.5 and G3.

Hi RiDP team,

A Ricoh support team has requested Tungsten Automation to escalate this issue to RiDP as you can only be contacted through partner.

They have issue with Ricoh Unified Client and CA signed certificate on server side. For specific server, whenever customer uses CA signed certificate the client/device could not connect to server. Self signed certificate works fine.

A Ricoh suppor team has investigated and believed it could be related to how the device handles SSL communication.

Here is their feedback.

It seems that certificate management is being handled through a device management solution, which differs from the standard method of managing certificates via WIM. We kindly ask that you contact the mainframe design team through your ongoing RiDP inquiry, so that accurate and detailed information can be shared with them.

Will update more information later.

Hello Team,

We would like to clarify an observation related to scanning orientation via the Auto Document Feeder (ADF), and to confirm if the behavior is model-specific or configurable.

1. On the IM C300 model, when the user places portrait-oriented pages in the ADF, the resulting PDF is returned in landscape orientation. While PDF format output is expected, the user prefers the scanned output to remain in portrait orientation as per the original paper placement.

2. To validate this, we tested the same behavior on the IM C2000 model. In this case, placing the paper in ADF (landscape by default) still returns the soft copy in portrait orientation, which seems aligned with expectations. In both models, the "orientation" setting was marked as “readable” (or equivalent setting).

3. Interestingly, when we manually set the orientation to 90 degrees counter-clockwise on the IM C300, the output appeared correctly in portrait format.

Could you please clarify the following:

• Is this scanning behavior expected for the IM C300 model?

• Is there a programmatic way to detect whether a device expects ADF input as portrait or landscape?

Looking forward to your insights. Thanks in Advance.

Hello,

I would like to get the maintenance signature of our NDD Print Client application.
The application is compatible with 11x and 12x devices that support the SmartOp panel.

Changes:
- Improved compatibility by allowing embedded clients to continue interacting with previous Host versions when Entra ID is not used. This ensures seamless operation for legacy integrations.
- Upgraded all HTTP requests to HTTPS to enhance security and align with modern best practices.

Note: The package is unsigned and its passing all the tests in ssdkpkg_checker tool.

Best regards;

Hello,

This is a question about the "Guest" functionality of our Authentication and access to Web Browser NX. A customer would like to be able to access our Secure Scan application (which is web-based and uses the Web Browser NX) without being authenticated.

Our Authentication has a "Guest" button which just hides the authentication and allows access to any apps that appear on the desktop. Access to these apps is controlled by the SP-5-420-XXX settings.

Even when allowing all access using these settings, the user is unable to access our Secure Scan app. Nor can they access the Web Browser NX app by itself. They are perfectly capable of accessing Scan, Copy, etc. Just not the Web Browser NX. They can even access the normal Web Browser.

Is this by design? Should a "Guest" user be able to access this app? If so, is there a setting I am missing to allow this?

Also, I am able to reproduce this in our lab. I will attach the device tracelog from when I attempted to access the Web Browser NX as a guest. I attempted the access at exactly 10:28AM, but I can't really find anything in the tracelog that gives me any information on why I couldn't access it.

When I try to go to either Secure Scan or Web Browser NX, all I get is a "Please wait" screen and nothing else happens.

Regard
Bryan

• Issue:

The Printix Ricoh Go app successfully sent an HTTP PUT request to the device to set the jobStoppedTimeoutPeriod to 30 seconds after initiating a ScanEx scan (see the sample request as below). However, the scan was not canceled after the 30-second timeout when a paper jam occurred. We also tried put field jobId (for example: "jobId": "1m4ep7jmkzn6") in the request body, but it did not make a difference.

PUT http://gw.machine.address:54080/rws/service/scanner/jobs/{deviceScanId} HTTP/1.1
Host: gw.machine.address:54080
X-Application-Id: 1667825665
Content-Type: application/json

{
    "useTimeout": true,
    "jobSetting": {
        "jobStoppedTimeoutPeriod": 30
    }
}

• Device model:

Ricoh MP C407 (firmware updated to the latest version)

• Test Steps:

Refer to the attached device log MachineInfo_C497P100609_20250609_181609.tar.
Test start time: 17:58, Jun 9; jobid: 1m4ep7jmkzn6. 
Test result: The scan was not cancelled.

1. Log into the Printix Ricoh Go app and start a ScanEx scan.
2. Printix Ricoh Go app sends the PUT request with url http://gw.machine.address:54080/rws/service/scanner/jobs/{deviceScanId} to set the jobStoppedTimeoutPeriod setting for this scan job.
3. Make a paper jam and then do not take any actions.
4. Collect the device logs.

• Questions:

As per Ricoh Scan GUI Service Developer's Guide (see screenshot "Set jobStoppedTimeoutPeriod setting.jpg"), the jobs/{jobID} PUT request can be used to configure the jobStoppedTimeoutPeriod setting. After job execution, device should automatically cancel the job if there is no change in the job status or no user operation. The time until cancellation follows the setting of jobStoppedTimeoutPeriod.

• During testing, the scan did not seem to be canceled after the jobStoppedTimeoutPeriod timeout specified in the PUT request. Could you clarify why the scan was not automatically canceled?
• To ensure the device automatically cancels the scan when there is no user operation, is setting the jobStoppedTimeoutPeriod using the jobs/{jobID} PUT request a valid approach??
• Furthermore, to ensure the jobStoppedTimeoutPeriod setting takes effect, what is the appropriate time to send the jobs/{jobID} PUT request?

NOTE: When sending request (/rws/service/scanner/capability) to device to get device capability, we did get the jobStoppedTimeoutPeriodRange:
06-09 17:58:11.411 22409 22409 D PrintixGo:ScnJbEvtHndlr: jobStoppedTimeoutPeriodRange is not null: {"step":"1","maxValue":"1200","minValue":"10"}
 

Thank you.

Hi,

We would like to get a production ID for the application. The following is the application information:

Product ID: 1711276436

Product Name: ePRINTit SaaS

Version: 1.0.0

Thank you,

Jordan

• Issue:

Printix Ricoh Go app did not receive system reset event from IM C320F if paper jam occurred during ScanEx scanning.
 

• Device model:

Ricoh IM C320F
 

• Test Steps:

Refer to the attached device log MachineInfo_A0B4P801271_20250604_152636.tar.
Test start time: 14:52, Jun 4; jobid: 1m415g7jjhb7.
System Auto Reset Timer is set to 60 seconds (see the attached "timer settings.jpg")

1. Log into the Printix Ricoh Go app and start a ScanEx scan.
2. Make a paper jam and then do not take any actions.
3. Collect the device logs.

• Questions:
   

1. The Printix Ricoh Go app did not receive the system reset event (jp.co.ricoh.isdk.sdkservice.system.SystemManager.SYSTEM_RESET_INFO) after the paper jam, is it expected? What can do so we can receive the system reset event under this condition?
    
2. From the log we can see that it appeared device decided not to logout when auto logout timer expired, so the Printix Ricoh Go app did not receive any AUTH SERVICE state changed events. Is there any way for the app to receive the auto logout timer event directly?
   
   // Auto logout timer triggered, but device decided NOT to trigger logout
   06-04 14:55:49.794  3813  3813 I SdkServ : CMN:SYS:jp.co.ricoh.advop.auth.LOGOUT_ASK receive
   ... ...
   06-04 14:55:49.795  3813  3813 I SdkServ : ATH:SMC:previous:LOGIN next:LOGOUT_ASK_ANS_NG
   
   06-04 14:55:49.997  3813  3813 I SdkServ : ATH:MGR:send NOTIFY_LOGOUT_FAILED locked from jp.co.ricoh.advop.smartscannerex
   
   
   Thank you.

• Issue:

Scan cancellation fails when a paper jam occurs if SimpleScanEx (v1.03) is installed on the device. For comparison, we also tested the behavior with SmartScanEx (v1.07) installed on the device

• Device model:

Ricoh MP C407 (firmware updated to the latest version)
 

• Test Steps:

Successful case (Test start time: 12:01, Jun 2, jobid: 1m3vjptnxzn6, see the device log: MachineInfo_C497P100609_20250602_122350.tar)

1. Install SmartScanEx on the MP C407 device.
2. Log into the device and the Printix Ricoh Go app sends the intent to trigger a ScanEx scan.
3. Make a paper jam and then the Printix Ricoh Go app sends a cancel scan intent to cancel the ScanEx scan. 
4. The scan cancellation succeeded with response success.

Failure case (Test start time: 15:29, Jun 2, jobid: 1m3vyx0j9zn6, see the device log: MachineInfo_C497P100609_20250602_154241.tar)

1. Uninstall SmartScanEx and then Install SimpleScanEx on the MP C407 device, reboot device.
2. Same as step 2 as above.
3. Same as step 3 as above. 
4. The scan cancellation failed with response state_mismatch.
    

• Questions:

1. ​​​​​​​When following the test steps, is it expected to see the scan cancel failure when using SimpleScanEx as the ScanEx app on the device? Why was the scan cancel successful when SmartScanEx was used as the ScanEx app?
2. Is there anything we can to ensure the scan cancel is successful during paper jam when using SimpleScanEx as the ScanEx app on the device?

Thank you.


 

Hi,

Please find attached version 3.2.10 of the PaperCut MF application for a maintenance signature.

The changes are described as follows:

• Fixed an issue on Ricoh where device memory doesn't free up instantly after integrated scanning

Thanks