wiki.millerjs.org

User Tools

Site Tools

yaesufc-40control

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
yaesufc-40control [2026/07/18 05:23] – [The Test Sketch] adminyaesufc-40control [2026/07/18 05:32] (current) – [Photos & Media] admin
Line 155: Line 155:
   * Lets you send commands from the Arduino IDE Serial Monitor: wakeup, the full init sequence, individual ''E0''/''F0''/''F1''/''F2'' commands (with frequency in MHz, auto-converted to BCD), and arbitrary raw hex bytes.   * Lets you send commands from the Arduino IDE Serial Monitor: wakeup, the full init sequence, individual ''E0''/''F0''/''F1''/''F2'' commands (with frequency in MHz, auto-converted to BCD), and arbitrary raw hex bytes.
   * Frames commands correctly, with the ~50 ms wake gap after ''0xFF''.   * Frames commands correctly, with the ~50 ms wake gap after ''0xFF''.
-  * Detects "success by silence" - if an ''A1'' arrives and ~250 ms pass with no trailing ''A2''/''B0'', it declares the tune matched, and drives status LEDs (D13 success, D12 fail). +  * Detects "success by silence" - if an ''A1'' arrives and ~250 ms pass with no trailing ''A2''/''B0'', it declares the tune matched, and drives status LEDs (D13 success, D12 fail, though realistically these are kind of guesses). 
-  * Collapses rapid RFI bursts into a single suppressed-count line so real, well-spaced bytes remain visible. +  * Collapses rapid RFI bursts into a single suppressed-count line so real, well-spaced bytes remain visible - though this is kind of tricky because bad enough RFI will either crash the Arduino, or reset the USB interface. 
-  * Loudly flags any unrecognized byte, so new response variants can't hide.+  * Loudly flags any unrecognized byte, so new response variants can't hide. I'll update this page as I find more.
  
 ==== What it does NOT do (yet) ==== ==== What it does NOT do (yet) ====
  
-  * **It is not a controller.** It cannot key your radio - you supply the carrier by hand (or with a separate PTT arrangement). The commanded sequence is issued by you, timed against the carrier you're holding. +  * **It is not a controller.** It cannot key your radio - you supply the carrier by hand (or with a separate PTT arrangement). The commanded sequence is issued by you, timed against the carrier you're holding. I've just got a morse key next to my keyboard. 
-  * **It does not trust its own success/fail output under RFI.** The noise filter improves readability but does not make the line reliable; a stray byte in a quiet gap can still mis-decode. +  * **It does not trust its own success/fail output under RFI.** The noise filter improves readability but does not make the line reliable; a stray byte in a quiet gap can still mis-decode, and RFI can crash it out easily. 
-  * **The response-code interpretation is provisional.** ''A2''=fail and ''B0''=no-carrier are well-supported; ''A4''/''A8''/''E4'' are guesses awaiting clean data. +  * **The response-code interpretation is provisional.** ''A2''=fail and ''B0''=no-carrier are well-supported and have been consistent; ''A4''/''A8''/''E4'' are guesses and have been a lot harder to get consistently. 
-  * **No memory / recall logic, no E0 handshake automation** beyond a bare ''init'' command for experimentation.+  * **No memory / recall logic, no E0 handshake automation** beyond a bare ''init'' command for experimentation. I plan eventually test this, but I may just end up running this tuner as a "dumb" remote ATU where it regularly has to do a full cycle anyway. We'll see how things end up. 
   * It is a **bench diagnostic tool**, full stop. It is not fit for unattended or production use.   * It is a **bench diagnostic tool**, full stop. It is not fit for unattended or production use.
  
 +==== Honesty Moment ====
 +I did use generative AI to help me with this sketch. I'm not super great at putting this kind of stuff together in a clean fashion. Between the work of those before me, and banging my head on the keyboard, I was able to get sequences that worked, and got the tuner doing what it needed to do. Once I got that far, I used Anthropic's opus to clean it up. 
 +
 +If you don't like that, I understand, and you should be able to use the above descriptions and resources to write your own methods. 
 ==== Code ==== ==== Code ====
  
Line 183: Line 187:
  *  *
  * Acknowledgement: builds on the reverse-engineering of the Yaesu tuner  * Acknowledgement: builds on the reverse-engineering of the Yaesu tuner
- * control protocol published by John Price (WA2FZW), and on the anonymous+ * control protocol published by John Price (WA2FZW), and Albin Stigo's (SM6WJM) 
  * FC-30 reverse-engineering notes. Thanks for sharing openly.  * FC-30 reverse-engineering notes. Thanks for sharing openly.
  *  *
Line 451: Line 455:
   * Investigate the MONITOR / PC port.   * Investigate the MONITOR / PC port.
  
-===== Photos =====+===== Photos & Media ===== 
 + 
 +  * {{ :yaesu:fc40:fc_40_antenna_tuner_manual_en_35bf.pdf}} 
 +  * {{ :yaesu:fc40:fc-40_brochure.pdf}}
  
-{{gallery>:yaesu:fc40:photos}}+{{gallery>:yaesu:fc40}}
  
yaesufc-40control.1784352214.txt.gz · Last modified: by admin
Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki