Sensors.com (ACKme NETWORKS)  

Los Gatos,  CA 
United States
http://ack.me
  • Booth: 743


Secure device and cloud connectivity

Your Product Connected... The only complete silicon-to-cloud solution provider; Fully certified wireless modules, embedded stacks, cloud connectivity and OEM cloud solutions

Founded and based in Los Gatos California and Sydney Australia, ACKme Networks a brand of Sensors.com is radically simplifying how product companies can participate in the Internet of Things (IoT). Our customers skip years of investment and add tremendous value to their products by leveraging our complete solution of wireless modules, connectivity software, and secure cloud services to transform their stand alone products into securely connected devices that come alive with the interaction of people and content. Join the IoT revolution.d content. Join the IoT revolution!

ACKme Website:   https://www.ack.me
WiConnect API:     https://wiconnect.ack.me   (Wi-Fi)
TruConnect API:    https://truconnect.ack.me  (Bluetooth Low Energy)

Brands: ACKme Networks, Sensors.com, WiConnect, TruConnect, SDC


 Show Specials

  • In celebration of 30 Years; Sensors.com and ACKme networks is offering a 20% discount on all ACKme evaluation and development kits to any attendee of Sensorsexpo and conference.

    Bluetooth Low Energy Developers

    • AMS001-E01: Wahoo
      • The AMS001-E01 ‘Wahoo’ evaluation board provides a quick and easy way to evaluate and develop using TruConnect with the surface mount AMS001 or AMS002 Bobcat modules. Using the Bobcat modules is a breeze with Wahoo, simply power the Wahoo board via either a USB cable, a coin-cell or a Lithium-Polymer battery and start sending messages, controlling PWM and much more.

    Wi-Fi Developers

    • AMW006-A02: Mantis
      • The AMW006-A02 ‘Mantis’ is a shield type design designed to connect directly to your favourite microcontroller development tools.
         
    • AMW006-E03: The Moray
      • AMW006-E03 ‘Moray’ development & evaluation board provides a quick and easy way to evaluate and develop using WiConnect with the surface mount AMW006 Numbat module.
         
    • AMW006-E01: The Seabass
      • If rather than using WiConnect you want to develop on Broadcom WICED development environment.Seabass provides a quick and easy way to evaluate and develop using WICED with the surface mount AMW006 Moray module.
         
    • AMW004-E03: The Mackerel 
      • WiConnect development and evaluation platform for the surface-mount AMW004 Wi-Fi networking module. 
         
    • AMW004-E01: The Snapper
      • If rather than using WiConnect, you want to develop on Broadcom WICED development environment. Snapper enables development with the AMW004 WICED module using the WICED SDK. General support for WICED development is available on the WICED community forum.

     

    Just swing by our booth to pick up your discount validation voucher


 Press Releases

  • ACKme Networks changed the market with its easy-to-use Wi-Fi modules such as the AMW004 ‘Wallaby’ and AMW006 ‘Numbat’ family members, and today ACKme redefines the benchmark by which all Bluetooth Low Energy (BLE) / Bluetooth Smart modules are now measured.

    For many, BLE offered a new and easier method by which products could create a serial link with apps on smart phones and tablets but without a serial port profile supported by the native stack, developing with BLE still provides a number of hurdles.  Enter TruConnect™ and the Bobcat family of Bluetooth LE / Smart modules.

    All fully certified ACKme ‘Bobcat’ modules run TruConnect™ software, an easy-to-use application and a member of the SDConnect™ IoT software framework. The application enables full module control and configuration via a serial interface virtually eliminating the difficult and time-consuming software development effort vastly reducing product development cycles.

    Bobcat is currently available in 2 versions:

    Bobcat LP (AMS001), designed for customer applications focused on extreme low power, such as those powered by coin cell batteries. Bobcat LP offers a transmit power of +4dBm while drawing only 10.8mA, during receive it only uses 12.8mA (-94dBm) with a typical range of >50m (150ft) line of sight. Even lower current draw is possible when reducing the RF transmit output power settings.

    Bobcat LC (AMS002) is designed for customer applications where cost is key. The Bobcat LC module does not offer the additional low power capabilities of Bobcat LP but maintains identical transmit power and receive sensitivity characteristics.

    Bobcat LP and Bobcat LC both share an identical footprint and software interface, TruConnect™, allowing design transportability depending on requirements.

    Pricing around $5 USD in low production volumes. Modules and evaluation platforms can be sourced from all leading distributors.

     

    GERMAN VERSION

    LOS GATOS, Kalifornien--(BUSINESS WIRE)-- Die Firma ACKme Networks hat den Markt mit ihren benutzerfreundlichen Wi-Fi-Modulen verändert, etwa mit der Produktlinie, zu der das AMW004 „Wallaby” und das AMW006 „Numbat” gehören; heute setzt ACKme den Maßstab neu, mit dem alle Bluetooth Low Energy (BLE) / Bluetooth-Smart-Module inzwischen gemessen werden.

    Für viele Anwender ist mit BLE eine neue, einfachere Methode entstanden, nach der mit bestimmten Produkten eine serielle Verbindung mit Apps auf Smartphones und Tabletcomputern hergestellt werden kann. Ohne ein vom nativen Stack unterstütztes Serial Port Profile wirft die Entwicklung mit BLE jedoch noch immer zahlreiche Probleme auf. Hier kommen TruConnect™ und die Bobcat-Produktlinie von Bluetooth-LE- und Smart-Modulen ins Spiel.

    Alle vollständig zertifizierten ACKme-„Bobcat”-Module laufen mit TruConnect™-Software. Diese benutzerfreundliche Anwendung ist Bestandteil des Software-Frameworks SDConnect™ IoT. Die Anwendung ermöglicht die vollständige Kontrolle und Konfiguration des Moduls über eine serielle Schnittstelle, womit die Schwierigkeiten und der große Zeitaufwand bei der Softwareentwicklung praktisch wegfallen und dementsprechend die Entwicklungszyklen für Produkte stark verkürzt werden können.

    Bobcat gibt es momentan in zwei Versionen:

    Bobcat LP (AMS001), konzipiert für Kundenanwendungen mit äußerst niedrige Spannungen, etwa mit Knopfzellen betriebene Anwendungen. Bobcat LP bietet eine Übertragungsleistung von +4dBm und verbraucht nur 12,8mA; während des Empfangs braucht es nur 12,8mA (-94dBm), mit einer Sichtlinie, die gewöhnlich ein Spektrum von >50m umfasst. Auch ein noch geringerer Stromverbrauch ist möglich, wenn die Einstellungen der HF-Übertragungs-Ausgangsleistungen herabgesetzt werden.

    Bobcat LC (AMS002) ist konzipiert für Kundenanwendungen, bei denen die Kosten eine entscheidende Rolle spielen. Das Modul Bobcat LC bietet nicht die zusätzlichen Kapazitäten des Bobcat LP für niedrige Spannungen, ermöglicht aber die gleiche Übertragungsleistung und hat die gleichen Eigenschaften bei der Empfangsempfindlichkeit.

    Bobcat LP und Bobcat LC haben die gleiche Geometrie und das gleiche Software-Interface, TruConnect™. So wird Design-Transportfähigkeit nach Bedarf ermöglicht.

    Der Preis liegt bei etwa 5 US-Dollar bei niedrigen Produktionsvolumen. Module und Bewertungsplattformen können von sämtlichen führenden Vertriebshändlern bezogen werden.

    Über ACKme Networks

    Die Firma ACKme hat ihren Sitz in Los Gatos im Silicon Valley in Kalifornien (USA) und betreibt Designzentren in den USA und in Australien. ACKme hat ein Team von Branchenveteranen zusammengestellt, um drahtlose Hardware, Software und Cloud-Konnektivität zu vereinfachen.

    ACKme greift auf die führenden Standards und Tools der Branche zurück und entwickelt integrierte drahtlose Module, intelligente Software für Internet-Konnektivität sowie Anwendungen wie etwa integrierte Firmware mit vielen Funktionen, sicherem Networking-Transport, Cloud-Konnektivität und skalierbare Lösungen für die Cloud.

    Die Ausgangssprache, in der der Originaltext veröffentlicht wird, ist die offizielle und autorisierte Version. Übersetzungen werden zur besseren Verständigung mitgeliefert. Nur die Sprachversion, die im Original veröffentlicht wurde, ist rechtsgültig. Gleichen Sie deshalb Übersetzungen mit der originalen Sprachversion der Veröffentlichung ab.

  • So many new features: RESTful APIs, New webserver, mDNS device discovery, SMTP mail client, 128 Bulk Flash support and so much more!

    WiConnect

     

    • Secure HTTP webserver with RESTful API and Websockets that can be used on the wireless softAP or WLAN client interface. The web server enables 100% wireless control and data exchange with the module using a web client such as a phone, tablet or PC. See Networking and Security, HTTP Server with RESTful API.
    • responsive web application based on the WiConnect Javascript API library. The web app may be 100% customized to suit end-product requirements. The new WiConnect web app includes a web console and graphical drag and drop file browser.
    • Device discovery to enable network clients to discover ACKme devices and WiConnect services (such as the HTTP webserver), and enables WiConnect to discover services offered by network servers. The discovery protocol supports various protocols including mDNS/Zeroconf,LLMNR and Netbios. See Networking and Security, mDNS.
    • SMTP email client enabling the module to send secure email
    • Support for external bulk serial flash up to 128 MBytes. See File System, Internal, Extended and Bulk Flash.
    • Out-of-band GPIO to indicate a status change to one or more configured events e.g. TCP client data available, Network status change, etc
    • Auto-connect feature for TCP/UDP clients and UDP server. See TCP Client Auto ConnectUDP Client Auto Connect and UDP Server Auto Connect.
    • API for TCP keepalive, see Wireless Serial Port example.
    • Improved power supply monitoring and brownout performance.
    • Force safe mode option to aid validation of recovery, see App Note, Recovery from Safe Mode.
    • API to dynamically read and write all GPIOs simultaneously.
    • Automatic HTTP POST of dynamic module information to a remote HTTP server.
    • ADC lookup table automatically converts raw ADC values into meaningful pre-calibrated data.
    • Individual control of GPIO direction and output values in ultra-low power sleep mode
    • Added a Web App recovery feature to recover the web app if critical web app files are corrupted or missing, or the webserver root is misconfigured
    • Lowered sleep power dramatically: 43µA for the AMW004 (Wallaby) module, 49µA for the AMW006 (Numbat) module
    • Improved Wi-Fi roaming performance
    • Improved operation of the AMW006 UART driver
    • AMW004 Wallaby module throughput up to 10 Mbit/s, Numbat throughput up to 4 Mbit/s
    • Added a TLS server to provide a secure extension to the existing TCP server functionality
    • Added a UDP server
    • Remote file management is enhanced with the ability to download files from, and upload files to, an HTTP server
    • Precise memory management of Tx and Rx network buffers is now possible to allow throughput optimisation for transmit or receive intensive applications
    • Detailed information is now provided to show connected clients, softAP status and full details of network join results
    • Responses to commands, such as the scan or ls command, can now be buffered by WiConnect to enable even the lowest memory host microprocessors to talk to WiConnect
    • Configuration files (that contain a list of WiConnect variables) can be saved and reloaded to streamline setup after an OTA upgrade
  • TruConnect is an embedded application that provides host microprocessors with Bluetooth Low Energy (BLE) wireless connectivity. TruConnect is designed to substantially reduce design effort and aid time-to-market in applications looking for BLE connectivity to other BLE capable devices. TruConnect by Sensors.com, is designed to run on BLE modules and is fully licenced for use on all BLE modules designed and manufactured by ACKme Networks.

    A host microprocessor communicates with the application via a serial interface. A host microcontroller can configure the module and stream data to and from connected Bluetooth devices. Application operation may be customized by setting individual configuration variables.

    TruConnect provides a powerful set of commands to enable host control, together with variables to enable host configuration. Beyond commands and variables, TruConnect provides a rich feature set for wireless and peripheral command and control. TruConnect can start and stop services and use GPIOs for control and indication.

    Serial Interface

    TruConnect provides one of the easiest to use and flexible serial BLE interfaces in the industry. The TruConnect serial interface provides UART support, different serial communications modes including command mode and stream mode, and is easily configured for use by humans and machines.

    See Serial Interface.

    Bluetooth Low Energy

    TruConnect provides an easy-to-use serial API allowing you to focus your efforts on application development, rather than the time-consuming complexity and interoperability issues associated with the development of a wireless network stack.

    TruConnect supports operating the ACKme module in Central and Peripheral roles.

    See Commands and Variables.

    Peripherals

    Various peripheral APIs are available to provide access to general purpose IO function including pulse width modulators (PWM), ADCs, DACs, and standard I/O.

    See Peripherals.

     

    Release Notes for TruConnect 1.5.0

    TruConnect 1.5 provides the following new functionality as well as general improvements and stability enhancements.

    • Added an option for advertise forever in BLE peripheral mode
    • Added various scan options for BLE central mode
    • Added several options to control power consumption, including auto sleep and wake timeouts, sleepwakeand auto/manual shutdown for use with an external regulator
    • Added a 64-byte storage variable for custom data including security keys
    • Added a way to connect with and control a remote Bobcat module to access & control peripheral functions including GPIOs, ADCs, PWMs, etc.
    • Added a static GPIO activity function to indicate recent activity on the BLE or UART interface
    • Added a dynamic GPIO ble_blink function to signal data exchange on the BLE interface
    • Added a way to set the blink pattern of the status_led when connected / not connected
  • The Sensors.com TruConnect Android Library is a Java library for developing Android apps that interact with TruConnect running on fully licenced modules or products such as the AMS00x modules. Using the TruConnect Android Library you can connect to the TruConnect module, switch it to remote COMMAND mode and issue TruConnect commands to it. See Serial Interface for a description of remote COMMAND mode.

    This application note describes the TruConnect Android Library and the demonstration app. To illustrate how the library works, it describes some simple modifications to the demonstration app.

    Prerequisites

    The demonstration app requires a BLE-capable Android test device, such as a smart phone or tablet, and a Wahoo evaluation board, containing an AMS00x Bobcat module running TruConnect.

    This application note assumes some familiarity and experience with:

    • Java
    • mobile development
    • event driven application development
    • the Android SDK
    • an IDE such as Android Studio.

    Seehttp://developer.android.com/ for detailed documentation of Android development.

     

    Set Up

    Obtain a copy of the TruConnectAndroid Library fromhttps://github.com/ackme/TruConnectAndroid

    Obtain the Android SDK and Android Studio fromhttps://developer.android.com/sdk/index.html.

    Open Android Studio and import the TruConnect Android project, at the top level of the TruConnect Android Library working copy.

    Switch on USB debugging mode for your Android test device and connect it to the computer running Android Studio.

    With the factory settings, the TruConnect module begins to advertise immediately on applying power. Advertising stops after a few minutes. Press the Reset button to start advertising again.

    Alternatively, to make the TruConnect module advertise forever, open a TruConnect terminal to the module and set bl v h d : advertising high duration to 0:

    set bl v h d 0

    github.png

    AndroidStudio.png

    Structure of the TruConnect Android Library

    The TruConnectAndroid Project contains the truconnectandroid package, and the demonstration app package.

    The truconnectandroid package contains the following packages:

    • BLE - enums and classes for handling BLE commands and connections
    • test
    • truconnect - enums and classes for handling TruConnect commands and responses.

    The central class of the truconnect package is the TruConnectManager class. This contains methods corresponding to all TruConnect commands and variables. It also contains methods for handling scanning and connection from the Android device, and for sending commands and receiving command results, via the TruConnectHandler class.

     

    Building and Running the Demo App

    In Android Studio:

    • Select the app package.
    • Click the Run App button.
    • Android Studio builds the demo app, uploads it to your test device and runs it.

    With the Wahoo board:

    • Power up, or press reset to start advertising.

    The demo app has two activities, corresponding to two display windows:

     

     

    MainActivity DeviceInfoActivity 
    Command Mode
    DeviceInfoActivity 
    Stream Mode

    DeviceInfoActivity

    Data Received

     

    On startup, the MainActivity display shows.On your test device:

    • Tap the Scan button. The demo app scans, detects the TruConnect module and displays its ID.
    • Tap the TruConnect module ID in the scan list. The demo app switches to the DeviceInfoActivity display and displays some information from the sensors and buttons on the Wahoo board, connected to TruConnect module GPIOs.
      • The ADC field displays the GPIO 9 value, corresponding to the Wahoo thermistor.
      • The GPIO field displays the value of GPIO 12, corresponding to Wahoo Button 2.
      • The LED ON/OFF button controls GPIO 14, the red LED in the Wahoo tricolor LED. The button indicator is lit when the LED is on.
    • Tap the Read Values button. This sends commands to the Wahoo board, obtains the command results and refreshes the data displayed in the fields.
      • The ADC value may change. If you place a finger on the Wahoo thermistor (circled) the value may decrease as the thermistor heats.
      • If you update while pressing Button 2 on the Wahoo board, the GPIO field value changes to 1. Release Button 2, update and the value returns to 0.
    • Tap the LED ON/OFF button on your test device. The Wahoo board red LED lights in the tricolor LED.
    • Tap the Command mode button to switch to Stream mode. In Stream mode, you can send data to the Bobcat module and receive data from the module. Type in the app text field and tap Send to send data. In the TruConnect terminal on the module, type data to see the data appear immediately in the app data received panel.

     

    Structure of the Demo App

    The demonstration app contains two activities, and a service that maintains the BLE connection when switching between activities.

    The demonstration app, in the app package, contains:

    • Activity classes:
      • MainActivity - view of Scan button and the list of devices scanned
      • DeviceInfoActivity - view of connected TruConnect module information
    • Service class:
      • TruConnectService - the shared service that maintains the BLE connection to the TruConnect module
    • Device - represents a BLE device found by the scan
    • DeviceList - provides the array of devices listed in the scan list

     

    The activities receive intents from the TruConnectService as BLE events take place.

     

    Modifying the Demo App

    This section describes some simple modifications to the TruConnect Android demo app. These are intended to provide an indication of how the code is structured.

    We perform some minor re-styling, to match the http://sensors.com theme, and add another GPIO to the device info display.

    In the file paths below, /TruConnectAndroid refers to the directory containing the working copy of the TruConnectAndroid repository.

    Changing the Logo

    The ACKme logo icon used in the demo app can be replaced with a logo of your choice. The icon files are .png files located in the resource directories. The pixel resolutions are as shown below:

    • /TruConnectAndroid/app/src/main/res/drawable-hdpi/ackme_icon.png (72×72)
    • /TruConnectAndroid/app/src/main/res/drawable-mdpi/ackme_icon.png (48×48)
    • /TruConnectAndroid/app/src/main/res/drawable-xhdpi/ackme_icon.png (96×96)
    • /TruConnectAndroid/app/src/main/res/drawable-xxhdpi/ackme_icon.png (144×144)

     

    Create copies of your icon at the required resolutions in the resource directories. In our example we created icon files namedsdc_icon.png.

    The logo icon is specified in two places in the application manifest,/TruConnectAndroid/app/src/main/AndroidManifest.xml.

    Replace the instances of the line android:icon=”@drawable/ackme_icon” with a specification for your new logo. For example:

     

    ...

    <application

        android:allowBackup="true"

        android:icon="@drawable/sdc_icon"

        ... >

    ...

        <service

              android:name="ack.me.truconnectandroiddemo.TruconnectService"

              android:icon="@drawable/sdc_icon"

              ... >

        </service>

    ...

    </application>

    Rebuild the app and run it on your test device to see the changes.

    Adding a Control for Button 1

    This section demonstrates how to add a control for Wahoo Button 1 to the Device Info activity.

    Wahoo Button 1 corresponds to GPIO 6.

    The layout of the DeviceInfoActivity is specified in

    /TruConnectAndroid/app/src/main/res/layout/activity_device_info.xml.

    The (Button 2) GPIO field is specified with a TextView tag containing the attribute android:text="GPIO".

    Copy the specification for the (Button 2) GPIO TextView to create another TextView for Button 1 directly above it in the XML. Note that as well as creating the new TextView, with modified attributes, we also modified the original (Button 2) GPIO TextView attributes. This layout aligns the Button 1 and Button 2 displays horizontally:

     

    <RelativeLayout xmlns:android="http://schemas.android.com/apk/res/android"

        ...

        <TextView

              android:layout_width="wrap_content"

              android:layout_height="wrap_content"

              android:text="@string/gpio_b1_value_title"

              android:textSize="30sp"

              android:id="@+id/gpio_b1_value"

              android:gravity="left"

              android:layout_below="@+id/adc_value"

              android:layout_alignParentStart="true"

              android:layout_marginTop="30dp"/>

     

        <TextView

              android:layout_width="wrap_content"

              android:layout_height="wrap_content"

              android:text="@string/gpio_value_title"

              android:textSize="30sp"

              android:id="@+id/gpio_value"

              android:gravity="right"

              android:layout_above="@+id/led_button"

              android:layout_alignParentEnd="true" />

    ...

    In the file /TruConnectAndroid/app/src/main/res/values/strings.xml, add the button title stringgpio_b1_value_title, with content GPO B1:, above the gpio_value_title string, and modify the gpio_value_title string content to GPO B2::

     

     

      ...

    <string name="update_button_text">Read Values</string>

    <string name="gpio_b1_value_title">GPIO B1:</string>

    <string name="gpio_value_title">GPIO B2:</string>

    <string name="adc_value_title">ADC:</string>

    ...

    The remaining changes are in the file

    /TruConnectAndroid/app/src/main/java/ack/me/truconnectandroiddemo/DeviceInfoActivity.java.

    At the beginning of the DeviceInfoActivity class definition, we declare variables for Button 1:

    • the declarations for TEST_B1_GPIO GPIO number
    • the TextView instance mGPIOB1TextView
    • A flag to track updating: mGPIOB1UpdateInProgress

     

    public class DeviceInfoActivity extends Activity

    {

    public static final String TAG = "DeviceInfo";

    private static final int ADC_GPIO = 12;//thermistor on wahoo

    private static final int TEST_GPIO = 9;//button2 on wahoo

    private static final int TEST_B1_GPIO = 6; // Button 1

    ...

    private TextView mADCTextView;

    private TextView mGPIOTextView;

    private TextView mGPIOB1TextView;  // Button 1 .

    ..

    private boolean mADCUpdateInProgress = false;

    private boolean mGPIOUpdateInProgress = false;

    private boolean mGPIOB1UpdateInProgress = false; // Button 1

    ...

    In the onCreate method, add a line for the Button 1 TextView, as shown:

     

     

    protected void onCreate(Bundle savedInstanceState)

    {

    super.onCreate(savedInstanceState);

    setContentView(R.layout.activity_device_info);

    mADCTextView = (TextView)findViewById(R.id.adc_value);

    mGPIOTextView = (TextView)findViewById(R.id.gpio_value);

    mGPIOB1TextView = (TextView)findViewById(R.id.gpio_b1_value); // Button 1

    ...

    Add the TEST_B1_GPIO initialization to the DeviceInfoActivity.initGPIOs method:

     

     

    private void initGPIOs()

    {

    ...

    mTruconnectManager.GPIOFunctionSet(TEST_GPIO, TruconnectGPIOFunction.NONE);

    mTruconnectManager.GPIOFunctionSet(TEST_B1_GPIO, TruconnectGPIOFunction.NONE); // Button 1

    ...

    mTruconnectManager.GPIOFunctionSet(TEST_GPIO, TruconnectGPIOFunction.STDIO);

    mTruconnectManager.GPIOFunctionSet(TEST_B1_GPIO, TruconnectGPIOFunction.STDIO); // Button 1

    ...

    mTruconnectManager.GPIODirectionSet(TEST_GPIO, TruconnectGPIODirection.INPUT);

    mTruconnectManager.GPIODirectionSet(TEST_B1_GPIO, TruconnectGPIODirection.INPUT); // Button 1

    ...

    }

    Add a line to update the Button 1 GPIO to the DeviceInfoActivity.updateValues method, and a flag to track processing of the command:

     

    private void updateValues()

    {

    mADCUpdateInProgress = true;

    mGPIOUpdateInProgress = true;

    mGPIOB1UpdateInProgress = true; // Button 1

     

    Log.d(TAG, "Updating values");

    mTruconnectManager.adc(ADC_GPIO);

    mTruconnectManager.GPIOGet(TEST_GPIO);

    mTruconnectManager.GPIOGet(TEST_B1_GPIO); // Button 1

    }

    This has the effect of sending the TruConnect command to get the value of the Button GPIO. The response to the command is delivered by the TruConnectService as an intent with the action ACTION_COMMAND_RESULT. The BroadcastReceiver accordingly calls the handleCommandResponse method, which extracts the TruConnect command response as variable result from the Intent extra bundle.

    Finally, in the DeviceInfoActivity.handleCommandResponse method, add a case to handle the Button 1 GPIO update. Note that the commands are queued and processed in the order called. In the updateValues() method, the GPIO get command for Button2,TEST_GPIO, is called first, so the corresponding flag mGPIOUpdateInProgress is processed first when handling the command response.

     

    private void handleCommandResponse(Intent intent)

    {

    ...

    switch (command)

    {

    ...

    case GPIO_GET:

    if (mGPIOUpdateInProgress)

    {

    message = String.format("GPIO B2: %s", result);

    mGPIOTextView.setText(message);

    mGPIOUpdateInProgress = false;

    Log.d(TAG, "Updating "+message);

    }

    else if(mGPIOB1UpdateInProgress)

    { // Button 1

    message = String.format("GPIO B1: %s", result);

    mGPIOB1TextView.setText(message);

    mGPIOB1UpdateInProgress = false;

    Log.d(TAG, "Updating "+message);

    }

    ...

     

    Build and run the app to see the result of these changes.

    Press Button 1 on the Wahoo and click the Update button on the app.

     

    for more information check out: https://truconnect.ack.me


 Products

  • AMW004 (Wallaby)
    802.11b/g/n low power Wi-Fi networking module...

  • Our AMW004 ‘Wallaby’ module is a fully certified small form factor, low power WICED-based Wi-Fi networking module perfectly suited to deeply embedded applications requiring medium/high data throughput in medium to high volume.

    The module runs an embedded TCP/IP networking stack with SSL/TLS/HTTPS security and an onboard u.FL and PCB trace antenna all in a physical footprint of just 31.2 x 17.8mm (1.25" x 0.7").

    Wallaby ships with WiConnect firmware, our easy-to-use and reliable serial Wi-Fi networking application that includes free support for cloud connectivity powered by Sensors.com (usage optional).

  • AMW006 (Numbat)
    Ultra-low power Wi-Fi networking module for battery powered applications...

  • The AMW006 ‘Numbat’ module, is an ultra-low power Wi-Fi networking module with full regulatory certification. Featuring an low-power MCU, it is designed for battery operated applications requiring moderate data throughput in any volume.

    The module runs an embedded TCP/IP networking stack & webserver with RESTful API/websockets and  SSL/TLS/HTTPS security, and offers RF pads allowing for maximum antenna flexability.

    Numbat ships with a licensed version of WiConnect, our reliable and easy-to-use serial Wi-Fi application that includes free support for cloud connectivity powered by Sensors.com (usage optional).

  • AMS001 'Bobcat LP'
    AMS001 'Bobcat LP - Ultra Low Power BLE module...

  • GET TO MARKET, FAST!

    The ‘Bobcat’ family of Bluetooth SMART modules from ACKme Networks vastly reduces development effort and fast-tracks your latest wireless product to market.

    Focused on ultra-low power, the AMS001 ‘Bobcat LP’ module is a fully certified small form factor Bluetooth Low Energy (Bluetooth SMART) module perfectly suited to battery powered operation for medium to high-volume applications.

    The AMS001 module provides an integrated Bluetooth Low Energy stack (4.1), support for SECURE over the air (OTA) upgrade and includes an on-board PCB-style antenna all in a physical footprint of just 17.6 x 11.4 x 2.3 mm.

    ACKme's TruConnect firmware is pre-installed on all Bobcat modules. TruConnect is an easy-to-use application enabling module control and configuration via a serial interface. TruConnect virtually eliminates difficult and time-consuming software development effort and vastly reduces product development cycles.

    Ideal for Wireless cable replacement, Battery status, Blood pressure monitor, Proximity, Thermometer, Glucose meter, plus much more

  • AMS002 'Bobcat LC'
    AMS002 'Bobcat LC' - Low Cost BLE module...

  • GET TO MARKET, FAST!

    The ‘Bobcat’ family of Bluetooth SMART modules from ACKme Networks vastly reduces development effort and fast-tracks your latest wireless product to market.

    Focused on low cost, the AMS002 ‘Bobcat LC’ module is a fully certified small form factor Bluetooth Low Energy (Bluetooth SMART) module perfectly suited to battery and line powered operation for medium to high-volume applications.

    The AMS002 module provides an integrated Bluetooth Low Energy stack (4.1), support for SECURE over the air (OTA) upgrade and includes an on-board PCB-style antenna all in a physical footprint of just 17.6 x 11.4 x 2.3 mm.

    ACKme's TruConnect firmware is pre-installed on all Bobcat modules. TruConnect is an easy-to-use application enabling module control and configuration via a serial interface. TruConnect virtually eliminates difficult and time-consuming software development effort and vastly reduces product development cycles.

    Ideal for Wireless cable replacement, Battery status, Blood pressure monitor, Proximity, Thermometer, Glucose meter, plus much more


Send Email

Type your information and click "Send Email" to send an email to this exhibitor. To return to the previous screen without saving, click "Reset".