Powered by RND
PodcastsUddannelseHacker Public Radio

Hacker Public Radio

Hacker Public Radio
Hacker Public Radio
Seneste episode

Tilgængelige episoder

5 af 137
  • HPR4517: Cheap Yellow Display Project Part 4: The hardware
    This show has been flagged as Clean by the host. Hello, again. This is Trey. Welcome to part 4 in my Cheap Yellow Display (CYD) Project series. If you have hung in there with me so far on this journey, thank you. If you have missed earlier episodes, you can find them on my HPR profile page https://www.hackerpublicradio.org/correspondents/0394.html If you have questions, comments, concerns, or other feedback, please leave an episode comment, or drop me an email (Using the address in my profile). Even better, you could record and upload your own show which shares your viewpoint or expertise. To review, I finally have an actual project to build using the CYD. It is a portable, programmable morse code "Keyer memory" which can be connected to any of my HF transceiver radios by simply plugging it in to the code key input port. Then I could transmit stored messages by simply touching their specific icon on the touch screen. So, now I purchased a pair of CYDs. Each arrived in an anti-static zipper bag with a USB C cable, a 6 inch long 4 pin PB1.25mm to Dupont 2.54mm cable harness, a plastic case holding the CYD itself and a small plastic stylus. There are pictures in the show notes. Depending on how many IO connections I may need, and how I plan to power this, I am probably going to need more 4 pin PB1.25mm wired connectors. You can see a description of the various features and connectors on RandomNerdTutorials writeup about this board ( https://randomnerdtutorials.com/cheap-yellow-display-esp32-2432s028r/ ). The only difference I can see between this description and what I received is that mine have both a MicroUSB and USB C port. Of course, first thing, I had to plug it in and see what happens. It appears to be running some kind of simulation of a web site. The backlit display looks alright. It is not super high resolution, but for the price, it will suite my needs. The touch screen is responsive, but it is pressure sensitive and works best using the provided stylus or a fingernail and not your finger tip. So, I have the CYD. What other hardware do I need? I need to address how one of these will actually connect to my radios. Modern amateur radio transceivers which support continuous wave (CW) transmission (Which is another name for Morse code) generally can use one of two different pieces of hardware for input. The first is what we call a straight key. Below is a photo of the one I own. This is a classic, old fashioned telegraph style code key. It is designed to quickly and easily be pressed down to close a circuit and when released the circuit is opened, effectively making it a normally open push button switch. To send a dot, the operator holds down the key for a short period of time, then releases it. To send a dash, the operator holds down the key for a longer period of time, before releasing it. (We will discuss actual timing specifications for morse code in a future podcast) Connectivity for the switch has been standardized to use a 3.5 mm mono male phone connector which has only sleeve and tip connections. The second option is a paddle style electronic keyer. There are many styles of these, and I am including a picture of the one I use, which once belonged to a close friend of mine who is now silent key. In general, the paddle is two separate normally open switches. In the most common configuration, if an operator presses and releases the paddle on the right, a dash is sent. If the paddle on the right is held, a continuous series of dashes will be sent until that paddle is released. The left paddle works similarly. If it is pressed and released, a single dot is sent. If it is pressed and held, a series of dots is sent until it is released. The function of these paddles can be swapped from left to right using the radio configuration. There is additional functionality which can be configured in some radios for when both paddles are pressed simultaneously, but I am not going to describe those here. The paddle generally uses a 3.5mm stereo male phone connector with the sleeve being common. The tip of the phone connector is wired to the left paddle and ring of the connector is wired to the right paddle. Most modern radios have a built in keyer which can be configured for a paddle and will automatically transmit the dots or dashes at whichever speed is configured based on the paddle pressed. You can see this phone connector illustrated on Wikipedia's phone connector page. . https://en.m.wikipedia.org/wiki/Phone_connector_(audio ) You can learn more about all the various devices which can be used for sending morse and how they function at Morse Code World . https://morsecode.world/keys.html Ideally, controlling all the morse code timing within the CYD would be best. That way, it could be connected as a straight key and any keyer settings already configured within the radio shouldn't matter. However, If I wish to also be able to manually send morse code myself using my paddles, without disconnecting the CYD and reconfiguring the radio, that could be problematic. I may need to factor in the possibility of connecting my paddle to the CYD and then building in code to respond to inputs from the paddles. As I mentioned in a previous episode, I have an Arduino Nano on my desk as a practice oscillator for my paddles. I may be able to reuse some of that code on the CYD. So, if I want the CYD to appear to the radio like a straight key, I will need it to be able to control a switch quickly and accurately. But I also want the CYD and the radio to be electrically isolated from each other. This calls for a relay. I was able to find and order some inexpensive relay modules which work nicely with Arduino and ESP32. These allow connectivity to 5v power and to one of the CYD's GPIO pins. These feed an optocoupler circuit, which, in-turn, drives the coil of the relay. This provides inductive kickback protection to the CYD and can drive a coil which would require more current than the GPIO can provide. Inductive kickback rabbit trail: An inductor is simply a coil of wire. Direct current flowing through any wire generates a magnetic field. Within the inductor, because the wire is coiled, the magnetic field builds from each pass of the wire in the coil. If you include an iron core, it sustains the magnetic field even better. This is the basis for an electro magnet. A relay is simply a momentary contact switch controlled by an electromagnet. One unique property of an inductor is that, current wants to keep flowing in the direction it was applied. To be specific, when the current source is removed, the magnetic field still exists for a while, and it effectively "generates" an electric current within the coil, in the same direction as the one which initially created the magnetic field to begin with. If it has a path to flow, this current will create another weaker magnetic field, which creates its own electric current, in a diminishing loop. If the circuit which drives the coil of a direct current relay is not ready for this continued push of current, damage can be done. Many times this is countered by wiring a "flyback diode" in parallel with the coil and in the opposite direction in which current will be applied. This way, when the current source is stopped, the diode gives a path for the inductive kickback current to safely flow while the magnetic field dissipates. Explained in greater detail at https://inductive-kickback.com/2019/04/inductive-kickback-made-simple-to-grasp-easy-to-handle/ The switch side of the relay is a single pole double throw (SPDT) and makes connections available for common, normally closed (NC), and normally open (NO). It will be easy to connect the common and NO connections to a 3.5mm mono male connector so that it may be plugged into the "key" port on any radio transmitter. I will need to do some testing on the speed of the relay, but I think it will work just fine. Once I start writing some code for the CYD, I will be able to connect and test the relay. Well, this is a good place to end this episode, and it is one of the longest in this series so far. In the next episode, we will begin to look at how we design the user interface for our program, something I do not know anything about (yet). Stay tuned weekdays for additional exciting episodes of Hacker Public Radio, and, at some point, the next episode in this series. If you like what you have heard, please leave an episode comment, or drop me an email (Using the address in my profile). If you have more than a single sentence to contribute on the subject, I encourage you to record an episode with your thoughts and expertise. If you dislike what you have heard, you are encouraged even more strongly to record and upload your own show which shares your viewpoint or opinion. Until next time. Provide feedback on this episode.
    --------  
  • HPR4516: Browser User Agent
    This show has been flagged as Clean by the host. A while ago I visited a web site that is an archive for old historical documents. It is a data base from where documents can be downloaded as pdf-files. As a visitor I can login to the archive as a guest. When I find a document of interest after search I can right click on the pdf icon and download the document. But I can not. No download when I click on the pdf icon. This is the first time I visit this archive so I do not know exactly how it works. It was time to investigate the root cause. I use Firefox on a Linux machine. I tested several methods to see if any would solve the issue. I tried by changing settings for pop-ups. I changed Firefox security settings. I disabled VPN. I disabled Firefox extensions for blocking trackers. I tested also the Chromium browser as well as the Epiphany browser. All those methods resulted in no difference; nothing happened. I was in contact to a friend on Windows and also staff at the Archive, both telling me that from Windows it worked, including with Firefox. So now I knew the archive works and that it works on Firefox. So I thought, can this somehow be related to Linux? I asked in a Linux forum if someone on Linux could test to download. One person in the forum tested and solved the problem. I would not define it as a Linux problem, but a site design that affected Linux users. The trouble was something I had not thought of: The User Agent. When my browser contact a web site, my browser can tell the site what kind of browser I use, which operating system I use and more. This information can be used by the site to optimize the presentation of the content for me. For to me unknown reason, maybe a mistake, maybe related to some old design compatibility issue, this site did not accept the information my user agent provided. The solution is to tell the web site I am something else. In the browser has Developer tools. When opening the developer tools from meny, typically a developer window with tools and analytics is opened at the bottom part of the web page. One tool is network. Within network I can simulate how the site looks on different devices, with different network connections and also with different User Agents. The tools are similar in both Firefox and Chromium. The exact list of standard options differ and Chromium has more options preloaded. In this specific case, when I in Developer tools on Firefox change User Agent to Chrome Desktop, which relates to Chrome on Windows as I understand, and then reload the web page I can now download the pdf file from the archive. When this web site interpret me to be this other type of user, they can understand each other without any issue. I have reported back to the site owner and hopefully this specific site will not need this work around for the browser User Agent in the future.Provide feedback on this episode.
    --------  
  • HPR4515: Privacy? I don't have anything to hide...
    This show has been flagged as Clean by the host. Hello, this is your host, Archer72 for Hacker Public Radio In this episode, what do you have to hide? This topic was brought to my attention when I came across this video from The Hated One . This youtube host is extremely privacy focused, and has interesting opinions on not only US privacy and security topics, but also internationally. This particular video was regarding locking down the settings on Firefox. The claim besides increasing security is to lower bandwidth and memory usage and double rendering speeds. While a lot of these steps the author took seemed excessive, they might help you. I use a few of these settings as a takeaway to this video, as well as an extension that I find very useful. The author is correct in saying that our browsing habits track a lot about your personal life, so here are a few steps that I did follow. First, I selected Strict Blocking under Content Blocking about:preferences#privacy Strict blocking Firefox setting Next, I did not set my history settings to Use custom settings for History and Always use private browsing mode , this is maybe useful for some. Under Address Bar I left everything unchecked, besides Search Engines Firefox address bar settings Next, check the box in Ublock origin settings enable Advance User settings to enable more granular control. Ublock Origin settings Ublock Origin granular control Now, change the default behavior of Ublock origin to Block media elements Block remote fonts Disable JavaScript By checking the boxes for these items Transcript: How to configure Firefox settings for maximum privacy and security Provide feedback on this episode.
    --------  
  • HPR4514: YouTube Subscriptions 2025 #9
    This show has been flagged as Clean by the host. I am subscribed to a number of YouTube channels, and I am sharing them with you. Links: https://www.youtube.com/@NASA360 https://www.youtube.com/@NASAedge https://www.youtube.com/@NASAGoddard https://www.youtube.com/@NASAJPL https://www.youtube.com/@ReelNASA https://www.youtube.com/@NASAXrocks https://www.youtube.com/@NatureVideoChannel https://www.youtube.com/@NixiePixel https://www.youtube.com/@Normul8or https://www.youtube.com/@norwegiancruiseline https://www.youtube.com/@NotesinSpanishofficial https://www.youtube.com/@ObjectivityVideos https://www.youtube.com/@OLFConference https://www.youtube.com/@ourfakehistory2211 https://www.palain.com/ Provide feedback on this episode.
    --------  
  • HPR4513: Living the Tux Life Episode 2 - Ventoy
    This show has been flagged as Clean by the host. Living the Tux Life Episode 2 Show notes Things i mention in the show Ventoy Setting up Hibernation in Linux Mint Sleep Modes in Linux Guake Termainl Diodon Provide feedback on this episode.
    --------  

Flere Uddannelse podcasts

Om Hacker Public Radio

Hacker Public Radio is an podcast that releases shows every weekday Monday through Friday. Our shows are produced by the community (you) and can be on any topic that are of interest to hackers and hobbyists.
Podcast-websted

Lyt til Hacker Public Radio, De tre Principper med Stærk & Donkin og mange andre podcasts fra hele verden med radio.dk-appen

Hent den gratis radio.dk-app

  • Bogmærke stationer og podcasts
  • Stream via Wi-Fi eller Bluetooth
  • Understøtter Carplay & Android Auto
  • Mange andre app-funktioner
Social
v8.0.1 | © 2007-2025 radio.de GmbH
Generated: 11/25/2025 - 8:30:32 AM