voltages, so ADCs are vital for the microcontroller to be able to read them. The development of microprocessors brings a software advantage. Older electronics hardware is notoriously hard to develop software for and, if it is analogue, manufacturers may not even be able to code for it. But, as microprocessors continue to evolve, manufacturers are also developing better software to programme them with. These advances are also benefiting original equipment manufacturers (OEMs). For example, Mantracourt’s T24 is a wireless telemetry system that engineers can use to communicate data across factories and other industrial facilities. Communication is achieved by attaching a sensor to a standard IP67-rated T24 transmitter enclosure, which then transmits data to either a wireless range extender or a base station, depending on the size of the facility. Finally, this data can then be communicated to a T24 Toolkit software, so users can view live data, set alarms, and log data when needed.
DEDICATED, EXPERT SUPPORT Traditionally, when an industrial sensor or another piece of equipment experienced an error, the support process was very onerous. The OEM would send an engineer out to visit the site, recalibrate the device and perform the necessary checks themselves. This is why Mantracourt recently released the T24 toolkit to allow engineers to communicate with equipment remotely. Operators in these industrial environments
Mantracourt’s recently released T24 toolkit allows engineers to communicate with equipment remotely.
can use the toolkit to test communications with different modules, and check radio link quality. As well as this, they can access factory-level support remotely so that engineers can configure and calibrate different modules, ensuring everything runs as it should in the end-user’s facility. The system can also be paired with
Mantracourt’s SensorSpace platform for data capture and analysis. To this end, not only can technical support be accesses remotely, but the manufacture themselves can also manage and monitor system performance remotely.
Page 1 |
Page 2 |
Page 3 |
Page 4 |
Page 5 |
Page 6 |
Page 7 |
Page 8 |
Page 9 |
Page 10 |
Page 11 |
Page 12 |
Page 13 |
Page 14 |
Page 15 |
Page 16 |
Page 17 |
Page 18 |
Page 19 |
Page 20 |
Page 21 |
Page 22 |
Page 23 |
Page 24 |
Page 25 |
Page 26 |
Page 27 |
Page 28 |
Page 29 |
Page 30 |
Page 31 |
Page 32 |
Page 33 |
Page 34 |
Page 35 |
Page 36 |
Page 37 |
Page 38 |
Page 39 |
Page 40 |
Page 41 |
Page 42 |
Page 43 |
Page 44 |
Page 45 |
Page 46 |
Page 47 |
Page 48 |
Page 49 |
Page 50 |
Page 51 |
Page 52 |
Page 53 |
Page 54 |
Page 55 |
Page 56 |
Page 57 |
Page 58 |
Page 59 |
Page 60 |
Page 61 |
Page 62 |
Page 63 |
Page 64 |
Page 65 |
Page 66 |
Page 67 |
Page 68 |
Page 69 |
Page 70 |
Page 71 |
Page 72 |
Page 73 |
Page 74 |
Page 75 |
Page 76 |
Page 77 |
Page 78 |
Page 79 |
Page 80 |
Page 81 |
Page 82
