Requirements and Known Limitations of Dispatcher Paragon Embedded Terminal for Ricoh

Requirements

  • Dispatcher Paragon Embedded Terminal for Ricoh is a software extension of Ricoh devices.

  • The terminal requires a licensed and configured Ricoh ESA™ Platform at the MFP (SDK/J version 4+).

  • Java Card is required to be loaded in the device (already delivered, by default, with newer types of Ricoh devices).

  • Valid certificate present (for secured connection)

    • Before Build 36 strongly recommended

    • Build 36 and higher mandatory

    • See chapter Configuring Ricoh, section Create a MFD certificate on Ricoh devices

Known Limitations

Accounting

  • Accounting of scans performed via the native scanning application is not supported.

  • Printing from USB is not supported, such jobs will not be accounted.

Payment system integration

  • The copy operation may not stop immediately once the minimum balance is reached. Depending on the device, there can be a small delay that allows the users to overrun their balance. For example, MP C305 charges for two A4 copies but stopped after six. Therefore, registration of the debt has to be allowed in Dispatcher Paragon Payment System. Otherwise, the user would be able to continue copying even after using up credit.

  • The credit balance is not displayed on devices with small displays.

Quotas

  • It is possible to reach a negative quota balance. It is mainly caused by a slow connection between the device and the server.

  • If a user has less balance then is needed to perform five copies, the user is prevented from performing any copy jobs. To allow copying, the quota balance must satisfy the following conditions:

    • BW COPY, COLOR COPY, COLOR, BW – if defined, the balance of each of them must be at least five.

    • COPY – must be at least BW COPY + COLOR COPY or BW + COLOR (if they are defined), depending on which of the two sums is higher.

  • Similarly, if the user has a quota for all pages enabled, they must have at least five pages available to be allowed to copy. If the user quota balance goes below five pages during a copy job, their access to the copy operation is restricted.

Scanning

  • On devices without a paper size sensor (most of the A4 models, e.g., Ricoh Aficio MP 171, Aficio MP 171 SPF, Aficio MP C400 Series, Aficio MP 201, Aficio MP 201 SPF, Aficio MP 301 Series, Aficio MP C300 Series, Aficio SP 5200S + Aficio SP 5210SF + Aficio SP 5210SR, MP C305 SP, Aficio MP C305 Series, MP C401 Series, etc.), the following behavior may occur:

    • Every even page may be rotated by 180 degrees in the resulting file when scanning from the automatic document feeder (ADF) to JPEG format.

    • Every even page may be rotated by 180 degrees in the resulting file when scanning manually from the glass to multiple TIFF files or to a single TIFF file. Note that a duplex option for scanning from glass makes no sense.

    • Duplex scanning from the ADF works properly for multi-page PDF/TIFFs, other output file types may have every other page rotated upside down.

    • A4 paper size may be enforced instead of auto-detection.

  • If the MFD is unable to detect the paper size automatically, scan cannot be made.

Finishing options

  • Proper functionality of Advanced Finishing options is guaranteed only with Dispatcher Paragon Universal Print Driver.

  • Punching is not supported on Ricoh devices.

  • Not all Finishing options are supported on every device. For detailed information, please see the Hardware Compatibility List (HCL).

Other

  • When a disconnected USB card reader is connected to the device again (or the device is woken up from sleep mode), it may take up to one minute (device dependent) till the USB card reader responds again.

  • The configuration options initial-screen and separatedScanWorkflows are not supported.

  • It is only possible to log out from the Dispatcher Paragon application using the hardware button on SDK/J devices. To log out after copying, the user first needs to navigate to the Dispatcher Paragon application.

  • The native software logout button does not work on Android devices.

  • When a user works with native applications, an inactivity timer is started as a background process. This timer is reset after each operation changing the device state (i.e., copy, scan, print). Following a terminal inactivity timeout due to the native application or MFD menu use, the user will automatically be logged out.

  • EC, ECDHE, ECDH, DH, DHE cipher suites are disabled because the TLS connection is not stable in these settings. That forces to communicate on TLS 1.0 only.