medical software (Dentrix,etc) not being able to use Kyocera products

[KyoServiceManager]

Re: medical software (Dentrix,etc) not being able to use Kyocera products

I did just read the system requirements for Dentrix and it stated they recommend using PCL5 for all printers.

[copiertec]

Re: medical software (Dentrix,etc) not being able to use Kyocera products

I can try some of the options you guys have given me, I did email the client and am waiting to hear back, I will keep you posted.

[PrintWhisperer]

Re: medical software (Dentrix,etc) not being able to use Kyocera products

I've come across a couple different proprietary software packages that output PostScript print data or PCLXL print data directly to the printers IP, not through the print driver. Since Kyoceras native language is PreScribe, Postscript & PCLXL print data usually error CF248. When I talk to their tech support the question is: "Do you need Lexmark or HP LJ4 print output?"
No thank you. Just a path to the print driver please. =^..^=

As usual BC is on track so please do not get confused by this 'incompatibility' nonsense.

DO YOU GET AN ACTIVITY LIGHT BLINKING when the job is sent or not? If it blinks a couple times and nothing prints, the job was discarded for bad code.

If no lights blink, the data never made it to the device, and the code is NOT in play (yet).


Kyocera, just like Canon, Sharp, Ricoh and all the others use a standard print emulator which will render standard PCL code in PCL5 and generally PCL XL/6 as well. The place where it gets proprietary is generally in their own manufacturer's drivers with printer specific code such as PJL commands or emulated Postscript (everyone has it, Kyocera calls it Prescribe).

You can use just about any manufacturer's UNIDRIVER to print to any device and it will render, you just won't get device specific options like extra trays and such.

Similarly, send a PDF directly to a device (with PS support) and it prints without a driver because it is written in Postscript and the emulator can render it without driver involvement.

Medical software often uses 'Report Writers' (e.g. Crystal reports) which creates it's own code and passes it through the driver, ignoring any settings made there. This often includes JOB options which may be incompatible such as Media Type or Tray selection so the job will render, but may not have an available option that was requested (panel beeps and asks for attention). This was seen with EPIC software requesting Recycled as the media type regardless of the KX driver setting for Media.

Until you get Activity at the device, you have a PATH/PORT problem setting up a printer in the medical software. When you finally get a job to the device, do a MM977 data capture and you can have the code analyzed for validity and source. Sometimes they want a UNC path and a shared printer object.

Happy Hunting!