C3350 papercut embedded

[wseyller]

Has anyone used the C3350 on papercut with the i-option and memory upgrade to get the embedded interface.

If so is it stable for you. Seems challenging getting it managed without errors. I can make it work but it is painful.

I have used the standard interface for a long time without problems.

Sent from my XT1254 using Tapatalk

[wseyller]

So far I have tried 3 different papercut servers and two different C3350. So far not working right.

Currently I setup my laptop as a papercut server connected directly to the 2nd copier using cat5 cable.

This is a problem with the embedded with i-option interface only. Standard UI works perfect.

When adding the device in papercut or making changes the status will show "connection confirmed with i-option" but the control panel shows "please wait" for what seems forever. I finally just use the sub power off then back on and the papercut interface shows up just fine after.

The real problem is when using the card swipe. Happens with both AU-201H or AU-205H model reader. After swiping card you get an error on the papercut interface of the copier "Unable to Unlock Device, please try again".

There have been times I've got it to work, just takes many tries and alot of finesse. But after a day or after some period of time I eventually gives the Unlock device error.

Also when trying to delete the device from papercut if gives error and is hard to remove.

Latest firmware 607-W99, with sub controller 607-899, and engine firmware 1800

It was suggest to me to change softswitch 25 from hex value 00 to 10 which did nothing.

Still working on figuring this out. Just wanted to post this in case anyone else is going through the same situation. I will post when I find out more.

[EarthKmTech]

Got 4 of these going into a paper cut environment next week.

Not sure if using web browser version interface though, would not surprise me.

[wseyller]

I have been working with papercut support for quite a while now dealing with this "unable to unlock device" error using the i-option interface.

I have been testing and sending debug logs for a month now. I believe they are involving Konica Minolta now and they say they are gonna try testing in-house so as to relieve me of all the time I'm having to spend on this.

The "unable to unlock device" error only happens when doing card swipe. Username/pass and identity number works fine. Strangely swipe will work if you leave show account confirmation checked, but we never like to leave it checked.

It is glitchy as hell with i-option interface overall. If after making a change and device status show connection confirmed the display might be stuck on "please wait". Pressing sub power off then on will bring papercut interface back.



If using the standard interface you should have no problem except possible when using papercut 15.2 which has a issue with the C3350. Better to use 15.1. You might receive an error about pullprint app in slot #2 not found error in device status. Papercut found out about it when looking through all my debug logs. Then I experience the pullprint issue on a new install I did shortly after. I had to downgrade to 15.1 to resolve. Papercut will fix this in next release.



Sent from my XT1254 using Tapatalk

[EarthKmTech]

very informative post, thanks for that.

I will let you know the scenario when I do the install, sounds like they are going to have a solution soon enough anyway.

[wseyller]

This issue still seems to exist. C3350 with i-option is stable without card reader for a few months but now customer wants card readers. Latest everything, firmware, Papercut 16.1 and loadable driver with au-205h.

Get the unable to unlock device.

Anyone else successful

Sent from my Nexus 6P using Tapatalk

[emujo]

I recently installed this in our demo room, C3350 with AU-205H, and latest version of papercut MF. Running same firmware and LDD with no errors. I am not using the additional memory as it is not required for I-option. EMujo

[wseyller]

I recently installed this in our demo room, C3350 with AU-205H, and latest version of papercut MF. Running same firmware and LDD with no errors. I am not using the additional memory as it is not required for I-option. EMujo

I am wondering if the type of prox cards make a difference too. The one customer has a mixture and have mentioned that one card does work while a couple others don't. All cards will self associate ok. the error happens on swipe to login.

I have someone from KMBS that is gonna try and test it out for me.

[Synthohol]

Had an issue similar to this a year ago. Turns out if you only enable card logon and disable keyboard logon on the papercut server all was right with the program.
May be something to try.
Good luck.

[wseyller]

This customer uses a four digit pin code so they wouldnt go for that. I also have ACDI ticket and they are looking into it also.

Sent from my Nexus 6P using Tapatalk