TCP Communication to Domino Printer

Having some issues getting a TCP connection working and thought I’d ask here and see if anyone has any experience.

We are trying to send commands via TCP to a Domino V-Series Printer. We have confirmed that a command actually leaves ignition using both the TCP module and a Python script, and arrives at the printer port, but nothing ends up being updated. Using a third party TCP tool called Hercules, we are able to send commands to the printer and it works fine there.

I’m not sure if we aren’t sending command characters via the string correctly? Or if there is something else. At least in terms of human readable, it seems to transfer identically comparing between Ignition and Hercules’ commands. I’m just not sure if there is something going on behind the scenes.

we have tried using commands in the following formats

$01FillSerialVar=$0202$03,$02BB 05 2024$03$17

[SOH]FillSerialVar=[STX]02[ETX],[STX]BB 05 2024[ETX][ETB]
<SOH>FillSerialVar=<STX>02<ETX>,<STX>BB 05 2024<ETX><ETB>

Are you using the TCP & UDP driver?

Consider not, if so. Direct use of sockets is far more reliable, like the following discussion about sending commands to Zebra printers:

So far we have tried both routes. Using the TCP driver and using a script that looks very similar to that one. The device just doesn’t seem to like the string we are sending across. I just started digging through some wireshark data to see if I can find anything there.

Are you using the actual ascii values? Perhaps something like:

soh = chr(1)
stx = chr(2)
etx = chr(3)
etb = chr(23)

strOut = soh + 'FillSerialVar=' + stx + '02' + etx + ',' + stx + 'BB 05 2024' + etx + etb

That was it. I wasn’t sure what the ASCII values were and was hoping the printer would still understand the hex values.

Thanks!

1 Like

Jython understands hex escapes in strings using the form \xHH, so the string could also be written:

strOut = "\x01FillSerialVar=\x0202\x03,\x02BB 05 2024\x03\x17"
1 Like