Jump to content

Search the Community

Showing results for tags 'IridiumSBD'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • News
    • Announcements
    • Suggestions
    • New users say Hi!
  • Spotlight!
    • Sponsor Spotlight
    • Sponsor Giveaways
  • Energia
    • Energia - MSP
    • Energia - TivaC/CC3XXX
    • Energia - C2000
    • Energia Libraries
  • MSP Technical Forums
    • General
    • Compilers and IDEs
    • Development Kits
    • Programmers and Debuggers
    • Code vault
    • Projects
    • Booster Packs
    • Energia
  • Tiva-C, Hercules, CCXXXX ARM Technical Forums
    • General
    • SensorTag
    • Tiva-C, Hercules, CC3XXX Launchpad Booster Packs
    • Code Vault
    • Projects
    • Compilers and IDEs
    • Development Kits and Custom Boards
  • Beagle ARM Cortex A8 Technical Forums
    • General
    • Code Snippets and Scripts
    • Cases, Capes and Plugin Boards
    • Projects
  • General Electronics Forum
    • General Electronics
    • Other Microcontrollers
  • Connect
    • Embedded Systems/Test Equipment Deals
    • Buy, Trade and Sell
    • The 43oh Store
    • Community Projects
    • Fireside Chat
  • C2000 Technical Forums
    • General
    • Development Kits
    • Code Vault
    • Projects
    • BoosterPacks


There are no results to display.

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start



Website URL





Found 1 result

  1. While working with Mikal Hart's IridiumSBD library I ran into a problem if I tried sending a message that exceeded 120 characters in length. Considering I'd paid $250 for the transceiver which claims a 340 character message capability, I was a bit frustrated, to say the least. FWIW, Sparkfun support was responsive, though not clear on the solution. However, after spending time doing the requisite RTFM, coupled with examining the code, I realized that the library didn't check, or account for, two different versions of the AT+SBDWT command. If the command AT+SBDWT= is issued, followed by a text string, the limit is 120 characters, and anything longer generates an "ERROR" response. If, instead, an AT+SBDTW command, no "=" sign, is issued, the device responds with "READY" and expects a text string of up to 340 characters (within 60 seconds), and on success issues a "0" response. Mikal's code doesn't check the length of the submitted string, and triggers an error, but with no other explanation. I added a test for the string length (it's included in the function call) to select the appropriate command, as well as adding a new error code indicating a message length error. Given that I consider my programming skils at the beginner+ level (it's been almost 20 years since I was a "professional"), I hesitate to update the library on github. What's the best approach to save others the hours I spent tracking this down??? Bob
  • Create New...