Support for Multiple PIDs During Fast Bootloader Re-enumeration in RfIdeasPlugin
Incident Properties
Question
HI Team,
We are enhancing our RfIdeasPlugin(1667760129) by adding support for Fast Bootloader to significantly reduce the firmware update time. This process involves transmitting data in 4KB chunks for faster performance.
As part of the Fast Bootloading sequence, we re-enumerate the reader's PID to 1. The steps involved are as follows:
1. Connect the reader with the correct initial PID (e.g., 3BFA)
2. Verify if the reader supports Fast Bootloader
3. Re-enumerate the reader’s PID to 1
4. Disconnect the reader
5. Wait for 3 seconds
6. Detect the reader with the new PID (1)
7. Re-scan and re-establish the connection
At step 7, I’m facing an issue while attempting to claim the reader connection.
Scenario:
When the plugin is deployed, the printer registers the reader’s current VID and PID. However, after re-enumeration, the reader’s PID changes. As a result, the printer no longer recognizes the updated PID, causing the plugin to crash with the error message “RfIDEASPlugin keeps stopping” (refer to Image 1). This ultimately leads to a failed connection attempt.
This issue seems to be caused by a mismatch between the VID/PID registered by the printer (3BFA, as shown in Image 2) and the reader's PID (0001) after re-enumeration.
I reviewed the SmartSDK documentation but couldn’t find any reference to support for multiple PIDs—other than adding entries to the Program Device List, which unfortunately does not resolve the issue in my case.
Could you please advise if the printer can be configured to support multiple PIDs?
Alternatively, is there a way to bypass the “RfIDEASPlugin keeps stopping” issue so that I can continue with the firmware update process?
Any suggestions or alternative approaches to handle this scenario would be greatly appreciated.
Looking forward to your guidance.
Thanks.
Prod signed binaries can't be installed
Incident Properties
Question
We recently got back some prod signed binaries from a maintenance request, but we are unable to install them on any of our printers. Can we double check that these were signed? If we beta sign the same binaries we originally sent they are able to install successfully.
Ricoh Compatibility Testing Request
Incident Properties
Question
We've fixed a customer reported issue and are requesting compatibility testing for a new build of our Embedded
Android app. We had 3 customers report the same issue with an error message displayed on our app's page
count summary screen after using the Smart Copy app with paper select set to Auto and a paper size of A3.
We should schedule a time to review the VM used in our last certification to determine if any updates are needed.
Please let us know if anything additional is needed or if there are any questions.
If possible, please provide an estimate for when work will begin on our request.
Thanks.
MAINTENANCE SIGNATURE FOR SMARTSHARE V2.0.10
Incident Properties
Question
Hello,
We would like to ask for a maintenance signature for Smartshare Android embedded solution.
- stability improvements and bug fixes
King regards
Anderson
New Access Token
Incident Properties
Question
Hi We would like to request a new access token with an additional Serial Number.
Item |
Description |
Product ID* |
1979711549 |
Vendor Name* |
ePRINTit |
Application Type* |
“Web Application” |
Partner key (Public)* |
*Attached as Publickey.pem |
Expiration Date |
3 years |
Serial number |
3940P500195, 3929PA01713 |
Product name* |
ePRINTit SaaS |
Location* |
|
Function |
|
Target Version |
|
Attachments:
Thank you,
Jordan
Maintenance Signing Request
Incident Properties
Question
Maintenance release. We added support for the RFIdeas Wave ID Plus Mini Logic MD30L00 card reader.
Validate Failed Error Message
Incident Properties
Question
Hi We are trying to run our application from the WebBrowser NX on a Ricoh IMC 3000. When we proceed to the copy, print or scan and try the call to get the capabilities, the device is returning a pop-up with the message "Validate Failed". This is then preventing the application from calling any of the Ricoh functionality. Do you know what could be causing this. Is it possible that this is an issue with the access token or would this be a user management setting on the printer?
REQUEST FOR MAINTENANCE SIGNATURE FOR V3.8.16
Incident Properties
Question
Request for maintenance signature, bug fixes and other enhancements.
MAINTENANCE SIGNATURE FOR SMARTSHARE V2.0.9
Incident Properties
Question
Hello,
We would like to ask for a maintenance signature for Smartshare Android embedded solution.
- Improvements in messages and logs in http and https requests;
- 'Please wait' box between screen transitions;
King regards
Anderson Palhano
Reply to 5511 Async Job Events not received on certain models
Incident Properties
Question
Hi,
Following the latest advised from RIDP on incident 5511 (which is now closed):
- Reproduce the problem with whatever application you see fit -- we just need to know which app is used. If you use the scan sample app ideally it is not modified, though logging the raw JSON it receives for the scan event object would be one modification I'd make. Be sure to use the latest sample app from the latest development kit.
- Collect a new set of device logs.
We gave the customer the latest sample app and asked them to provide the new set of device logs. Please find the device log attached.
Thanks