Scanning PDF in color
Incident Properties
Question
Hello,
The Ricoh scanning application (on the MPC 3002 model) has 3 PDF file format options to scan to, PDF, PDF Archive and High Compression PDF. According to the SDK/J scanning API (see the scanning developers guide - Combination of Attributes That Can be Set) the PDF format can either use JBIG or JPEG2000 compression set. JPEG2000 is only available on wide format devices and is not available on the MPC 3002 model. JBIG only supports Monochrome (B&W) color.
When using the Ricoh scanning application I am able to scan a color PDF file. I do not understand how this is possible based on the API documentation I have read. Is there any way to produce color PDF files on this model (i.e. without JPEG2000 scan compression) via the scanning API without using high compression PDF or PDF archive formats?
Scanning gray scale
Incident Properties
Question
Hello,
The scanning API has support for Color, Monochrome (B&W) and Auto Color Select (see ScanChromaticity class), however on the Ricoh scanning application on MFDs there is also a gray scale option (see attachment). Is it possible to do gray scale via the scanning API?
Thanks,
Daniel
Xlet intercommunication
Incident Properties
Question
Hi Support
Just a little advice needed please.
We are just embarking on development of both a 4X-7X login/Authentication Xlet and a 4X-12X PullPrint Xlet.
There is a need for communication between these xlets and we will also need to provide communication between our current 10X-12X login/Authentication Xlet and the new 4X-12X PullPrint Xlet.
I have been looking through the documentation on the AAA authentication service and the section 'Communication between applications', detailed in 'sdkj_xlet_develop_xlet_eR113.pdf' document.
The communication is only as far as I can see required one way, from either the 4X-7X or 10X-12X login/Authentication Xlets to provide the PullPrint Xlet with the logged in users details.
Firstly is the AAA Authentication Service available for the 4X platform? If yes is this the best method for us to communicate authentication info to our 4X PullPrint Xlet?
I would like to provide a consistent communication method to our PullPrint Xlet from both our Login/Authentication SDKJ platforms.
You advice will be greatly received.
Many thanks and best regards
Nick
Card reader documentation
Incident Properties
Question
Hi Support,
Do you have any documentation that you can provide me that explains how to set up a card reader on the 12x platform?
I have had several cases where Ricoh tech have been on site and they have struggled to configure the device with the card reader. instead of me trying to walk them through it i would just like to include the doc as part of our package that we send out so that they have it ready and installed before we install our software.
Many thanks!
Embedded Device Client for Ricoh machine wake up from sleep with terror code SC-997-00 “Functional problem has occurred.”
Incident Properties
Question
When the device come out of sleep/power save mode.
Error:
Smart Service Call
Service has been called.
Functional problem has occurred.
Please wait.
SC997-00
The error message is cleared with a complete reboot of the machine
It should be noted that if the Check Status light is ignored all device functionality (including the Omtool xlet) is unaffected. Functionality only seems to be adversely affected when the Check Status button is pressed to invoke the error.
Firmware version of device is 1.16. They are up to date with all firmware and java versions. Screen shot is attached.
They also looked at the heap size, tried increasing and it didn't help with this issue. They don't believe the heap size is the issue.
Please do note there is no error seen in our application log.
I have attached the snapshot of the error, device logs and firmware version snapshot.
Thanks
Niranjini
Compatibility with MFP's in Viet-nam
Incident Properties
Question
Hi,
When it comes to installing SDK/J solutions, are MFP's sold in foreign countries just as compatible as MFP's sold in the US?
We have a customer in Viet-Nam that wants to run our Ricoh certified software on a MP C2004SP.
Regards,
Jean-Marc Palmier
UI for print release
Incident Properties
Question
Gerardo
During our online session a couple of weeks ago, you showed me a sample UI that may be of use for our print detail screen.
No rush, but when you have a chance, could you let me know where that sample can be found. It was the one with the coloured button panel at the bottom left of the screen.
Many thanks and best regards
Nick
File IO
Incident Properties
Question
Hi Support
I am trying to find some information on file io on the mfp. I have reviewed the 'sdkj_xlet_develop_panel_eR114.pdf' under section ImageIcon class and under Bitmap image usage, it states:
When creating image files dynamically, the image files must be placed on the working directory of HDD first. There are some important notes on accessing the HDD working directory; refer to the section "Cautions concerning HDD work directory" in the document "Important Descriptions."
I cannot find the sections that detail how file io is handled on the mfp. Could you please point me to the documents and sections that cover reading/writing and deleting files on the mfp.
In a nutshell our webservice sends an image stream (qrcode bitmap) and I see from the documentation that I cannot stream this directly to the image object but need to firstly write this to the mfp hdd and then display the image from the hdd file. This is a dynamic and transient file that needs to be written, read and then deleted.
Many thanks and best regards
Nick
Xlet taking about 5 minutes to talk to the server once started from the new devices
Incident Properties
Question
Hello,
In US Bank, whenever we stop and start the Xlet, it takes about 5 minutes even before our code could communicate to the back end server to retrieve the configuration.
We start the wireshark trace followed by starting the Xlet. I have attached the wireshark trace (as zip file) along with two snapshots.
WireSharkStartTime.png : You can see the time (21.46.50.159) when wireshark trace was started
ServerCall.png: You can see the time (21.52.34.339) when the HTTP call was made to the backend server.
Thanks
Niranjini
BTW: Unable to load wireshark trace *.pcapng and so loaded as a zip file.
Maintenance signature request for v2.0.2
Incident Properties
Question
Supported SDK/J versions:
10.x
11.x
12.x
Supported display panels:
HVGA
WVGA
SVGA
Modified jar files:
RicohClient.jar
RicohCommon.jar
No changes were made to the DALP file other than bumping the version.
There's only one bug fix in this version for one of our larger clients:
Cheers,
-Larry