Need to send print job to HP M402n with two different share names each share printing from diff tray

[drw22]

We have serveral printers in our water testing lab that have different paper loaded in trays with the ability to select which print tray we want to send a job to (actually the instructions to choose which print job to is set up in a data file and all the user has to do is to select to initiate the print process. These printers have LPR queue naming techniques to allow the print jobs sent to same ip address but the hp lj pro m402n doesn't seem to have that capability and it would be nice to set this up programmically for ease of use. Can anyone show me a work around to get this to work? I can set up different share names to the same network printer and put different settings in and when I send a test print out everything prints as expected. But when I use the legacy app we are using to print the different documents we use, it maps LPT1 to one of the share names associated with it but the output does not print from the correct source tray for one of the share names. Since there is no way to set up the lpr queue in the m402n, there appears no way to identity which settings to use. I would appreciate any help you might be able to give.

Don

[Repairatrooper]

Just to be sure I am clear, are you creating multiple "driver instances" for the printer and mapping each of those with a different share name? If so, setting the print preferences on the driver instance for each share should force the correct output. Unless your legacy program is creating PCL codes that the 402 misinterprets.

[drw22]

Printing to the different share names for the 402 through a windows app DOES work. The problem seems to be printing to the shares via the cmd box that runs the console C legacy app.

In this legacy app we have carried forth the legacy code that issues a

"net use LPT1 \\{server name}\{printer share name} /USER:{user name} {user pw}"

to map LPT1 to the share name. I am going to try to do all this manually in the off hours of our business in the next 2 days to try to see if I can see exactly where the problem is.

But one thing that stands out to begin with is that I read somewhere online that the 402 does not honor the lpr virtual printer queues that the other printers we are using have and have no problem with the legacy app printing thru the net use mapping. We have to go into these other printer settings via a web browser and enter these lpr print queue names to get this to work and I see no equivalent of this in the 402. I will try to check this out some more in next several days.