TP Studio v2.58-1 with canon Pro-10S & iP8760 - Linux Mint 22.2
Pro-10S connected over ethernet (via router - fixed DHCP address allocation) - bjnp://192.168.1.38:8611
iP8760 connected over USB - tpu://Canon/iP8700_series/SN=21****
Both printers print 100% OK
Printer Monitor for Pro-10S reports "Printer not connected or switched off"; also fails to report Ink Levels via toolbox
This glitch seems to have emerged after switching from a WiFi connection to cabled ethernet. Network connection reporting & Ink Level Check worked as expected under WiFi. (change to ethernet due to usability issues over WiFi)
I can see that I am not the first to raise this query, but I have not been able to find a solution on this forum. Assistance sought please.
Tx.
Pro10S - Connection SNAFUs
Re: Pro10S - Connection SNAFUs
Well I'm a little perplexed. With no intervention by me, the TurboPrint Monitor is now correctly reporting printer status, and the Toolbox is recording and displaying ink levels etc for the Pro-10S. Can anybody suggest what caused this improvement - given that the only activity undertaken with the printer was to print with no changes to config parameters?
Re: Pro10S - Connection SNAFUs
Hello riclin,
thank you for your follow up message. Normally, the status and ink messages should work via the BJNP connection. It looks as if the printer could not be found, possibly because it was blocked by another process? Some Canon printers also can connect via TCP/Socket protocol - this could be an alternative connection type with a different approach to get status and ink.
thank you for your follow up message. Normally, the status and ink messages should work via the BJNP connection. It looks as if the printer could not be found, possibly because it was blocked by another process? Some Canon printers also can connect via TCP/Socket protocol - this could be an alternative connection type with a different approach to get status and ink.
Re: Pro10S - Connection SNAFUs
Hmm - well although the issue appears to have sorted itself out, it would be reassuring to know what precipitated the fix. Your suggestion that the TP process may have been blocked by another process sounds reasonable - but not knowing what the "other process" was is a little perplexing. I am as suspicious of problems that resolve themselves for no apparent reason as I am regarding the initial problem.