Background
I have a very old
EPSON R300 inkjet printer
It has served me well for many years. I thought it was at least 10 if not 15 years old. I got it before I even became interested in Linux. For many of those years now I have been using this printer extensively on Linux.
It has been a really good printer and has been incredibly cheap to run. Many years ago I got a number of sets of ink for it. I think they only cost me £15! A colleague at work later on gave me more sets of ink. I ended up with a large bag full of ink cartridges which I have been working my way through ever since.
I used the printer infrequently for many years. This is far from ideal for an ink jet printer as doing so tends to cause the ink jet nozzles to clog up. Unsurprisingly in later years it has become somewhat temperamental. The problems consisted of paper mis-feeds (Probably down to the rubber take up rollers going hard over time) and missing bits of print (This I assume due to infrequent use of the printer and age of ink jet cartridges all of which were well out of their expiration date).
The mis-fed paper could be solved by individual feeding each sheet through the printer. The poor / missing print could be solved by a combination of running the print head clean routine or by replacing the offending cartridge.
Latterly I had print problems again and as per usual after cleaning the heads and then finally changing the cartridge the printer resumed printing normally.
Shortly after this I bought myself an Apple iMac mini and thought it could be useful to be able to print from it. I visited the EPSON website downloaded and installed the EPSON print driver for my trusty R300 printer.
I tried printing from my iMac and received a warning stating something like some of the components within your printer are worn and may need servicing. I’d never seen a message like this before as I normally print using open source print drivers on Linux which never report such things.
When I tried printing on my Apple Mac no black text was visible on the page. I tried running the head cleaning routine and this made no difference. I eventually had to resort to changing the colour of the text within the LibreOffice document. This allowed me to print text that was at least legible.
At the time I was a little suspicious of all this as the printer had been working so well just a few days previous. I plugged my trusty printer back into my trusty PC running an old version of Ubuntu using the open source printer drivers. Fired up LibreOffice and tried to print a document. To my surprise the printout was very good. While it was not as good as when the printer was new the quality of the black and coloured text was actually very good.
My suspicion though I can’t prove it is that the EPSON print driver has worked out that the printer is 10 plus years old and needs to be returned to EPSON for servicing (or to purchase a new printer). To ensure this the driver is crippling the output from the printer.
The Open Source print drivers have none of the nefarious nonsense and allows the printer to operate. As I said I cannot prove any of this however I’ll leave this up to you decide what you think is going on here.
At this point I was going to end the podcast however the story didn’t end there.
The story continues
My mother wanted me to print out some holiday insurance documents for her. She sent me a copy of her documents as I told
All content for Hacker Public Radio is the property of Hacker Public Radio and is served directly from their servers
with no modification, redirects, or rehosting. The podcast is not affiliated with or endorsed by Podjoint in any way.
Background
I have a very old
EPSON R300 inkjet printer
It has served me well for many years. I thought it was at least 10 if not 15 years old. I got it before I even became interested in Linux. For many of those years now I have been using this printer extensively on Linux.
It has been a really good printer and has been incredibly cheap to run. Many years ago I got a number of sets of ink for it. I think they only cost me £15! A colleague at work later on gave me more sets of ink. I ended up with a large bag full of ink cartridges which I have been working my way through ever since.
I used the printer infrequently for many years. This is far from ideal for an ink jet printer as doing so tends to cause the ink jet nozzles to clog up. Unsurprisingly in later years it has become somewhat temperamental. The problems consisted of paper mis-feeds (Probably down to the rubber take up rollers going hard over time) and missing bits of print (This I assume due to infrequent use of the printer and age of ink jet cartridges all of which were well out of their expiration date).
The mis-fed paper could be solved by individual feeding each sheet through the printer. The poor / missing print could be solved by a combination of running the print head clean routine or by replacing the offending cartridge.
Latterly I had print problems again and as per usual after cleaning the heads and then finally changing the cartridge the printer resumed printing normally.
Shortly after this I bought myself an Apple iMac mini and thought it could be useful to be able to print from it. I visited the EPSON website downloaded and installed the EPSON print driver for my trusty R300 printer.
I tried printing from my iMac and received a warning stating something like some of the components within your printer are worn and may need servicing. I’d never seen a message like this before as I normally print using open source print drivers on Linux which never report such things.
When I tried printing on my Apple Mac no black text was visible on the page. I tried running the head cleaning routine and this made no difference. I eventually had to resort to changing the colour of the text within the LibreOffice document. This allowed me to print text that was at least legible.
At the time I was a little suspicious of all this as the printer had been working so well just a few days previous. I plugged my trusty printer back into my trusty PC running an old version of Ubuntu using the open source printer drivers. Fired up LibreOffice and tried to print a document. To my surprise the printout was very good. While it was not as good as when the printer was new the quality of the black and coloured text was actually very good.
My suspicion though I can’t prove it is that the EPSON print driver has worked out that the printer is 10 plus years old and needs to be returned to EPSON for servicing (or to purchase a new printer). To ensure this the driver is crippling the output from the printer.
The Open Source print drivers have none of the nefarious nonsense and allows the printer to operate. As I said I cannot prove any of this however I’ll leave this up to you decide what you think is going on here.
At this point I was going to end the podcast however the story didn’t end there.
The story continues
My mother wanted me to print out some holiday insurance documents for her. She sent me a copy of her documents as I told
HPR4547: Cheap Yellow Display Project Part 6: The speed and timing of Morse
Hacker Public Radio
1 week ago
HPR4547: Cheap Yellow Display Project Part 6: The speed and timing of Morse
Hello, again. This is Trey.
Welcome to part 6 in my Cheap Yellow Display (CYD) Project series. Thank you for hanging in there with me on this rambling series. If you wish to catch up on earlier episodes, you can find them on my
HPR profile page
https://www.hackerpublicradio.org/correspondents/0394.html
To review, my project is to build a portable morse code "Keyer memory" which can be connected to any of my amateur HF transceiver radios by simply plugging it in to the code key input port. This is based around an ESP32 platform which comes prepackaged on a yellow PC board with a color touchscreen display, WIFI, and Bluetooth. We fondly call this contraption the Cheap Yellow Display.
So far, I have defined the necessities, collected the required hardware, and failed miserably building the graphical user interface (GUI).
While I sort out the technical challenges getting my GUI code to play nicely with the CYD's touchscreen, it is important that we spend some time discussing Morse code itself, and the timing standards we will need to follow.
I am not going to dive too deeply into the history behind telegraphs and Morse code, but it is very interesting. If you want to learn more, Wikipedia has the origins and evolution written out quite nicely at
https://en.wikipedia.org/wiki/Morse_code
For our purposes, we will fast forward from the year 1820 (When telegraphy began) all the way to 1865 when the International Telecommunication Union (ITU) standardized, what it called "International Morse Code". When I say Morse Code for the remainder of this podcast, I am referring to this ITU International Morse Code.
Morse code typically includes the following characters:
The 26 letter basic Latin alphabet
The Indo-Arabic numerals 0 to 9
There is also a single accented Latin letter (É), which is written as an E with an accent mark, and a handful of punctuation marks.
These characters are encoded using a sequence of short and long signals. Each short signal is referred to as a
dit
. Each long signal is referred to as a
dah
. At a young age,
Hacker Public Radio
Background
I have a very old
EPSON R300 inkjet printer
It has served me well for many years. I thought it was at least 10 if not 15 years old. I got it before I even became interested in Linux. For many of those years now I have been using this printer extensively on Linux.
It has been a really good printer and has been incredibly cheap to run. Many years ago I got a number of sets of ink for it. I think they only cost me £15! A colleague at work later on gave me more sets of ink. I ended up with a large bag full of ink cartridges which I have been working my way through ever since.
I used the printer infrequently for many years. This is far from ideal for an ink jet printer as doing so tends to cause the ink jet nozzles to clog up. Unsurprisingly in later years it has become somewhat temperamental. The problems consisted of paper mis-feeds (Probably down to the rubber take up rollers going hard over time) and missing bits of print (This I assume due to infrequent use of the printer and age of ink jet cartridges all of which were well out of their expiration date).
The mis-fed paper could be solved by individual feeding each sheet through the printer. The poor / missing print could be solved by a combination of running the print head clean routine or by replacing the offending cartridge.
Latterly I had print problems again and as per usual after cleaning the heads and then finally changing the cartridge the printer resumed printing normally.
Shortly after this I bought myself an Apple iMac mini and thought it could be useful to be able to print from it. I visited the EPSON website downloaded and installed the EPSON print driver for my trusty R300 printer.
I tried printing from my iMac and received a warning stating something like some of the components within your printer are worn and may need servicing. I’d never seen a message like this before as I normally print using open source print drivers on Linux which never report such things.
When I tried printing on my Apple Mac no black text was visible on the page. I tried running the head cleaning routine and this made no difference. I eventually had to resort to changing the colour of the text within the LibreOffice document. This allowed me to print text that was at least legible.
At the time I was a little suspicious of all this as the printer had been working so well just a few days previous. I plugged my trusty printer back into my trusty PC running an old version of Ubuntu using the open source printer drivers. Fired up LibreOffice and tried to print a document. To my surprise the printout was very good. While it was not as good as when the printer was new the quality of the black and coloured text was actually very good.
My suspicion though I can’t prove it is that the EPSON print driver has worked out that the printer is 10 plus years old and needs to be returned to EPSON for servicing (or to purchase a new printer). To ensure this the driver is crippling the output from the printer.
The Open Source print drivers have none of the nefarious nonsense and allows the printer to operate. As I said I cannot prove any of this however I’ll leave this up to you decide what you think is going on here.
At this point I was going to end the podcast however the story didn’t end there.
The story continues
My mother wanted me to print out some holiday insurance documents for her. She sent me a copy of her documents as I told
