Tulip Serial Connection

[jasonh]

I’m testing a new printer we may be purchasing in the future, and I’m connected to the printer via a Serial to USB cable.
My janky test app has a list ports button to confirm the printer is connected:

When I try printing I get the following error message:

My trigger is pretty basic, I’m not sure what could be causing the issue?

I would appreciate any help or ideas to test out. I am able to print using notepad in windows so I know it’s semi working at least!

[jmlowden]

Try making a button to run the disconnect function to diconnect that Identifier, then try connecting again.

[jasonh]

Thanks Jim,
I updated my test app and removed additional triggers to make things more simple. While i’m a but further than yesterday, I’m not successful in printing labels… yet.

Here’s my super fancy app:

So at this point no connections have been made. I press the connect button to make the RS232 connection:

And this is what the console in the Tulip Player reports back:

When I click the “Print Hello Tulip EXP” button, I get a single blank label to print out. I guess it’s something! Here’s what that trigger looks like:

Clicking the “Print Hello Tulip Static” button does nothing.

I will get an error if I haven’t clicked connect first, but that’s by design. Same thing goes for the “Connect AND Print Static Text” button. That button’s trigger is just the connect and print static text trigger put together.

…and the disconnect is just a disconnect:

The printer does work. I can open notepad and print a label right now:

I would greatly appreciate any ideas or things to try.

[jasonh]

So it turns out the Expression was the cause. The returns in the expression work on the labelary site, but breaks the message in Tulip.

Turing this:

Into this:

Fixed the problem. It would be helpful in the future to have a knowledgebase article that specifically talks about what is/is not possible in an expression for ZPL. If anyone else has this issue, hopefully this post will point you in the right direction!

[Beth]

Thank you for sharing your solution Jason! I’m glad you figured it out and everything is working nicely now. I will work with @L_Churchill and team to update the KB with this information