New 5050 runs slow on accounting side

[Guest]

Whenever adding new accounts, or refreshing the machine account list it is very slow. The 6030s we have and taskalfa 250ci we have can process about 200 accounts in about 20 secs, where the 5050 takes a few minutes.

Is there any reason for this. Is it just this slow, or could there be some sort of issue.

[oxtails]

is your firmware upto date? i know a lot of issues regarding speed of display etc have been recently improved.

[ChrisN1313]

Found out the new display on the 5050 doesn't have its own cpu and this is why it runs slow, unlike the taskalfa where it has its own cpu just for the display.

[aragul]

The 5050 has a cpu for the display, but it uses a web browser and html+javascript files for the interface, while the taskalfa 500ci uses a standalone program with QT Embedded for its interface.

It looks like KM-NET for Accounting can mess around with Job Accounting on the copiers somehow. I've never had to mess with it... yet.

[JtheCopyGuy]

Customer has a KM5050 and they complain of "accounting being slow". We've updated the Firmware and formatted the HD and restored their user data. The odd thing is it seems to be a gradual issue.
Also they are having printing issues due to their network, most of them are on a spotty wireless and it seems like the jobs are getting cut off mid-transmission, which causes the printer to choke on a job.
One of our Techs proposed that perhaps all of the fragmented data is causing the slow job accounting issue.
Just curious if anyone has run into something similar?

[blackcat4866]

How many active job account IDs are loaded onto your machine? I'm trying to remember the specs... my recollection is that they claim 1000 possible unique IDs. In reality the job accounting function bogs down to a creep at 937 unique IDs.