TKTalkie v3 Released!

[lerxstrulz]

Make sure you update the SDCard zip file too! 

 

Haha yep thanks for the reminder...sheesh I need some more coffee...

[lerxstrulz]

Ok, now next step:

 

In the serial console enter:

 

echo=1

 

That will turn on BLE verbose ouput, then try again with the APP and all of the BLE cmd/response will display and let's see what that says.  What version of the Arduino IDE are you on?  Did you go back to 1.8.1 or are you on 1.8.2?

[TKSnake[TK]]

Ok, now next step:

 

In the serial console enter:

 

echo=1

 

That will turn on BLE verbose ouput, then try again with the APP and all of the BLE cmd/response will display and let's see what that says.  What version of the Arduino IDE are you on?  Did you go back to 1.8.1 or are you on 1.8.2?

 

Done. Also, to answer your last question first, I did upgrade to 1.8.2 since there didn't seem to be a need to downgrade since I was able to correct the file errors by manual copy & paste). I verified the sketch before I loaded it to the device.

 

Here I enabled echo and then connected the phone. I then turned up the headphone volume to ensure everything was working. I then listed all the profile files for your reference.

> Got startup value DEBUG: true
> Get setting: profile
> Check setting profile = TKCONF2.TXT
> Return value TKCONF2.TXT
> Got startup value PROFILE: TKCONF2.TXT
> Get setting: echo
> Check setting profile = TKCONF2.TXT
> Check setting access_code = 76253
> Check setting debug = 1
> Return value 
> Got startup  value ECHO: false

----------------------------------------------
TKTalkie v3.0
(c) 2017 TK81113/Because...Interwebs!
www.TKTalkie.com
Debugging is ON
Type debug=0 [ENTER] to disable debug messages
----------------------------------------------

> PROFILE: TKCONF2.TXT
> Get setting: access_code
> Check setting profile = >debug=1<
> Saving config data:
> Opening file SETTINGS.TXT
> 0: profile=TKCONF2.TXT
> 1: access_code=76253
> 2: debug=1
> 3: 
> Startup Settings Updated

>echo=1<
> Saving config data:
> Opening file SETTINGS.TXT
> 0: profile=TKCONF2.TXT
> 1: access_code=76253
> 2: debug=1
> 3: echo=1
> Startup Settings Updated

> RX: connect=6e1f193819d5263|76253
> BLE Cmd: connect Value: 76253 Uid: 6e1f193819d5263
> Received access code 76253
> DEVICE ID 6e1f193819d5263...Send Access OK
{"cmd":"access","data":"1"}
> RX: config=6e1f193819d5263
> BLE Cmd: config Value:  Uid: 6e1f193819d5263
> Sending config
{"cmd":"config", "data": { "ver":"3.0",> Filter: .WAV
STARTUP.WAV
"sounds":["STARTUP.WAV"],"effects":["TKT_CLK1.WAV","TKT_CLK2.WAV","TKT_CLK3.WAV","TKT_CLK4.WAV","TKT_CLK5.WAV","TKT_CLK6.WAV","TKT_STA1.WAV","TKT_STA2.WAV","TKT_STA3.WAV","TKT_STA4.WAV","TKT_STA5.WAV"],> Filter: .WAV
CHATTER.WAV
"loops":["CHATTER.WAV"],> Get setting: profile
> Check setting profile = TKCONF2.TXT
> Return value TKCONF2.TXT
"default":"TKCONF2.TXT","current": {"name":"TKCONF2.TXT","desc":"Wireless w Chatter"},"name":"Wireless w Chatter","volume":0.4000,"mic_gain":3,"linein":5,"lineout":29,"startup":"STARTUP.WAV","loop":"CHATTER.WAV","loop_gain":0.1000,"high_pass":0,"voice_gain":3.1000,"voice_start":0.0610,"voice_stop":0.0210,"silence_time":350,"button_pin":0,"button_click":"TKT_CLK3.WAV","input":0,"effects_gain":0.4500,"eq":1,"eq_bands":"-0.1000,-1.0000,-0.1000,-1.0000,-1.0000","bitcrushers":"16,22050,16,36287","noise_gain":0.1500,"effects_dir":"/effects/","sounds_dir":"/sounds/","loop_dir":"/loops/","profiles":[> Filter: .TXT
SAMPLE.TXT
WIRED_BG.TXT
WMIC_BGL.TXT
TKCONFIG.TXT
TKCONF2.TXT
> Load Settings File /profiles/SAMPLE.TXT
> Opening file /profiles/SAMPLE.TXT
{"name":"SAMPLE.TXT","desc":"Sample Profile"},> Load Settings File /profiles/WIRED_BG.TXT
> Opening file /profiles/WIRED_BG.TXT
{"name":"WIRED_BG.TXT","desc":"Wired w Chatter"},> Load Settings File /profiles/WMIC_BGL.TXT
> Opening file /profiles/WMIC_BGL.TXT
{"name":"WMIC_BGL.TXT","desc":"Wireless w Chatter"},> Load Settings File /profiles/TKCONFIG.TXT
> Opening file /profiles/TKCONFIG.TXT
{"name":"TKCONFIG.TXT","desc":"Wireless w Chatter"},> Load Settings File /profiles/TKCONF2.TXT
> Opening file /profiles/TKCONF2.TXT
{"name":"TKCONF2.TXT","desc":"Wireless w Chatter"}],"mute":0,"bg":1}}
> RX: volume=6e1f193819d563|0.45
> BLE Cmd: volume Value: 0.45 Uid: 6e1f193819d563

>files<
SETTINGS.TXT
EFFECTS/
  TKT_CLK1.WAV
  TKT_CLK2.WAV
  TKT_CLK3.WAV
  TKT_CLK4.WAV
  TKT_CLK5.WAV
  TKT_CLK6.WAV
  TKT_STA1.WAV
  TKT_STA2.WAV
  TKT_STA3.WAV
  TKT_STA4.WAV
  TKT_STA5.WAV
LOOPS/
  CHATTER.WAV
PROFILES/
  SAMPLE.TXT
  WIRED_BG.BAK
  WIRED_BG.TXT
  WMIC_BGL.BAK
  WMIC_BGL.TXT
  TKCONFIG.BAK
  TKCONFIG.TXT
  TKCONF2.BAK
  TKCONF2.TXT
SOUNDS/
  STARTUP.WAV
HELP.TXT

When I tried to load my wired mic profile (WIRED_BG.TXT), the app seems to have just loaded a different profile (TCONFIG.TXT).

> RX: load=6e1f193819d5263|TKCONFIG.TXT
> BLE Cmd: load Value: TKCONFIG.TXT Uid: 6e1f193819d5263
>load=TKCONFIG.TXT<
> Load Settings File /profiles/TKCONFIG.TXT
> Opening file /profiles/TKCONFIG.TXT
> Parse Setting: name = Wireless w Chatter
> Parse Setting: volume = 0.4000
> Parse Setting: linein = 5
> Parse Setting: lineout = 29
> Parse Setting: startup = STARTUP.WAV
> Parse Setting: loop = CHATTER.WAV
> Parse Setting: loop_gain = 0.1000
> Parse Setting: high_pass = 0
> Parse Setting: voice_gain = 3.1000
> Parse Setting: voice_start = 0.0610
> Parse Setting: voice_stop = 0.0210
> Parse Setting: silence_time = 350
> Parse Setting: button_pin = 0
> Parse Setting: button_click = TKT_CLK3.WAV
> Parse Setting: input = 0
> Parse Setting: mic_gain = 3
> Parse Setting: effects_gain = 0.4500
> Parse Setting: eq = 1
> Parse Setting: eq_bands = -0.1000,-1.0000,-0.1000,-1.0000,-1.0000
> Parse Setting: bitcrushers = 16,22050,16,36287
> Parse Setting: noise_gain = 0.1500
> Parse Setting: effects_dir = /effects/
> Filter: .WAV
TKT_CLK1.WAV
TKT_CLK2.WAV
TKT_CLK3.WAV
TKT_CLK4.WAV
TKT_CLK5.WAV
TKT_CLK6.WAV
TKT_STA1.WAV
TKT_STA2.WAV
TKT_STA3.WAV
TKT_STA4.WAV
TKT_STA5.WAV
> 11 Sound effects loaded
> Parse Setting: sounds_dir = /sounds/
> Parse Setting: loop_dir = /loops/
> Play sound file /sounds/STARTUP.WAV on player 1
> Sound File Length: 4122
> Play sound file /loops/CHATTER.WAV on player 2
> Sound File Length: 2614725
> Sending config
{"cmd":"config", "data": { "ver":"3.0",> Filter: .WAV
STARTUP.WAV
"sounds":["STARTUP.WAV"],"effects":["TKT_CLK1.WAV","TKT_CLK2.WAV","TKT_CLK3.WAV","TKT_CLK4.WAV","TKT_CLK5.WAV","TKT_CLK6.WAV","TKT_STA1.WAV","TKT_STA2.WAV","TKT_STA3.WAV","TKT_STA4.WAV","TKT_STA5.WAV"],> Filter: .WAV
CHATTER.WAV
"loops":["CHATTER.WAV"],> Get setting: profile
> Check setting profile = TKCONF2.TXT
> Return value TKCONF2.TXT
"default":"TKCONF2.TXT","current": {"name":"TKCONFIG.TXT","desc":"Wireless w Chatter"},"name":"Wireless w Chatter","volume":0.4000,"mic_gain":3,"linein":5,"lineout":29,"startup":"STARTUP.WAV","loop":"CHATTER.WAV","loop_gain":0.1000,"high_pass":0,"voice_gain":3.1000,"voice_start":0.0610,"voice_stop":0.0210,"silence_time":350,"button_pin":0,"button_click":"TKT_CLK3.WAV","input":0,"effects_gain":0.4500,"eq":1,"eq_bands":"-0.1000,-1.0000,-0.1000,-1.0000,-1.0000","bitcrushers":"16,22050,16,36287","noise_gain":0.1500,"effects_dir":"/effects/","sounds_dir":"/sounds/","loop_dir":"/loops/","profiles":[> Filter: .TXT
SAMPLE.TXT
WIRED_BG.TXT
WMIC_BGL.TXT
TKCONFIG.TXT
TKCONF2.TXT
> Load Settings File /profiles/SAMPLE.TXT
> Opening file /profiles/SAMPLE.TXT
{"name":"SAMPLE.TXT","desc":"Sample Profile"},> Load Settings File /profiles/WIRED_BG.TXT
> Opening file /profiles/WIRED_BG.TXT
{"name":"WIRED_BG.TXT","desc":"Wired w Chatter"},> Load Settings File /profiles/WMIC_BGL.TXT
> Opening file /profiles/WMIC_BGL.TXT
{"name":"WMIC_BGL.TXT","desc":"Wireless w Chatter"},> Load Settings File /profiles/TKCONFIG.TXT
> Opening file /profiles/TKCONFIG.TXT
{"name":"TKCONFIG.TXT","desc":"Wireless w Chatter"},> Load Settings File /profiles/TKCONF2.TXT
> Opening file /profiles/TKCONF2.TXT
{"name":"TKCONF2.TXT","desc":"Wireless w Chatter"}],"mute":0,"bg":1}}

 

It did the same thing when I tried to load SAMPLE.TXT.

 

When I tried to change the default profile from TKCONF2.TXT to SAMPLE.TXT (using the star icon), it changed to TKCONFIG.TXT instead.

> RX: default=6e1f193819d5263
> BLE Cmd: default Value:  Uid: 6e1f193819d5263
>default<
> Setting default profile to TKCONFIG.TXT
> Filter: .TXT
SAMPLE.TXT
WIRED_BG.TXT
WMIC_BGL.TXT
TKCONFIG.TXT
TKCONF2.TXT
> Saving config data:
> Opening file SETTINGS.TXT
> 0: profile=TKCONFIG.TXT
> 1: access_code=76253
> 2: debug=1
> 3: echo=1
> Startup Settings Updated
> Default profile set
{"cmd":"default","data":"1;TKCONFIG.TXT"}

When I attempted to change it to WIRED_BG.TXT, it did the same thing.

 

When I tried to delete TKCONF2.TXT (using the trash icon), the following happened:

> RX: delete=6e1f193819d5263
> BLE Cmd: delete Value:  Uid: 6e1f193819d5263
>delete<

>files<
SETTINGS.TXT
EFFECTS/
  TKT_CLK1.WAV
  TKT_CLK2.WAV
  TKT_CLK3.WAV
  TKT_CLK4.WAV
  TKT_CLK5.WAV
  TKT_CLK6.WAV
  TKT_STA1.WAV
  TKT_STA2.WAV
  TKT_STA3.WAV
  TKT_STA4.WAV
  TKT_STA5.WAV
LOOPS/
  CHATTER.WAV
PROFILES/
  SAMPLE.TXT
  WIRED_BG.BAK
  WIRED_BG.TXT
  WMIC_BGL.BAK
  WMIC_BGL.TXT
  TKCONFIG.BAK
  TKCONFIG.TXT
  TKCONF2.BAK
  TKCONF2.TXT
SOUNDS/
  STARTUP.WAV
HELP.TXT

 

The profile wasn't deleted.

Edited May 2, 2017 by TKSnake

[lerxstrulz]

Great I see the problem.  The file names are not being sent with the commands.  I'll take a look at the app.  Stand by....

[Airborne Trooper[501st]]

I got my BLE fixed too. The Yellow and White on the 3.5mm needed to be swapped. I did exactly like your photo shows so you might want to change it. Having the same issues too with profiles.

[lerxstrulz]

Alright gentlemen I have corrected the app (left in some debug testing in the last release   )

 

Sending the updates to the app stores, so keep an eye out.  Thanks for the catch!

[TKSnake[TK]]

Alright gentlemen I have corrected the app (left in some debug testing in the last release )

 

Sending the updates to the app stores, so keep an eye out. Thanks for the catch!

Seemingly, there was an update released four days ago that my phone just downloaded, v1.0.1. Not sure if that would skew the results. What release should I be looking for on the Google Play Store? Edited May 3, 2017 by TKSnake

[lerxstrulz]

Seemingly, there was an update released four days ago that my phone just downloaded, v1.0.1. Not sure if that would skew the results. What release should I be looking for on the Google Play Store?

1.0.6 is latest

 

Sent from my SAMSUNG-SM-G930A using Tapatalk

[lerxstrulz]

Sigh. I forgot to update the version displayed on the splash page. Latest is version 1.0.6 and will show that in the app store but the splash screen will say 1.0.1

 

Sent from my SAMSUNG-SM-G930A using Tapatalk

[Airborne Trooper[501st]]

Still waiting for it to show up in the Apple App Store

[TKSnake[TK]]

Sigh. I forgot to update the version displayed on the splash page. Latest is version 1.0.6 and will show that in the app store but the splash screen will say 1.0.1

 

Sent from my SAMSUNG-SM-G930A using Tapatalk

 

I figured that out after I uninstalled and reinstalled the app

 

Speaking of which, my SETUP.TXT looked like this:

[profile=WMIC_BGL.TXT]
[access_code=76253]
[debug=1]
[echo=1]

One of these issues caused the app to register an invalid access code upon initial pairing. When I removed the SD card and zeroed them out, it worked fine.

 

The bigger problem is that, after using the updated app last night to delete a profile, it displayed no profiles afterwards. After some troubleshooting, I discovered that somehow all my profiles became corrupted.

 

Windows couldn't delete the corrupted files because their names had turned into non-ASCII characters, so I had to reformat the entire card and start from scratch.

 

I reloaded the backed-up configs from my PC onto the card and then started up the TKTalkie.

 

Sometimes it takes multiple attempts to connect the app to the device.

> RX: disconnect=6e1f193819d5263
> BLE Cmd: disconnect Value:  Uid: 6e1f193819d5263
> RX: connect=6e1f193819d263|76253
> BLE Cmd: connect Value: 76253 Uid: 6e1f193819d263
> Received access code 76253
> DEVICE ID 6e1f193819d263...Send Access OK
{"cmd":"access","data":"1"}
> RX: config=6e1f193819d5263
> BLE Cmd: config Value:  Uid: 6e1f193819d5263
> RX: connect=6e1f193819d5263|76253
> BLE Cmd: connect Value: 76253 Uid: 6e1f193819d5263
> Received access code 76253
> DEVICE ID 6e1f193819d5263...Send Access OK
{"cmd":"access","data":"1"}
> RX: config=6e1f193819d5263
> BLE Cmd: config Value:  Uid: 6e1f193819d5263
> Sending config
{"cmd":"config", "data": { "ver":"3.0",> Filter: .WAV
STARTUP.WAV
"sounds":["STARTUP.WAV"],"effects":["TKT_CLK1.WAV","TKT_CLK2.WAV","TKT_CLK3.WAV","TKT_CLK4.WAV","TKT_CLK5.WAV","TKT_CLK6.WAV","TKT_STA1.WAV","TKT_STA2.WAV","TKT_STA3.WAV","TKT_STA4.WAV","TKT_STA5.WAV"],> Filter: .WAV
"loops":[],> Get setting: profile
> Check setting profile = WMIC_BGL.TXT
> Return value WMIC_BGL.TXT
"default":"WMIC_BGL.TXT","current": {"name":"Test1.TXT","desc":"Wireless w Chatter "},"name":"Wireless w Chatter ","volume":0.5000,"mic_gain":3,"linein":5,"lineout":29,"startup":"","loop":"","loop_gain":2.0000,"high_pass":0,"voice_gain":1.0000,"voice_start":0.0700,"voice_stop":0.0200,"silence_time":350,"button_pin":0,"button_click":"","input":0,"effects_gain":5.0000,"eq":0,"eq_bands":"-1.0000,0.0000,1.0000,0.0000,-1.0000","bitcrushers":"12,16384,10,10240","noise_gain":0.0000,"effects_dir":"/effects/","sounds_dir":"/sounds/","loop_dir":"/loops/","profiles":[> Filter: .TXT
TEST1.TXT
WMIC_BGL.TXT
> Load Settings File /profiles/TEST1.TXT
> Opening file /profiles/TEST1.TXT
{"name":"TEST1.TXT","desc":"Wireless w Chatter "},> Load Settings File /profiles/WMIC_BGL.TXT
> Opening file /profiles/WMIC_BGL.TXT
{"name":"WMIC_BGL.TXT","desc":"Wireless w Chatter "}],"mute":0,"bg":0}}

EDIT: removed problem issue which was the result of an unsupported file name (file name > 8 chars)

 

Sometimes it takes me two or more attempts to save a configuration or select a new profile as the default profile. The former is more annoying because I have to attempt a save again and re-enter the name and description.

> RX: save=6e1f193819d526|WMIC_BGL;Wireless w Chatter
> BLE Cmd: save Value: WMIC_BGL;Wireless w Chatter Uid: 6e1f193819d526
> RX: save=6e1f193819d5263|WMic_BGL;Wireless w Chatter 
> BLE Cmd: save Value: WMic_BGL;Wireless w Chatter  Uid: 6e1f193819d5263
>save=WMic_BGL;Wireless w Chatter <
> Save settings file WMic_BGL.TXT with description Wireless w Chatter 
> Backup File: /profiles/WMic_BGL.BAK
> Opening file /profiles/WMic_BGL.BAK
> Opening file /profiles/WMic_BGL.TXT
> **ERROR** creating backup file!
> Save to: /profiles/WMic_BGL.TXT
> Opening file /profiles/WMic_BGL.TXT
Settings saved to /profiles/WMic_BGL.TXT
{"cmd":"save","data":"1"}

> RX: config=6e1f193819d5263
> BLE Cmd: config Value:  Uid: 6e1f193819d5263
> Sending config
{"cmd":"config", "data": { "ver":"3.0",> Filter: .WAV
STARTUP.WAV
"sounds":["STARTUP.WAV"],"effects":[],> Filter: .WAV
"loops":[],> Get setting: profile
> Check setting profile = SAMPLE.TXT
> Return value SAMPLE.TXT
"default":"SAMPLE.TXT","current": {"name":"WMic_BGL.TXT","desc":"Wireless w Chatter "},"name":"Wireless w Chatter ","volume":0.5000,"mic_gain":3,"linein":5,"lineout":29,"startup":"","loop":"","loop_gain":2.0000,"high_pass":0,"voice_gain":1.0000,"voice_start":0.0700,"voice_stop":0.0200,"silence_time":350,"button_pin":0,"button_click":"","input":0,"effects_gain":5.0000,"eq":0,"eq_bands":"-1.0000,0.0000,1.0000,0.0000,-1.0000","bitcrushers":"12,16384,10,10240","noise_gain":0.0000,"effects_dir":"/effects/","sounds_dir":"/sounds/","loop_dir":"/loops/","profiles":[> Filter: .TXT
SAMPLE.TXT
WMIC_BGL.TXT
> Load Settings File /profiles/SAMPLE.TXT
> Opening file /profiles/SAMPLE.TXT
{"name":"SAMPLE.TXT","desc":"Sample Profile"},> Load Settings File /profiles/WMIC_BGL.TXT
> Opening file /profiles/WMIC_BGL.TXT
{"name":"WMIC_BGL.TXT","desc":"Wireless w Chatter "}],"mute":0,"bg":0}}

> RX: default=6e1f193819d263|WMIC_BGL.TXT
> BLE Cmd: default Value: WMIC_BGL.TXT Uid: 6e1f193819d263
> RX: default=6e1f193819d5263|WMIC_BGL.TXT
> BLE Cmd: default Value: WMIC_BGL.TXT Uid: 6e1f193819d5263
>default=WMIC_BGL.TXT<
> Setting default profile to WMIC_BGL.TXT
> Filter: .TXT
SAMPLE.TXT
WMIC_BGL.TXT
> Saving config data:
> Opening file SETTINGS.TXT
> 0: profile=WMIC_BGL.TXT
> 1: access_code=76253
> 2: debug=1
> 3: echo=1
> Startup Settings Updated
> Default profile set
{"cmd":"default","data":"1;WMIC_BGL.TXT"} 

I also now have problems deleting profiles.

> RX: delete=6e1f193819d5263|WMIC_BGL.TXT
> BLE Cmd: delete Value: WMIC_BGL.TXT Uid: 6e1f193819d5263
>delete=WMIC_BGL.TXT<
> Deleting file /profiles/WMIC_BGL.TXT
> Cannot delete current profile
{"cmd":"delete","data":"0;Could not remove profile"}

I can deleted the Sample profile...

> RX: delete=6e1f193819d5263|SAMPLE.TXT
> BLE Cmd: delete Value: SAMPLE.TXT Uid: 6e1f193819d5263
>delete=SAMPLE.TXT<
> Deleting file /profiles/SAMPLE.TXT
> Get setting: profile
> Check setting profile = WMIC_BGL.TXT
> Return value WMIC_BGL.TXT
{"cmd":"delete","data":"1;SAMPLE.TXT"}

... the remaining profile was uncorrupted, but would not load onto the Config Manager screen. I verified the files on my PC, reloaded the Sample.txt profile, deleted the TK76253_BL.txt file, and loaded it back into the TK Talkie. All the profiles came up OK. I even deleted a few more and everything is OK, for now.

 

I'm worried there's a pointer error somewhere in the COnfig Manager that may not be acting correctly. Last night, I deleted the last profile and then everything else became corrupted. but when I did that today, the other profiles were seemingly OK.

Edited May 5, 2017 by TKSnake

[lerxstrulz]

Here are the rules profile deletion follows:

 

1.  Cannot delete the currently loaded profile:

 

 

I also now have problems deleting profiles.

> RX: delete=6e1f193819d5263|WMIC_BGL.TXT
> BLE Cmd: delete Value: WMIC_BGL.TXT Uid: 6e1f193819d5263
>delete=WMIC_BGL.TXT<
> Deleting file /profiles/WMIC_BGL.TXT
> Cannot delete current profile
{"cmd":"delete","data":"0;Could not remove profile"}

 

 

 

 

2.  If the profile you are deleting is the default profile, it sets the currently loaded profile to default and updates the settings file.

 

The next update will have some better error messaging regarding these rules.

 

 

 

When I loaded the Sample profile on the app and click Save, it came up with the hidden profile's name TK76253_BGL. However, when I tried to save using this name, the app errored out.

> RX: save=6e1f193819d5263|TK76253_BGL;TK WMic with BGL
> BLE Cmd: save Value: TK76253_BGL;TK WMic with BGL Uid: 6e1f193819d5263
>save=TK76253_BGL;TK WMic with BGL<
> Save settings file TK76253_BGL.TXT with description TK WMic with BGL
> Backup File: /profiles/TK76253_BGL.BAK
> Opening file /profiles/TK76253_BGL.BAK
> Opening file /profiles/TK76253_BGL.TXT
> **ERROR** creating backup file!
> Save to: /profiles/TK76253_BGL.TXT
> Opening file /profiles/TK76253_BGL.TXT
**ERROR** saving to: /profiles/TK76253_BGL.TXT
{"cmd":"save","data":"0"}

 

 

It was definitely having a problem writing to the SD card.  In the photo above, it looks like Windows is seeing the (TKTalkie) SD card as a hard drive.  I see other entries that have SD next to them.  Did you use the SD Formatter on it?  Have you tried any other cards?  If that happens again, can you connect via the serial console and enter "files" (no quotes) and see if it can list the contents of the card?  

 

And yes, SD card library only supports the 8.3 filename format, so longer filenames can cause an issue.

Edited May 3, 2017 by lerxstrulz

[TKSnake[TK]]

Here are the rules profile deletion follows:

 

1.  Cannot delete the currently loaded profile:

 

 

 

 

 

2.  If the profile you are deleting is the default profile, it sets the currently loaded profile to default and updates the settings file.

 

The next update will have some better error messaging regarding these rules.

 

 

 

 

It was definitely having a problem writing to the SD card.  In the photo above, it looks like Windows is seeing the (TKTalkie) SD card as a hard drive.  I see other entries that have SD next to them.  Did you use the SD Formatter on it?  Have you tried any other cards?  If that happens again, can you connect via the serial console and enter "files" (no quotes) and see if it can list the contents of the card?  

 

And yes, SD card library only supports the 8.3 filename format, so longer filenames can cause an issue.

 

I don't think the rule I was trying to delete was the default profile. I usually switch the default to another rule before I delete because I figured this would be an issue.

 

And yes, I forgot to run the files command, but I think the reason it couldn't overwrite is because, as you mentioned, the program uses the 8.3 filename format, and therefore it couldn't overwrite due to the filename length. Therefore, you can disregard any report I made regarding the TK76253_BGL.TXT file as the name isn't supported anyhow.

 

I'll keep messing around with it. I used the SDCard formatter yesterday and today after my profiles became corrupted, but there's always a chance that perhaps the card is just going bad and it's not actually an issue with the app or TKTalkie software. I may try a different SD card or buy a new low-capacity HD card to compare performance.

 

Thanks for your help and developing something awesome

Edited May 3, 2017 by TKSnake

[lerxstrulz]

I don't think the rule I was trying to delete was the default profile. I usually switch the default to another rule before I delete because I figured this would be an issue.

 

 

You can delete the default (startup) profile...it will just update your settings to use the one that is currently loaded, so no worries.

 

And yes, I forgot to run the files command, but I think the reason it couldn't overwrite is because, as you mentioned, the program uses the 8.3 filename format, and therefore it couldn't overwrite due to the filename length. Therefore, you can disregard any report I made regarding the TK76253_BGL.TXT file as the name isn't supported anyhow.

 

Yeah unfortunately that's a limitation of the SD card library...boo.  I looked at another library, but there was a big speed difference.

 

I'll keep messing around with it. I used the SDCard formatter yesterday and today after my profiles became corrupted, but there's always a chance that perhaps the card is just going bad and it's not actually an issue with the app or TKTalkie software. I may try a different SD card or buy a new low-capacity HD card to compare performance.

 

I've had a couple cards go bad...and not cheap cards either lol.  I have noticed these little micros like to be left alone for the most part To be fair while I'm going through my testing protocols the card gets inserted and removed one BILLION times (it's Science...) I have been using the SanDisk HD cards but recently switched to a PNY HD card and it is working just as well and does not cost as much

 

it's not actually an issue with the app or TKTalkie software

 

Don't worry brother...I'm not one of those devs that believes I write perfect code...I've been doing this long enough to leave ego out of it.  I use this project as well so I want it to work and work WELL and welcome all feedback.  There are a things in there that are improvements offered by others.  We used to have a guy at work we called "Works for me" because that was always his answer when you had any issues with his code (he no longer works here lol.)  I appreciate the feedback!

 

Thanks for your help and developing something awesome 

 

No sweat man...thank you for your help!

[Airborne Trooper[501st]]

Works great now! Only thing I can think of next is putting the calibrate feature in the app.

[lerxstrulz]

Works great now! Only thing I can think of next is putting the calibrate feature in the app.

 

I may add that later, I thought it wasn't really needed simply because you can easily adjust these values on the fly with the app and test quicker than you could with the serial interface

[Airborne Trooper[501st]]

I've got to remember to do that tonight actually with my fans on and everything. I have a convention this weekend so want everything perfect. 

[TKSnake[TK]]

Question: I barely have my Pyle Pro turned up but the LIne Out volume from the TK Talkie is still very loud. Seems like the app only lets me turn the Line OUt Volume down to 13. Is there any way to turn it down farther so I have more gain control on the Pyle Pro and don't risk having the Pyle Pro too loud or making feedback into the mic so easily? This was a big issue yesterday on my May the 4th troop.

Edited May 5, 2017 by TKSnake

[lerxstrulz]

Question: I barely have my Pyle Pro turned up but the LIne Out volume from the TK Talkie is still very loud. Seems like the app only lets me turn the Line OUt Volume down to 13. Is there any way to turn it down farther so I have more gain control on the Pyle Pro and don't risk having the Pyle Pro too loud or making feedback into the mic so easily? This was a big issue yesterday on my May the 4th troop.

 

Actually, that particular setting works in reverse. 13 is loudest.  And I just realized that is not indicated anywhere. The audio board works that way for some reason.  Try turning it "up" on the app and it should get quieter.  The valid settings are 13 to 31...again...idk why they built the board that way. As a matter of fact I'm adding that to the next release so that it is more user friendly.  I have mine set on 27.

Edited May 5, 2017 by lerxstrulz

[TKSnake[TK]]

Actually, that particular setting works in reverse. 13 is loudest.  And I just realized that is not indicated anywhere. The audio board works that way for some reason.  Try turning it "up" on the app and it should get quieter.  The valid settings are 13 to 31...again...idk why they built the board that way. As a matter of fact I'm adding that to the next release so that it is more user friendly.  I have mine set on 27.

 

Thank for the clarification. It sounds like my audio receiver, wherein setting it to -40dB is quieter than setting it to -10db. Perhaps adding a negative (-) to the value in the GUI (and maybe having the slider work in reverse) could help make it more intuitive. Just my 2 credits

Edited May 5, 2017 by TKSnake

[lerxstrulz]

Thank for the clarification. It sounds like my audio receiver, wherein setting it to -40dB is quieter than setting it to -10db. Perhaps adding a negative (-) to the value in the GUI (and maybe having the slider work in reverse) could help make it more intuitive. Just my 2 credits

 

This is what happens when you let engineers design user interfaces

[Airborne Trooper[501st]]

Forgot to tell you that everything worked great last weekend at our local comic con we did Saturday and Sunday. 

[TKSnake[TK]]

Mine is also working good!

 

I think I narrows the problems I have down to one of the RX or TX wires between the BLE module and the main board, on the BLE side. Might need to take off the shrink wrap, re-solder, and then re-wrap. Seems like there's a possible open. When I fiddle with the wire, the app works fine, and it's snappy.

 

I like this box and am trying to get the word out to some fellow Anovos builders on FB  

Edited May 19, 2017 by TKSnake

[Airborne Trooper[501st]]

On the tutorial for the BLE, the RX and TX labels are wrong for the male 3.5mm jack. Once I swapped it around mine began working.

[TKSnake[TK]]

On the tutorial for the BLE, the RX and TX labels are wrong for the male 3.5mm jack. Once I swapped it around mine began working.

 

The placement is good, but I think I have a loose female pin connector on one of my wires, so I'll need to solder it on instead of relying on clamping alone.