First, we connect successfully to the Printer API using the following lines:
Zebra.Sdk.Comm.Connection _ZebraApiConnection = ConnectionBuilder.Build("TCP_MULTI:10.100.120.236:9100:9200");
_ZebraApiConnection.Open();
Next, with an open connection to the Zebra Printer API, we attempt to call ZebraPrinterFactory.GetLinkOsPrinter(_ZebraApiConnection) which returns null.
We can access the printer through the web ui and says:
Status: READY
This issue happens on multiple ZT410 printers with the latest sdk (V2.15.2634), firmware (V75.20.21Z) and link-os (V6.2).
We are using C# .NET.
Link to SDK here https://www.nuget.org/packages/Zebra.Printer.SDK/2.15.2634?_src=template
Separate from above issue, on one of the printers when executing the following code:
Zebra.Sdk.Comm.Connection _ZebraApiConnection = ConnectionBuilder.Build("TCP_MULTI:10.100.120.237:9100:9200");
_ZebraApiConnection.Open();
We receive the following exception:
Zebra.Sdk.Comm.ConnectionException: Could not open connection
at Zebra.Sdk.Comm.MultichannelConnection.Open()
The printer throwing the connection exception is available through the web ui and shows the following status:
Status: PAUSED
ERROR CONDITION PAPER OUT
Both of these issues happen consistently every time the code is executed. Has anyone else had this issue and any luck resolving. Happy to provide additional details if helpful.
Issue connecting to ZT410 using Zebra Printer SDK// Expert user has replied. |
1 Replies
Do the two issues happen only to the particular printers or happen to all printers in your network?
Before calling ZebraPrinterFactory.GetLinkOsPrinter(_ZebraApiConnection), could you check if _ZebraApiConnection is truly open, i.e. _ZebraApiConnection.Connected is true.
Zebra.Sdk.Comm.Connection _ZebraApiConnection = ConnectionBuilder.Build("TCP_MULTI:10.100.120.236:9100:9200");
_ZebraApiConnection.Open();
ZebraPrinterLinkOs printer = null;
if (_ZebraApiConnection.Connected) {
printer = ZebraPrinterFactory.GetLinkOsPrinter(_ZebraApiConnection);
}Regarding the 2nd issue, it looks like a different manifest of the first issue. I suspect that your network configuration may have restrictions on accessing the printers.