SmartSDK

Hi  Team, 

We would like to seek clarification regarding the two RICOH Firmware Update Tool versions we have seen: IM C3000 (8.01) and IM C3010 (2.02). We found these version details on the Ricoh support portal. Could you please help us understand why these different versions exist, even though they appear to be for the IM series models?

Ricoh IM C3010-

IM C3010/C3510 Downloads | Ricoh Global

Ricoh IM C3000-

IM C3000/C3500 Downloads | Ricoh Global

The reason we are looking for clarification is that our customer, who is facing an issue with IM C3010 models, has upgraded the firmware to the latest 2.x version. However, they are encountering an issue where our Pharos Entry application stops working.

We do not have the same model in our lab, so we validated the behavior using the IM C3000, which already has a higher firmware version than the IM C3010. Below are the details shared by the customer regarding the IM C3010 model:

• IM C3010 was upgraded from version 1.10.1 to 2.00 (please find the attachment for IM C3010).

We are in the process of obtaining the WIM logs, but in the meantime, we would like to understand the differences between these versions.

Thanks!

Hi

Our customer is using KofaxRicohAndroid Client for scanning jobs, they meet an issue when deleting scanned files on device after scanned and sending completed.

It shows error 403 Forbidden, and it occurs on 2 devices IM C5500 and MP C5504ex only.

These devices are running an 3rd authentication provider (Kofax Unified Client)

Do you know any reason that it prevents logged-in user deleting file on HDD?

------------------device logs file is attached-------------------------

12-03 10:52:23.414  3992  3992 E kofax.client: KOFAX_SCAN
12-03 10:52:23.414  3992  3992 E kofax.client: jp.co.ricoh.ssdk.sdkservices.wrapper.common.InvalidResponseException: 403 Forbidden
12-03 10:52:23.414  3992  3992 E kofax.client:     at jp.co.ricoh.ssdk.sdkservices.wrapper.common.Utils.createInvalidResponseException(Utils.java:49)
12-03 10:52:23.414  3992  3992 E kofax.client:     at jp.co.ricoh.ssdk.sdkservices.wrapper.rws.service.storage.Files.deleteFile(Files.java:141)

Thank you

Ngoc

Maintenance Signature Request for

> Abacus (1711276312)

> AbacusLogin (1711276313)

Fixes:
1.Admin Login: Implemented "Machine Administrator" login.
2.Fix for allowing special characters in AD passwords.
3.Resolved issues in the login and scan modules regarding unhandled exception.

Hi Team,

For the FAR authentication process, we would like to establish an LDAP connection programmatically. To do this, we require certain details, which we intend to retrieve from the LDAP configuration section. I am able to retrieve most of this information, such as the LDAP server, search base, and username, but the password value is not accessible due to security restrictions. Is there a way to use the available LDAP configuration details (LDAP server, search base, username) along with the password to create an LDAP connection, even though the password itself cannot be read directly?

Hi RiDP,

I have reviewed the documentation for SmartSDK and noticed that there are many paper sizes listed in the definition of the Smart SDK WebAPI. However, when I call the API /rws/service/scanner/capability, I noticed that the response does not include all of these paper sizes. Specifically, some paper sizes like 11x17 are missing from the API response, even though they appear in the SmartSDK WebAPI definition.

I have attached information regarding the scan sizes I retrieved from both the SDK WebAPI and Device Capabilities. The documentation also mentions that the lists originalSizeList, originalSizeExtendList, and originalSizeNotSupportedByAdfList from the API are derived from the paper sizes defined in the Smart SDK WebAPI.

My question is, does this mean that the paper sizes listed in the Smart SDK WebAPI are not necessarily supported by all devices? If so, how should I proceed when using paper sizes that are not included in the API response (e.g., the 11x17 size is listed but only the 11x17_landscape size is returned)? How can I use these sizes in my application?

Additionally, I would like to clarify the following points:

1.What is MediaSizeName in DSDK? 
In the documentation, I see a column "MediaSizeName in DSDK" when defining paper sizes and documents in the Smart SDK WebAPI. What does this value represent, and how is it used in the system?

2.What is the difference between paper sizes with and without values in the "Definition" column in DSDK?
For example, the 11x17 size does not have a value in the "Definition" column in DSDK. What is the difference between those sizes that have a value in this column and those that do not? Does this affect how I should use these sizes in my application?

3.Regarding Scan GUI Service:
The documentation mentions two types of Scan GUI Service (S)(Griffin-C2) and scan GUI service. Could you let me know which type of scan GUI service the scan GUI module/application is using?

Thank you for your time, and I look forward to your response.

Hi RiDP,

Please help to create a maintenance signature for the attached version (1.3.0.616)

This version includes fixing the bugs below:

- Ricoh UC - When device changes its IP address, the client keeps sending old IP address to server.

Thank you

We are requesting a new maintenance signing request.

Update includes bug fixes and improved security and validation of ssl certificates.

Hi RiDP,

We are using Ricoh Scan GUI to scan on SmartSDK devices. A customer wants to use a scan size (11x17 vertical) which is not supported by Ricoh Scan GUI yet.

I would like to check if you have any plan to update Scan GUI, like adding more original/paper size, in the future.

If yes, is there any ETA?

Thanks.

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:
1-Improvement in the authentication process by PIN and Card to allow users to log in to embedded systems using their Azure AD credentials.

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

Best regards;

With PrintixGo app installed on device alone, it could sign-in/out without issue. After installed Kofax Unified Client, Printix sign-in failed and we found the following logs:

12-13 10:48:41.265  3817  3817 I SdkServ : CUI:MGR:handleAuthServiceStateChanged state:logout trigger:login_failed userID[] FAR:false,[],null
12-13 10:48:41.265  3817  3817 D SdkServ : CUI:MGR:userName:**** userID[] error:S0216-002(-13) CP:none DSD:none FP:none PP:none SP:none BP:none MAP:none UAP:none DAP:none NAP:none CUP:none SVP:none sT:null sD:null sRA:null LFR:null FAB:false FAT:[] FAP:[] FAS:null
 

After uninstalled Kofax Unified Client manually, the issue still occurred. Then after rebooted the device, Printix could sign-in without any issue.

Attached device log which includes the following operations:

1) Printix installation, Printix sign-in successfully,

2) Kofax Unified Client installation, Printix sign-in failure,

3) Kofax Unified Client uninstallation, Printix sign-in failure,

4) Reboot device, Printix sign-in successfully.

We investigated the log but did not find any obvious clue. Could you please take a look and advice what could be the cause?

Thanks a lot.