Jump to content

lerxstrulz

501st Stormtrooper[TK]
  • Posts

    166
  • Joined

  • Last visited

Posts posted by lerxstrulz

  1. 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.

  2. Thanks. I meant to append that it is making only 3 beeps, which seems to suggest that there's an error opening up the settings.

     

    I used the SD Formatter as you suggested, but still had the same issue.

     

    It seems that I can create profiles, and can change the default to the new profile, but I can't change, delete, or set as default a previously existing profile (the latter gives me three beeps). Even the Sample Profile is affected.

    What happens if you try those commands from the serial interface?

     

    Sent from my SAMSUNG-SM-G930A using Tapatalk

  3. The Config Manager seems really buggy on my Galaxy S6.

    1. I can save a profile, but it won't show up on the list after it saves, making me thing it didn't save, When I restart the app and TK Talkie, it's there.
    2. It won't delete profiles
    • I had to manually edit the SD Card to remove some profiles and change the default profile (see below).
    1. It won't change the default profile. It worked when I switched from the Sample Profile to my first custom profile, but no longer seems to function.
    • Ex.: when I switch from my wireless mic profile to my wired mic profile, the TK Talkie produces four beeps and restarts, but the profile is still on my default profile.

    The red light stays solid on the BLE module, and I can still affect changes to other settings, like volume, mic gain playing the startup sound, etc.,, but the Config Manager doesn't seem to be as responsive. Not being able to switch between profiles or set the default profile (without removing the SD Card) is worrisome.

     

    Yeah the whole point of the app is so you don't have to remove the SD card ;)  

     

    Are you saving to a new profile (i.e. changing the file name)?  It sounds like in general there is an issue accessing the SD card.

     

    The 4 beeps means it can't update the SETTINGS.TXT file, which is where the default (startup) profile entry is stored.  (http://www.tktalkie.com/troubleshoot#6)  

     

    First thing I would try is backing up the contents of the card on your computer, then reformatting it with SD Formatter.

  4. I got a present in the mail yesterday, Brent! Thanks for the quick delivery! I noticed on mine too I get the startup sound instead of clicks. Didn't have time last night to really look into it so glad Erik figured it out. I am going to redo the end of my BLE as I was getting Time Out error when trying to connect to my iPhone.

    ah the tx/rx wires are prob opposite.

     

    Sent from my SAMSUNG-SM-G930A using Tapatalk

  5. On another note, when I got my v3 set up last night, after I talked, it would play my startup sound instead of the click.and static effects. Turns out that the config that was generated pointed effects to [effects_dir=/sounds/] instead of [effects_dir=/effects/]. This is actually an artifact from the Sample Profile provided from the site. Once i fixed the directory it was business as usual.

    Thank you will get that fixed!

     

    Sent from my SAMSUNG-SM-G930A using Tapatalk

  6. Got the hardware upgraded and the sketch uploaded (no thanks to Windows messing up the file text). I was wondering: in the video you mentioned you were able to program the BLE module's name. How is this accomplished? I couldn't seem to find how to do this in the tutorial or the help file.

     

    It's a trade secret!  ;)

     

    No, actually I just built a little breadboard using "Method 3" from this page:

     

    http://www.martyncurrey.com/arduino-with-hc-05-bluetooth-module-at-mode/

     

    I'm using an Arduino nano on the board and have it setup so that I just stick the BLE in there and then program it via the serial interface.  I'll try to grab a pic of it.  It's crude but it works great ;)

  7. I've updated the page at tktalkie.com/compare and also ran across this:

     

    Troop Talk Beta for Android

     

    It's an Android app, however, it's really buggy (it IS a beta, of course) and there is significant lag between the time you talk and when you hear what you've said (it's less than a second, but still very noticeable.)  This is the main reason there has not been an Android app as of yet.  The author of the iOS app tried, I tried, but the audio processing hardware on Android is just plain slow.  You cannot get true, real-time processing.  I tried this new app and could not get any consistent results out of it.  Hopefully Android ups their game on their audio hardware.

  8. Probably, I've kind of lost track of all of them now and whats stull available and what's not.

     

    edit; maybe it's time some one (ie me) did a full round up post of what's currently an option. Clearly I won't have used or even seen all of them but just a list of options and a basic summary pro/con of each would be helpful.

    I compiled a list at www.tktalkie.com/compare a while back. It was recently updated when TRamp updated their unit, but not since the TKTalkie has been offered for sale and the iOS app that is discontinued is still in there. Guess I will update it tonight.

     

    It was compiled from information from vendor websites as well as input from some of the vendors themselves.

     

    Sent from my SAMSUNG-SM-G930A using Tapatalk

    • Like 2
  9. The SD card is good. I can insert it in the card adapter and my computer reads it just fine

    You might want to format it with the SD card formatter anyway...Most SD cards come "computer" formatted for cameras and phones which is a little different. It might not make a difference, but best to cover all bases. I did have a card that I formatted using my computer and then couldn't read it on the audio shield. It worked after I used the SD card fornatter.

     

    Having said that I just picked up a PNY ultra hd card and it worked right out of the box.

     

    Sent from my SAMSUNG-SM-G930A using Tapatalk

  10. LOL I have the absolute worst luck. I'm pretty sure my audio shield shorted out last night since it refuses to read the SD card. I have a few at the house from times my several burnt Teensy 3.2. I'm hoping I can get one to work or I will just throw in the towel and order one built by Brent. At least I know my BLE works :)

    Ouch well before you do that have you tried another SD Card? Also try using the SD Card formatter listed at www.tktalkie.com/troubleshoot

     

    Sent from my SAMSUNG-SM-G930A using Tapatalk

  11. I noticed that the BLE module you photographed for the v3 tutorial has a different amount of pins than the BLE module you linked to eBay in your tutorial. Which one is the correct one to buy? I just want to make double sure before I purchase something I can't use.

     

    That one in the tutorial is just missing the two extra pins...they are not used for normal operations so either one works.  

    • Like 1
  12. I read through the Github files and know it's the SD card not being read. I am having to replace my female jack for the BLE to plug into because it's a loose fit.

     

    Yes 3 beeps means it can't load a file from the SD card.  However, the BLE should not have anything to do with that other than maybe the loose fit is causing a short or disconnect.

  13. I just downloaded a LightBlue app so I'll test when I get home from work. It would flash, then I'd enter the profile name, choose the BLE, put the code in and as soon as I would pair it the BLE light would become solid but the app froze at that greyish tint and eventually say timeout.

    Ok then​ you are getting a connection.

     

    I would double check the TX to RX connections I mentioned.

     

    Also, no you don't have to leave the BLE connected once you've got everything tuned. I do take mine with me on troops so I can adjust it to the environment if needed, but I don't leave it plugged in while I troop.

     

    Sent from my SAMSUNG-SM-G930A using Tapatalk

×
×
  • Create New...