My apologies. You're correct. The Homeflasher does not appear to work the ESP32s3. The good news is, the HomeFlasher did not permanently 'Brick' you display. I can offer 2 options: 1. Install VS code & flash your display from the source code. (its really not that hard, but can take some time to install, & compile; especially the 1st time) 2. Direct flash your display, by following the revised README.md & notes.txt instructions, found at the GitHub Repository. Method 2 should/will work, but the instructions may involve additional steps, as they assume that Python 3.8 or later has been installed Please let me know which method you used, and how it worked Tnx & GL, Jim(KW4KD)

My apologies. I agree, the Homeflasher does not appear to work the ESP32s3. The good news is, it didn't permanently 'Brick' the display. I can offer 2 options: 1. Install VS code & flash your display from the source code. (its not that hard, but can take some time to install, & compile; especially the 1st time) 2. Direct flash your display, by following the revised README.md & notes.txt instructions, found at the GitHub Repository. Method 2 should/will work, but the instructions may involve additional steps, as they assume that Python 3.8 or later has been installed on you computer. Please let me know which method you used, and how it worked Tnx & GL, Jim(KW4KD)

The video is nearly 5 years old. If you had seen it, when it was first was released, they were shorter then.

Cool 🙂. The Github site should get you going. But to be honest, the external interface details are light. Especially an interface with your TX. I just used some standard Ebay Arduino building blocks. Contact me via QRZ if I can help. Tnx Jim(KW4KD)

Well Thank You. Appreciate the endorsement. And maybe more important great to see/hear that you're building stuff. GL, Jim(KW4KD)

Appreciate the update.

Fair question, but not really. I no longer use Windows. But did google the two software apps, and they both seem to still lead to active websites. So suspect, while the apps may be upgraded, the basic idea should still work. Give it a try, and let the rest of the community know how it works out.

Hi Pino Thanks for your interest & question. If you follow the process outlined in the 1st video kzbin.info/www/bejne/fpOcnmlmgdmGgNk ,@~the 5 minute mark, the directory references will automatically get corrected to match your local directory structure. The project was originally built on a Linux machine. But today I cloned it, on a Windows 10 machine, (with a totally different directory layout) Also, the process now is even more automatic, than when the referenced video was done. I found as the install process moved along, some error messages appeared, but I just followed the prompts, and they all resolved themselves. BTW, If you're really not that interested in source code, the much faster way to get going is to flash the .bin file to your ESP32. The GitHub site has links to the bin file, and the flash loader. GL & let me know how it works out for you. tnx, Jim(KW4KD) PS: The decoder section is still a work in progress. I at some point I hope to do another video explaining further whats going on under the hood. The general goal is to have a decoder that operates with as little intervention as possible. And final point, the decoder supposedly is optimized for "rag chew" QSO's

@@jmhrvy1947 Thanks Jim for your answer.... now I am going to listen to your video. I am a Linux user and I would like to modify your project to adapt it to my needs...i.e. to make it send decoded chars via Wi-Fi to my PC where I have a GAMBAS3 program that displays chars and also sends code to an IC-7300 via CAT. At present I have a simple Arduino program that sends chars via USB serial connection, but it is quite slow and not so precise. I lack experience with Code and PlatformIO....it seems to me too complex 😞 Best 73 Pino ZP4KFX

"....it seems to me too complex@@pinox61" QSL that. But what I like is how well it (VsCode/PlatformIO) works with a github project. Ideally you will have to do a minimal amount of configuration to get this project up and going (in its current form). Now the changes your proposing sound fairly complex. The unit/project, as it stands, is designed to just plug directly into your 7300's key input, and does wireless keying that way. To be honest, unless there's distance issue, it would seem that linking your blue-tooth keyboard directly your computer would be a quicker/simpler solution. But I probably don't appreciate what all your doing there. Bottom line, good luck, and again, thank you, for taking an interest in the work that's going on here. Jim(KW4KD)

Steve, Appreciate your interest in the project. And I hope you'll see it through to completion. I know these display's look similar. But this project is built around a 480x320 display. Not a 320x240. The 480x320 allows for 16 lines, @40 characters/line, and 12 horizontal pixels/character. There a similar issue in the vertical direction, with the character height set at 20 pixels. In an earlier iteration of this project I did support both screen resolutions. And you can see evidence of that, in the TFTMsgBox.h file. There, if you comment out line 14, #define HiRes, this part of the code will try to accommodate the lower res screen. But today, that's only a fraction of code, and all the rest of the project makes no allowance, for change in the pixel count. You're welcomed to change the code any way you want, but if your main objective is learning CW, then time wise, I recommend getting the ILI9488 SPI display. That said, I congratulate you for getting as far into the project, as you apparently have. Other things to emphasize: 1. While most any generic Bluetooth keyboard will work, the project is really designed around the Logitech K380. So for the best user experience, that's the one to have. 2. The project is still in active development. So please check the github site regularly (last update was 2 days ago) Again, thanks for the comment, & congrats on your hard work. Jim(KW4KD)

Thanks for the comment. If you're interested in the decoder part. I hope you'll revisit the github site (next week). Should have an update in place that's an improvement over what's shown in this video Jim(KW4KD)

Thanks for the question. If I follow it, there are 5 memories, "F1" through "F5", on it now. Its possible to add more, by following that code. "F1" is intended (setup) to store the call of the station your talking to. And there's a 6th memory for your call (accessed through the "Settings" screen, & sent using the "enter" key). The others are intended for simple "canned" messages. Like "CQ". In my mind, the project is targeted for "ragchew" QSO's, over contesting. So it doesn't have an auto-indexing number memory. Hope that helps. Jim(KW4KD)

Thanks will explore making this as a contest keyer .. similar to Arduino based contest keyers.

If you build one, would appreciate any feedback you care to share about your experience. @@elmanish

QSL calling CQ, and having a speed demon return the call. That's not supposed to be how it works. But like to think, if the decoder can't copy the returning station, there's no embarrassment in saying, "TU for the call & hope to catch you next time, when conditions are better". The hobby needs more folks calling slow CQs. As for the ESP32, I too ignored it for a long time. (seemed like overkill for most of my projects) But being able to host bluetooth and running RTOS, seemed like a good fit for combining the two sides of Morse code. That (combining the two) proved to be a bigger challenge than expected. Took me several months to get the two play nice, on a single ESP. The problem is how to get usable crash reports (from code you didn't write). But that's another video. Thanks for the comment & hope to hear you calling CQ soon. Jim(KW4KD)

Thanks for the comment. Especially appreciate the point, "the advantage of building something from scratch: you know every bit of it". I'll amplify that & say, "HB gear comes with an unlimited warranty & at home repair service." Hope things settle down long enough for you to see your project on the air. Jim(KW4KD)

Thanks Tom think maybe you're the 1st one to recognize that side of the project. Jim(KW4KD)

Dick, Really appreciate your endorsement. As said earlier, w/o your input, the project wouldn't be what it is. What I fear is missed in the video is just how much bang for the buck (or fun) can be had with this lil unit. Jim(KW4KD)

Thank you for your comments. I just watched your video "Stand alone SDR radio by S52UV". And especially enjoyed your description of the parts selected, and what the software was doing. My "take away" (and this true for for all computer based solutions) is there is more than one way to get the job done. I wish you success with the ESP32-A1S. Just subscribed to your channel. But please drop me a line when you post any progress related to that effort. GL, Jim(KW4KD)

Good Question. But No. Its CW only. Adapting it to do RTTY would be possible, if it had the program space. But the Blue Pill version does not. FT8 is a time synced encoding protocol. This setup has no geo-synced clock. So that's off the table too. Thank you for asking Jim(KW4KD)

Congratulations.. Nice Job and thank you for the comment. Given what you have done, this is what I would suggest you do. In the BluePill_CWdecoderW_ToneDetect.ino file, look at line 346. It should read, "#define ARSIZE 43". Change 43 to 44 Next, at line 390, which now reads "85" change it to "85," and then insert a new line after it, and enter the value "106" In the table/array "DicTbl1", at now line 438 and reads, " "." " . Change it to " ".", " And last change, insert a new line that reads " ";" " recompile and load your modified sketch to the bluepill. It should now decode "-.-.-." as ";" The binary value of decimal 106 is 1101010. The first "1" is a marker, or place holder, and the following 1's and 0's represent the dash dot pattern sent as morse code for the character. Now you have the power to add/decode any characters you like. Good Luck, Jim(KW4KD)

Merci pour votre réponse rapide. Je suis en train d'étudier pour passer le certificat de radioamateur. Je vous souhaite une bonne continuation. 73s de Jean-Louis-14FRS3818@@jmhrvy1947

Rebonjour, je viens d’effectuer la modification pour ajouter le caractère " ; " , et cela fonctionne correctement...Je vous remercie vivement pour votre aide et pour votre décodeur qui fonctionne à merveille...73s de Jean-Louis 14FRS3818

That is terrific. Was fearful, that the quotation marks would make the instructions too confusing to follow. Good luck with your studies for the exam. Its a great hobby. One which you can go in many directions. My personal favorite is building the hardware you use. Just worked Japan this morning with a 50 watt home brew station. At 76, that still puts a grin on my face. But so does reading that folks like yourself are looking at getting into the hobby 73, Jim(KW4KD)@@jean-louisrico-moulins3304

Appreciate your interest. The short answer is, no. There are no formal wiring diagrams; However, the "sketches" (found at the link in the intro description) are commented. And explain which pins are used, and what they do. As for powering up the processors, its your call. If you want to go deeper into CW, I have some other video projects that describe more advance decoder(s) and keyboard based senders. These do have wiring diagrams Tnx es GL Jim(KW4KD)

@jmhrvy1947 thank you. I guess I will need to Google the pinout for my bug connector, and go from there. I have several Uno and Nano boards I have used for various projects. This will be fun!

Thanks for the comment. To your question, what I settled on, was attaching a pulley to one end of a steel cable (~ 18" to 2 ft in length. i.e., Long enough go around the limb I wanted to use as the attach point) and an "S" hook on the other end cable, To the pulley I looped parachute cord long enough to go from the ground to the limb. And attached the messenger line to the "S" hook. That way I could pull the cable over the limb. And by having tension on both ends of the cable could hook the "S" hook back on the pulley side of the cable. Once the "S' hook was in place, it basically made a "slip" knot/noose that the harder the pull on the pulley, the tighter the cable gripped the limb. The pulley allows me to raise an lower the antenna (an inverted"V") at will. Happily the setup is still working today.

@@jmhrvy1947 just what I was wondering about. The pulley is also a great idea!

Andreas, First, let me say thanks for all your videos. All informative, and all well done. Hope there're many more to come. Your correct, as a programmer, staying "main stream" is generally the path to take. There was a lot, in this project, that the video didn't cover. One, was the display library. Its in fact, an Arduino library. To make it work in the ESPIDF, a number of Arduino IDE core files were also ported. So "Arduino fans" will find commands like "delay()" will work here too. My belief is users will have the advantage of both worlds. As for implementing this project, using an "off the shelf" board, that's a great concept. On the flip side, the project repository includes the Gerber package needed to order the board from JLCPCB. Here in the US, I bought 10, for $5, plus postage. Beyond that, project concepts can readily be confirmed using just Dupont jumpers. Think 7 are needed to connect the display to the ESP32. So for those building just one, jumpers will work fine. But for a "group build" I'd recommend going the JLCPCB route. Thanks for the opportunity to cover some points missed in the video... 73, Jim(KW4KD)

@@jmhrvy1947 Indeed, JLCPCB offers a good service. We even use their assembly service for our projects. It is cheap and you can use smaller parts as well as ICs that can not be hand soldered. And it is a cool feeling when you get a professionally looking PCB of your own design…

Hello,I didn't find it meaningful. Morse code is not used today. What will work for us?

Appreciate the comment. And yes, both the schematics & gerber files are out there (at least they should be; contact me if you don't find them). So the boards can be had through places like JLCPCB. IMO, in spite of its simplicity, its a remarkable CW transceiver, and fun operate. again tnx for checking it out. Jim(KW4KD)

Ryszard, I'm impressed you got as far as you did. For the Blue Pill version, you're correct the STM32_TouchScreen_Calibr_native was corrupt. I've updated the github repository with new calibrate & decoder files (for the blue pill). I don't own a display with an ID=0x1581, so can't confirm that 'out of the box' these new files wont have an issue with your display. But given that your display worked with the clock demo, there's every reason to believe they can be made to work with it. Please download them & check out the "readme" note found in the 'arduino' folder. Finally, if you have a connection with QRZ.com, & if needed, please Email me directly. Want to see you get your decoder up and going GL, Jim(KW4KD)

@@jmhrvy1947 tnx :) Jim everything is fine now.

Thanks for taking to time to report that this method is still viable. It takes a number steps to get it done. But the software is free. This time of the year some might find it helpful for cutting Xmas figures that they have drawings for.

No, I'm sorry. That code is long gone. Doubt that it would compile today, since most all the libraries it used have had many updates of their own. FWIW, the code used here formed the core, of the balance bot videos, that followed. That code is out there. But again, wouldn't bet on it compiling, without 1st having to do a number of "tweaks" to get it to work with today's libraries. Thanks for your interest in the project, and taking the time to ask the question.

First & foremost, always appreciate folks taking the time to share their experiences. My guess as to why the code failed to work today, on a different MPU. 1. Parts of it were written specifically for the atmega32U4. and 2. The code , now 8 years old,. is trying to link to libraries that have, in all likely hood, been revised a number of times since then. All too often a revised library isn't backwards compatible. Rendering code that once compiled and ran fine, useless. Not complaining. Its just the way it is

@@jmhrvy1947 Then I think I must learn a lot about programming and try to build my own library the best I can. Thanks soooo much for your reply.

Thanks... If time permits, please check out the other 2 videos, in this series. Jim(KW4KD)

Thanks Guy... Just glad to know you're still "out there"

Thanks Tom. Appreciate the encouragement. To your question about opposite sideband. I did.... Tried, this morning, to pull the plots back up but couldn't find them. Bottom line, it depends on which filter is selected. My favorite is the middle filter (with 97 taps, a theoretical BW of 2000Hz, and shifted 750Hz) . It will let some of the opposite side spill in. But for "normal" band conditions (and congestion) I like it. Its not a "brick wall", so it will "hear" really loud signals fairly distant from the "tuned" frequency. Don't know how that would be for true SSB work. But for CW, & for me, it puts the signal I'm listening to "front & center", while still providing "situational" awareness of what's going nearby. The Narrow filter, with 195 taps, is useful, when the QRN is high, or the signal is weak. But pushes the interrupt timing envelope, which can cause 'clicks' in the audio. For less than optimal conditions the "clicks" are often less annoying than the constant QRN. So each filter has its place. Sorry for not providing more of an analytical answer.

Andy, Many thanks for your interest in the project. Its been through a couple iterations since the vid was posted. Today, I use a black pill (STM32F411). A faster processor, with more programming space. Build info for the F411 version is also available on Github. Several months back another viewer asked the same question. And I agreed to build one. That unit went to Canada. Shipping costs turned out to being more than twice the price of the unit. Bottom line, the experience was a big disappointment for both of us. On the flip side, the feedback from those who have built the unit themselves, has been favorable. I posted the project, thinking that it would/could be a Father/Son project. (Or some other pairing.) Often the younger members of our world know way more about Arduino like processors than we do, but never thought (or heard) of ham radio/CW. Maybe there's a young person near you, that you can team up with, and make this project a reality. If you all get into it, and need more info, please contact me (QRZ.com is a good way to go ) Tnx & GL, Jim(KW4KD)

@@jmhrvy1947 Thank you sir. i just ordered 6.with me luck lol.ttyl

Agree. That higher clock speed would allow you to "see" a bigger picture of whats in the "Neighborhood" . The Sound board is capable of sample rates of >96Khz. But, with the F411 @ <100Mhz, had to run it at 48Khz. Thanks for the comment & interest in the project. Jim(KW4KD)

I doubt it, as the orientation does not impact the build dimensions. But as mentioned in the video, spacing was changed to allow for vertical mounting.