Muhammad Awais

JSON, or JavaScript Object Notation, is a lightweight open standard format that uses human-readable text to transmit data objects in the form of pairs of attributes and values. It is used primarily to transmit data between a server and a web application as an alternative to formats and languages such as XML for lightweight, flexible formatting of data for Internet communication in a way that is both machine-readable and human-readable.

Let’s look briefly at how JSON can be used, how it compares to XML (Extensible Markup Language), and the role JSON can play as a lightweight format for information transport in Internet of Things and embedded applications. In an Internet-of-Things application, every “Thing” connected to the network should have an API that allows access to key data elements.

This data needs to be streamed at an appropriate rate over the Internet to a server directly, or to a gateway or other device in the local network. Near-real-time access to sensor data at the gateway or at the server allows contextual information derived from that data to be served up in a timely manner, so minimising network overheads is clearly valuable.

JSON

Although originally derived from the JavaScript scripting language, JSON is a language-independent data format and code for parsing and generating JSON data is readily available in a large range of programming languages, making it easy to get up and running with the language of your choice. JSON objects are human readable – they are basically freeform text documents. Whilst JSON objects contain rich information and are a highly flexible way to represent data, they are easy for programmers and database administrators to use.

XML is well established as a language of choice to describe structured data and to serialise objects, and various XML-based protocols exist to represent the same kind of data structures as JSON for the same kind of data interchange purposes. When data is encoded in XML, the result is typically larger than an equivalent encoding in JSON, mainly because of the presence of closing tags in XML.

While the API is a key consideration in implementing a RESTful solution for moving around and accessing your data, the format of the payload is also equally as important. XML is one traditionally popular language in these sorts of applications, but JSON is not as verbose as XML and does not contain detailed processing instructions. Being a more lightweight data interchange format, it is faster to use JSON to send bits of data, such as data from a sensor for example, around the Internet of Things.

JSON is promoted as a lower-overhead alternative to XML, providing similar data exchange capabilities with support for creation, reading and decoding of data in the real world with lower overhead. The increasing popularity of REST over SOAP in modern APIs also promotes greater use of and support for JSON as the preferred data exchange format, since you are no longer limited to only returning XML.

JSON-RPC is an RPC protocol built on JSON, as a replacement for XML-RPC or SOAP. It is a simple protocol that defines only a handful of data types and commands. JSON-RPC allows for notifications – information sent to the server that do not require a response – and for multiple calls to be sent to the server that may be answered out of order. This flexibility in choosing messaging options to get the data where it is needed with the priority that is needed in the most lightweight possible way is attractive in resource-constrained and bandwidth-constrained Internet-of-Things networks or embedded systems.

JSON1

Modern web browsers incorporate native JSON encoding and decoding, increasing performance due to the fact that functions no longer need to be parsed as well as eliminating potential security vulnerabilities where JSON is evaluated as Javascript. Native JSON is generally faster compared to the JavaScript libraries used in the past to parse JSON, as well as more secure.

As an example of JSON in use for an existing embedded Internet-of-Things solution, the “Razberry” platform. This adds the hardware required for the Z-wave wireless home automation protocol to the Raspberry Pi single-board computer, turning an inexpensive device into a Z-wave home automation gateway and exposing control of your home automation network via a JSON interface.

Furthermore Google BigQuery added support for JSON a few years ago, explicitly mentioning the potentially useful role of JSON in connecting data collected from sensor networks and the Internet of Things to BigQuery, bringing the power of Google’s Big Data manipulation expertise together with the Internet of Things and sensor networks as the sources for that Big Data.

JSON is one of many tools available in the Internet-of-things toolbox, and can easily be used with many applications. And here at the LX Group our engineers have an excellent understanding of the standards required for effective communciation between devices within Internet-of-things platforms, and are ready to integrate it with your new and existing products.

To get started, join us for a confidential discussion about your ideas and how we can help bring them to life – click here to contact us, or telephone 1800 810 124.

LX is an award-winning electronics design company based in Sydney, Australia. LX services include full turnkey design, electronics, hardware, software and firmware design. LX specialises in embedded systems and wireless technologies design.

Published by LX Pty Ltd for itself and the LX Group of companies, including LX Design House, LX Solutions and LX Consulting, LX Innovations.

Muhammad AwaisJSON – the Open Data Object

The Bluetooth Special Interest Group has recently announced the publication of the Bluetooth 4.1 Specification with some interesting improvements to the standard, which greatly increase the usability of this wireless technology in devices for the “Internet of Things”, which offers new applications that allow such devices to serve as both hub and peripheral devices.

This paves the way for Bluetooth 4.1-enabled devices such as sensors to connect directly to the Internet. It also allows devices such as fitness dataloggers and headsets to collate data from sensors such as temperature sensors and heart rate monitors over Bluetooth networks then report back to a smartphone or tablet with their collected data. In turn, those devices could be used as sensors that other devices can communicate with and pull data from.

This new profile is the first major update of the Bluetooth specification since version 4.0 was released in 2010, including the Low Energy specification, a subset of version 4.0. The version 4.1 updates are all software related, so it is possible for over-the-air firmware updates to upgrade existing Bluetooth 4.0 systems with new firmware, with no hardware changes or replacement, to make them Bluetooth 4.1 compatible.

Bluetooth 4.1 adds support for bulk data transfers at higher data rates, so that information collected from sensors over a period of time can be downloaded in bulk from multiple sensors. Bluetooth is still a low data-rate protocol compared to, say, Wi-Fi or Ethernet, but as Bluetooth is expected to handle ever-larger streams of data from embedded sensors this is a useful improvement – downloading data from sensors to a datalogging appliance might take, say, a few seconds instead of 10 or 20 for existing systems.

Bluetooth 4.1 allows Bluetooth devices to act as both a peripheral device and a hub at the same time, allowing a Bluetooth device that may have previously been networked with a smartphone or tablet to itself act as hub for other Bluetooth peripheral devices.

For example, your Bluetooth 4.1 enabled smart watch might be able to grab weight information logged from a Bluetooth-enabled scale and display it for you as well as being able to pass that data along to a smartphone. Bluetooth 4.1 also adds improvements to the sleep-wake cycle of the Bluetooth radio, allowing Bluetooth devices to automatically connect more easily (if allowed) without manual intervention.

Another example could be a bathroom scale that can automatically connect and download the distance walked from your Bluetooth-enabled pedometer or exercise tracker when you walk into the bathroom.

Bluetooth 4.1 improves coexistence between Bluetooth devices and 4G Long Term Evolution (4G LTE) cellular devices, to prevent potential interference. Although this is not a significant problem for Bluetooth 4.0 devices today this was considered to be a potential problem in future as more and more Bluetooth 4.0 devices are in use, talking to 4G connected smart-phones or tablets.

The new specification also increases the time-out period between devices, so that removing a Bluetooth device (such as your phone, for example) outside the proximity of another Bluetooth device it is connected to for a short moment and then back again may not mean that the Bluetooth connection has to be reconnected, improving user experience.

Furthermore it also lays the groundwork for IP-based connections between Bluetooth devices, in the same way a Wi-Fi router connects to multiple Wi-Fi devices, giving Bluetooth devices a way to talk directly to the Internet. Plus version 4.1 adds a standardised way to create a dedicated channel which could be used for IPv6 communications over Bluetooth in the future, enabling the possibility of native IPv6 networking from the Internet down to the LAN right down to wireless sensor nodes, in a similar way to how 6LoWPAN enables this type of connectivity for 802.15.4 wireless networks.

However, adding IPv6 connectivity to Bluetooth devices may substantially increase the power budget of battery-operated devices, especially Bluetooth Low Energy devices designed for extreme power efficiency, so this may not be an appropriate choice in all cases.

Bluetooth

Such Internet connectivity directly to Bluetooth devices opens up interesting potential for the future development of Bluetooth, for example phone calls made over VoIP directly to a person’s Bluetooth headset, or the remote viewing of health data from medical sensor devices by healthcare professionals.

These improvements to the Bluetooth standard, such as IPv6 support, the ability to act as a hub instead of only as a peripheral, better radio sleep-wake cycles, timeout changes and improved data rates make Bluetooth 4.1 easier to use in the development of networks of wireless, power-efficient networked devices that aren’t intended to always be paired directly to a single Bluetooth enabled smartphone or tablet – in other words, Internet-of-Things networks and devices.

As you have just read, the new Bluetooth profile offers a great amount of promise in terms of functionality and convenience for the end user. Here at the LX Group our engineers have an excellent understanding of many wireless platforms – including Bluetooth – and are ready to integrate it with your new and existing products.

To get started, join us for a confidential discussion about your ideas and how we can help bring them to life – click here to contact us, or telephone 1800 810 124.

LX is an award-winning electronics design company based in Sydney, Australia. LX services include full turnkey design, electronics, hardware, software and firmware design. LX specialises in embedded systems and wireless technologies design. https://lx-group.com.au

Published by LX Pty Ltd for itself and the LX Group of companies, including LX Design House, LX Solutions and LX Consulting, LX Innovations.

Muhammad AwaisBluetooth for the Internet-of-Things

The new ZigBee Smart Energy 2.0 (SEP2.0) ZigBee Application Profile brings with it powerful new ZigBee capabilities for smart energy metering and control networks. With its ability to transport rate, demand, and load management messages to and from networks of smart energy appliances and the “Smart Grid” across a wide variety of wired and wireless media, the profile promises to be a key element of residential energy management systems.

Capable of passing energy-related messages across a HAN, or Home Area Network, using numerous different types of wired or wireless physical media, SEP2.0 is aimed at enabling the next generation of interactive smart appliances, HVAC, lighting and energy management systems – a “Smart Grid” of energy-efficient technology.

An IP-based HAN enabled by ZigBee Smart Energy 2.0 makes it possible to manage every aspect of the energy consumption and production of a home or building, whilst moving the information around a network built entirely around the Internet Protocol and interconnected with existing networks and the Internet.

The ZigBee Smart Energy 1.0/1.1 Profile was originally developed to allow 802.15.4/ZigBee low-power wireless mesh networks to support communication between smart meters and products that monitor, control and automate the delivery and consumption of electricity – and potentially other household utilities such as gas and water, moving into the future.

The functionality of the Smart Energy 1.x Profile was primarily intended to support the functional requirements of smart meters being used by electricity, gas and water utilities to manage their distribution networks, automate their billing processes, and communicate with customers’ energy management systems.

ZigBee-enabled smart meters act as communications gateways between the utility and the consumer, enabling the exchange of messages about pricing, demand response and peak load management. At least this technical capacity exists in theory, but electricity retailers will only bother with it if they have a revenue model in implementing such technology.

The ZigBee Smart Energy 2.0 Profile was created in response to the need for a single protocol to communicate with the growing universe of energy-aware devices and systems that are becoming common in homes and commercial buildings. For that reason, a diverse range of Function Sets were defined under SEP2.0, including Demand Response and Load Control, Metering, Billing, Pre-Payment, Directed Messaging, Public Messaging, Price Information, Distributed Energy Resource Management and Plug-in Electric Vehicle Management.

One or more of these Function Sets can be used to implement one of the Device Types defined in SEP2.0, such as Meters, Smart Appliances, Load Controllers, Smart Thermostats, In-Premises Displays, Inverters and Plug-in Electric Vehicles to name just a few.

ZigBee Smart Energy 1.x access the MAC/PHY layers of the 802.15.4 radio hardware via the ZigBee Pro protocol stack, but SEP2.0 replaces the ZigBee Pro protocol stack with the ZigBee IP stack, which uses the 6LoWPAN protocol to encapsulate the proprietary ZigBee packet structure within a compressed IPv6 packet. At the transport layer, IP packets bearing messages containing standard ZigBee command and data packets are exchanged using the familiar HTTP and TCP protocols.

When used in combination with the SEP2.0 Application Profile, the ZigBee IP stack provides a media-independent interface between the network and MAC layers of the stack that allows SEP2.0 packets to be carried across nearly any IP-based network.

A recent version of SEP2.0 includes support for communication across ZigBee and 802.11 wireless LANs as well as powerline communication (PLC) networks. SEP2.0 will also have improved future support for 802.15.4g, where the physical layer of the ZigBee/802.15.4 network is a sub-gigahertz radio at, say, 900 MHz for long-range outdoor telemetry or environments where the 2.4 GHz spectrum is congested. Support is also improving for other popular network technologies such as Ethernet.

Amongst the first SEP2.0 enabled products to hit the market will be Energy Service Portals (ESPs) which serve as a bridge between an energy utility’s communication infrastructure and the IP-based Home Area Network. These portals are provided to consumers by utility companies, and use the SEP2.0 Energy Services Interface profile to provide a bridge between the SEP1.x protocol used by most existing smart meters and the home’s IP-based network.

Zigbee Smart Energy

A ZigBee-enabled home energy management system can employ multiple Application Profiles to provide unified control of all home energy systems. For example, a smart home energy management system may use the Smart Energy (SE) profile to pass the utility’s load management and demand response messages to the home’s major loads and energy sources.

The Home Automation (HA) and RF for Consumer Electronics (RF4CE) profiles may then be used to communicate with Smart Appliances, lighting systems and other consumer-controlled products. Energy-aware homes will also employ a large number of end-point applications such as smart thermostats, in-home energy displays (IHDs), and tablet-based control panels that use SEP2.0-enabled ZigBee or Wi-Fi radio links to communicate with the home’s ESI and other elements of its energy management system.

SEP2.0-equipped network endpoints may also be implemented with the physical layer of the network using power line communications, networking smart appliances without RF spectrum congestion.

The ZigBee Alliance has created well-defined provisions for interoperability with, and upgrade paths from, the earlier SEP1.x standard to SEP2.0, which is good news for engineers looking to upgrade or to interoperate with existing SEP1.x technology. There is no significant increase in the processing power required in your hardware, although the key generation and exchange functions in the SEP2.0 security layer may be tough for 8-bit microcontrollers to handle unless they have security acceleration capability, handling the cryptographic maths in dedicated hardware.

Unfortunately, in terms of memory, SEP2.0 and the applications it supports require significant increases in both flash and RAM over what is required for most SEP1.x applications. Storing the code for a SEP1.x stack, a small application profile and a simple user application requires roughly 160 kb of flash in a typical microcontroller, plus 10-12 kb of RAM. Implementing comparable functionality under SEP2.0 requires about 256 kb of flash and 24-32 kb of RAM.

As an example of an existing hardware reference solution targeting SEP2.0, Texas Instruments provides an example consisting of the CC2533 802.15.4 RF system-on-chip, which runs the MAC/PHY layers of the SEP2.0 stack on its built-in 8051 core, combined with one of TI’s ARM7 Stellaris 9000-series microcontrollers as the application processor, running the remainder of the network stack and the application code.

Most of the microcontrollers in this powerful family include a fully-integrated Ethernet MAC, CAN interface, USB host controller, and enough memory and processing power to implement many simple SEP2.0 applications.

It is also worth considering some of the highly integrated single-chip solutions on the market such as the Texas Instruments CC2538, which integrates a 2.4 GHz 802.15.4 radio, ARM Cortex-M3 32-bit microcontroller core, hardware security acceleration for SEP2.0 and plenty of flash and RAM to support the ZigBee IP stack, SEP2.0 profile and application code with support for over-the-air firmware flashing capability for updates in the field, all in a single chip.

As you have just read, the new profile offers a great amount of promise in terms of functionality and convenience for the end user. Here at the LX Group our engineers have an excellent understanding of the Zigbee platform and have put this to use to create various systems for a wide range of customers – and we can do this for you too.

To get started, join us for a confidential discussion about your ideas and how we can help bring them to life – click here to contact us, or telephone 1800 810 124.

LX is an award-winning electronics design company based in Sydney, Australia. LX services include full turnkey design, electronics, hardware, software and firmware design. LX specialises in embedded systems and wireless technologies design.

Published by LX Pty Ltd for itself and the LX Group of companies, including LX Design House, LX Solutions and LX Consulting, LX Innovations.

Muhammad AwaisThe new Zigbee Smart Energy 2.0 Application Profile

Let’s take a brief overview of the web applications and cloud platform available from Exosite – a provider of Internet-of-things cloud services that help you collect, store, visualise and interact with data from your networked devices in the cloud. Exosite provides a cloud platform that can be connected to your Internet-connected sensors and other devices.

Once your device is connected, data is flowing into the cloud and you can set up logical rules to process and act on that data, log timestamped historical data or use Exosite’s built-in scripting language to process and interact with that data. Time-series information can be used to visualise, command or control devices, either in real time or in response to trends over time.

Their platform makes it easy for product developers to create cloud-capable connected products with a range of microcontrollers and RF solutions from different hardware vendors. Exosite’s “One Platform” and “Portal” families of cloud Platform-as-a-Service and web applications provide value to developers and device OEMs, helping to minimise risk and time to market for developers of Internet-of-Things connected products. Exosite can help you to quickly prototype and deploy systems to meet your needs for cloud-based remote access to devices and their data.

Exosite’s data platform is a hosted-served system that removes barriers to market entry and empowers companies to quickly prototype and deploy their own Internet-of-Things solutions using Exosite’s web service APIs. The system is designed with product developers in mind, meaning that it has a built-in framework that eliminates the complexity of infrastructure and simplifies IoT development. Exosite’s “One Platform” makes it easy for product developers to create cloud-capable products.

Furthermore the Exosite developer site provides a wealth of convenient user guides, API documentation, application notes and support information, as well as example source code and reference projects covering a range of different programming languages and architectures. There are libraries for interaction with the Exosite API in a range of different programming languages, allowing you to work with the languages that best suit your needs.

Working and maintaining the software is simplified as Exosite supports over-the-air firmware and software updates from their cloud service, if supported in the particular hardware used. This allows for remote wireless management of your devices, allowing firmware updates, feature enhancements, and other maintenance rolled out without the need for physical on-site service of hardware devices offers great value and convenience, improving user experience and reducing support costs for networks of Internet-of-Things connected devices.

With Exosite you can build pre-configured settings in the cloud for your families of devices, enabling newly manufactured devices to know exactly what version of software to install – right from the cloud, without any local intervention – as soon as they come online on the Internet.

As well as automatic provisioning, Exosite’s built-in device management tools make it easy to manage software installations and updates. When it comes time to update your devices in the field, you can simply upload your new content, select the device model type you would like to update, and hit deploy. Your new firmware is then deployed automatically, from the cloud, to every one of your connected devices of that type out there in the world. If those devices are not always connected to the Internet, they will automatically update themselves with the new software the next time they connect to the Internet.

Gathering data from an Exosite system isn’t difficult at all, and it allows you to aggregate and monitor data from your network of devices in the cloud in real time – as well as run powerful scripts to combine multiple lower-level inputs and build custom dashboards to report on defined metrics in an easily interpretable, visible way.

Exosite is easy to integrate with other systems, allowing you to easily push data out of its cloud platform into existing, external services. Since Exosite is based around cloud infrastructure, you can scale your application without having to worry about infrastructure or server administration.

You can build your own web app, or customise Exosite’s own app. You can get started with an Exosite developer account for free and use their simple but powerful set of APIs to start interacting with your devices in real time over the Internet. When you’re ready to scale up with your commercial solution, you can easily move up to a paid account, giving you an OEM-ready “white label” platform with the features and capabilities needed to build a business around your connected Internet-of-Things application.

For a better end-user experience designers can easily customise the website theme, control the user experience, configure device options and set up pricing plans for your customers, but you can grow at your own pace without worrying about the scalability of the underlying server infrastructure.

Exosite supports a range of open source and proprietary hardware development kits and platforms, reducing the time required to develop and build Internet-of-Things connected hardware solutions. For example, Exosite provides libraries for use with Ethernet-enabled Arduino and Arduino-compatible development boards, as well as support for development kits and development boards with network and Internet connectivity from hardware vendors such as Microchip and Texas Instruments.

exosite microchip

Combining these hardware development tools with Exosite’s cloud platform allows you to get online with cloud-connected hardware quickly, getting your sensor data online and getting physical devices interacting with the cloud. Exosite makes it easy to connect, manage, and share your sensor or device data online.

Testing or getting started with Exosite is simple, as the free developer account has everything you need to start interacting with your devices in real time over the Internet. You get a web dashboard account, full access to the API, a cloud scripting environment, and the ability to upgrade features a-la-carte.

This account is aimed at allowing you to build your own Internet-of-Things environment on a one-off basis. If you find value in it and want to deploy it as a business solution for a wider audience then you can easily upgrade to a paid “white label” account in order to do so. Finally the developer account includes two devices and one user, while a paid account gives you support for many more devices, many more users, SMS messaging capability from the cloud and more.

It’s no secret that the Internet-of-things not only holds a lot of promise for connected devices and the possible products you can profit with – however getting started can seem like a maze with literally scores of options, platforms and hardware types.

To make your start in the IoT as smooth and cost-effective as possible, partner with the LX Group. We have experience in all stages of IoT product development – along with every other stage of design to manufacturing. To get started, join us for a confidential discussion about your ideas and how we can help bring them to life – click here to contact us, or telephone 1800 810 124.

LX is an award-winning electronics design company based in Sydney, Australia. LX services include full turnkey design, electronics, hardware, software and firmware design. LX specialises in embedded systems and wireless technologies design.
Published by LX Pty Ltd for itself and the LX Group of companies, including LX Design House, LX Solutions and LX Consulting, LX Innovations.

Muhammad AwaisExosite – the rapid Internet-of-things development platform

Let’s consider some of the security concerns presented by today’s connected embedded devices and “Internet of Things” networks. Where does security potentially fall down with these kinds of systems, and what can be done to keep systems secure?

Internet-of-things networks and Internet-enabled hardware appliances bring with them all the established security concerns associated with computer networks and electronic technology – for example, if users are not forced to set strong passwords, or educated in choosing good passwords, then poor passwords can be chosen. RFID access tokens can be lost by authorised personnel, as can mechanical keys.

Where security depends on a computer or electronic hardware system, an attacker with physical access to the hardware can do just about anything without restriction. Transport layer security should be used to help increase (but not make foolproof) the security of TCP/IP communications over the Internet. Wi-Fi access points shouldn’t be transmitting at excessive power levels, allowing easy abuse by people outside the intended working range of the Wi-Fi network.

All these traditional concerns about network security and physical security are maintained in an Internet-of-Things environment, but new threats and challenges are potentially emerging with the growth in connected, embedded technology. What if attackers can potentially unlock the door to your house, or maybe even set fire to your house, by exploiting vulnerabilities in a web server and manipulating Internet-connected physical devices?

Devices such as the Lockitron, a crowd-funded gadget that fits over a standard deadbolt and allows you to lock or unlock your home from a smartphone app, may be convenient to use, but is the risk of connecting Internet-based attacks and vulnerabilities with the physical environment around your home or workplace worth this convenience? Even if a server responsible for providing Internet services for Internet-of-Things deadbolts is relatively secure and hard to attack, what if breaking into a single server means you can then burgle 100, or 1000 or 10,000 homes with their doors unlocked on demand?

Furthermore, with relatively good (but never invulnerable) server-side security, this sort of attack may still be considered worthwhile by organised attackers. Where the stakes are potentially high, strong end-to-end security from the physical hardware right through to communications, Internet services, servers and mobile apps is important.

As we have an increasing level of connectivity reaching into devices that interact with the physical world the consequences of security failures escalate, as do privacy concerns. Possible remote security attacks on a car’s engine systems – because the designers decided that the car’s entertainment system should be connected to Bluetooth and Wi-Fi to allow easy upload of music and media, but that the entertainment system should also be connected to the engine management unit for some bizarre reason – could potentially be life threatening, for example.

Similarly, attacks on life-critical implanted medical devices such as insulin pumps or pacemakers are an area where serious attention is justified, given the potential for an electronic attack to mean mortal harm.

There are also privacy concerns in an environment where Internet-of-Things sensors, wireless sensor networks and machine-to-machine sensor data collection become more ubiquitous in the home. The large amount of data being collected from smart lighting, home automation appliances, smart energy management and control appliances and other sensor networks around your home could reveal a lot of information – what time you’re home, what time you’re not home, what time you sleep, how often you exercise or how often you cook, for example.

What if the information from smart energy metering appliances could be compromised by a potential burglar, who would then know what time your home is not occupied? What if data could be mined about your personal exercise or cooking habits from the fusion of information from smart appliances in your home?

lx2

Could that information be used for commercial benefit, for example by advertising or marketing agencies or health insurance providers? If your refrigerator keeps track of every food item you buy, there is obviously going to be interest – ethical or not – from market research companies, or health insurance companies, in looking to get access to this sort of information from the network.

We generally understand that information that people have generated is personal information – your information is your information, you own it and you control it, and there are expectations of privacy. But that understanding is not so clear when the information is generated by the machines around you, autonomously, without human control.

Is the information generated by your refrigerator, your lighting, your home automation appliances, exercise appliances or your car really “your” personal information which you expect privacy around? Do you “own” and control the privacy and security of that information? And is that a question that the general public is thinking about?

If all our collected data, data which may be considered personal or sensitive, is stored in the “cloud” because the cloud provides scalability, then our information is only as secure as the cloud service we use and we have no direct control over the security. So can we trust any given cloud service provider? How secure is it, really? And does a particular proprietary hardware product give us any choice in the servers or Internet services it uses?

If we unlock and lock our house with a gadget that only connects to its manufacturer’s web service on a server in a foreign country, for example, does that mean that the government of that country can legally compel that provider to provide that data on every time you arrive or leave home, no matter where in the world you live?

As you can see, integrating security into any Internet-of-things product should be a prime concern – from both a physical and software perspective. Furthermore educating the end-user through appropirate documentation is also paramount. Overall the consequences of poor security should not scare you, as these challenges can be met with the appropriate level of design.

Here at the LX Group we can help you in all stages of IoT product development, ensuring a level of security to meet your needs is included – along with every other stage of design to manufacturing. To get started, join us for a confidential discussion about your ideas and how we can help bring them to life – click here to contact us, or telephone 1800 810 124.

LX is an award-winning electronics design company based in Sydney, Australia. LX services include full turnkey design, electronics, hardware, software and firmware design. LX specialises in embedded systems and wireless technologies design.

Published by LX Pty Ltd for itself and the LX Group of companies, including LX Design House, LX Solutions and LX Consulting, LX Innovations.

Muhammad AwaisOvercoming security issues in Connected Devices

Should your next product or design be an Internet-of-Things product? That is, should every embedded design always feature Internet connectivity, or machine-to-machine communications, where the possibility exists? There are lots of different perspectives on this question, several advantages and disadvantages and pros and cons that need to be weighed up.

Although Internet-of-Things connectivity is very popular and hyped at the moment, it isn’t always going to be a worthwhile fit that provides valuable advantages for all devices in all situations.

Internet connectivity provides advantages – data collection and logging with the data stored in the cloud, accessible via the Internet from any device anywhere in the world, or the possibility of convenient remote access and control of devices via the Internet, for example, but this type of Internet connectivity brings with it concerns over security, safety and privacy.

There is a very slight potential that devices connected to the Internet can be accessed by unauthorised persons, if and only if exploitable security vulnerabilities exist. This is a serious concern for Internet services that control real, physical hardware that is potentially dangerous if misused, or for hardware that controls security-critical systems such as building access-control systems for example.

Control of security-critical real-world hardware, and the secure and confidential management of personal information (data collected from health and medical data-logging instruments such as RF heart rate sensors, for example, or information from a home automation system that indicates the typical hours that people are at home and are not at home) needs to be taken into account when deciding to have embedded automation systems exposed to the Internet.

lx1

Product designers need to consider whether the benefits of Internet connectivity are worth the risks. Consumers expect that such data will be collected and handled with some degree of privacy and security, and the convenience of Internet-based data collation and access to data will only be accepted by the market if it doesn’t also come with unacceptable privacy concerns.

If your design incorporates Internet connectivity, does this connectivity contribute to a positive, easy user experience or does it potentially make the user experience more difficult? If your product or design requires the consumer to have an existing Wi-Fi or Ethernet network to provide Internet connectivity, for example, is this inconvenient for some consumers?

Even though most consumers already have Wi-Fi networks, is the product still worthwhile for consumers that don’t? What about if the Internet connection to the LAN, or a mobile or cellular Internet connection if that’s what you’re using, fails? Can your design still function usefully in an environment without Internet connectivity, or is it completely useless?

Can the device work in a transparent, convenient way for the end user in an environment where the Internet connectivity is unreliable and may be off-line sometimes? For example, can data be temporarily buffered in local memory while the device is off-line, and then transmitted to the Internet service later, reconnecting transparently without user intervention?

Adding Internet-of-Things connectivity to a design can introduce hardware complexity, and extra cost for your device. It can mean other increased costs such as server and hosting costs, the costs of wireless LAN or other network infrastructure, the cost of cellular network access if cellular modems are used, and potentially the significant costs associated with RF regulatory compliance, testing and approval for consumer products which are intentional RF radiators. Such regulatory requirements may be simplified or eliminated if the RF connectivity component of your design is eliminated.

Are these costs worth it for the benefits? Or are you simply over-engineering, and adding “Internet of Things” connectivity because it’s in vogue and it’s a trendy buzzword? Do these features provide value for money in the context of your particular product, or are they simply features for features’ sake?

Overcomplicated, over-engineered systems that try and pack too many features into a single design can potentially suffer from disadvantages such as increased hardware cost and size, decreased market uptake due to relatively high cost, relatively high power consumption, more difficult and complicated user interfaces, and greater challenges in trying to assure the reliability, security, low maintenance and support costs of your design.

Furthermore a larger, more complicated system inevitably has more points of potential hardware (or software) failure, more work to be done in debugging and quality assurance, and more potential points of security vulnerability.

All this may sound like the Internet-of-things is a negative point of difference for existing and potential products – however this couldn’t be further from the truth. You already know that connected devices are the way of the future. The key to success in manufacturing, information security and customer satisfaction lies in the right design and working with a team who understand the IoT and how it can be put to work for your benefit.

Here at the LX Group we have experience embedded hardware design for the IoT, including security, regulatory standards and compliance testing, working within standards and design for manufacture. To get started, join us for a confidential discussion about your ideas and how we can help bring them to life – click here to contact us, or telephone 1800 810 124.

LX is an award-winning electronics design company based in Sydney, Australia. LX services include full turnkey design, electronics, hardware, software and firmware design. LX specialises in embedded systems and wireless technologies design. https://lx-group.com.au

Published by LX Pty Ltd for itself and the LX Group of companies, including LX Design House, LX Solutions and LX Consulting, LX Innovations.

Muhammad AwaisShould your product be enabled for the Internet-of-Things?

Most projects on crowdfunding platforms such as Kickstarter, especially technology projects, end up being delayed weeks, months or sometimes even more than a year beyond their “estimated delivery” date. Why do these crowd-funded technology projects seem to get delayed?

What sorts of factors are responsible for the apparent lack of on-schedule progress commonly seen with technology projects on crowd-funded platforms, and what are some of the potential perils of crowdfunding the design and production of new technology products produced by amateur industrialists on these platforms?

Delays tend to correlate with the complexity of the project, the level of over-funding, lack of maturity of the prototype engineering (which is sometimes nothing more than concept art) at the beginning of the funding campaign, and the constraints of the team running the project – for example, are they working on this project only part-time or after hours, is the project run by an individual rather than a team, and is the project being attempted with no other funding sources?

Founders of crowd-funded projects tend to be optimistic about the imminent success of their idea or product – that’s why they launched their project in the first place. As optimistic project founders see their idea through rose-coloured glasses, and they believe that their idea is the exception to the rule, and that success is imminent.

By reading about the success of other contemporary projects, or the fictionalised ease of development for iconic products such as the original Apple computer – founders can often believe that their abilities are much greater than what is truthfully so. Which is a pity – as many great ideas can be derived from those with non-engineering backgrounds.

When launching a crowd-funding campaign, it’s easy to show the things that work and gloss over the things that don’t in the launch video. It’s easy to create a computer rendering of some artwork of what you imagine that your conceptual product might look like, or even a beautiful cosmetic model that looks good with no functionality, without having an actual prototype that addresses the actual engineering risk required to implement the technical claims for the product that you’re pitching.

While some crowd-funding platforms such as Kickstarter have tightened up their rules for technology projects in this regard, it can still be a problem. The prototype engineering possessed by project creators at the time of campaign launch is often rougher than what is shown in the video, or even non-existent, without any video or images provided to the backers that show close-up detail of functional, working prototypes.

This isn’t really a reason that crowd-funded projects get delayed past the “estimated delivery date” set by project creators, but this slightly misleading behaviour can be a reason why backers get the mistaken impression that technology projects are more developed than they actually are at the time of launch, leading to unrealistic backer expectations.

Anyone can draw a picture of a flying car and claim that it’s a working, existing prototype with no engineering risk, so to address the perceived problem with unrefined and over-promised technology or “gadget” projects on Kickstarter, new rules were enacted banning product renders and simulations with no real-world substance, and requiring project leads to explain the risks that exist in the process of making their idea a reality. Over the coming years we’ll see if this improves the punctuality and delivery success rate of Kickstarter technology projects.

Another reason for possible delays is the ever-present temptation for “feature creep”, addition of new features, engineering changes or improvements. In many cases, if a new feature or concept is developed that would clearly contribute to an improved product many project creators would happily trade off some delivery delay for a superior product.

Another important factor often seen in crowd-funded projects is that many amateur engineers and product designers have little or no concept of the importance of design for manufacturability – design, documentation, assembly, construction techniques and supply chains for materials and components that are compatible with large-scale industrial manufacturing – then working with regulatory agencies to have their product approved for use in major markets can cause complete product redesigns if not planned for originally.

This is especially important for “over-funded” crowd-funded projects where the demand for the product has significantly exceeded expectations. What happens when you set a goal of $10,000 for your Kickstarter project, but eventually collect fifty times that in pledges?

The scope tends to broaden, especially with very successful projects. Big funding can catalyse big, ongoing dreams – and pursuing these dreams inevitably bleeds into the process of delivering the core expectations of the campaign itself on the promised schedule. Larger than anticipated demand also requires that highly-scalable, high-volume manufacturing processes such as injection moulding for enclosures, where it may not have been originally intended for such manufacturing processes to be used.

smartbus

Many DIY hobbyist mechanical and electronic construction projects that are hand-crafted need to be translated into a manufacturable design for scalability – PCB designs using standard photo-lithography file formats such as Gerber, with manufacturable design rules, metal and plastic parts for machining drawn up in an industry-standard fashion with materials and tolerances properly specified, cable assemblies designed and documented in a manufacturable way, etc.

Making a garage-made prototype into a design which is compatible with industrial manufacturability at any scale required can be a tricky business. DFM can be assisted by relying on the experience of your manufacturing partner and using their insights to drive design revisions, and/or by performing factory manufacturing of small sample or prototype runs, assessing the manufacturing process and the finished product and revising the design documents based on what you’ve learned.

Toolmaking for injection-moulded plastics is a well-known challenge for small or inexperienced hardware start-ups, due to its cost and the impracticality of iterative design. Even though a typical heat-treated steel injection-moulding die may be used to manufacture as many as a million plastic components at a very low cost before it needs replacement, the initial design and fabrication of the die can easily cost between $50,000 and $100,000. It can also take several weeks or months to make the tool, and if any changes or iterations of the plastic design are required then the same cost is required for a new die.

For a small hardware start-up with limited funding, mould tools really need to be designed and fabricated correctly the first time. Unfortunately, this is not easily compatible with agile, rapid iteration during your product development process, but options such as 3D printing for plastic prototyping, prototype die making in softer metals such as aluminium or diecast zinc and alternative manufacturing methods such as laser cutting, vacuum forming or thermoforming can reduce the cost burden of tooling for plastics manufacturing.

Designing your product using electronic components that can be sourced economically in sufficiently large volumes to meet scalable demand, and specifying a usable bill of materials with components sourced directly from their manufacturers and/or high-volume distributors is another potential cause of difficulties with manufacturability for designers moving into the production of a high-volume product for the first time.

It can also be difficult to convince a factory to work with you as a relatively small, new start-up, since factories tend to make their money on volume and start-ups generally can’t offer high-volume manufacturing. If a factory is willing to work with you on a moderately small volume manufacturing project it’s probably because they share your excitement about what you’re doing and they also hope that you’ll grow quickly, bringing more business for the factory along for the ride.

In short, the process of taking a great idea and developing it into a product via a crowd-funded platform can either be a total success or a complete failure. The difference in outcomes can be predicated by planning, research and teaming with experts in product design and manufacture.

If you’re considering launching the “next great thing” via a crowd-funded platform – or if you have the funding and are now at the “where do we go from here?” stage in your real product development, it pays to partner with an organisation that has experience in all stages of product design.

Here at the LX Group we have experience in short-run product development, and can scale your design for any quantity required. Don’t risk scaling up your product with hobbyist-level engineering – instead, join us for a confidential discussion about your ideas and how we can help bring them to life – click here to contact us, or telephone 1800 810 124.

LX is an award-winning electronics design company based in Sydney, Australia. LX services include full turnkey design, electronics, hardware, software and firmware design. LX specialises in embedded systems and wireless technologies design.

Published by LX Pty Ltd for itself and the LX Group of companies, including LX Design House, LX Solutions and LX Consulting, LX Innovations.

Muhammad AwaisPlanning for success with crowdfunding projects

IBM-SemtechIt seems like scarcely a week can go by without major advances in the Internet of things (IoT) sector. The latest news comes from a collaboration between Semtech and IBM that resulted in a technology capable of manage and transmitting sensor data wirelessly over a range of 9 miles (15 km), a distance that’s impressive by any measure.

 

The collaboration between tech giant IBM and Semtech (a NASDAQ-listed a company that manufactures mixed signal semiconductors) was demonstrated this week in the Semtech/Future Electronics category of the European Utility Week show in Amsterdam.

The technology is essentially a sensor platform comprising of a software and hardware element. IBM’s Mote Runner software provides the user interface and Semtech’s SX127x, an ultra-low power long-range transceiver, brings the hardware. The platform is a series of radio-frequency sensors and gateways with the customisable interface provided by IBM.

 

The Mote Runner software is already being used in a number of related applications out in the field. For example, it’s used to operate systems that measure air quality in several major cities and also to gauge snow accumulation in the Sierra Mountains in California. It affords users the ability to upload and modify applications over the air. Other possible uses include monitoring the health of manufacturing machinery, medical devices, train systems and agricultural and irrigation systems.

The package means that remote deployment, monitoring, development, integration and customisation are all possible via a simple visual interface. In short, it should be a simple task for engineers to set up and connect the many networks that will contribute to IoT as a whole.

 

The hardware aspect is brought to the IoT table by the SX127x uses Semtech’s trademarked long-range frequency modulation technology, LoRa. It was designed to significantly improve frequency modulation techniques for more reliable and stable data transmission over wireless networks. Essentially, it’s a long-range multi-modem capable of receiving several packets of data from different sources simultaneously.

 

According to the news announcement released by IBM, the pending explosion in smart connected devices will result in 2.5 quintillion bytes of new data being produced each day and it certainly seems like it wants to be the one transmitting as much of it as possible.

 

The new wireless technology may be limited depending on the lay of the land in the surrounding area. For example, to achieve the maximum range, an even landscape in a rural environment is necessary. In densely populated urban areas, the distance is likely to see a drop to around 3 miles (5 km). According to the press release, the current maximum distance for comparable technology transmitting data using a low-power system is just 1.2 miles.

 

Many are optimistic about the potential for the IBM/Semtech collaboration. One analyst from market research company, Reticle Research, told NewsFactor that it could be a “significant missing piece” slotted into the IoT puzzle. According to the director for wireless products at Semtech, Hardy Schmidbauer, “The biggest request we hear from our clients is longer battery life, low cost, ease of use and longer distances,” He went on to say that “With IBM, we now have an answer to all of these questions.”

 

It certainly seems like an interesting project so watch this space for any major developments in the upcoming months.

Muhammad AwaisIBM & Semtech Make 9-Mile Range Wireless System

When your organisation understands that creating new IoT devices is necessary, but you’re not entirely sure about the future of the technology with regards to which platform to settle on – it can be difficult to make an informed decision. The “paradox of choice” can often stall progress, until now. With the Waspmote platform from Libelium, you can use an incredibly wide range of wireless technology and platforms to meet your IoT goals.

Libelium’s Waspmote platform is an open source wireless sensor network platform specifically focussed on the implementation of low-power modes, allowing individual battery-powered nodes (or “motes”) to be completely autonomous and to run for many months or years without maintenance.

Depending on the duty cycle, types of sensors and the radio used, it is possible for a Waspmote node to run for as long as five years on a single battery. The advanced Waspmote “mote” for wireless sensor networks is at the centre of Libelium’s complete ecosystem for Internet-connected wireless sensor networks and Internet-of-Things applications.

Waspmote allows for highly flexible implementation of wireless sensor networks – the connection of almost any type of sensor you can think of to any cloud platform, using many different common wireless networking technologies. Using the waspmote platform is a great way to implement Internet-connected sensor networks for Internet-of-Things and wireless sensor network applications, with a huge range of supported sensor types as well as a range of different options for network and Internet connectivity.

There are many different options for wireless connectivity in a Waspmote system, including 3G, GPRS, 802.15.4/6LoWPAN, 802.11 WiFi and Bluetooth. A combination of multiple different radio interfaces can be chosen if desired. Both 2.4 GHz and 800 MHz ISM 802.15.4/6LoWPAN radio hardware is available for use with Waspmote. With the right choice of radio hardware, radio link distances of up to 12 kilometres are possible.

Waspmote’s hardware architecture has been specifically designed to enable extremely low power consumption. Power to any of the sensor interfaces can be turned on and off under software control, as well as power to the radio transceivers.

Three different sleep modes make Waspmote one of the most power efficient wireless sensor network platforms on the market, with a current consumption claimed as just 70 nanoamps in hibernate mode. There are more than 60 different sensors available to connect to Waspmote – soil moisture, GPS, temperature, humidity, vehicle detection, light, PIR and radiation sensors to name just a few.

The platform also supports over-the-air programming (OTAP), allowing firmware development and update across a network of wireless sensor nodes without the need for physical access to the hardware. It is possible to choose unicast, multicast or broadcast delivery of new firmware updates across the wireless network, controlling which nodes receive the update.

The huge range of different Waspmote sensors available enables a huge spectrum of different application possibilities in industrial monitoring and automation, smart cities, environmental sensing, agriculture and home automation. In a typical network of Waspmote sensors, a number of end nodes are equipped with 802.15.4/6LoWPAN hardware, appropriate sensors for the desired application, and power supplied from a battery or other sources such as solar power.

These nodes send their sensor data over the 802.15.4 mesh network back to the gateway node, which is equipped with an Ethernet interface as well as an 802.15.4 radio. The (IPv4) Ethernet gateway changes the 6LoWPAN IP header to IPv4 while keeping the UDP transport layer, and it sends the data to the IPv4/IPv6 tunnelling machine which changes the header to the proper IPv6 format and sends the information (now using IPv6) to servers on the Internet, and from there to services, and ultimately users, who use the collated sensor data.

The Meshlium gateway reads the sensor frames coming in from the nodes and stores them locally, sending them out to external cloud services on the Internet. The frames coming in from Waspmote nodes are received over the 802.15.4 mesh network and sent out to the Internet via the Ethernet, WiFi or 3G interfaces, if present.

Data is sent from the Internet-connected gateway out to a cloud server on the Internet via HTTPS and/or SSH for security, and the Waspmote ecosystem is compatible with any cloud platform you like.

Libelium Waspmote

Notably, there is no lock-in or closed compatibility with any one particular web service, unlike with some alternative products on the market targeted at Internet-connected embedded applications. You can choose your servers, and choose your cloud software platform.

As well as being based around open hardware, the Waspmote IDE is distributed under an open source license. The Waspmote platform provides professional-grade wireless sensor network infrastructure combined with a strong commitment by Libelium to the philosophy of open-source technology.

Waspmote supports encryption libraries, ensuring the authenticity, security and integrity of the information collected from the wireless sensor network. Different encryption algorithms such as AES-256 and RSA-1024 are implemented.

As well as offering cryptology and security, strong mesh-network scalability, support for 802.15.4/6LoWPAN, support for an open, flexible choice of web services and cloud server infrastructure, the Waspmote platform offers easy and fast deployment, over-the-air programming for easy firmware maintenance and an intuitive graphical programming interface.

The highly power-efficient Waspmote hardware platform also lends itself to flexible power solutions, such as battery power, remote power from solar PV, or potentially other types of energy-harvesting power supplies – as well as use in almost any contemporary application.

Waspmote offers an open, approachable and easy-to-implement platform, which we can integrate with your needs to form a solution in a short time frame and your required budget. Getting started is easy, join us for a confidential discussion about your ideas and how we can help bring them to life – click here to contact us, or telephone 1800 810 124.

LX is an award-winning electronics design company based in Sydney, Australia. LX services include full turnkey design, electronics, hardware, software and firmware design. LX specialises in embedded systems and wireless technologies design. https://lx-group.com.au

Published by LX Pty Ltd for itself and the LX Group of companies, including LX Design House, LX Solutions and LX Consulting, LX Innovations.

Muhammad AwaisWaspmote from Libelium – an open and versatile IoT platform

BRW-fast-100LX Group has been awarded top honours as one of Australia’s fastest growing businesses in the 2013 BRW Fast 100 list. LX as positioned 45 in this year’s esteemed awards due to their sustained average growth over the four years to 2013.

LX Group is a multi-award-winning Australian electronics design house traditionally specialising in wireless and low-power electronics designs. LX Group is at the forefront of IoT (Internet of Things) and M2M (Machine to Machine) technology – the convergence of hardware devices, the cloud and apps.    

LX’s motto, “we take your concept and make it a reality”, reflects their passion for innovative electronic product development.

Simon Blyth, the Managing Director of LX is ecstatic with the company’s success and attributes the growth to the LX team’s passion for what they do and their focus not just on working in the company but on developing and growing the company. “No matter how busy you are, you have to spend time working on the company. Look at where the company is now, and where it can be. Think of business initiatives as small start-ups and give them the time and attention that all start-ups need to be successful”.

The BRW Fast 100 list ranks Australia’s fastest growing, public and private, small and medium business from all of Australia’s major vertical industries who present solid business practices required to deliver exceptional growth. The BRW Fast 100 list is considered to be the premier guide to Australia’s fastest growing small and medium businesses.

The LX Team is thrilled to make its first appearance on the BRW Fast 100 List.

Muhammad AwaisLX Group 45 in 2013 BRW Fast 100 Awards!