RXOP

I've been using ROC to test some things on our devices and I noticed that one of our machines can't start the the RXSP Servlet from either version of ROC (1.3.4 or 1.6.1). When I go to start the servlet by hand it gives me the error code J522. My guess is that the device has an old firmware and needs updating but I have no idea how to verify that.

1. How do I get the current firmware?
2. How do I check if that firmware is the latest version?

Thanks

Hi,

We recently obtained a new ACL file with values for setting auto reset and auto logout timers. We're getting an error from the MFP when trying to set the values. Is a minimum FW required for the MFP to support this SP mode setting? We're trying to turn on the System Auth Reset Timer and set it to 61 seconds.

Thanks,

Nick.

Hello,

I am attaching a request for a new ACL.  This includes the model codes for the new G2.5 devices.

Regards,

 Bryan

See attached ACL request

Hello,

We recently came upon a weird issue where the installation of our application on a MFP using our deployer (which uses RXOP) was working but the creation of a shortcut on the homescreen was failing. We eventually figured out that someone had changed the Administrator Authentication Management settings and that was the source of the issue. After some trial and error we found out that the "Machine Administrator Authentication" setting had to be set to "On" and the "Administrator Tools" setting under Machine Administrator had to be checked.

What I would like to know is if it is normal for the installation of the application and the creation of a shortcut on the homescreen to require different permissions. I ask because I would like to document the settings required for installing an application (which includes the creation of the icon on the home screen). 

The way we create the shortcut in our deployer is by making a call to Configurator.setHomeScreenIconSetting().

Thanks,

Peter

I've created a new ACL request file with a bunch more values. Since it's so hard to get information from the core team I've added a bunch of values that look useful to us so I can test them and see if they do what we need. Once I have an idea of what values we need I'll create a new ACL request with only the values we need.

Note that for most of these I have no idea what the values are so I've just written "ALL", if there's a different value that needs to go there let me know.

Hello

Continue the incident ID#: 2980,

I see newest RXOP 3.7 lib is using old 3rd libraries commons-codec-1.3.jar and common-httpclient-3.1.jar.

Can we upgrate to newest 3rd libraries to replace them?

Thank you

Ngoc

We are developing an installer to automate the setup process of a MFP so our solution can be fully useful from the beginning. We tried to run ROC pointing to a device with SDK/J 7.24 and another with 10.24. Are those versions supported by rxspServlet? We always get the "[172.16.0.250] rxspServlet not found." from those devices. From Android devices it works as expected.

Best regards

We are using the default version of RXOP created by RICOH to work with our embedded solutions. After the installation of Android solutions, we noticed that the panel reboots without a direct reboot command (even with the no_reboot argument). With our SDK/J solution, we used to stop-uninstall any previous solution, install-start the current version and then explicitly reboot the device. Now, with SOP, when we uninstall any previous solution and install the current version it reboots without the explicit reboot command. If we then explicitly reboot the device there are listeners that are not deallocated (those listeners are created when the solution is instantiated). It seems that the explicit reboot command through RXOP is not totally killing the application. If we do a hardware reboot (shutdown and power on the device) everything works fine.

We noticed that behavior working with the Tracking implementation, that it stored more and more listeners according to the number of soft reboots we did. It seems an issue with RXOP. It should work closely as a hardware reboot, doesn't it?