All posts tagged: Software

Agile project management practices, which can be applied to the management of hardware development or other engineering projects – and not just the software development projects for which these methods were mostly originally developed, have the potential to deliver increased customer satisfaction compared to traditional project management methods such as the “waterfall” technique.

These improvements in customer satisfaction that can be achieved by Agile projects come about because of a combination of many different advantages that Agile practices can offer, particularly in the ways that Agile project techniques involve and engage the customer, the customer’s feedback, ideas and expertise throughout the product development lifecycle.

These Agile project management practices can increase the satisfaction of your customers by keeping the customers involved and actively engaged through the development cycle of their new product, making the customer feel like they are a valuable, integral part of the project team – which, of course, they are.

This enables rapid and precise feedback between the customer (or customer representatives and advocates on the team such as the “Product Owner”, who often play an important role in Agile project teams) and the development team.

Furthermore this also gives the development team an intimate contextual understanding of the customer’s requirements, specifications and ideas by keeping the customer or customer champion embedded in close contact with the development team. Finally, customer satisfaction is increased thanks to your progress and with the product; these practices can help to make the product itself fundamentally better, too.

Whilst these kinds of Agile project methodologies can work at their best when an actual customer representative is available frequently for team meetings, to communicate product requirements and business needs, if a customer representative is not available then the Product Owner, a role filled by one member from the project management team, can perform this role effectively.

The “Product Owner”, who is a core part of many Agile project teams, is an expert on the customer’s needs and product requirements, and serves as an advocate for customer and business outcomes, constantly directing the team in a direction that is focused on customer results and customer centred value, rather than considerations such as what is technically easiest, or technically most elegant, which otherwise may be given greater emphasis by the engineering or development teams.

Agile project management practices can deliver improved customer satisfaction and customer-focused outcomes by keeping the product backlog updated regularly and prioritised, allowing the team to quickly and efficiently respond to urgent issues, to newly established product requirements, or other changes that need to be addressed, without wasting time with less organised project management or implementing new features or changes that are less urgent and less important to the customer and business outcomes. Agile practices can also deliver improvements in customer satisfaction and product outcomes by demonstrating working functionality to customers in every sprint review.

This rapid iteration of new prototypes and repeated demonstration of working software or hardware technology gives the customer and/or the Product Owner a very clear understanding of the project progress that is being made, inspires new ideas for features or changes either in the product itself or in the ways that the product may be used or marketed, and allows for rapid discussion of changes, improvements or design specifications that are desired between the customer and the project team.

Another way that Agile management practices can result in a project with relatively strong satisfaction for the customer is by delivering products to market quicker and more often with every release.

Finally, another factor that can allow Agile project management techniques to deliver greater customer satisfaction from your project is by possessing the potential for better results with self-funded or crowd funded projects; allowing the scope, scale or schedule of a project to rapidly be changed even in the middle of the project development cycle.

This means, for example, that Agile projects can adapt to be most compatible with a changing or insecure funding environment, a self-funded environment with very limited access to cash flow and resources, a crowd funding project that has delivered funding less than what has been hoped, or a crowd funding project that has turned out much more successful than anticipated, with plenty of upfront funding available, but with demands for manufacturing scale and product fulfilment that are much larger than originally anticipated.

These and other Agile hardware development techniques can be harnessed by any organisation. However if this is new to you, or it seems like a complex path – then consult the experienced team here at the LX Group.

We can partner with you – finding synergy with your ideas and our experience to create final products that exceed your expectations.

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

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

In the adoption of Agile project management practices to the development of hardware or combined hardware-software engineering projects, and the adaptations to common Agile techniques that may be applied for best results with hardware projects, let’s consider some of the challenges that may be faced and how you might address them.

For example, do you develop software and firmware only after you’ve developed and assembled an iteration of physical prototype hardware? Or do you develop an iteration of your software and firmware concurrently with the development and assembly of the corresponding hardware and use other methods such as simulation to stand in for the hardware until an iteration of the physical hardware is ready?

When using Agile project management techniques, it is desirable to be able to rapidly produce and demonstrate a working prototype of your technology and to rapidly iterate and refine and build on each prototype without necessarily having a perfectly engineered product ready to go at the first iteration. When you’re working with hardware, however, you need to deal with the lead time required to source components, to fabricate printed circuit boards, to have prototype layouts assembled by an external pick-and-place assembly contractor or to have custom plastics injection-moulded and so on.

What if the lead-time required for these processes is longer than the time allocated to a particular iteration or sprint? These types of external supply and manufacturing dependencies are unique to hardware, and aren’t present in software development – so they present a unique challenge when trying to apply agile methods to the management of hardware projects. While these constraints may seem like a daunting challenge to adoption of Agile in the hardware engineering industry, techniques and tools such as in-house rapid prototyping, 3D printing, CNC milling of simple PCBs and the like present part of a potential solution, allowing for rapid, agile iteration of hardware prototypes.

A prototype iteration of a hardware system doesn’t have to physically involve hardware, either. Simulation and visualisation tools can play a valuable role of validating the design and performance of all the components that come together into a new product, even before a prototype is actually physically constructed. FPGAs and logic synthesis may also be valuable tools here, allowing for validation of soft cores before physical hardware is constructed. One of the challenges for combined software and hardware development is that software can normally be developed fairly rapidly and the development broken down into smaller iterative chunks. Hardware, on the other hand, may require months to show a working component or feature, which has been implemented starting from scratch.

If the software development must wait for the hardware to be created before final testing, this can create significant testing delays. Hardware must also often follow strictly defined process models, meet compliance standards, and it can be difficult to make late changes to hardware. This means that feature creep can be difficult and expensive in hardware engineering, although Agile methods are traditionally more accepting of “feature creep” compared to traditional “waterfall” management methods.

Traditionally, the priority for embedded software, for example, would be to write the hardware drivers first, to allow evaluation of the new device and to allow testing. Testing is more complex when software must fit within a small, cheap microcontroller with limited resources in an embedded system, with timing well controlled to prevent race conditions and other timing issues. This means that at some point testing on the actual hardware is generally important. A problem often seen when businesses who create hardware and the software that runs it face when trying to “go Agile” is that they attempt to take methods and practices developed for software (such as Scrum, an Agile project management framework), and try to use it for everything, including hardware development.

Scrum is based upon “sprints” of relatively short lengths (two weeks to 30 days), with highly defined tasks that must be completed during the sprint. The nature of software development makes this an excellent framework for rapid progress; but scrum isn’t necessarily the best framework for hardware development. If the products are in a highly regulated industry, such as medical or aviation hardware, then the documentation must follow industry requirements for specification and design, as well as normal testing and functional requirements documentation. This makes it extremely difficult to use scrum by itself, since the processes for hardware are frequently much more rigid, defined, and design-oriented than those normally defined by scrum.

On the software side, because software must interface, communicate with, and control hardware, development issues using Agile are more complex for combined software/hardware projects, and the stories (definition of the functions for a specific feature) that the developers define for each sprint are accordingly more complex. Large projects with large amounts of hardware and software dependencies can be even more challenging.

One method of dealing with hardware that isn’t ready to test is to decouple software and hardware development, via an abstraction layer, to allow software development to continue more rapidly. Can the interfaces to the hardware module be specified, and the specifics abstracted away to allow other parts of the hardware and software development to continue around the hardware component that is behind schedule? The challenge is to find a method that allows the rapid development of software with concurrent development of the hardware, that can best meet the requirements of each process. A good approach can be the use of different Agile techniques for hardware projects than those used in software projects. Agile techniques are not abandoned – simply implemented a little differently, with different specific Agile techniques chosen for the most effective results.

With Commitment-Based Project Management (CBPM), which has been described as an “agile without using Agile” technique with broad applicability outside the software engineering sector, the emphasis is on the delivery of at least a component or piece of the hardware that works, in the case of an embedded computing or other combined hardware-software project, in order to allow the development or testing of the software that will work on that hardware component. This is very different from the traditional “waterfall” project management approach, where the entire hardware system needs to be built first. While the “scrum” method for software projects is based on sprints with small portions of the software completed at a time, hardware development can benefit from a different approach.

With Agile, both hardware and software features are broken down into smaller chunks – only the Agile methodology can be a bit different for each. Once software is working, it can be deployed either on any available hardware modules that are ready, or in a test or simulation environment. This allows the early identification and fixing of race issues and bugs that arise, and reduces the amount of “fixing” and lengthy hours reworking that must occur during late integration and testing when the hardware is ready.

And that’s the goal of successful agile development – to reduce the total time required, decreasing errors, mistakes and the chances of unforseen events, which will increase the time to market for your new or revised product. Here at the LX Group you can leverage our product development expertise and experience for your total benefit. Our consultants, engineers and experts in many fields can guide you to your goal of product success. To get started, join us for an obligation-free and confidential discussion about your ideas and how we can help bring them to life – click here to contact us, or telephone 1800 810 124.

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

Since the early days of computer and networking development in the late 20th century, the open-source hardware and software movement have become a growing force in the world of agile product development.

Using such open-source methods may seem to be a great idea, however there are some potential advantages and disadvantages of choosing to use open-source software and hardware – both using other people’s existing open software or hardware technology, or releasing your own intellectual property as open-source software or hardware for use in the development of Internet-of-Things solutions. What are some of the potential benefits and challenges associated with open source?

For some proponents of open source technology, the most important advantage of open source technology is that it is “free as in free speech”, and this means that software, updates, or other technology or support cannot be withheld by some company – åjust because it decides that you shouldn’t be using their software any more for whatever reason; they can’t just take their ball and go home.

With open-source software or hardware nobody can stop you from using it down the line, and there is at least some form of future access to the technology, even if it is obsolete, less popular or less well supported in the future.

Another key selling point often associated with open software or open hardware is that it is often, if not usually, free as in zero money. Sometimes developers or software vendors may provide an upgraded product, special features or special paid maintenance or support for an open source product – where these special features are commercialised on top of an underlying open-source platform, but generally the underlying open software or hardware technology is freely available for you to work with.

With modern Internet bandwidth, free software can easily be distributed in minutes via Internet download, without the cost of distributing or producing physical disk media. This makes it possible to get free software into the hands of users cheaply and conveniently, which is obviously good for the user, but also good for the software developer because new software can reach many users much faster, getting used in people’s hands sooner and with much greater potential uptake. This can be particularly attractive to small, independent developers.

Obviously in the case of Open Hardware this is a little different, since hardware still costs money to manufacture. However, Open Hardware generally means that design information such as schematics or CAD/CAM design files are freely downloadable for users to look at or potentially incorporate into modified versions or their own electronic designs.

This re-use of existing designs and technology, if you’re happy with the terms of the open-source licenses that may be used, can make design and prototyping faster, potentially getting your product to market (or a potential product or prototype ready for the investment or crowdfunding stage) that much faster.

In many cases, an open source software or hardware project is developed by one person who is often frequently directly accessible to users for direct advice or support. Many authors will provide helpful, patient support – often with a direct level of technical literacy that you’re often not likely to get from commercial “user support” staff reading from a script.

Even if you can’t talk directly to the developer, many open source software or hardware projects will have some kind of associated mailing list or web forum for community discussion, where other users or developers can help you out with advice and support.

Open source software and hardware allows you to get “under the hood” with the design details in a way that you can’t with proprietary technology. This means that you can inspect the engineering, fix problems, identify potential vulnerabilities, and extend or modify the engineering to suit the needs of your application. This is clearly in contrast to closed software or hardware where you are basically at the mercy of the commercial developers when it comes to future development suggestions, security advisories or bug fixes.

One argument in favour of open source technology is that it can be more secure – with many developers and users looking over the source code, security vulnerabilities become much more visible. Whereas closed source software depends to some extent on “security through obscurity”, open source software brings with it an expectation that having lots of users and developers looking through open-source code, maintaining, developing and tweaking it results in better, more secure software – where potential vulnerabilities are detected and corrected.

Applying this sort of “peer-review” to open source software means that the white-hat hackers are able to keep ahead of the black-hat hackers – or, at least, any unfair potential advantage that the black-hat hackers have is minimised.

Nevertheless, we must recognise that this applies a bit differently to hardware than it does to software. If a security vulnerability is discovered in a piece of software and it is openly discussed, a patch can rapidly be developed to correct it and deployed freely to everybody using that software, quickly and easily, thanks to the Internet.

However, if a security vulnerability is discovered in some hardware system which is used by tens of thousands of customers worldwide, what happens if it is not possible to deploy a software or firmware update to correct the problem?

If fixing the vulnerability requires actually buying new hardware to replace an otherwise mostly functional hardware device it is clear that customers may be reluctant to do this, and many systems may be left insecure. In such a situation, if a security vulnerability is discovered and discussed openly then this can easily have more negative effect on security than it does a positive effect, at least in the short term, or in small businesses or home environments where the hardware upgrade may be financially prohibitive.

Another potential advantage of open source technology is that it encourages commercial technology companies to try harder to make their own offerings more attractive, and it encourages innovation and competition – especially when the agility and speed of development by individual open source software or hardware developers, or small businesses, is taken into account.

Open source technology raises the bar, effectively, by saying to customers that this certain set of functionality is what you can get “free as in free beer” – and, to be honest, this is as far as it needs to go for “open source motivation” with some customers. This sends a message to commercial vendors that they may need to offer superior functionality, superior support or usability in order to remain competitive with open-source offerings.

Commercial developers can’t rest on their laurels, and are constantly motivated to innovate and improve their product. Otherwise, an open source product will come along that eats their lunch – as long as it is providing a comparable level of quality, usability and support.

On the other hand, smaller existing commercial hardware or software offerings may not be able to compete with a product that is available for free, and some may argue that open source competition can create a situation to anticompetitive “dumping” – dumping a whole bunch of product on the market at low or no cost in an effort to drive prices down, potentially forcing competitors out of business.

Thus when considering the use of open-source technologies for your next product design or iteration – there are many perspectives to take into account. Do you keep your product “open” and take advantage of the cost savings – but risk higher levels of competition? Or do you work with a closed or existing commercially-available ecosystem?

There’s much to consider, and if you’re not sure which way to turn – the first step is to discuss your needs with our team of experienced engineers that can help you in all steps of product design, from the idea to the finished product.

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

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

Although we have recently been focusing on the systems and hardware that can be used in various Internet-of-things applications, there’s much more to learn and understand. One particular aspect is the way in which devices send and receive data between themselves and servers – and an example of that is MQTT.

Message Queue Telemetry Transport, or MQTT, is an open protocol for machine-to-machine (M2M) communications that enables the transfer of telemetry-style data in the form of messages from a network of distributed devices to and from a small message “broker” server – whilst maintaining usefulness over high-latency, expensive or bandwidth-constrained networks. This publish/subscribe messaging transport protocol is designed to overcome the challenges of connecting the rapidly expanding physical world of sensors and actuators as well as personal computers and mobile devices.

The origin of MQTT goes back to the late 1990s, where co-inventor Andy Stanford-Clark of IBM became immersed in M2M communication whilst working with industry partners to mine sensor data from offshore oil platforms, to inform better preventative and predictive maintenance. One of those industry partners was Arlen Nipper of Arcom, an expert in embedded systems for oilfield equipment. Together, Stanford-Clark and Nipper wrote the initial version of MQTT in 1998, and their open-source messaging software has continued to be improved over the following years.

Until recently, one of the challenges limiting widespread development of IoT technologies has been the lack of a clearly accepted open standard for message communication with embedded systems. Today, however, MQTT looks set to play an increasingly significant role in facilitating the Internet-of-Things. In much the same way that the HTTP standard paved the way for the widespread adoption of the World Wide Web as a tool for the sharing of people-to-people information on the Internet, MQTT could set the stage for the machine-to-machine equivalent of the WWW.

MQTT is particularly well matched with networks of small, distributed, lightweight, and pervasive devices – not just mobile phones and personal computers, but embedded computers, sensors and actuators – which can make up the “Internet of Things”. The MQTT protocol specification enables a publish/subscribe messaging model in a very lightweight way, useful for connections with remote devices where a small code footprint is required – low-cost 8-bit micro controllers, for example – and/or where network bandwidth is at a premium.

There is also another standard for sensors – MQTT-S, for which this specification is aimed at embedded devices on non-TCP/IP networks, such as ZigBee/802.15.4 wireless sensor mesh networks. MQTT-S is an extension of the MQTT protocol aimed at wireless sensor networks, extending the MQTT protocol beyond TCP/IP infrastructures for non-TCP/IP sensor and actuator networks. Furthermore, MQTT is already widely supported by servers and brokers including IoT implementations such as cosm, Thingspeak, nimbits, and more.

MQTT is already used in a wide variety of embedded systems. An example documented by IBM demonstrates a pacemaker that communicates via RF telemetry to an MQTT device in the home of a patient – allowing nightly data uploads to the hospital for analysis. This allows recovering patients to leave hospital earlier to recover at home whilst still being monitored by medical professionals. Or if an unexpected event occurs, the system can immediately alert the hospital and emergency services without any patient interaction.

Furthermore IBM has recently announced its’ new “MessageSight appliance”, designed to handle heavy-duty real-time sharing of large amounts of data between sensors and devices and using the MQTT protocol to do so. Finally, IBM and Eurotech have bought MQTT to the open standards process of OASIS – the Organisation for the Advancement of Structured Information Standards. OASIS is a non-profit international consortium that drives the development, convergence and adoption of open standards for the global information society.

The OASIS standardisation process started in March 2013, with the goal of establishing MQTT as an open, simple and lightweight standard protocol for M2M telemetry data communication. The newly established OASIS MQTT Technical Committee is producing a standard for the MQTT Protocol – together with requirements for enhancements, documented usage examples, best practices, and guidance for use of MQTT topics with commonly available registry and discovery mechanisms.

Although MQTT does seem to be championed by IBM, the OASIS recently called for industry representatives earlier this year to sponsor the formation of its MQTT Technical Committee, and was answered by Cisco, the Eclipse Foundation, Eurotech, IBM, Machine-To-Machine Intelligence, Red Hat, Software AG and TIBCO. The group will take the MQTT 3.1 specification, donated to the committee by IBM and Eurotech where it was originally developed, and work to standardise and promote its adoption it as an open standard.

In defining MQTT standards and making them open for all, this allows its’ use and will hopefully guarantee a future standard allowing interaction with devices from all suppliers and manufacturers who choose to work with it. It’s a standard that holds a lot of promise for the future of an efficient and affordable Internet-of-things.

At the LX Group we have a wealth of experience and expertise in the IoT field, and can work with the MQTT standard, hardware and software to solve your problems. Our goal is to find and implement the best system for our customers, and this is where the LX Group can partner with you for your success.

We can create or tailor just about anything from a wireless temperature sensor to a complete Internet-enabled system for you – within your required time-frame and your budget. For more information or 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.

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

Continuing from our previous articles which are focusing on a range of currently-available Internet-of-Things systems, we now move forward and explore another addition to the Internet-of-Things marketplace in more detail – the system known as “ThingSpeak”. Considered to be one of the first openly-available IoT platforms, ThingSpeak operates on their own free server platform, or you can run the software on your own personal servers – and as the entire system is open-source, it’s easier to work with and customise.

As with the other systems examined, ThingSpeak gives your devices the opportunity to interact with a server for simple tasks such as data collection and analysis, to integration with your own custom APIs for specific purposes. Due to the open-source nature the start-up cost can be almost zero, and unlike other systems ThingSpeak is hardware agnostic – giving your design team many hardware options. However as always, let’s consider the main two components in more detail.

Hardware – You don’t need to purchase special base units or proprietary devices. As long as your hardware is connected to the Internet and can send and receive HTTP requests – you’re ready to go. For rapid prototyping, examples are given using many platforms including netduino, Arduino, mbed, and even with the competitive Twine hardware. This gives you a variety of MCU platforms from Atmel and ARM Cortex providers to work with, and as these development platforms are either open-source or inexpensive, your team can be up and running in a short period of time.

Furthermore creating your own devices can be quite inexpensive – a simple device based on an Atmel AVR and Ethernet interface can be manufactured for less than $20 in volume, and doesn’t require any software licensing expenses. To save on hardware costs, it could be preferable to have various sensors in a group communicate back to one connected device via inexpensive Nordic NRF24L01 wireless transceivers – and the connected device can thus gather the data into the require fields for transmission back to ThingSpeak.

Software – Thanks to the open-source nature of ThingSpeak either working with the existing server software or creating your own APIs isn’t a challenge. Interaction is easy with simple HTTP requests to send and receive data, which has a useful form. Each data transmission is stored in a ThingSpeak “channel”. Each of these channels allows storage and transmission of eight fields with 255 alphanumeric characters each, plus four fields for location (description, latitude, longitude and elevation – ideal for GPS), a “status update” field and time/date stamp. Data sent over the channels can be public or private – with access via your own devices and software finalising the security.

Once sent to the server this data can be downloaded for further analysis, or monitoring using various HTTP-enabled entities – from a simple web page, mobile application or other connected device. Various triggers can be created to generate alerts for various parameters, and can be sent using email, twitter, or other connected services such as an SMS gateway. After being in operation for almost three years, the platform has matured to a reliable service that has exposed many developers to its way of doing things, so support and documentation is becoming easier to find.

Overall the ThingSpeak system offers your organisation a low barrier to the Internet of Things. Creating a proof-of-concept device or prototype hardware interface can be done with existing or inexpensive parts, and the use of ThingSpeak’s free server can make an idea become reality in a short period of time. And once you device on the service, by internalising the server software, you can have complete control and security over your data.

If you’re interested in moving forward with your own system based on the ThingSpeak, we have a wealth of experience with the required hardware options, and the team to guide you through the entire process – from understanding your needs to creating the required hardware interfaces and supplying firmware and support for your particular needs.

Our goal is to find and implement the best system for our customers, and this is where the LX Group can partner with you for your success. We can create or tailor just about anything from a wireless temperature sensor to a complete Internet-enabled system for you – within your required time-frame and your budget. For more information or 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.

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

Many organisations, pundits and ourselves at the LX Group have discussed various aspects of what is generally termed the “Internet of Things” with great enthusiasm. And there’s many good reasons to be interested in this new level of technology. However from an external viewpoint, many people are still concerned that this “Internet-connected devices” is just a fad, being proposed by boffins and experimenters to automate their coffee machines or send a tweet when their children arrived home from school.

However nothing could be further from the truth. The Internet is real, devices are getting connected and more information than ever is being made available from connected systems. Industries of all types can take advantage of this to their benefit – and thus the concept of the “Industrial Internet” is born. This isn’t a new, separate Internet but instead a term for benefiting from the intelligence available with new technology to enhance any industrial operation.

This concept can be broken down into three specific categories:

Intelligent devices – these are the local hardware devices that work within existing or new installations that serve as the bridge between the installation and the larger overall system. Examples can range of a variety of connected instrumentation, sensors, local user-interfaces, or any other type of data-gathering and transmission device. In the past these may have been current-loop or other proprietary connections – but instead these devices are connected by a wired or wireless IP (internet protocol) connection.

The benefits of intelligent devices are several – their hardware cost can reduce over time with increasing volumes and popularity of the technology used; with a standardised interface the deployment and training costs for staff can be minimised; and with constantly-connected devices more data about the system operation can be gathered, allowing greater levels of analysis and faster decision-making cycles.

Intelligent systems – As the sum of all the parts, an intelligent system contains the new and existing hardware, networking and computing power that combine to offer a level of synergy unavailable from preceding technologies. With new levels of data output from intelligent devices, insightful programming by systems analysts and a strong background knowledge, optimisation of any operations can be achieved.

With knowledge comes understanding – allowing optimisation of all parts of the system. From simply matching machine usage to off-peak electricity prices to detecting device irregularities in real time, you can find savings in operations, system maintenance and also learn new insights about system operation in general. By monitoring device status in real-time you can reduce required holdings of consumables, pro-actively organise preventative maintenance instead of waiting to be notified of a fault, and fine-tune operations based on external and internal factors.

Intelligent decision-making – Over time as more operation data is gathered, analysed and verified by humans – the burden of decision-making can often be transferred to the system itself. The greater the number of data channels and volume of data being recorded offers the opportunity for a higher level of prediction of future events. Just as existing weather scenarios can often be used to predict future behaviour – a system can make decisions based on captured data that fit within predetermined parameters. From a simple laser printer that can order its’ own service call when the drum needs replacement; or an off-site diesel generator that can use data such as the load from attached refrigeration systems, ambient temperature and the amount of sunlight to determine how much fuel needs to be ordered and when it is required; or a delivery truck that can monitor speed, distance travelled, engine fluid levels, location and driver history and then decide when it needs a service – intelligent decision making can reduce the number of person-hours required for any organisation, and also help predict and determine situations that may not have been possible to realise with existing systems.

The Industrial Internet exists today, and using systems designed with the three categories mentioned earlier will help your organisation become more efficient, understand more about itself, and find cost benefits in all measurable areas. However the biggest step is the correct implementation of such a system. Like any plant or equipment purchase, making the right decision first – and once – will set your organisation on the path to increased efficiency and profitability – and this is where the LX Group can partner with you for your success.

We can discuss and understand your requirements and goals – then help you navigate the various hardware and other options available to help solve your problems. We can create or tailor just about anything from a wireless temperature sensor to a complete Internet-enabled system for you. For more information or 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.

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

There has been much discussion about the increasing possibilities available to existing systems by using the Internet of Things for two way transmission of data for logging and control purposes. However there is so much more than just working with data in a more efficient and cheaper method.

The concept and reality of the Internet of Things also allows devices to have increased levels of intelligence to further their defined tasks. This may sound like science-fiction, however it is possible – and already demonstrated in may consumer devices. For example – recent smart phones can download and install operating system updates without any intervention by or technical knowledge required from the user.

Using this same method your IoT devices – if designed appropriately – can be updated with new firmware just like our example smart phones. You can do this with two methods – by either using existing hardware such as “Electric Imp” modules that can be fitted in existing hardware, or creating new or re-designed hardware with the appropriate microcontroller/wireless chip combination.

When your devices can remain connected – or connect when necessary, they can also offload processing requirements to the cloud service or other connected server hardware. By programming your devices to simply send, receive and act on data the processing work can be offloaded to the server-side, reducing the requirement for faster device CPU speed, memory and so on. This in turn can reduce the hardware purchase cost, physical size, and also the power requirements for the device – saving money at all stages of operation.

All this sounds great – and has been put into practice in many fields. Let’s run through a few examples from a wide variety of examples.

Remote Point-of-Sale devices – Within the broad field of vending machines, point-of-sale devices, unattended ticketing machines and more – so much can be done to make stakeholders’ lives easier and cheaper. Product prices can be updated in real-time; data from the POS machine can be served to the central host giving real-time data and sales analysis; environmental data can be used to price cold drinks in real-time – for example when the local temperature increases or you know a certain area will be busier than usual – increase the drink price. The concept of supply and demand can be tweaked to your advantage with the right technology. And of course service calls and device monitoring can occur.

Passenger Information Systems – Almost every public transport system has some sort of PIDS (Passenger Information Display System), however their level of usefulness is usually determined by the ability of the system to run on-time. Remote displays may be programmed with timetable data to show when services should arrive, and on-board displays can show the “next station is…” type of data.

However when things go wrong – such as diversions, breakdowns, late-running or data required in an emergency – this data cannot be updated by local operators or staff in unattended stations. Thus the ability for a bus or train to communicate with a central server can allow relevant data to be displayed in real-time to the required PIDS units. Redundancy can be employed to allow for various failures, for example RFID technology at a railway station can be used to detect when a particular train arrives and departs. And when timetables change, stations are altered or new information is required to be displayed – it can all be done remotely or even while on the move.

Cube Satellites – In the last twelve months various groups have been working on tiny satellites that are launched into space along with regular commercial satellite payloads. Although this is a far-out example, it’s a demonstration of what we’re talking about. Each of these tiny satellites contain inexpensive consumer-level microcontrollers that control sixteen AVRs each running their own firmware, collating data and sending it back to earth via UHF radio link. The firmware for each of these AVRs can be uploaded and thus alter the satellite’s function when required.

The IoT is more than just wireless data – it’s about control. Having more control over your assets and revenue stream can increase business efficiency and profitability. With the right applications and minds on the task, even the simplest thing can be constantly tweaked to maximise gains. Here at the LX Group we can discuss and understand your requirements and goals – then help you navigate the various hardware and other options available to help solve your problems. We can create or tailor just about anything from a wireless temperature sensor to a complete Internet-enabled system for you. For more information or 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.

After reading various articles in the media and elsewhere, or examining your competitors’ products – you may start to ponder if the “Internet of Things” really matters. That’s a fair question, and the same can often be asked when a new technology emerges from the horizon. However unlike other changes in technology the leap to an IoT can be considered as revolutionary instead of evolutionary – and thus it does matter.

But why? As mentioned in our previous articles, the ability for something to be connected to the a network is tremendous. With intelligence provided by bespoke hardware at the client side, they can now receive or send data when the device is programmed to do so at an appropriate time. Consider the following examples:

Monitoring temperatures of multiple points in a production facility – No longer do you need to use a wired connection back to the main system – instead each temperature sensor can be equipped with a wireless module and communicate to the server via WiFi. Sensors can be relocated, added, or deleted without the effort to rewire – and with the advances in energy harvesting they can possibly be self-powered. A minimal microcontroller between the sensor and wireless module can also continuously monitor all status and notify the server of an error – and the server can detect a total failure and alert technicians without delay via many channels.

Consumer-device interaction – By now you’ve seen the LED light that can be controlled via a smartphone. However that technology can be utilised in many more ways – imagine if you arrived home at night, and your car communicates with the home system to turn on various lights, HVAC, and even turns on the stereo. Or an alarm system that emails, tweets and texts you images of the room where motion is detected – as well as alerting the authorities.

Upgrading existing M2M connectivity solutions – If you have existing devices that communicate with a server over custom wireless data solutions or expensive GPRS packet-data links – there may be an opportunity to upgrade the communications to IP via WiFi.

For example, if you have twenty vending machines in an airport that has terminal-wide WiFi access – by switching the communications from cellular to WiFi you not only save on line subscription and data charges, you can also interact more easily with the machines for status updates and alerts. Converting equipment to standard wired or wireless IP communciations allows integration with a wide variety of current and future IoT systems giving you flexibility and more possibilities than ever before.

The Internet of Things is important, it does matter – almost anything can communicate with anything or anyone. It’s a simple statement, that describes an almost infinite amount of possibilities. And the race is on to introduce this functionality to existing and new products. Customers are becoming more savvy with the Internet and networking – and understand how it works. By creating solutions that makes life easier, simpler and more convenient for your customers via IoT technology you will be ahead of the pack – to your benefit.

If you want to find out more, move forward with your own designs to make them IoT-ready, or don’t know where to start – partner with an organisation who can pull together the software, hardware and know-how to make it happen – the LX Group.

Here at the LX Group we can discuss and understand your requirements and goals – then help you navigate the varioushardware and other options available to help solve your problems. We can create or tailor just about anything from awireless temperature sensor to a complete Internet-enabled system for you. For more information or 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.

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

Making your Home Smarter: Automation

The convenience and security of home automation are undeniable, and more and more people are
using it. Not only that, a smart home can be an energy-efficient one, as you have more control of your appliances. It is always nice to have your lights automatically dim as you leave your room or play your favourite song just by clapping your hands. Home automation might cost a bit to install but the benefits are worth the investment.

Defining a “Smart” Home

A smart home incorporates a network that connects appliances and devices. This network allows anything that utilises electricity to
communicate with each other and respond to your commands. Controlling the devices could be done using a computer, wireless controller, or by voice. The system can be similar to a personal assistant who awaits your every beck and call. Lighting, home theatre, security, temperature regulation and entertainment are the most common systems to be automated.

A Short History of Home Automation

It was just a few years back when only society’s well-off could afford an automated house. But now, the developments in electronics technology have paved the way for much cheaper systems, enticing more families to convert their abode to smarter homes. How did smart homes begin?

It was in 1975 when Scottish company Pico electronics created X10, the technology that gave birth to home automation. X10 allowed compatible appliances and devices to “talk” to each other using the existing electricity connections inside a house.

Receivers are installed in the appliances and devices, and a remote control or keypad acts as the transmitter. Pressing the remote control sends out data wirelessly, encapsulating simple codes like 0010 for “on” and 0011 for “off”. The X10 was revolutionary during that time although it has its limitations. For instance, communication among the devices using electrical wires can be unreliable – the signals are heavily attenuated by the 120/240 volt system that is used in American homes.

More technologies emerged since then, all trying to overcome the limitations of the X10. Z-wave and ZigBee moved away from using power lines and used a special frequency channel for sending out radio waves. Both technologies used low-power and low-cost modules that are connected, following a mesh topology. Being low-power allowed ZigBee modules to be manufactured in small sizes and use smaller batteries. Mesh networking provides reliability and a more extensive communication range.

Software

Choosing the right automation software is very important. Modules follow the same technical standard and they all work the same, but programs do not. You must choose a program based on ease of use. Activhome is recommended for beginners, as the user interface is simple to follow. You can control your appliances through your computer using it. If you want more customization, then Powerhome could be for you. This program allows you to create timed sequences as well as routines that fit your preference.

Adding other systems would require new programs. For example, if you choose to add a weather monitor, you will need Virtual Weather Station. This program allows your automation software (e.g. Activhome) to communicate with your climate sensors.

Hardware

The server, interface and modules are the hardware of your automation system. The server acts as the brain of the system and will always include controllers, timers and computers. Servers have become more intelligent over the years and may now accept commands from smartphones. E-home Automation products are examples of systems that can process commands from Apple’s iPhone. Interface refers to the connection between the different components of the system, while modules receive the commands for the devices.

Smart Grid and the Future

The term “smart grid” refers to a node in a network of electrical systems that can analyse behaviours and do actions based on what it sees as necessary to maintain the efficiency of the system. The ability to control home appliances and lighting is viewed as an integral addition to the smart grid as it is being rolled out in a few countries.

A combination of home automation systems and smart grids will pave the way for better energy management in the future. A possible application could be turning on the air-conditioning system using the high power derived from a solar panel on a hot day. Smart grid technology will also evolve just like home automation so that this so-called “green automation” can be utilised in more homes.

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

IET Innovations Award – LX Group

IET, the London Institute of Engineering and Technology, has recognised LX Group’ pioneering design for the YellowBird ALERT (owned by Advance Alert Pty Ltd), by nominating it in two categories: Information Technology and Sustainability. The IET Innovation competition “…attracted entries from around the globe, demonstrating the innovation and imagination of engineers as they tackle their own local, economic and social challenges”

(http://conferences.theiet.org/innovation-awards/index.htm).

Innovation abounds at the IET Awards, and alongside YellowBird ALERT, innovative designs include smart metering, remote solar panel cleaning, ultra low power solar information transport and self healing electricity distribution networks.

YellowBird ALERT is an emergency alert system that warns of natural disasters. To date, YellowBird ALERT has won awards in the Future Electronics Awards and the National Resilience Award.

The competition has attracted entries from around the globe, from a gamut of organisations and corporation including Vodafone, British Telecommunications and Siemens Industrial, and universities including Birmingham, Manchester and Edinburgh. In the true spirit of technological innovation, LX Group is joined by many independent organisations from India through to America.
# # #

LX Group, is an award winning Australian electronics design house with services that include software, firmware & hardware development, wireless and low power electronics designs. LX Group, offers clients a range of professional solutions designed to take a new product from concept to the product.
For more information about LX Group please visit www.lx-group.com.au or call 1800 810 124.

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