SmartSDK

• Question:

How to trigger the aborted state with job status reason timeout / scanner_jam / exceeded_max_page_count during ScanEx scanning?

• Device model:

Ricoh IM C7010 (firmware updated to the latest version)

• Test steps

We would like to trigger the aborted state during ScanEx scanning, but it did not seem this had ever happened (see timer settings "0 - device timer settings.jpg"). The following are the tests we have tried.

1. Test start time: 10:51, May 25. job id: 1m36bmrgshb7. See video "1 - scanning paper jam.mp4".

Started ScanEx scanning from ADF and made a paper jam, the scan job status got stuck on processing_stopped with job status reason scanner_jam, and we had never received the scan job event with status aborted and jobstatus reason scanner_jam / timeout.

2. Test start time: 11:35, May 25. job id: 1m36e68fyhb7. The wait time for next original was set to 90 seconds (see "2 - Wait Time for Next Original(s).jpg"). See video "3 - scan from flatbed and wait for next original.mp4".

Started ScanEx scanning from flatbed and then wait until the "wait time for next original" timed out, we received the scan job event with jobstatus completed.

3. Test start time: 11:41, May 25. job id: 1m36ehe1w8y6. The wait time for next original was set to Off.

Started ScanEx scanning from flatbed and then we received the scan job event with jobstatus completed.

4. Test start time: 11:46, May 25. job id: 1m36etw7e639. The wait time for next original was set to Continuous Wait. See "4 - Continuous wait.jpg".

Started ScanEx scanning from flatbed and then wait, the scan job status got stuck on processing_stopped with job status reason wait_for_next_original_and_continue, and we had never received the scan job event with status aborted and jobstatus reason scanner_jam / timeout

• Information Collected

See "Screenshots, videos and device log.zip".
Download link: 
https://fileshare.kofax.com/?ShareToken=9F6763460375A6211FA2D7AA69294F2C32177C74
 

Questions:
 

1. See "5 - job status reasons.jpg", Common Information > WebAPI Specifications > Data Attribute Value Definition, jobStatusReason "scanner_jam" is defined for status "aborted"; while in screenshot "6 - job status reasons.jpg", Common Information > WebAPI Specifications > Scanner, jobStatusReason "scanner_jam" is NOT defined for status "aborted". Is that possible that aborted status can be triggered with job status reason "scanner_jam" during ScanEx scanning? If yes, how to trigger it?
2. Is that possible that aborted status can be triggered with job status reason "timeout" during ScanEx scanning? How to trigger it and where can we set the timeout the value?
3. Is that possible that aborted status can be triggered with job status reason "exceeded_max_page_count" during ScanEx scanning? How to trigger it and is there a need and where to set the max_page_count?

Thank you.

 

Hi Team,

Our customer recently has encountered a problem while printing from USB.

They have tested printing jobs from multiple models but IMC3510 has this issue specifically for tracking USB print jobs. They also said the same scenario with IMC300 was successful and the jobs were tracked properly.

Below is the scenario they are following:
1.Insert USB
2.Login to UC 
3.Open Print from USB native app
4.Give print
5.Check job reports and see no tracked print jobs for IMC3510 but print jobs tracked for IMC300

When I have investigated the logs I found that IMC3510 is sending job source as 'diprint', while the IMC300 is sending job source as 'sdk' which I think is the cause for this issue.

Can you please let me know:

1. Is this a known issue for the model IMC3510?
2. Or is this any driver or configuration issue?
3. What is the expected job source for a USB print? I am thinking it should either be 'sdk' or 'usb_port'.
4. Could you please explain the different types of job sources sent from device.

I am attaching the logs from both the devices.

The issue was reproduced at 05-19 08:11 on IMC3510 (non-working). Uploaded tar with name IMC3510.
The issue was reproduced at 05-21 13:36 on IMC300 (working). Uploaded tar with name IMC300.

Thanks

Hi RiDP,

Could you please help to create a maintenance signature for the attached version (1.3.0.629)

This version includes a fix for a customer:

- Device would not sleep after a print or copy Job.

Thank you.

Hi, 

We would like to ask for a maintenance signature for Smartshare Android embedded solution.

• Improvement in error messages;
• Loading screen when loading processes;

Best regards

Anderson Palhano

Hi RiDP,

Could you please help to create a maintenance signature for the attached version (1.3.0.627)

This version includes a fix for a customer:

- Print job does not appear in device report of Output Manager.

Thank you.

Hi RiDP,

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

This version includes fixing the bugs below:

- Unified Client for Ricoh 1.3.0.8 | Scans over 10 pages fail

Thank you

Request for maintenance signature, bug fixes and other enhancements.

Request for maintenance signature, bug fixes and other enhancements.

Hi RiDP,

Could you please help to create a maintenance signature for the attached version (1.3.0.625)

This version includes a fix for customer:

- Add Tungsten Capture as quick launch workflow in to Unified Client.

Thank you.

Please production sign the 3 attached cards managers.