data Archives | Page 2 of 2

All posts tagged: data

You may have seen the term “Internet of Things” bandied about recently in the popular press and media outlets, and like many fads considered it to be some sort of “buzzword” or meaningless phrase created by social media gurus that can be safely ignored.

However nothing could be further than the truth. The IoT (as we will now refer to it) is a broad definition for how almost any device around us can be connected to each other and other services over the Internet.

That may sound a little broad, so let’s consider some examples:

Checking the room temperature at home remotely, and control the HVAC if required – so you arrive home to a pleasant environment
Monitoring and controlling water flow levels for irrigation systems in four different states from a central office
Receiving an email from isolated vending machines when they detect possible theft, excess vibration or tilting
Real-time position monitoring of valuable cargo shipments as they travel between warehouses

With fixed or reliable wireless Internet access in all these examples, you can accomplish it all and much more. The IoT allows you to be in more than one place at the same time – to receive data from anywhere – and to control from anywhere – as long as Internet access is available.

Furthermore the volume and types of data that can be collected is only limited by your requirements and device type. With a constant IP connection between a sensor and your IT system – data can be gathered for real-time analysis. Information is power – and the more you know about your assets and their performance – the more agile your decision-making can become.

This type of machine communication isn’t new – for example you’d be familiar with terms such as M2M and telematics for many years. However the concept of channelling all the data over the Internet or a private IP network is what the IoT is about.

Existing sensors and actuators (the devices that send and receive data) can usually be adapted to the new IoT with little effort. For example, a sensor with a 4-20mA current loop output can be engineered with a current sensor that can be read with a basic microcontroller – and then interfaced to the IoT node.

As most IoT environments are skewed towards the consumer and technically-literate hobbyist, there will be work involved in adapting the system for your particular needs. For example, the provider may offer a range of doorbell or simple temperature sensors – but not devices that can transmit or receive data over standard data buses such as IIC or SPI. In situations like these, your engineering team or parter will be required to create interfaces between your current devices and the bridge to the IoT.

Enabling your devices to work with the IoT can be a challenge, due to the variety of systems and standards on the market, each with their own pros and cons. There are many points to consider, and these can include:

The initial costs of interface hardware, staff training and ongoing maintenance

Can you use your existing actuators and sensors – or create your own ones, or must you acquire new ones that are specific to the IoT system under consideration?
Is the required power and communications infrastructure available when upgrading particular areas to the IoT?
Will the data and commands be transferred using an external Internet-based host system, or can you keep the data within internal private networks?
If using an external host system, can they offer you an agreed SLA value?
Is the host system using proprietary data protocols – forcing you to use the host system provider’s engineering team to add your own devices to the system?
What security features are available to stop unauthorised access to the devices and the host system?

The Internet of Things is more than an exciting concept – it exists today, and your organisation can benefit from it. However due to the incredibly combination of systems and options – consider partnering with an independent organisation that has your needs first and foremost.

Here at the LX Group we can discuss and understand your requirements and goals – then tailor anything from a modified 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.

As mentioned in our previous discussion of the 4-20 mA current loop, there are many forms of wired data transmission that can be used in products, and today we’d like to review another form – the Inter-integrated Circuit bus (or I2C bus for short). This is also known as the “two wire interface” and has been around for quite some time. Invented by NXP (previously Philips Semiconductor) the I2C bus is a multi-master serial single-ended data bus used to allow systems to communicate with a huge variety of electronic devices.

From a hardware perspective it is quite simple – each device connects to the serial data and clock lines, which are controlled by the master device. The clock and data lines are connected to Vdd via pull-up resistors, for example:

The master device controls the bus clock and initiates communications with each slave device. Communications are initiated by sending the slave device address – which is unique to each device – and then either data write or request commands. Then the slave device will act upon received data, or broadcase the required number of bytes of data back to the master device.

You may be wondering how the slave addresses are organised – each device manufacturer applies for an address range from NXP for their products. Some devices will only have one set address, and some can have their address altered – for example by changing the last three bits in the binary representation of the addresses. This is done in hardware by connecting three pins to Vdd or GND.

The speed of the I2C bus varies, and can range from 10 kbps to 3.4Mbps – with the speed usually proportional to the total device power requirements. The usual speed for the majority of devices is 100 kbps.

The decision to use the I2C bus can be simple, due to the popularity of the interface even on the most inexpensive of microcontrollers – and many design engineeers are familiar with the bus due to the history.

But what sort of devices can make use of the I2C bus? There are literally thousands available, in a wide range of categories. These can include simple temperature sensors, EEPROMS, motor controllers, LCD interfaces, I/O expanders, real-time clocks, UART interfaces, ADC/DACs, and more.

Apart from the huge range of devices, the advantages of using the I2C bus include industry expertise, the ability to address literally hundreds of devices using only two master I/O pins, and that devices on the bus can be “hot swap” – that is you can add or remove devices from the bus without powering off the entire system. This in itself is perfect for systems with maximum run-time requirements, as technicians can replace faulty device modules with reduced down-time for the end user.

However there are disadvantages to the I2C bus, two of which need to be taken into consideration. The first is that the maximum physical length of a bus run is usually around 20 metres, and in some cases much less. You can use bus extension devices from NXP (and others) that will allow much further physical distances – however designers need to ensure the capacitance across the bus stays at around 400 picofarads.

The second disadvantage is the possibility of slave address clash. You may have two specialised devices with the same slave address. In these situations you need to use an address multiplexer IC on the bus which first needs to be controlled, and then the device selected is addressed as normal. Nevertheless, as part of normal prototyping and planning these disadvantages can be removed or minimised with appropriate engineering.

It can be said that the I2C data bus may not be the “latest technology”, but it can effectively solve problems in the right circumstances. However there are many options, and choosing the right one is a fundamental step for the success of your project. So if your design team is set in their ways, or you’re not sure which data communication method is best for your application – it’s time to discuss this with independent, experienced engineers.

At the LX Group we have experience designing a wide range of data gathering and control systems over short and long distances – and using this experience we can determine the most effective method of returning data and control signals no matter the application or geography. Our engineering team have developed a number of systems in this area and have extensive experience with the core technology requirements of such systems.

We understand the importance of high availability, accuracy and integrity of the systems, combined with the need for future proofing infrastructure rollouts. 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.