The Canon 1731 Support Code Error message is an attempt by Canon to combat the use of generic ink cartridges in their latest printer models. You are still able to use non genuine cartridges if you use the correct procedure.
This is the reason that we warn customers not to update their printers software. Updating your printers software often does nothing to enhance the printers performance and is totally unnecessary.
The latest printer models which can be affected by this software update include the following: MG5760, MG5765, MG5766, MG6860, MG6865, MG7760, MG7765, MG7766.
Canon 1731 Support Code Error Solution
If you see the error message to the left simply click on the "Do not detect" and keep printing. The 1731 Error code should only occur if you have updated your printers software or if your printer is extremely new and has already had the firmware updated from the factory.
To overcome this error you need to disable the ink detection function on your printer.
To disable this function press and hold the printer's Stop button for at least 5 seconds, and then release it.
Once this has been performed you can continue printing as normal. The only difference is that you will no longer be able to check ink levels. If the function for detecting the remaining ink level is disabled, the ink tanks will be displayed in gray on the LCD screen when checking the ink levels.
Be sure to keep an eye on the ink levels by physically removing cartridges when you think they may be getting low.
Update to the Canon 1731 ErrorJust a quick update concerning the 1731 error. We have been in contact with our suppliers and we now believe that the above error code is not just to do with the software update and that it may have just been a small glitch which occured with a handful of printers.
We have had no feedback from customers in regards to this error occuring so we will keep you updated if any further issues like this occur.
Further to this we dont recommend that you turn your ink detection system OFF on your printer as this is not at all necessary at this time. We will keep you posted if there are any further issues however it seems like we may have jumped the gun on this one.