Sending Null Termination With Commander Task

Legacy Poster

• July 06, 2015 20:08

Hi,

 

We are working with a system that is sending an XML payload to commander via TCP socket.  The XML payload will transformed and a print job initiated.  The problem I'm coming across is getting the socket to properly close with the other system.  Basically, that system is expecting a null termination of the XML response that Commander sends back to it.  I know there are ways to send other values at the end of a response (LF, CR, EOT, etc...) but I have not been able to get a null value across.

 

Does anyone know of a way to send a null value through an embedded commander response?  I've attached several screenshots of the test config.

 

The Task list:

[attachment=1707:TaskList.png]

 

The Task Details:

[attachment=1705:TaskDetails.png]

 

The Embedded XML that will be sent back:

[attachment=1706:TaskEditor.png]

 

 

Thanks in advance for any help with this.

 

 

 

0

• 

  Shotaro Ito

  ★ BarTender Hero ★

  • July 13, 2015 03:44

  As I understand, In current version(10.1) there's no way to send NUL (00H) code from Commander, though it can send other control codes.

  Try there's any workaround in receiver's side.

  0
• 

  Legacy Poster

  ★ BarTender Hero ★

  • August 20, 2015 01:09

  As I understand, In current version(10.1) there's no way to send NUL (00H) code from Commander, though it can send other control codes.

  Try there's any workaround in receiver's side.

   

  Thanks for the reply. We ended up adding EOT termination on the receiver end.

  0

Please sign in to leave a comment.