EPSON - TMU200B - healthcheck not working on network printer

[kammots]

The printer model is a M119B. I took out the parallel card and replaced it with an ethernet adapter. When I try to add this printer to OPOS, I select the 200B then in the under detailed model select 200BE. I am able to assign the IP but when I click on Checkhealthnet Interactive I get the message below.

Error occured in calling the checkhealth method

Claim(5000) = 106 (0x00000006a)

ResultCodeExtended = 10002 (0x00002712)

Any help/suggestions are appreciated.

Thank you.

[James M SellerDeck]

Hi there

Have you checked you have the correct baud rate set up for the printer? To check this, switch the printer off, hold down the feed button, and switch it on again, a settings report should print out, and tell you what the baud rate is.

You can set the baud rate by right clicking the M119B printer that you have added to the OPOS setup, and going to communications settings.

If that is different in there to waht you have on the print out, change it and try the check health again.

Hope that helps

[kammots]

the baud settings are unaccessible through the OPOS and the print test does not print anything about the baud information.

When speaking with my hardware department they mentioned that the detailed model number is the 119, but it is actually a 200B. Sorry for any confusion.

thank you for your response, any other ideas?

[James M SellerDeck]

Hi there

Do you know what com port you have the printer connected to? Do you have other hardware aswell, like a pole display or cash drawer?

Im not familier with the printer model you are using, is it a serial cable that connects it to the pc?

[kammots]

Using the OPOS software, the printer is not installed through Windows and does not have a port assigned. I use TMNnet Winconfig to assign the correct IP address to the MAC address of the network card on the printer. The printer connects to a cat5 cable that goes to the router.

There are no other devices connected directly.

The only issue seems to be with this model. Someone else had a similar problem and started looking into upgrading the firmware. I think I will try that route, thank you for your replies.