<![CDATA[Profiles for VoiceAttack & other projects]]>https://veterans-gaming.com/blogs/blog/8-profiles-for-voiceattack-other-projects/ Personal blog including Advanced Voice Control Systems profiles for VoiceAttack, and other projects.

]]>enDIY - External Temperature and Humidity Sensor - AVCS-DHT1 Build Guidehttps://veterans-gaming.com/blogs/entry/45-diy-external-temperature-and-humidity-sensor-avcs-dht1-build-guide/
  1. Preparing the Sensor
  2. Preparing the Case
  3. Preparing the Arduino
  4. Final Assembly
  5. Uploading the Code

  Get Help & Support

image.png

I have written a new voice control profile called 'AVCS SENS' for VoiceAttack specifically dealing with sensors and weather commands.  I wanted to use the Shared Memory feature of the AIDA64 Extreme sensor monitoring program to enable my VoiceAttack profile to speak the requested computer sensor value when asked over text-to-speech.

Once I had sensor values from AIDA64 Extreme in VoiceAttack, I then added a DHT11 Temperature & Humidity sensor to the Arduino Uno on my prototype breadboard, connected to my PC through USB.  Now reading this as well from my VoiceAttack profile, I could do a little math to get a more absolute and objective value from the computer sensors, a CPU temperature in "degrees over ambient", for example, or "delta-T over ambient" as you may hear it called in analysis videos such as this one here talking about case testing methodology used by Gamers Nexus.  This is the true means to understand what computer sensors for temperature are reporting at any given time, by first accounting for the temperature of the room.

Finally, with this relative sensor data now available, I've been able to write a simple diagnostic algorithm which can identify & flag atypical sensor values, as compared to stored baseline values on file, for voice commands in VoiceAttack.  Without an AVCS-DHT1, outdoor weather and sensor report commands are still available, yet indoor weather & sensor diagnostic commands will be unavailable.  I wanted to make it possible for anyone using my new AVCS SENS profile for VoiceAttack to either be able build their own AVCS-DHT1 USB external temperature & humidity sensor,
or buy one designed & built by me, according to this simple Arduino project build guide, and therefore unlock these additional voice command features for AVCS SENS.
 

My DIY USB Temperature & Humidity Sensor 'AVCS-DHT1' - for use in my AVCS Voice Sensors & Weather Profile
parts list below contains links to specific items which I directly purchased myself for this project on Amazon only, but any store will do, and also any equivalent part which performs the same will work (brand names/quantities do not matter!)
if you are using a different case than the exact one linked below, or other components, please see the note in the AVCS SENS Wiki page regarding Sensor Calibration
 

image.png

Project Required Parts List                                                    
(all prices listed in USD - price and availability may be different past last publish date of this guide)
 

Arduino Nano (or equivalent clone) - with NO header pins soldered on!
(HiLetgo Nano v3.0 5V) (3 pack)  -  $24.49
https://www.amazon.com/dp/B01DLIJQA2
$8.16 per board

USB Cable - USB 2.0 Type A to Mini-B (3ft. or 1 meter, at least)  (or equivalent part)
(iSeekerKit Nylon Braided 3ft.) (3 pack)  -  $8.99
https://www.amazon.com/dp/B08LL272SK
$3.00 per cable

DHT11 Temperature Humidity Sensor Module 3.3V-5V (or DHT22, or equivalent part)
(HiLetgo w/Dupont Wires) (5 pack)  -  $10.29
https://www.amazon.com/dp/B01DKC2GQ0
$2.06 per sensor

Plastic Electronics Project Case @ 1.97" x 1.10" x 0.59" (50mm x 28mm x 15mm)
(Zulkit ABS Project Boxes) (5 pack)  -  $7.99
https://www.amazon.com/dp/B07PZ24LFD
$1.60 per item

Metal Film Fixed Resistor 10K ohm (0.5Watt) - just one will be needed
(EDGELEC Pack of Resistors) (100 pack)  -  $5.99
https://www.amazon.com/dp/B07QJB31M7
$0.06 per resistor

Strong Double-Sided Foam Adhesive Tape (or equivalent product) - only need a few inches
(Gorilla Brand Heavy Duty Mounting Tape) (1" x 120" roll)  -  $11.34
https://www.amazon.com/dp/B082TQ3KB5
$0.20 approx. amount used

Neodymium Magnet 8mm x 2mm (round, size is important!) - just one will be needed
(FINDMAG Box of Magnets) (100 pack)  -  $9.99
https://www.amazon.com/dp/B09BB1VT4J
$0.10 per magnet

Total:
$15.18 (USD)  (for 1 sensor*) - (total if all parts purchased with amounts above:  $79.08)
*(also required - drill/rotary tool, solder and soldering iron, electrical tape, tweezers, scissors, 'nippers', 'spudger' type tool, and SuperGlue)

This project requires the following skills & knowledge:

  • Basic understanding of Arduino (what it is/what it does)
  • Basic experience with electrical soldering
  • Basic skills with drill or Dremel/rotary tool and bits
  • Use of and precautions relating to SuperGlue type adhesive
  • Ability to make precise cuts with scissors within 1-2mm
  • Ability to carefully follow instructions (some are crucial)
  • Entry level experience with VoiceAttack (import profile, etc.)
  • Ability to work w/ tiny parts in a small space in timely manner
  • A positive attitude and willingness to adapt and overcome (not exactly required, but always recommended ;) )
     

Part 1 - Preparing the Sensor                                              

image.png

preparing the DHT sensor and stripping the braided wires - image a1

1. Separate the DHT11 (or DHT22) from the breakout board it is mounted on (if not supplied without one).  Either snip the wires from the DHT as close to the board as possible with "nippers" (image a1), or de-solder them from the breakout board.  If supplied with the Dupont ribbon wires, remove the plastic ends and prepare the wire ends by cutting them even and strip the wires leaving at least 1.5cm bare.  We want around 75-100mm (2.95-3.93") of flexible braided wire so we can zig-zag the excess, allowing us to remove the plastic lid with sensor and not risk yanking the soldered wires out.

image.png

solder wire ends - image a2

2. Twist the wire ends and tint them with solder to make them stiff, yet not so much as to increase their width with too much solder & slag - three of them must fit through the holes on the Arduino.

 

 

3. Once the DHT has been separated from the breakout board, with the side with holes facing you and pins down, cut the third pin from the left, or second from the right, as in image a1.

image.png

gently bending the pins, resistor legs, and wires - image a4

4. Prepare the DHT pins by gently curving them into hooks facing away from the side of the sensor with holes.  Gently bend the legs of the 10K ohm resistor (as shown in image a4) so that it will sit in the hooks of the two DHT pins closest together, as seen with the sensor face down (holes down, as in image a5).

 

image.png

resistor placement - image a5

5. Bend two of the three wire ends away laterally away from the third wire, into a gentle hook shape, and the third wire opposite those in the same manner. Lay the 10K ohm resistor into the right two wire-hooks of the DHT sensor (face down - image a5).

image.png

 final goal for the resistor, legs, and wires: flat & straight - image a3


NOTE: The Resistor should be offset in a manner where its bulk and width can mostly lay flat along side the wires and not on top of them once completed (image a3).

 

 

image.png

gently crimping the DHT pins around resistor legs & wires - image a6

6. Lay the wire "hooks" into their corresponding DHT wire "hooks" over the resistor, and if able, use a tweezers to gently compress these DHT wire hooks to contain the wires and resistor for soldering, as well as the wire "hooks" themselves.  If this is not possible, you may want to secure the DHT to the table with scotch tape, lay the three wires in place in their "hooks", and scotch tape down the wires to the table with a gentle pull, to ensure they remain in place while soldering them firmly in place as one connection. 

 

image.png

soldering to the DHT - image a7

7. Solder each connection so that the wire, the wire "hook" from the DHT, and the resistor are fully encased, and not touching each other.

image.png

trimming legs from resistor, and any protruding slag - image a8

8. When cooled, use "nippers" to nip any protruding slag or wire ends, and the trailing legs of the resistor as it exits the solder as in image a8.  The wires should travel flat following the rear plane of the sensor, so that later, the front face of the sensor (with holes) can protrude out of a hole we will cut in the case lid.  Refer to images a3 and a8 to see the resistor in-line with wires, as an example.

image.png

wrap wires separately - image a9

9. Finally, wrap each exposed solder point with a separate small piece of electrical tape to ensure each cannot bridge contact with another in the event that something gets bent.  Just sandwiching a small rectangle of tape over each one will do, even if each has a tail of tape hanging off.  These bits of tape will be covered and held in place permanently once the sensor is mounted into the lid later.

 

 

SAFETY SAVES LIVES - SAFETY GOGGLES SAVE EYES!  BE SMART AND USE APPROPRIATE SAFETY GEAR WHILE WORKING!

 

Part 2 - Preparing the Case                                                  

Step-8a-1.png

drill 12 tiny air holes - image b1

1. Carefully remove the lid from the case - while holding the base in one hand, lid up, with the notch in the lid away from you, use a fingernail in the notch along with pressure from your finger to pry that side of the lid upwards.  If using a tool, be careful not to use too much pressure or the soft ABS plastic may deform or scratch if the tool jumps too fast once the lid becomes free.

image.png

keep notch at bottom - image b2

2. For the lid, we want to create a rectangular hole that will allow the front face of the DHT sensor to protrude.  The tapered sides of the blue sensor case widen towards its back which will keep it from protruding farther.  The lid is 25.9mm wide & 47.75mm tall.  The approximate width of the hole will be at or under 16mm tall and 12.60mm wide.  For this to work well, it is best to cut a slightly smaller hole than desired and slowly widen it with hand tools or low speed rotary tool - stopping and testing the fit until just right (as shown in image b6 below).  It is not easy to get exact, I've tried.  Just accept any slight tilt, it is a DIY after all.

image.pngport is upside down - image b3

The goal for the USB hole is to make it flush with the bottom of the case as it exits, and as wide as the USB port itself (8mm).  The port is 4mm tall, but as you can see in image b3, even I could not quite keep that height with that limit as I drilled and widened the hole.  Again, stop and check the fit - first dusting out any bits of plastic from the process, and sliding the Arduino Nano upside down as shown for a test fit.  It must slide flat with the case bottom and through the case wall as shown.

 

3. With the lid removed from the base, use a drill bit between 1mm-2mm at low speed to create 4 holes in the 'top', and 4 holes on each side near the top (as shown in image b1), for 12 total air holes.  The passthrough hole for the USB mini-B port will require drilling and widening with hand tools or a rotary tool at a low speed.  The port is about 4mm tall & 8mm wide.  High speeds may heat and melt the ABS plastic, so if you are working at an area for too long, back off and let it cool down.
 

image.png

place one small drop of SuperGlue at the arrow for magnet - image b4

4. Once all the holes are drilled and the rough edges cleaned up as much as possible, wipe the interior clean of plastic dust.  Using a strong SuperGlue, place a very small drop inside the case at the top near the four holes you drilled, as shown by the arrow in image b4.  Carefully place the tiny magnet over the drop of glue; non-magnetic tip tweezers or even chopsticks can really help - just be sure not to touch the SuperGlue as you position the magnet.

image.png

 test fit the sensor into lid - image b6

 

5. Finally, cut a strip of the double-sided adhesive foam tape about 25mm wide and 8mm tall - do not remove the backing yet!  Once the SuperGlue has dried (give it a few minutes) place the strip of tape over the magnet (image b5, below).

 

image.png

fully cover magnet with tape, do not remove backing (yet) - image b5

Part 3 - Preparing the Arduino                                           

image.png

setting the board to "Arduino Nano" and its COM Port - image c1

1. Open the Arduino IDE v1.8 (latest) (download and install first, if not already done) and make sure it is updated to current release version.  Place the Arduino Nano on a hard, non-conductive surface, and connect the USB cable to the device and then to the PC.  Refer to device instructions (per brand/model/type) as required, if the device driver is not installed automatically.  Under the 'Tools' Menu along the top, select the COM Port of this device, and set the board to Arduino Nano (as shown in image c1), and unless directed by device instructions, leave the Processor as "ATmega328P".

image.png

opening and uploading the Arduino Basics "Blink" sketch - image c2

2. Under the 'File' Menu along the top, select Examples > Basics > Blink to open this sketch (see image c2).  Next, click the Upload button ( image.png ) to send this sketch to the Arduino Nano.  Verify that the onboard LED slowly blinks on and off repeatedly to ensure this board is functioning, and that sketches are uploading properly.  If you have any problems at this stage, you will want to stop and perform other troubleshooting steps to verify that the Arduino IDE is set up properly to communicate with this board, and that the board itself is not faulty.  See Addendum at the bottom of this guide for help.

 

 

image.png

installing or updating the "Adafruit Unified Sensor" library - image c3

3. To get data from the DHT sensor, we will be using an open source DHT Sensor Library by Adafruit, which requires the Adafruit Unified Sensor Library, as well.  In the Arduino IDE, under the 'Tools' Menu, select 'Manage Libraries...' (or press CTRL+i) to open this window - it takes a few seconds to open.  First, select the Type of "All" (if not already selected), and the Topic of "Sensors".  In the search field, type "Adafruit Unified Sensor".  The list will be long, scroll down until you find the Adafruit Unified Sensor library (as pictured in image c3) - install it or update with the latest version, if not already.

image.png

installing or updating the Adafruit "DHT sensor library" - image c4

4. Next, in that same search field, type "DHT sensor library".  Again, the list will be long, scroll down until you find the item with the title "DHT sensor library" by Adafruit (as pictured in image c4) - again, install or update it if it is not installed with the latest version.

When you are finished, close the Library Manager and disconnect the Arduino from the computer.

If desired, use a light grit sandpaper on the edges of the Arduino Nano PCB board to make them smooth.

image.png

 AVCS-DHT1 Wiring Diagram (your resistor color may be different!)  -  image c5

5. Once you have verified that the Blink sketch is working from earlier steps, and that the Arduino IDE can properly upload to the Arduino Nano board, it's time to solder the wires from the DHT sensor to the Arduino.  Follow the wiring diagram (shown in image c5), separating the ribbon cable to individual wires for flexibility, as needed.

 

image.png

later, mounting will be upside down, as shown here - image c6

NOTE:  As stated before, the Arduino Nano MUST be upside down (shown in image c6) in the end.  You may wish to do as I have done, and push the wires through from the other (top) side of the board, soldering them into place on the underside (now facing up, like image c6).

Unlike the diagram, the brown wire from these pictures is the black/ground wire, the red wire is the yellow/signal wire, and the orange wire is the red VCC/5V from image c5!  Your wires may differ in color as well, if using those supplied with your DHT module as I have done.  Do not get them mixed up - follow any wire back to the DHT to identify it properly.

When complete, trim any protruding slag, or excess length from the wires as they exit the board, once cooled.

Part 4 - Final Assembly                                                         

image.png

gently press down on areas such as those noted with arrows - image d1

1. Cut a piece of the double-sided adhesive foam tape 23mm wide and 45mm tall, with a small notch cut out to allow wires to pass as shown in image d1.  Do not remove the backing to expose the second adhesive side, this backing will remain on permanently as an additional barrier between the sensor, the Arduino, and the wires in the case.

 

2. Place the completed sensor and wires assembly into its slot you cut out in the lid, from the inside.  Cover the entire unit with the tape you cut out, allowing the wires to fit through the notch.  Use a dull plastic "spudger" type tool (image d1) to gently but thoroughly press down at all contact points, bends, and flat areas where the tape should make full contact with the lid and sensor.  Avoid the area of the wires and resistor, and the soldering points - use only a finger or thumb and gentle pressure in the area over wires to ensure a light contact.  We don't want to break any of the solder or unintentionally bridge the contacts.


Do the same for the tape covering the magnet in the case - press into the bends and flat areas to ensure permanent contact.  Do not compress the part on the top of the magnet too much - we need this pile to be between 3-5mm to make contact with the Arduino Nano when it is finally in place.

image.png

first remove backing from tape, then apply the SuperGlue - image d2

3. Before proceeding, with the protective backing still on the tape covering the magnet (still "un-sticky"), test fit the Arduino Nano into the case one last time - make sure the USB port sits flush with the base of the case as it exits, and the PCB board is flush with the edge of the case with the USB port hole (such as in image d3).  Ensure that the back of the Arduino overlapping the magnet touches the tape and the peel covering it - this is the last chance to make it taller with another bit of tape, if you used a different or thinner type of tape not recommended by this guide.  It should be a foam type tape with some give, and adding to the height of the magnet enough to make contact with the Arduino (about as tall as the USB port on the other side, 4mm).

When ready, first remove the backing peel entirely from the double-sided adhesive covering the magnet - a sharp pair of tweezers can help here, it is NOT EASY and your luck may vary (condolences, I use this stuff all the time because it is so great, but for this one flaw - actually getting the backing off once it's in place can be painful!).

Once you're done fighting the Gorilla tape and got the backing peel off, place a small dot of SuperGlue inside the case near the USB port passthrough hole.  In the example image d2 there is almost too much, half this much would do - you can use a cotton swab to soak up some of the glue before it dries, but this entire procedure must be done swiftly.

Before the SuperGlue dries, very carefully slot the Arduino Nano into the case at an angle, with the USB port first, keeping the back from touching the tape yet - slide the Arduino USB port through the hole and then lower the back end down into position above the tape, keeping the PCB flush with the case wall, and the USB port through the hole as it makes contact with and compresses the SuperGlue.  Quickly dab up any SuperGlue that may leak out of the hole and outside the case.

 

image.png

apply light pressure on right and strong pressure on left - image d3

4. Referring to image d3, with light & gentle finger pressure, press down on the area noted by the arrow on the right, while also using a more firm finger pressure to press down on the area noted by the arrow on the left (over the tape/magnet).  Be sure not to put a lot of pressure on the right where those components are, it is not necessary - the SuperGlue will do its job, we just need to give it light pressure to help spread the SuperGlue and ensure flush contact as we put greater pressure on the left where there are no components and we want full contact with that tape.

image.png

 fully assembled - image d4

5. Before closing the lid, allow up to several minutes for the SuperGlue to dry.  Take this time to plan the bends or separations in the ribbon wire (if using one) so that each wire can sit in a sort-of zig-zag fashion once we do close the lid.  In image d3, the wires are actually a bit long and will require an extra 'zag' to fit, so I have separated the wires nearly to the first bend.  The first bend by the lid and notch in the tape must be acute & firm without crimping!

Once the SuperGlue is dry, carefully guide the wires into places they won't impede as you close the lid - start from the far end away from the wires, and lower it into place over the USB port side lastly.  Be careful not to force it closed, adjust as needed to ensure a tight fit without jamming the wires into hard crimps or bends which could sever tiny wires in the braid inside the wire jacket.

 

image.png

The Official AVCS-DHT1 sticker label - image d5

6. The AVCS-DHT1 Sensor (being magnetic) is designed to stick to a PC case in a vertical orientation somewhere not far from the intake, but far enough from intake fans to not be 'cooled by the wind'.  The back of the ABS plastic case on the sensor can potentially mar or scuff softer paint on a PC case, so it is advised to place a piece of black electrical tape or even Scotch Tape along this surface simply to ensure a softer contact with the PC.

All AVCS-DHT1 sensors built by me and sold in the VG Store will have this sticker label (shown in image d5), which also serves this purpose as a softer backing to help avoid minor scuffing over time.  If using one of these labels, carefully cut around the grey box on the label leaving about a 1-2mm margin as shown.  You may consider peeling back and folding a crease in the wax paper backing, then folding back into place over the adhesive surface, before cutting the label to size - this will help more easily remove the backing once you've trimmed off the edges of the label.

Unlike the high cost of shipping pre-built sensors around the world, I can offer these cool little AVCS-DHT1 sticker labels to anyone following this DIY Build Guide for a fairly low price in the VG Store including free domestic and international shipping to around 180 countries.  It's much cheaper to mail a small envelope than a box, of course. 😉  Click Here to open the VG Store in a new browser tab to check out these sticker labels.

Part 5 - Uploading the Code                                                

AVCS_DHT1_DIY_Sensor_v3

7. At long last, we can upload the Arduino sketch to the device and get some sensor data onto the computer!  Start by connecting the AVCS-DHT1 sensor to the computer with the USB cable, and mount it as noted, on the front or side of the computer near the intake but not within range of wind created by intake fans.  The area of the panel where the sensor sits should not be near any internal components which get hot under heavy PC use.

 

8. Open the Arduino IDE program again.  Under the 'File' Menu, select 'New' (or press CTRL+N) to create a new sketch called "AVCS_DHT1_DIY_Sensor_v3".  Select the entire contents of this new sketch and delete them so you have a blank text area to paste into.

Next, Expand Contents of the code block above - copy the entire contents of the code block here from line number 1 through line number 86.  You can copy the code block to your clipboard more easily by clicking the "Download Raw" button provided by Pastebin, and select all the text on that page & copy it.  Finally, paste the entire code into your sketch in the Arduino IDE (overwriting any contents) and save the sketch (CTRL+S).  Now we can upload the sketch from the Arduino IDE program to the Arduino Nano by pressing the ( image.png ) upload button just as we did with the Blink sketch above.  When uploading is done, close the Arduino IDE program and proceed with testing at step 9 below.

If you see any problems in the errors and information window below the sketch when trying to upload and if the title bar over this information window at the bottom of the sketch does not show the words  ( image.png ) when done, stop and get Help or Support from the links in the Addendum at the bottom of this guide.

 

image.png

 AVCS SENS profile version shown above may differ from latest - image e1

9. Launch the VoiceAttack program and switch to the AVCS Sensors & Weather Profile (if not already running and loaded).  When voice commands are available, say, "Open the Sensor Menu".  The AVCS SENS Main Menu will pop up.  Press the "OPTIONS" button, and then press the "Sensor Options" button.

In the Sensor Options screen, press the "Test Arduino DHT11 Sensor" button - there will be a voice reply of either "Test Succeeded" or, of course, "Failed".  Upon a successful test, the VoiceAttack Event Log (shown in image e1) will display several text messages, including a sample of the data received such as:

AVCS-DHT1 Data: [AVCS,22.75,65.00,72.95,73.00,DHT1]

image.pngimage.pngimage.png

DHT Monitoring in AVCS SENS is a
secondary monitor tied to the Sensor
and/or Weather Monitor.  If either of
these are started, DHT Monitoring
will try to start.  If no DHT sensor is
detected, indoor weather & sensor
diagnostic commands will not work.
If both Sensor & Weather Monitoring
are turned off while DHT Monitor is on,
the DHT Monitor will also turn off.

 

Congratulations on successfully building an AVCS-DHT1 Sensor!  Enjoy the indoor weather & PC sensor diagnostic voice commands!
*alternatively, if you were not so successful, please see links below in the addendum for help & support on a variety of topics.  I am also happy to provide assistance here if you would like to reply below, or through private message here or on Discord - whatever is preferrable

 

Addendum - Help & Support for this DIY Arduino Project

 If you need help, post up a reply below and I'll answer as soon as I see it.  Otherwise, here are some helpful links pertaining to this project:                                                                    

AVCS Help and Support Links

 

Arduino Links

 

VoiceAttack Links

"AVCS SENS", including the Profile Package for VoiceAttack, the AVCS SENS Wiki page, the AVCS-DHT1 Sensor and Sticker Label, and this DIY build guide, comprise creative works by SemlerPDX shared under CC BY-NC-ND 4.0 March/June 2022
AIDA64 is not affiliated with AVCS or this DIY project.  Images and text depicting the AID64 program(s), title, logo, or other elements belonging to AIDA64 or FinalWire Ltd. are used only for educational and/or instructional purposes, relating to demonstration & use, in this DIY project guide.
AIDA64 is a Registered Trademark of FinalWire Ltd. ©2010-2023 All rights reserved.

]]>45Thu, 02 Feb 2023 22:23:17 +0000AVCS CORE Profile Framework for VoiceAttackhttps://veterans-gaming.com/blogs/entry/41-avcs-core-profile-framework-for-voiceattack/  

AVCS_CORE_Title_QUARTER.png

Profile for  VoiceAttack
by =VG= SemlerPDX

 

Description:

AVCS CORE is the new framework for any VoiceAttack profile I release in future, and provides awesome tools to any VoiceAttack user.  It can be used alone and by itself, or as a base to build a VoiceAttack profile around, including its functions in your own creations.  The Quick Command Creator cannot possibly replace the very easy and very powerful voice commands we can create through VoiceAttack in the standard fashion, but allow users to quickly create simple keypress commands for a phrase, or even advanced multi-step macros that can use a limited selection of common VoiceAttack actions.  The very fun Voice Authorization System lets us create passphrases that we can gate a QCC Command behind, for example, "Execute self destruct mode", 'command code required!', "Picard 4 7 Alpha Tango", 'confirmed'.

I've even created a special home page and forum section here at the VG website, and a channel in the VG Discord, to provide Help & Support for the many users of my profiles - with voice controlled bug reporting to make it easy to let me know when I need to fix something.



As I plan to release more and more VoiceAttack profiles for various games, I needed a framework to standardize my methods, and to help keep profiles used by other people up to date and in proper working order.  I never quite expected such a large user base, and with that I've decided to offer much more direct support through in-profile options menus and help & support options that tailor themselves to whatever AVCS4 profile is active.  By checking for just 8 bytes of an update number on the VG website when loading, AVCS CORE can provide a pop-up choice for users to view the latest changelog, apply the latest patch (or open the website to download a new major update version), or just postpone until later.  I've even included an option to turn off minor patch update prompts, and to roll back to the last version if desired!



The purpose of this profile is to function as the backbone of any AVCS4 game profiles I release, such as the current AVCS4 Falcon BMS Radios profile, and provide users with a host of profile and update controls.  When AVCS CORE is first loaded by VoiceAttack, it will initialize itself and any other AVCS4 Profile that is switched to, bringing its full list of commands into the end game profile.  This includes the Quick Command Creator and Voice Authorization System, with new commands or codes saved to the Active Profile's save file.  Any other AVCS4 Profile that gets switched to will clear and re-load its own QCC Commands or VAS Passphrases (if any), working out of it's own save file as well.

Included is the AVCS CORE profile package that includes the AVCS CORE Profile designed for VoiceAttack, as well as the optional AVCS CORE Framework blank Template Profile for VoiceAttack profile builders.  To keep AVCS CORE startup fast for any AVCS4 Profiles, commands cannot be added directly to the CORE Profile, so the Template is available, and can include all of the functionality of AVCS CORE by including the CORE profile commands through its profile options.  This profile will have its own save file and config files folder in the VoiceAttack Apps folder along side other AVCS Profiles data.  Since AVCS CORE needs to load before any other AVCS4 Profile (including the AVCS4 Template Profile), it will be updated the least, and has been tested the most over a year and a half of development.  I will continue to support all AVCS4 Profiles through AVCS CORE and its powerful profile control options.



Say goodbye to the keyboard, and enjoy the immersion! Cheers!
 

Features:

AVCS_CORE_Info1.pngAVCS_CORE_Info2.pngAVCS_CORE_Info3.png
*The optional Push-To-Talk mode is disabled by default.  Say, "Turn On Push To Talk Mode" to enable


 

Download: (Click Here)

 

Tips for this profile:

Please use the voice command "Open Help and Support Menu" to communicate any bug reports.  These help menus can be expanded without new profile versions, so suggestions are welcome.
Thank you for checking out AVCS CORE for VoiceAttack!

(click here to view tips)
  • *On first import, you should say, "Initialize Profile" - after first time, this is automatic.  Any attempt to use commands before this will trigger auto-initialization.
  • If you get errors from my profile, Launch VoiceAttack and open Options (wrench icon in lower right):
  •   -Under last tab on top, System/Advance, check box next to "Use Nested Tokens" as in image 1 below
  •   -Unless absolutely required, during testing it's recommended to uncheck "Allow command segment info for composite commands"
     
  • Open the profile - if not already done, group commands by category and consolidate multi-part commands as in image 2 & 3 below
  • Click on the Description tab at the top to help sort commands further (see image 4)
  • Read a semicolon ";" as the word "or" and look at long commands as having many options like saying "2;Two;Too;To;Wingman"  (read as "2 -or- Two -or- Too -or- To -or- Wingman")

image 1image 2image 3image 4

 

 

Commands Reference:

 

 

CommRef-AVCS4-CORE-25.png

Say, 'Open the Command Reference', anytime to view available voice commands:

avcs_core_commref.PNG

 

 

Quote

 

v1.11 Major Profile Update (public release)

Please download and import this updated final version!  Link below and updated in the main post above!  AVCS CORE v1.11 will also import a new 'AVCS4 USER PROFILE TEMPLATE (v1.0)' - this template has not been changed from before.  If you had AVCS CORE v1.0 and that template profile already, you can delete this duplicate 'AVCS4 USER PROFILE TEMPLATE (v1.0)

*Follow instructions during update to import previous version Save Files and to uninstall and delete the previous AVCS CORE v1.0 profile and config files

I had hoped that AVCS CORE v1.0 would be the final version, but I had not anticipated issues with Joystick POV directional buttons in the Push-To-Talk system, and I had not included a handy way to delete saved PTT buttons or keys.  With this update, I'm happy to announce that AVCS CORE is now feature stable and (as far as I know) 100% bug free!  I keep throwing every curveball and edge case I can think up at it, even including the update or new version profile import process, and everything just works.  I don't have anything more to add, and there is nothing left to take away.

As the 'hub' profile for my AVCS4 BMS Radios profile, and others I plan to release in time, it has always been my goal to have AVCS CORE as an unchanging stable framework that I can use as a platform to support end-game profiles indefinitely.  Eventually, I plan to return to AVCS CORE to create a separate version packed with well designed and themed user interfaces for all options and menus which presently use simple VoiceAttack 'Get user input' actions, and while still supporting the original v1 simple 'get user input' interface version(s) which will remain free for all users.  The artwork and GUI coding will take some time, and I have many other projects on my plate, so I don't expect to be working on AVCS CORE again until late 2022 or even later.

I use AVCS CORE every day myself, with the included AVCS Template profile as my 'main' Windows voice control system, and am very glad to have this project version wrapped up for now.

Thank you all again for all the support and for the coffees!  Cheers! :coffee: 

Public Release AVCS CORE v1.11 Changelog Oct-1-2021

Fixes/Improvements:

	-Updated minimum required version of VoiceAttack to 1.8.9
	-Created new system in Push-To-Talk Mode for Joystick POV (4-way directionals only)
	-Created Delete system in PTT Mode to allow removal of any PTT entry already set
	-Fixed PTT Buttons Display List not retrieving correct keyboard key from keycode # (showing 'square' symbol instead)
	-Fixed CORE Config #2 (TTS file) error near 'AlreadyOn' phrase, CRLF (NewLine) missing, merging the variables into one

 

 

On 5/15/2021 at 11:02 PM, =VG= SemlerPDX said:

FINAL RELEASE TO v1.0

Please download updated final version!  Link below and updated in the main post above!  You don't have to remove the old 0.92 beta profile, but it is recommended to not use both at the same time or variables may get messed up.  Thanks to everyone for helping to finish up final testing and for your patience this year as I've been so busy with this website!

I cannot believe I'm finally here!  I've been working on this vision of a project for over a year and a half, and came up with the idea after the first "day one patch" due to a typo in one of my public voice command profiles.  I dreamed of a profile hub that could help manage any game profile I release, as well as work like a template for VoiceAttack profile builders to use for their own projects, including AVCS CORE functions and methods in an included Template Profile.

Several interesting voice control systems are used by me in various games, so it only made sense to flesh those out and place them in a central profile, then release game profiles which include AVCS CORE profile commands into themselves.  If I update a command system inside AVCS CORE, users only have to download that one profile, and likewise, I don't have to place those systems into each game profile and update each profile when a common command system is changed.  Additionally, since I place so many of my operational variables in flat text files, it is very easy to edit or update exactly how the hard set systems in the profile operate, and allowing 'patch' updates through these configuration files without forcing a new profile to be downloaded and imported.  And of course, through AVCS CORE, I can notify users of major profile updates requiring a new download, with the added bonus of special initialization logic to detect a new profile version and offer to import the previous save file containing user profile settings, or even delete the previous version configuration and/or save files.

With this final public release of AVCS CORE, I can even add new voice commands through patch updates between major profile updates if needed, to further minimize the need to force new profile download and imports for minor changes.  So long as AVCS CORE command systems do not change, it should be very easy to support additions to games through game updates, or even modify and add to existing commands with new alternate phrasings to help maintain my goal of conceptual command use, "any way you say it".


Huge thanks to everyone who helped out with comments, feedback, bug reports, and testing - there is no way I could have come this far without all the support and I just can't thank everyone enough!  Special thanks for the coffees!  I'm looking forward to using this framework in the coming months and years to release AVCS4 game profiles for plenty of titles, the end of this one project makes possible so many more!:coffee: 
 

Here's a copy of the latest changelog entry: 

Public Release AVCS CORE v1.0 Changelog May-11-2021

New Commands:
 -"Open the Command Reference" (or variations - open up-to-date command reference page online, or last updated reference file locally if offline)
 -"Set a Computer Name" (or variations - set a 'Computer' Assistant name for AVCS PTT mode, say before any command to wake listening temporarily)
 -"Set a Push to Talk Button" (or variations - set up to 6 total keyboard, mouse, or joystick buttons through automated script - just press when asked)

Fixes/Improvements:
 -Improved PTT (Push to Talk) Mode with voice controlled automated key/button detection during "Set" command
 -Added PTT Modes (chosen during "Set" command) for game/QCC commands only (default), or toggle VoiceAttack Global Listening Mode
 -Added PTT Mode 'Wake' by 'Computer' Assistant Name - set a name to say before any existing command to temporarily wake Global Listening Mode
 -Added Profile Misc. Commands to QCC, allows new commands or macros to be added via Live Update Patch Fix to CORE or AVCS4 profiles between major updates if needed
 -Added requirement to Include AVCS CORE Profile Commands through any used AVCS4 Profile Options, instructions provided during first-time init
 -Added optional File Explorer GUI to select item for QCC Advanced Commands 'Play a Sound File' and 'Open File Shortcut or Program' actions
 -Added option to Save File Options Menu to import save file (config settings, QCC commands, or all) from existing Profiles (for any game) or from file path entered
 -Fixed When setting Preferred, found duplicates of a non-AVCS profile (created unique list for AVCS and non-AVCS profile list choices)
 -Fixed QCC commands set in CORE persisted into next profile, should have been 'wiped' and unavailable in different AVCS profile
 -Fixed International Decimals - All Decimal Variables finally compatible for international users via cultural identification fix during init
 -Fixed infinite loop on Minor Version Rollback toggle and version display errors following toggle
 -Fixed many more minor issues throughout, from options menus to get-input pop-up boxes including direct profile name choice instead of shortname ID and version number ID

Any problems or new bugs, or brilliant ideas, feel free to drop some feedback!  Cheers! :drinks: 

 

Quote

v0.92b Major Profile Update (beta)

I have fixed the issue with international decimal separators, and everything should work well now for all users.  Initialization optimization has been a large focus of this update, especially when using CORE alongside AVCS4 Falcon BMS Radios.  Users will need to download this new version of the profile to take advantage of the updates and fixes listed below.

Thanks for your patience during the beta test rounds here, again, the end goal for AVCS CORE is to be a stable un-changing profile that can handle profile management for any new AVCS4 game profile I create in the future without needing updates itself, and I think we're well on our way to that.  Cheers!

Please be sure to download the AVCS4 Falcon BMS v1.3.92b Profile (if used), this updated changed the AVCS CORE function commands inside AVCS4 BMS, too...

  






BETA Release AVCS CORE v0.92 Changelog Dec-6-2020

	! USER NOTICE!
	-This is a major profile update, users of v0.91b must download the new v0.92 beta test profile
		-(AVCS CORE profile version 0.91b will be retired in 60 days)

Fixes/Improvements:
 -Improved AVCS_CORE profile initialization optimized again for decreased load time - most noticeable on first use
 -Fixed All Decimal Variables now compatible for international users via cultural invariant token "DECINV"
 -Fixed infinite loop on Minor Version Rollback toggle and version display errors following toggle

 

Quote

v0.91b Major Profile Update (beta)

Due to some initial issues right off the bat, it seems the concept of having some AVCS CORE functions outside the profile itself as part of an App for VoiceAttack would have included a bit more work, but more importantly increased the profile package size from around 1MB to over 25MB, and it's just not worth it.  The idea was specifically for things like my Save File Sort function that orders the lines of the save file into a readable alphanumeric sorting, where AVCS4 module specific entries were properly grouped together (like saved Quick Commands or VAS Passphrases), and any new AVCS4 profile such as Elite Dangerous could introduce new sorting rules by simply including a new version of the AVCS_CORE App for VoiceAttack in it's profile package.  This would have removed the need to update the base AVCS CORE profile that all AVCS4 game profiles rely upon anytime I wanted to modify those game-specific functions.

I've done away with the app completely now, and recreated the simple functions like sort and initialize as inline functions for VoiceAttack.  This requires everyone to download a new version of AVCS CORE and the AVCS4 Falcon BMS Radios (beta) profile if currently used.

Thanks for your patience during the beta test rounds here, the end goal for AVCS CORE is to be a stable un-changing profile that can handle profile management for any new AVCS4 game profile I create in the future without needing updates itself, and I think we're well on our way to that.  Cheers!

Please be sure to download the AVCS4 Falcon BMS v1.3.91b Profile (if used), this updated changed the AVCS CORE function commands inside AVCS4 BMS, too...

  






BETA Release AVCS CORE v0.91 Changelog Aug-22-2020

	! USER NOTICE!
	-This is a major profile update, users of v0.90b must download the new v0.91 beta test profile
		-(AVCS CORE profile version 0.90b will be retired in 30 days)

Fixes/Improvements:
 -AVCS_CORE App removed in place of internal systems - was too slow, and had compatibility issues


___ (previous version changelogs) ___

(click here to view previous changelogs)

 

Quote 















BETA Release v0.90 Changelog Aug2020

New Commands:
 -AVCS CORE Commands Included into AVCS4 User Template Profiles so users can add commands, adding to CORE increases its load time
 -"Create a new Voice Authorization Phrase" and other included commands in Voice Authorization System
 -VAS can allow QCC commands to be locked behind a required authorization phrase as set by users, in up to 10 weighted levels
 -Integerated Bug Reporting and debugging options for easy troubleshooting
 -Versioning allows for Mutiple prior versions (reinitialization required) for easy profile version rollback if desired
 -Included UPDATE command to allow users to import previous saved user settings and saved Quick Commands from previous version of profile
 -Full profile control through command, "Open CORE Options Menu"
 -Better user support through command, "Open Help and Support Menu"  (will expand in time)
 -User settings save file control through command, "Open Save File Menu"  (includes save file backup and restore system)
 -...and much more (see posts at avcs homepage)

Fixes/Improvements:
 -Set First Use to present user with Get Choice box for Profile Update Notifications and Preferred Profile (auto-switch) choice
 -Setting 'CurrentBackupIndex' and 'SaveFileBackupCount' to 'Not Set' inside F_SFS_LOAD_ALL  (was getting corrupted in save file)
 -Separated 'new_profiles.txt' file from AVCS4 profiles and AVCS CORE profiles to handle two imports before first time run/initialization of either
 -Added Duplicate Profile check, informs user of non-functional AVCS profiles (if ending in 'dash number' such as '-1')
 -Edited Preferred Profile command to allow for any user profile to be set to be auto-switched to after AVCS CORE finishes initializing
 -Included VoiceAttack Profile Builders Template profiles for use of AVCS CORE as a standalone profile framework for any game

___

BETA Release v0.80 Changelog July2020

New Commands:
 -"Add a new Voice Command" and others in new Quick Command Creator system
 - QCC can be used to create Simple Keypress Commands or Advanced Multi-Step Macros with a limted selection of common VoiceAttack actions
 -"Edit Keypress Timings" to open options menu to set custom timings

Fixes/Improvements:
 -AVCS CORE Profile and Updates Management systems allow version control and user notification of updates (minor or major)
 -Full Profile Update Control added with user choice, only downloads if allowed by user (only checks 8 bytes of a version number before that)
 -Profile Updates set to allow choice for majority of fixes/changes to occur without new VoiceAttack Profile download/import  *called "LIVE UPDATES"
 -Physical Profile Updates set to allow previous versions to remain installed without conflict, and also import/uninstall previous version files  *called "MAJOR UPDATES"
 -Fixed integer/decimal recognition in Save File system "LOAD_ALL" command
 -Set most profile variables to config files in VA Apps Folder (edit with "Open Advanced Core Options" command)
 -Set most commands to Text Variables, read from config files

 

 

 

]]>41Wed, 20 Oct 2021 20:39:02 +0000AVCS4 - How to Control Falcon BMS 4.34 In-Game Radios with Voice Commandshttps://veterans-gaming.com/blogs/entry/31-avcs4-how-to-control-falcon-bms-434-in-game-radios-with-voice-commands/ *Originally, this was designed for Falcon BMS version 4.34 - since then, it has always been and will continue to be updated to work with the latest version of Falcon BMS. Pro tip: never include a game version in URL's or graphics ;)


 

AVCS4_BMS_Title_QUARTER.png

Profile for  VoiceAttack
by =VG= SemlerPDX

 

Description:

These commands use VoiceAttack to translate the in-game on-screen radio menus from AWACS through Tanker into natural and intelligent voice command phrases that will fire keypress macros to help keep hands on the throttle and stick, and maintain immersion.  As an additional option, these commands can be locked behind a push-to-talk mode bound to your UHF/VHF transmit buttons in-game, allowing any other VoiceAttack command unrestricted access if needed, while still restricting these BMS radio command macros.  Finally, this single advanced control profile is extremely easy to edit or integrate into other profiles.

At VETERANS-GAMING, we fly with friends or AI Pilots, or a mix of both on our 24/7 Public Korean Campaign in Falcon BMS. We may go out with an AI wingman only to have a friend take their place mid-flight.  For this reason and others, I created this VoiceAttack profile based around restricting when the computer can execute keypress macros that match voice phrases, having to first check if that pilot was set to a human pilot and therefore disregard commands for that pilot.

Thanks to user requests during the beta, there is now an optional mode to reverse the Human Pilots system, to assume all pilots are humans unless told otherwise, and also a system to choose a different keyboard layout than QWERTY.  I have also added an optional Audio Feedback Mode to play a short radio cue sound when a command is successfully recognized.


Included is a single profile that handles every callsign and radio command variation in Falcon BMS, with instructions on how to add any custom callsigns to the single profile. The focus of this profile is only on the in-game Radio Menus, and creating an immersive interaction layer through VoiceAttack that is easy to manage and update, or integrate into other Voice Control systems for Falcon BMS.  My goal was an intuitive system, so there is no user manual - only a few infographics and quick reference pic of all the radio commands.  I personally keep that final pic on my tablet for reference when flying, to find radio commands I seldom used in the past when they were more difficult to access while busy with HOTAS in the pit.


Say goodbye to the keyboard, and enjoy the immersion! Cheers!
 

Features:

GTB-BMS-Info1c_QUARTER.gifGTB-BMS-Info2c_QUARTER.gifGTB-BMS-Info3c_QUARTER.gif
*Push-To-Talk mode disabled by default.   Say, "Turn On Push To Talk Mode" to enable

 

Download: (Click Here)

 

Tips for this profile:

(click here to view tips)
  • *On first import, you should say, "Initialize Profile" - after first time, this is automatic.  Any attempt to use commands before this will trigger auto-initialization.
  • If you get errors from my profile, Launch VoiceAttack and open Options (wrench icon in lower right):
  •   -Under last tab on top, System/Advance, check box next to "Use Nested Tokens" as in image 1 below
  •   -Unless absolutely required, during testing it's recommended to uncheck "Allow command segment info for composite commands"
     
  • Open the profile - if not already done, group commands by category and consolidate multi-part commands as in image 2 & 3 below
  • Click on the Description tab at the top to help sort commands further (see image 4)
  • Read a semicolon ";" as the word "or" and look at long commands as having many options like saying "2;Two;Too;To;Wingman"  (read as "2 -or- Two -or- Too -or- To -or- Wingman")

image 1image 2image 3image 4

 

 

Commands Reference:

 

OptionsCommands_QUARTER.png

HumansListCommands_QUARTER.png
*Replace the word "Human" with "Computer" when All-Humans Mode is ON
Normally, this profile assumes all pilots are Computers, use All-Humans Mode to invert this
 

RadioMenusReference_FULL_v1.2.png

Say, 'Open the Command Reference', anytime to view available voice commands
 

 

18 minutes ago, =VG= SemlerPDX said:

FINAL RELEASE TO v1.40

Please download updated final version of AVCS4 BMS (v1.40) and AVCS CORE (v1.0)!  Link below and updated in the main post above!  You don't have to remove the old 1.3.92 beta profile, but it is recommended to not use both at the same time or variables may get messed up.  Thanks to everyone for helping to finish up final testing and for your patience this year as I've been so busy with this website!

As I wrote in my post about the final public AVCS CORE v1.0 release, I cannot believe I'm finally here!  I've been working on this vision of a project for over a year and a half, and came up with the idea after the first "day one patch" due to a typo in one of my public voice command profiles.  I dreamed of a profile hub that could help manage any game profile I release, as well as work like a template for VoiceAttack profile builders to use for their own projects, including AVCS CORE functions and methods in an included Template Profile.

Two of the largest setbacks for the AVCS4 BMS Voice Controlled Radios project had been my misunderstanding of how to deal with international decimal separators, and the extremely unintuitive Push to Talk Button setup procedure.  With this final public release of AVCS4 BMS v1.40, I have at last overcome these issues, and the new Push to Talk Mode features are completely automated, voice controlled, and completely customizable including the classic default mode which only gates game commands behind the PTT key(s), and now an option to toggle Global Listening Mode with the use of the PTT button(s) (up to six keyboard, mouse, or controller buttons).  As an added feature, users can set a 'Computer' Assistant name that works like holding the PTT button(s) for a brief period, waking Global Listening long enough to issue commands.

I'm also happy to announce that users can just say, "Open the Command Reference", to view the latest updated command reference on the VG website, or the most recent command reference on file (if offline).

With this final public release including the AVCS CORE (v1.0) profile, I can even add new voice commands through patch updates between major profile updates if needed, to further minimize the need to force new profile download and imports for minor changes.  So long as AVCS CORE command systems do not change, it should be very easy to support additions to games through game updates, or even modify and add to existing commands with new alternate phrasings to help maintain my goal of conceptual command use, "any way you say it".


Huge thanks to everyone who helped out with comments, feedback, bug reports, and testing - there is no way I could have come this far without all the support and I just can't thank everyone enough!  Special thanks for the coffees!  :coffee:  I still have plans to build upon this framework, and find a way to create game profile specific themed GUI elements, but for pure functionality, I'll be using the VoiceAttack get-user input boxes until then.
 

Here's a copy of the latest changelog entry: 





Public Release AVCS4 BMS v1.40 Changelog May-11-2021

   This is a Major Profile Update, and requires downloading and importing the latest AVCS4 BMS Radios (v1.40) and AVCS CORE (v1.0) profiles:

New Commands:
 -"Open the Command Reference" (or variations - open up-to-date command reference page online, or last updated reference file locally if offline)
 -"Set a Computer Name" (or variations - set a 'Computer' Assistant name for AVCS PTT mode, say before any command to wake listening temporarily)
 -"Set a Push to Talk Button" (or variations - set up to 6 total keyboard, mouse, or joystick buttons through automated script - just press when asked)

Fixes/Improvements:
 -Improved PTT (Push to Talk) Mode with voice controlled automated key/button detection during "Set" command
 -Added PTT Modes (chosen during "Set" command) for game/QCC commands only (default), or toggle VoiceAttack Global Listening Mode
 -Added PTT Mode 'Wake' by 'Computer' Assistant Name - set a name to say before any existing command to temporarily wake Global Listening Mode
 -Added Profile Misc. Commands to QCC, allows new commands or macros to be added via Live Update Patch Fix to CORE or AVCS4 profiles between major updates if needed
 -Added requirement to Include AVCS CORE Profile Commands through AVCS4 BMS Profile Options, instructions provided during first-time init
 -Fixed International Decimals - All Decimal Variables finally compatible for international users via cultural identification fix during init
 -Fixed Issue where user was asked to set Keyboard type more than once during first few profile uses, even when already saved to file and loaded properly

Any problems or new bugs, or brilliant ideas, feel free to drop some feedback!  Cheers! :drinks: 

 

Quote

v1.3.92b Major Profile Update (beta)

Since the Beta Test for AVCS CORE has progressed, and changed the way it runs, AVCS4 BMS must be updated as well.  This will not be the norm, I don't expect many AVCS CORE updates, it is a fixed set of functions.  You can download and import both the new versions of AVCS CORE and AVCS4 Falcon BMS at the same time - just switch to the AVCS CORE 0.92 profile first to trigger the new version setup.

Update notes:
There were many issues with the radio commands beginning with a wildcard, to a degree that I'm not sure why there were not more reports of commands not working.  I have fixed all of these, as well as the problem with international decimal separators.  Another large focus of the .92 beta updates is initialization optimization, and I am hoping that load time is now on par with v1.2 from before the AVCS CORE integration.  Feedback on this is greatly appreciated, my goal is to ensure load time is as fast as possible across a majority of CPU's and builds.

Thanks for your patience during the beta test rounds here, again, the end goal for AVCS CORE is to be a stable un-changing profile that can handle profile management for any new AVCS4 game profile I create in the future without needing updates itself, and I think we're well on our way to that.  Cheers!

Please be sure to download the AVCS CORE v0.92b Profile (required), this updated changed the entire initialization methods in AVCS CORE function commands and AVCS4 BMS, too! 








BETA Release AVCS4 BMS v1.3.92 Changelog Dec-6-2020

   This is a Major Profile Update, and requires downloading and importing the latest AVCS4 BMS Radios (v1.3.92b) and AVCS CORE (v0.92b) profiles:

Fixes/Improvements:
 -Improved AVCS_CORE and AVCS4 BMS profile initialization optimized again for decreased load time - most noticeable on first use
  -(AVCS4 BMS profile initialization should be even much faster now!)
 -Fixed infinite loop on Minor Version Rollback toggle and version display errors following toggle
 -Fixed International Decimals - All Decimal Variables now compatible for international users via cultural invariant token "DECINV"
 -Fixed All Wildcard Commands fixed to allow both Wildcard and non-Wildcard recognition ("anything that ends with" or "just the raw command")
 -Fixed Audio Feedback Mode not playing sound when commands recognized
 -Fixed Audio Feedback Mode on/off text entry in VA Event Log 'not set'

 

Quote

v1.3.91b Major Profile Update (beta)

Since the Beta Test for AVCS CORE has progressed, and changed the way it runs, AVCS4 BMS must be updated as well.  This will not be the norm, I don't expect many AVCS CORE updates, it is a fixed set of functions.  You can download and import both the new versions of AVCS CORE and AVCS4 Falcon BMS at the same time - just switch to the AVCS CORE 0.91 profile first to trigger the new version setup.

Regarding the changes to AVCS CORE, and how they effect AVCS4 Falcon BMS:
Due to some initial issues right off the bat, it seems the concept of having some AVCS CORE functions outside the profile itself as part of an App for VoiceAttack would have included a bit more work, but more importantly increased the profile package size from around 1MB to over 25MB, and it's just not worth it.  The idea was specifically for things like my Save File Sort function that orders the lines of the save file into a readable alphanumeric sorting, where AVCS4 module specific entries were properly grouped together (like saved Quick Commands or VAS Passphrases), and any new AVCS4 profile such as Elite Dangerous could introduce new sorting rules by simply including a new version of the AVCS_CORE App for VoiceAttack in it's profile package.  This would have removed the need to update the base AVCS CORE profile that all AVCS4 game profiles rely upon anytime I wanted to modify those game-specific functions.

I've done away with the app completely now, and recreated the simple functions like sort and initialize as inline functions for VoiceAttack.  This requires everyone to download a new version of AVCS CORE and the AVCS4 Falcon BMS Radios (beta) profile if currently used.

Thanks for your patience during the beta test rounds here, the end goal for AVCS CORE is to be a stable un-changing profile that can handle profile management for any new AVCS4 game profile I create in the future without needing updates itself, and I think we're well on our way to that.  Cheers!

Please be sure to download the AVCS CORE v0.91b Profile (required), this updated changed the entire initialization methods in AVCS CORE function commands and AVCS4 BMS, too!

  








BETA Release AVCS4 BMS v1.3.91 Changelog Aug-22-2020

	! USER NOTICE!
	-This is a major profile update, users of v1.3.90b must download the new v1.3.91 beta test profile and AVCS CORE v0.91b
		-(AVCS4 BMS profile version 1.3.90b will be retired in 30 days)

Fixes/Improvements:
 -AVCS_CORE App removed in place of internal systems - was too slow, and had compatibility issues

 

 

On 8/12/2020 at 10:15 PM, =VG= SemlerPDX said:

v1.3.90b Full Overhaul & AVCS CORE Integration Update (beta)

I'm very proud to finally offer the next version of AVCS4 BMS because it includes an entire set of profile control and support from my new AVCS CORE Framework Profile for VoiceAttack.  While AVCS4 BMS has not functionally changed much from what users have come to expect, AVCS CORE adds entirely new features that remove any previous need to manually edit any commands in the traditional sense to modify any configuration settings or otherwise.

The only significant new command added directly to AVCS4 BMS is "Edit the Callsigns List" (and phrase variations of it).  This opens a simple Get Choice menu to offer options to add/change/edit/remove any callsigns recognized by the profile.

After that, most everything comes from the required AVCS CORE Profile Framework that will load before AVCS4 BMS, adding commands and features, as well as allowing auto-profile switching by setting AVCS4 BMS as a "Preferred Profile" in the CORE Options Menu (say, "Open Core Options", poke around, have fun!)



Please be sure to download the AVCS CORE 0.90b Profile from this download section as well, it is now a requirement for any AVCS4 game profile I release, such as the upcoming Elite Dangerous profile, and more... 








BETA Release v1.3.90 Changelog Aug2020

New Commands:
 -AVCS CORE Commands Included into AVCS4 BMS Profile to lessen profile switching to CORE when it was needed
 -"Create a new Voice Authorization Phrase" and other included commands from Voice Authorization System
 -VAS can allow QCC commands to be locked behind a required authorization phrase as set by users, in up to 10 weighted levels
 -Integerated Bug Reporting and debugging options from AVCS CORE for easy troubleshooting
 -Versioning allows for Mutiple prior versions (reinitialization required) for easy profile version rollback if desired
 -Included UPDATE command to allow users to import previous saved user settings and saved Quick Commands from previous version of profile
 -Full profile control through command, "Open CORE Options Menu"
 -Better user support through command, "Open Help and Support Menu"  (will expand in time)
 -User settings save file control through command, "Open Save File Menu"  (includes save file backup and restore system)
 -...and much more (see posts at avcs homepage)

Fixes/Improvements:
 -Set First Use to present user with Get Choice box for Default Keyboard Layout (QWERTY/AZERTY/etc..)
 -Setting 'CurrentBackupIndex' and 'SaveFileBackupCount' to 'Not Set' inside F_SFS_LOAD_ALL  (was getting corrupted in save file)
 -Separated 'new_profiles.txt' file from AVCS4 profiles and AVCS CORE profiles to handle two imports before first time run/initialization of either
 -Added Duplicate Profile check from AVCS CORE, informs user of non-functional AVCS profiles (if ending in 'dash number' such as '-1')
 -Edited Preferred Profile command to allow for any user profile to be set to be auto-switched to after AVCS CORE finishes initializing

___

BETA Release v1.3.80 Changelog Mar2020

New Commands:
 -"Add/Edit Callsigns List" commands to add or remove callsigns recognized
 -"Add a new Voice Command" and others included from Quick Command Creator system
 - QCC can be used to create additional phrasings, just set action to execute another command (by name)
 -"Edit Keypress Timings" to open options menu to set custom timings

Fixes/Improvements:
 -AVCS CORE Profile and Updates Management integeration (see AVCS CORE changelog)
 -Full Profile Update Control added with user choice, only downloads if allowed by user (only checks 8 bytes of a version number before that)
 -Profile Updates set to allow choice for majority of fixes/changes to occur without new VoiceAttack Profile download/import  *called "LIVE UPDATES"
 -Physical Profile Updates set to allow previous versions to remain installed without conflict, and also import/uninstall previous version files  *called "MAJOR UPDATES"
 -Fixed typo in command "Raygun" -- corrected from "Ragun"  (first fix via new live updates system)
 -Created 'Add New Callsigns' system using Get-Choice boxes
 -Set most profile variables to config files in VA Apps Folder (edit with "Open Advanced Core Options" command)
 -Set most commands to Text Variables, read from config files

 

 

On 1/2/2020 at 10:11 PM, =VG= SemlerPDX said:

v1.3 Patch has been released for BMS 4.34.1 (U1)

Just a simple hotfix for a bug found by Wheelchock, the standard "Ready for Departure" command was getting overwritten by the variable for the new "Carrier Ready for Departure" command added for the new U1 update for BMS. As a result, this command will call an Abort by attempting the same input key as the carrier departure. Basically, everyone does need this hotfix, can't be avoided.

Anyone can easily fix this themselve inside their own profile, if you already have v1.2, and you don't want to bother importing this new version - just open the command labeled,
"KEYPRESS_Variables →→→((ADJUST AI COMMS LISTS & KEYS USED BY THIS PROFILE HERE))←←←" and scroll down to the ATC Variables section, under the Carrier Page section,
you can change the #7 variable from "Set Text [KEY_ATC_ReadyForDeparture] to '7'" to "Set Text [KEY_ATC_CarrierReadyForDeparture] to '7'", and apply changes.

Otherwise, just download this new version... 








Patch Release v1.3 Changelog Jan2020

Fixes/Improvements:
 -Fixed issue with variable conflict for "Ready for Departure" - was pulling new variable from "Carrier Ready for Departure"

 

On 12/28/2019 at 3:53 PM, =VG= SemlerPDX said:

v1.2 Update has been released for BMS 4.34.1 (U1)

Falcon BMS 4.34 has just released Update 1, and with it has come some serious improvements and additional features.  For this profile, and the in-game Radio Menus in general, all that has changed is an addition of a "Ready for Departure" call as the 7th choice on Page 6 of the ATC Radio Menu.  I have added that command to the profile, but as it does conflict with the default "Ready for Departure" command, this Carrier specific command will need to be preceded by the word "Carrier" as a forced prefix word (see note in the large Command Reference pic).

Example use:  "This is Joker 7-1, Carrier Ready for Departure"

I've also added a bit of polish to the Audio Feedback system, allowing it to recognize the word "feedback" as two words, "feed back", to help us avoid repeating ourselves to get the commands to fire, as well as a null check on the Stereo Audio Feedback output channel, so it can recover if this saved setting is lost.  I've also updated the minimum version of VoiceAttack, so please be sure to update your VA program.
We've tested this version, just minor additions, and everything seems great - but let me know if any issues pop up!  Happy New Year! 








Patch Release v1.2 Changelog Dec2019
New Commands:
 -"Carrier Ready for Departure" : for ATC Page 6, new 7th item added for 4.34 (U1) update

Fixes/Improvements:
 -Added additional recognition words for turning on/off Audio Feedback Mode - "feedback" can now be recognized as "feed back"
 -Added Null Check on Audio Feedback Stereo Output Channel setting, if saved setting lost, will force user input on profile load
 -Updated minimum VoiceAttack version to latest release (v1.8.3) for compatibility

 

On 11/3/2019 at 10:31 AM, =VG= SemlerPDX said:

v1.1 Patch has been released

A small bug has been identified and removed.  This issue prevented the entire Human Pilots Registry system to function and should have been caught before the final release version.  All apologies to everyone who has been trying to use this new voice program.  In addition to this, I've decided to not use a wildcard to catch the name of the BMS program to send keypresses to, and have gone for the "Falcon BMS.exe" method.  Still, this will not catch every user, and players will need to test to be sure commands go through initially, and refer to VoiceAttack troubleshooting (and those tips we've highlighted already) to get commands to fire in the correct window.  I'm happy to help new users, and the community has been helpful as well.  Any questions, feel free to ask! 








Patch Release v1.1 Changelog Nov2019

Fixes/Improvements:
 -Changed common Send To default from *Falcon BMS* to "Falcon BMS.exe" to avoid conflict with open PDF's, etc. with Falcon BMS in name
 -Fixed Human/Computer Pilots Registry system - last minute addition of a mode check was to blame, has been removed for now

 Again, any issues feel free to let me know! :hi:

 

 

On 10/29/2019 at 5:50 PM, =VG= SemlerPDX said:

FINAL RELEASE TO v1.0

Please download updated final version!  Link below and updated in the main post above!  You don't have to remove the old 0.99 beta profile, but it is recommended to not use both at the same time or variables may get messed up.  Thanks to everyone for helping to finish up final testing!

SitRep:
I've finished with all final additions and proposed changes, and all known bugs and issues have been resolved.  We've tested quite extensively to try to break things, and it seems fairly stable.  The final version can be found in our download section, please rate and comment if you like and share this link if you can (click here).  There is now an Audio Feedback Mode that can be turned on or off at any time.  It plays a short sound when a command is successfully recognized, to save time and help avoid the frustration of not knowing if we have to repeat a command.

I've given the option to have the Audio Feedback sound effect to output through stereo left, right, or center channel(s), and this is set when you turn the mode on.  It is a radio cue up type sound, but a bit distinct compared to the ones in BMS to help differentiate feedback.  All three sound files are very tiny, and are included in a VoiceAttack Profile Package for easy importing into VA, and will be placed in folder in the VoiceAttack program folder under Sounds automatically when the profile is imported.

Finally, there is a single Variable Pause in the KEYPRESS_Variables command that controls the time between a keypress and release for every action in the profile.  Default is 50ms, and if a user has any issue with the keypress macros firing buttons too fast for their computer, this number can be increased slightly to slow down the system and fix any issues.


Huge thanks to everyone who helped out with comments, feedback, bug reports, and testing - I'm very happy with how well this profile has been developed, and I have a feeling it will be a solid tool for years to come!  I'll support any changes for future BMS versions, and will try to respond to any questions about this profile.
 

Here's a copy of the changelog: 








Final Release v1.0 Changelog Oct2019
New Commands:
 -Turn On/Off Audio Feedback Mode : Provides sound feedback upon successful recognition of a command (per user request)
 -Added a non-functional command to help recognize many variations of "Yes" words for the voice confirmations in profile

Fixes/Improvements:
 -New Variable Pause between any keypress/release for adjustment of the time any key is held down, in keypress_variable command. Default is 50ms
 -New Audio Feedback Mode has custom SFX included, and gives user option of stereo left, right, or center playback for easier distinction
 -New Speech notification on startup for Audio Feedback Mode (if enabled)
 -Speech notifications on startup for PTT mode and All-Humans mode (if enabled) have been greatly shortened.
 -Fixed issues with being able to set Humans in Computer Pilots mode and vice versa

Any problems or new bugs, or brilliant ideas, feel free to drop some feedback!  Cheers! :drinks: 

 

 

On 7/17/2019 at 9:14 PM, =VG= SemlerPDX said:

BETA UPDATED TO v0.99 (final beta!)

Please download newest version!  Link updated in the main post above!  You don't have to remove the 0.98 beta profile, but it is recommended to not use both at the same time or variables may get messed up.  Thanks to everyone for helping to finish up final testing!


Per request, to speed up the interaction of adding/removing pilots from the exclusion lists, you can now say the entire Callsign + Flight Number + Wing Number when asked for the callsign. 

Example: 
"Set a Human Pilot"
"say the callsign"
"Cowboy 7 3"
"Cowboy 7 3 - is this correct?"
"Yes"
...
(bypassing the need to individually set Flight Number and then Wing Number!)

This will jump to the confirmation at the end of the command and greatly reduces the time spent interacting with the voice control system configuration.   During my testing, I found there must be a clear separation between the Flight Number and Wing Number when spoken, to avoid "Cowboy 7 3" getting recognized as "Cowboy 73", and your own results may vary.  Please test and let me know.  The old system is still in place, and you can even just say the Callsign + Flight number, and it will notice and skip to the Set Wing Number segment of the script.  The entire idea was to allow a lot of options to recognize how we speak, and the only catch is that we need to enunciate and keep succinct breaks between words for this style of input.  Further beta testing in this final 0.99 phase should help judge if this will work or if it needs adjustment.


Additionally, there are now VoiceAttack command log notifications whenever the profile loads showing the current profile settings, and also voice notifications if either PTT mode or the new All-Humans mode are On. 
 

Here's a copy of the changelog: 








Beta v0.99 Changelog Jul2019
New Commands:
 -Change Default Keyboard Layout allows choices between QWERTY, QWERTZ, & AZERTY (per user request)
 -Turn On/Off All-Humans Mode : Reverse mode assumes all pilots are humans, add Computer Pilots individually as needed (per user request)
 -Copy of all Add/Remove Human Pilots commands for Computer Pilots & All-Humans Mode

Fixes/Improvements:
 -Can state an entire callsign plus flight & wing numbers when asked for Callsign (per user request to speed up the voice system interaction of adding/removing human pilots)
 -VoiceAttack log entries displays profile information on startup (current keyboard layout, push-to-talk mode on/off state, All-Humans mode on/off state) (per user request)
 -Speech notifications on startup for PTT mode and All-Humans mode if they are enabled (see above)
 -Forced profile initialization if not initialized on any command use (per bug report: on first download/import of profile, trying to use any command fails until voiceattack restarted)

 

 

 

 

]]>31Sun, 16 May 2021 06:14:58 +0000DIY - Custom Game Controller - 2 Dial HSI Course and Heading Knobshttps://veterans-gaming.com/blogs/entry/32-diy-custom-game-controller-2-dial-hsi-course-and-heading-knobs/
zPztEG1.jpg

 I have a touch screen monitor below my main one when I fly in flight simulators like Falcon BMS or DCS or Microsoft Flight Simulator.  It's great for the MFD buttons, as opposed to the actual wired USB Thrustmaster MFD's physically attached to the screen like I used to have, and I can use the monitor for other things, too.  But one thing I would love to have attached to the screen would be the Course and Heading knobs of the HSI (horizontal situation indicator) .

It would need to be removable so I can store it when not in use. 

I've heard about a micro-suction tape that can stick to anything smooth and flat without leaving a residue or losing stickiness, so this is a good excuse to buy some and play around with sticking things to my monitors.
 

← On the left is the (green) Arduino Micro board I used to test the concept with a rotary encoder on a breakout board, where I wrote the initial sketch with the Joystick and Encoder libraries.  Later, because I didn't want to sacrifice my Arduino Micro to this controller, I bought a 3 pack of these much smaller Sparkfun Pro Micro clones for fifteen bucks (blue one in the middle).  That one is gonna stay there for future tests and such, they'll be the heart of many projects in the future since they cost so little and include so much!

 


 

My DIY USB Game Controller - Rotary Encoders as Course & Heading Knobs for Falcon BMS / DCS / FSX
*parts list with links at bottom


The initial goals I had for this project were:h5w7NMM.jpg

  • Two Rotary Encoders with Push Buttons recognized as USB Game Controller in Windows
  • Thin and flat, without taking up too much viewing space on the monitor
  • Can stick and restick to the monitor with micro-suction tape
  • USB connector can be removed so it can be boxed (NetDot magnetic)
  • Fine control for one-degree per detent and Fast Speeds for turning quickly
  • Encased in semi-rigid form like shrink wrap so it won't scratch the monitor
  • Total cost for one single unit less than $10

 

 

 

 

 

 


4Y01eI2.jpg 

 

First, I affixed the Rotary Encoders and the Pro Micro clone to an 8cm x 2cm prototype PCB with a couple header pins bent outwards and crimped down, and with the two blue solid copper switch wires soldered in place from the top. I also ran the 10k Ohm resistors for the switches now.

 

These are for the push buttons built into the rotary encoders, and although they only have two pegs on the actual component, they require three wires from the controller board (ground, 5 volt power, and the blue switch wire going to the Pro Micro). All this added plenty of structure. There is no wiggle or play, I'm not gonna try to break it, but it is very rigid now.

 

 

 

 

H89ZiWv.jpg 

 

Here's a close look at the first stage of soldering. (okay, don't look too close) I don't have the highest quality tools or solder, or even a lot of skill and experience at this, but it's good enough -- and good enough should always be good enough for a DIY project for personal use.  If I wanted to, I could order a custom circuit board if I was going to make a bunch of these, but I'm happy as it is.

 

It is so cheap to buy some of this stuff, if you messed up, you can always just buy another.  Those Pro Micro controller boards cost about as much as a value meal at a fast food joint, so you can literally afford to make mistakes as you learn even if you're on a very tight budget like I am.  

 

 

 


ru0rmph.jpg

 

 

A homemade carbon filter fume extractor, a simple soldering iron with a power switch and a temperature controller, some handy dandy helping hands and that brass soldering tip cleaner make little projects like this very easy, and all these items together costs less than the Logitech mouse to it's right. Good enough to play.

 

If anyone reading this has any idea to get into working with things like this, my advice is to jump right in, get the most basic stuff you can get, not the cheapest, but things with good reviews from some good online store like Amazon, Sparkfun, Adafruit, etc.

 

 

 

 

 

Pinxa02.jpg

 

Soldering the top side here, used one of the helping hands to hold a string of solder from the spool. When I'm dealing with tiny bits that are between 0.5mm-2mm, anything that helps is appreciated. One slip and this 225C soldering iron would burn through any one of those tiny chips or components on the board. I find myself holding my breath and doing one or two, then letting go for a sec. I had to redo a few, and I always wait for it to cool down so I don't transfer too much heat to this poor little board.

 

I had a few bits of solid copper wire with colored insulators, from a breadboard jumpers kit, so I cut some to length, but used others as is. This resulted in an odd looking crossover of the Orange and Yellow wires, but they are not taller than the micro USB port on the other side of the board and that's fine.

 

 

 

 

 


xzlxtFJ.jpg   fzzbWnc.jpgOnce I was all done, I tested every connection for continuity and unintentional bridges, and it all checked out, so I encased it in shrink wrap.  By some sort of miracle, it works, it looks decent, and I think that will do just great!  I connected it to the computer and uploaded the sketch, which I had to modify slightly since I used a few different pins for the push buttons on the rotary encoders, now at pins 15 and 6 instead of 6 and 7.

I am thoroughly hooked on these NetDot magnetic adapters.  When I looked at the reviews for Pro Micro boards, one of the only issues I saw that I'd be concerned with is accidentally popping the micro-USB port off the Pro Mini board if dropped or yanked too hard.  A magnetic connector completely eliminates this issue, as well as the standard wear and tear issues that plugging and unplugging creates over time.  And they're as cheap as regular braided USB cables, too.  Why not?

 

 


Ocsopzo.jpg   dzvZVUh.jpg   CustomHSIgamecontrollerProperties.PNG

Here it is connected to the touchscreen monitor. It is far more satisfying to have tactile dials for these knobs than trying to make little circles on the screen with my finger over the touchscreen dials. The micro-suction tape keeps it in place and actually has some grab when trying to pull it off the screen. I've started using a peeling action but I doubt the screen would ever have problems.  I might get a 3D printed case someday and maybe even a 90 degree angle connector so the cord goes back behind the monitor naturally instead of downwards, but for now, it's done and working great.

Turning the dial with the most basic rotary encoder sketch from that Arduino library results in a "one degree per detent" meaning one turn is one click, and one click is one degree. No matter how fast you turn it, with 20 detents per 360 degrees with these encoders, it would take FOREVER to turn the dial from heading 000 to 180!!

I wrote two separate jump speeds to detect how fast the dial is being turned, one jumps 18 degrees per click, and the other 30 per click. Now, it's easy to twist the dial fast to get it spinning fast on screen, while also being able to dial in one degree at a time when needed.  All in all, it was a fun project and it's made me think seriously about getting a 3D printer someday to make little plastic cases for things like this.
 

Here's the code if someone wants to use it (or modify it to make it better):
Rotary Encoders HSI Course and Heading Knobs.ino for Arduino IDE
https://pastebin.com/drUnCfKN

spoilerIMG2415905122018.PNG
/* Simple HSI Knobs Sketch for Falcon BMS / DCS / FSX
 *  for Arduino Micro/Leonardo / Sparkfun Pro Micro or equiv. clones
 * by SemlerPDX June2019
 * VETERANS-GAMING.COM
 *  
 *  Pins:
 *  Rotary Encoder 1 - (OUTA-OUTB-SW) = Arduino Pins (0,1,15)
 *  Rotary Encoder 2 - (OUTA-OUTB-SW) = Arduino Pins (2,3,6)
 *  
 *  Encoder Library
 * http://www.pjrc.com/teensy/td_libs_Encoder.html
 * 
 *  Joystick Library 
 * by Matthew Heironimus
 * https://github.com/MHeironimus/ArduinoJoystickLibrary
 */

#define ENCODER_USE_INTERRUPTS
#define ENCODER_OPTIMIZE_INTERRUPTS
#include <Encoder.h>
#include <Joystick.h>

//Tell the Encoder Library which pins have encoders
Encoder axisXRotation(0, 1);
Encoder axisYRotation(2, 3);

//Rotary Encoder Push Button Pins
int buttonArray[2] = {15, 6};

//Rotary Encoder Interrupt Pins
int EncoderPin0 = 0;
int EncoderPin1 = 1;
int EncoderPin2 = 2;
int EncoderPin3 = 3;

//Delay Time between loops
int debounceDelay = 260;

//Variables to compare current to old values
int oldX = 0;
int oldY = 0;
int RxAxis_Value = 1;
int RyAxis_Value = 1;

//Intervals for Jump/Warp Speed Rotations
int JumpSpeed = 18;
int WarpSpeed = 30;

//Set generic joystick with id 42 with 2 buttons and 2 axes
Joystick_ Joystick(0x42, 
  0x04, 2, 0,
  false, false, false, true, true, false,
  false, false, false, false, false);  


void setup() { 

  //Set Encoder Pins as Pullups
  pinMode(EncoderPin0, INPUT_PULLUP);
  pinMode(EncoderPin1, INPUT_PULLUP);
  pinMode(EncoderPin2, INPUT_PULLUP);
  pinMode(EncoderPin3, INPUT_PULLUP);

  //Loop through buttons and set them as Pullups
  for(int x = 0; x < sizeof(buttonArray); x++) {
    pinMode(buttonArray[x], INPUT_PULLUP);
  }

  //Set Range of custom Axes
  Joystick.setRxAxisRange(0, 359);
  Joystick.setRyAxisRange(0, 359);
  
  // Initialize Joystick Library
  Joystick.begin(false);

}


void loop() {

  // Loop through button pin values & set to Joystick
  for (int x = 0; x < sizeof(buttonArray); x++) {
    byte currentButtonState = !digitalRead(buttonArray[x]);
    Joystick.setButton(x, currentButtonState);
  }


  // Read "Heading" X Axis Rotation Encoder Knob
  int newX = axisXRotation.read();
  if (newX > oldX) {
    //Determine speed of increment & set output
    int difX = newX - oldX;
    RxAxis_Value = speedVal(difX, RxAxis_Value, 1);
    Joystick.setRxAxis(RxAxis_Value);
    axisXRotation.write(newX);
    oldX = newX;

  }else if (newX < oldX) {
    //Determine speed of decrement & set output
    int difX = oldX - newX;
    RxAxis_Value = speedVal(difX, RxAxis_Value, 0);
    Joystick.setRxAxis(RxAxis_Value);
    axisXRotation.write(newX);
    oldX = newX;
  }


  // Read "Course" Y Axis Rotation Encoder Knob
  int newY = axisYRotation.read();
  if (newY > oldY) {
    //Determine speed of increment & set output
    int difY = newY - oldY;
    RyAxis_Value = speedVal(difY, RyAxis_Value, 1);
    Joystick.setRyAxis(RyAxis_Value);
    axisYRotation.write(newY);
    oldY = newY;

  }else if (newY < oldY) {
    //Determine speed of decrement & set output
    int difY = oldY - newY;
    RyAxis_Value = speedVal(difY, RyAxis_Value, 0);
    Joystick.setRyAxis(RyAxis_Value);
    axisYRotation.write(newY);
    oldY = newY;
  }


  //Send Joystick info through USB
  Joystick.sendState();
  delay(debounceDelay);
}


//Function to set Rotation value adjusted for the turning speed
int speedVal(int dif, int val, int dir){
  if (dif >= WarpSpeed) {
    if (dir == 1) {
      val = val + WarpSpeed;
    }else{
      val = val - WarpSpeed;
    }
  }else if (dif >= JumpSpeed) {
    if (dir == 1) {
      val = val + JumpSpeed;
    }else{
      val = val - JumpSpeed;
    }
  }else{
    if (dir == 1) {
      val = val + 1;
    }else{
      val = val - 1;
    }
  }
  //Correct Rotation within 360 deg.
  if (val < 0) {
    val = val + 360;
  }else if (val >= 360) {        
    val = val - 360;
  }
  return val;
}

 

 


Here's a cost breakdown:

Pro Micro  (clone of Sparkfun Pro Micro board sold by KeeYees) (3 pack)  -  $15.99
https://www.amazon.com/gp/product/B07FXCTVQP/
$5.33 per board

PCB Prototype Board Kit  -  $15.99
https://www.amazon.com/gp/product/B07CK3RCKS/ 
$0.25 (just a guestimate - it's one part out of a huge kit)

360 Degree Rotary Encoders (5 pack w/knob caps)  -  $8.89
https://www.amazon.com/gp/product/B07DM2YMT4/
$3.56 for 2 dials

Microsuction Tape (25cm X 30cm Sheet)  -  $14.95
https://www.amazon.com/gp/product/B00M7FC1K8/
$0.12 (just a guestimate - used 1.5cm x 6cm strip of a huge sheet)

NetDot 5ft Braided Magnetic Tip USB Micro Cable (3 pack)  -  $13.90
https://www.amazon.com/gp/product/B074TB8XTL/
$4.64 for 1 cord

(Not taking into account things like double sided sticky tape, solder, wires, or shrink wrap tubing segments used because they cost less than a few pennies)

Total:
$13.65 (USD)

_________________________________

I spent a fair bit more money than I initially expected to (almost $55!), but much of that went towards components or materials that I'll be able to use for several projects in the future.  At about $14 bucks, it is twice what I thought it would be per unit, so that will help me to better gauge other ideas.  It seemed like it would be cheap as dirt, using many parts I already owned, but it all adds up - they don't sell less than a sheet of micro-suction tape, and buying control boards in bulk is the only wise way to do it (if you can call 3 units "bulk", that is).


In conclusion, it was great to have an idea, play around with some proof of concepts, and then make it into a reality within a few days.  Single game controllers today.... one day, a full cockpit of switches!  Not sure what my next project will be, but among other ideas, I've considered making a custom control board for Kerbal Space Program, or maybe some kind of wireless gear that can connect to a computer and translate into RF to control some DIY RC cars or whatever with my Xbox controller already attached to my PC.  Eventually, I want to get into wireless stuff, and even RC, but I might start with button boards that use USB cables just like this one. 

If anyone has any questions on this project, feel free to ask.


Thanks for reading! 

]]>32Sat, 15 Jun 2019 08:25:05 +0000DIY - Wireless TrackClip Pro mod for TrackIRhttps://veterans-gaming.com/blogs/entry/30-diy-wireless-trackclip-pro-mod-for-trackir/
qLBxVFn.jpg

 I bought a Logitech G933 wireless headset last year and I'd like to make my TrackIR TrackClip Pro into a wireless unit as well.  I need to be able to remove it from the G933 when not in use, TrackClip Pro's break if you look at them too hard, so taking it off is a primary requirement.  I'll want to be able to recharge it with the same cord the G933 uses, too.  I'm not a pro at this stuff, so any thing that works well and doesn't cost too much will be just fine with me.

I know that if I ramp up the voltage from one single 3.7V battery, I can achieve 5V @ 1A for the 3 LED's on the TrackClip, and should retain a duration of more than 4 hours (overly hopeful estimate).  I'll need to do some testing, if I have to, I'll use the second 3.7V battery like in the image here just for longer time between charges.

 

 

 

 

 

 

My DIY TrackIR "Wireless Rechargeable" Track Clip Pro mod
*parts list with links at bottom
 

The initial goals I had once I began were:hI7g3Yf.jpg

  • Tiny form-factor, less than 5cm long, less than 2.5cm wide & tall
  • Can power TrackClip for between 4-8 hours continuously
  • Tiny on-off slider switch
  • Rechargeable via micro-A USB female plugin
  • Output to TrackClip via USB (type A) female outlet plug (as in picture above)
  • Encased in semi-rigid form like shrink wrap, adapted plastic case, or custom 3D printed plastic case
  • Velcro strap to easily mount on headphones
  • Total cost for one single powerpack unit less than $10 USD  

 


fnvI6Vr.jpg 

 

 

 

Soldering leads to the TP4056 (03962A) Charging Board with Protection.  This is the brains of this unit, and will make sure the rechargeable 3.7V battery will not discharge past 2.5V and will not recharge over 4.2V.  It acts as the buffer between the battery and the voltage booster.

 

 

 

 

 

 

rHLDhRw.jpg 

 

Here is the 03962A Charging Board and battery holder wired to the MT3608 DC to DC Step Up Boost Converter.  I did this for initial testing and to set the trim-pot (blue square box with round brass peg) on the boost converter from the 18V setting it shipped with to the 5V that I need.  It will take the 3.7 Volt battery and step up its voltage to something usable by the TrackClip Pro without the need for a second battery.

 

 

 

 

 


hKiHu6f.jpg

 

 

Trying to keep the size small, mounting the breakout boards close together makes it about the size of a stick of gum, plus the AAA sized battery.  I put a USB female plug in for size reference along with the Bic lighter.  The 10440 is a 3.7 Volt Lithium Ion rechargeable battery in a AAA size.  According to a features sheet on a batteries info website, "Lighter weight and higher energy density than any other rechargeable battery".  I'll be ramping up it's voltage to a full 5V.

 

 

 

 

 

 


c25gjkN.jpgI used a portion of shrink wrap tubing around the 03962A Charging Board on the left, and MT3608 Boost Converter on the right is hot glued to the battery holder and to the 03962A in the middle.

Through the shrink wrap I cut holes for the LED indicator lights on the charging board.  The tiny switch has a pin through the breakout board and is soldered in place, with another pin bent and wrapped around the edge of the board, and soldered to it's wire (I didn't have red shrink wrap, but the thicker top right wire is the load line, and is red under there).  Even with all of that, I just don't trust tiny switches to stay in place and solder is not structural, so it got a healthy dose from the hot glue gun.  As you can see, I've used the highly skilled technique known as "just glob it on".

 

 

 

 

 

 


OjjV4BX.jpg   UNQlfmT.jpgI've cut the cord on the Track Clip Pro, spliced the wires to the Boost Converter, and used shrink wrap tubing to contain the entire unit.  I've left a bit of the wire jacket hanging below the wires and hot glued in place, and then shrink wrapped under a little tension. This causes a slight bend in the wire, shown in these pics and it helps the unit bend the newly magnetic end inwards to the screw under this panel.

A NetDot micro-USB magnetic adapter makes connecting a charging cable easy, and gives one end of my battery pack a strong magnet to work with. The NetDot magnetic charging adapter is so strong it is very well stuck to the screw on the corner of the G933 headset under the panel.  It doesn't come off and swing around when I move my head around, and that's all that really matters to me.  Function before looks.

 

 


8J2MzkV.jpgsJ8UdQ7.jpg

It's finally finished and working great!  I expect it will last for a few years before I'll want to carve off the outer shrink wrap and replace the 10440 battery, and seal it back up with a new shrink wrap tube (and some new cut-outs for the switch and lights).

Here's a cost breakdown:

NetDot Magnetic Bi-Directional microUSB Plug Adapters
https://www.amazon.com/NetDot-Generation-Magnetic-Adapter-Compatible/dp/B076QC2RQT/
$4 (per male/female adapter pair)

TP4056 (03962A) Charging Board with Protection
MT3608 DC to DC Step Up Boost Converter
(in a pack with 3 of each board, plus 5 battery holders)
https://www.amazon.com/dp/B07NHHCNNQ
$1.00 per breakout board

The battery holder I used was actually the AAA type:
https://www.amazon.com/gp/product/B07C2XT5C5
$0.58 (one)

3.7V 10440 AAA Lithium Ion Rechargeable Battery (x4 @11.69 - w/Charger $19.09)*(note: these are NOT AAA batteries! They must be charged with a special charger, and shouldn't be used for normal AAA battery powered devices!)
https://www.amazon.com/10440-Rechargeable-Lithium-Battery-350mah/dp/B010ABNW5S/
(or)
https://www.amazon.com/10440-Lithium-Rechargeable-Battery-Charger/dp/B06X9TZ1CG/
$2.92 / battery

Tiny switch with nice long legs (they come in a pack of a hundred for six bucks):
https://www.amazon.com/Cylewet-Vertical-Switch-Arduino-CYT1016/dp/B01N7NCW8N/
$0.06 (one)

(Not taking into account things like hot glue sticks, solder, tape, or shrink wrap tubing segments used because they cost less than a few pennies)

Total:
$9.56 (USD)

_________________________________

Looking back to the start, I've met my goals or caused some to become redundant (like velcro) and the cost for this single battery unit was less than $10, though I do have enough parts to make 2 more, I'm happy to put those in my Arduino projects bins and eat the costs there.

This thing cost me about ten bucks, it works well, and I also have another $26 in extra parts (NetDot's and 3.7V batteries, battery holders, charging and boost breakout boards...).  I learned a bit about larger shrink wrap tubing, it only shrinks so far.  And I think it was all worth it.  Had a flight earlier, with 8 minutes to taxi, I just got up out of my PC chair from a hot pit, and walked over to the fridge to get a soda all without taking off my headset or TrackClip Pro, strolling around while listening in to the Tower and waiting for my clearance to taxi.  It was a feeling of true freedom!

If anyone has any questions on this mod, I'd be happy to help if I can. 

See you at Angels 20!

]]>30Sat, 08 Jun 2019 01:07:22 +0000