Data Logger

Abstract

The data logger (100, 3100) includes a sensor interface for connecting at least one sensor or actuator to the data logger (100, 3100), an accessible memory (SD card) for storing data received from the at least one sensor or actuator, and a controller (3199) for controlling the operation of the data logger (100, 3100), the data logger (100, 3100) including a plurality of modules (110, 120; 3110, 3120), each module being connected to a housing of an adjacent module. The data logger has a housing electrically and mechanically connectable to the data logger, at least one module (120) functions as a logging and / or actuation module (LAM120, 3120) including a sensor interface and at least a portion of an accessible memory (SD card), and at least one module (110, 3110) connected to the at least one LAM (120, 3120) functions as a control and communications module (CCM) and includes a controller (3199) that controls internal and external communications of the data logger (100, 3100).

Description

[Technical field]

[0001] The present invention relates to a data logger and a data logger system that may be used for data acquisition, advantageously for use in process control. [Background technology]

[0002] The following discussion of the background art is intended solely to facilitate understanding of the present invention and is not an acknowledgment or admission that any of the material referred to is or was part of common general knowledge as of the priority date of this specification.

[0003] Data loggers are widely used in science and engineering to acquire data, commonly for process control. The data is acquired from one or more sensor(s) that are connected to the data logger, typically via a cable, although wireless implementations are known.

[0004] Data loggers may be of a general purpose type or designed for very specific applications. Those designed for specific applications are usually customized, following a potentially intensive process control design process. Data loggers such as these can be expensive and are not intended for hobbyists or simple control applications, e.g., business applications. Such accessibility is not feasible at the price.

[0005] General purpose data loggers may in principle be applied to a range of measurement and control applications, see for example en.wikipedia.org / wiki / Data_logger. General purpose data loggers are generally programmable, but usually only a limited number of parameters can or cannot be changed. Again, such data loggers may be relatively expensive. Again, accessibility problems arise. Less expensive data loggers may also offer less programming flexibility.

[0006] Slow network speeds tend to hinder data loggers that rely on streaming data.

[0007] It would be advantageous to provide a more flexible data logger for data acquisition, particularly for use in process control. Summary of the Invention

[0008] In one aspect, the present invention provides a method for producing a method for treating a cancer cell comprising: a sensor interface for connecting at least one sensor or actuator to the data logger; an accessible memory for storing data received from at least one sensor or actuator; a controller for controlling the operation of the data logger; Provide The data logger includes a plurality of modules, each module having a housing electrically and mechanically connectable to the housing of an adjacent module; At least one module functions as a logging and / or actuation module (LAM) that includes a sensor interface and at least a portion of the accessible memory, and at least one module connected to the at least one LAM functions as a control and communications module (CCM) and includes a controller that controls internal and external communications of the data logger.

[0009] A logging and / or actuation module (LAM) may communicate with at least one further LAM to form a stack of LAMs. The modularity of the data logger allows flexibility in providing the required number of sensors and actuators, for example in a process control system. The possibility of co-locating a stack of LAMs, and an optional CCM, allows the stack to be formed within the same footprint available for the location of the data logger. The stack of modules may be located within an enclosure, for which standard industrial types may be useful. Other arrangements are possible. For example, a LAM may be "daisy-chained" to at least one further LAM, although this may have limitations due to the data communication speed available over the network.

[0010] LAMs of the same or different data loggers can be conveniently networked by serial communication over a wireless network. The serial communication may be provided with a protocol selected from the group consisting of a short-range protocol (preferably Bluetooth), a long-range protocol (preferably LoRA) and TCP / IP. The serial communication is advantageously possible with a variety of user devices, including those from the group consisting of mobile phones, smartphones, tablets, portable and computing devices.

[0011] The controller for controlling the operation of the data logger preferably includes a microcontroller, although in some applications a microprocessor may be used. Preferably, the controller module also allows control by communication, in which case it is further referred to as a control and communication module (CCM). Conveniently, a communication bus, preferably a CAN communication bus, is included to allow communication between the CCM and LAM(s), devices within the CCM and LAM(s), and user devices. As an alternative to CAN communication, users may develop their own communication protocols. Alternative differential pair signaling systems may also be used, such as RS485 communication. RS485 is electrically very similar to CAN, using differential twisted pair wires operating within the range of 0-5 volts. Alternatives to CAN may require the use of software algorithms to handle collisions of information on the electrical bus.

[0012] Conveniently, the LAM or CCM is provided with at least one user configurable input and at least one user configurable output. For example, the button (input) and indicator (output), preferably an LED, may be configured for a specialized application selected by the user of the data logger. The LAM conveniently allows for a single button operation, for example, allowing the user of the data logger to select the mode of LAM operation, providing an easy to use module that is conveniently usable for hobbyist as well as professional applications. The user selected mode of LAM operation may include, but is not limited to, an output actuator, such as a sleep state, a logging state, or an alarm indicating that a sensed signal is out of tolerance, e.g., a sensed pressure has exceeded a threshold for activating an alarm. The indicator output may visually indicate an alarm or a selected process state. If the controller includes logic, for example in the form of a state machine with the data logger monitoring the transition between states, pressing the button may provide a transition from one state to another. The button may thus enable a transition from an automatic control to a manual control mode.

[0013] The CCM may include one or more internal and / or external antenna(s) to enable wireless communication via protocols such as those mentioned above. Optionally, the antennas and / or antenna arrangements may be configured to meet MIMO standards. Conveniently, wideband antennas may be included to accommodate a multitude of possible wireless communication protocols. Such antennas are preferably mounted internally to the data logger. In other embodiments, a standard wireless antenna corresponding to a particular wireless communication network may be provided.

[0014] The data logger may advantageously store data on-board in accessible memory, for example a USB drive or SD card, which may form at least a portion of the accessible memory. Although not limited to a selected memory storage device, the accessible memory may include multiple memory storage devices, with a port provided for each memory storage device in each LAM of the data logger. The accessible memory may also include external non-accessible storage, optionally flash storage on a circuit board contained within the module, from which data is retrievable by wireless communication.

[0015] Alternatively or additionally, the data logger can accommodate streaming of data over a wired or wireless network, for example via cloud computing. However, streaming has limitations, one of which is that the maximum data throughput of sensed signals over the network may not be fast enough to keep up with the signals being processed (and therefore not real-time). Latency and delays in transmitting sensor signals may also be an issue. Therefore, it is preferable that an accessible memory is provided within the data logger to store (for later processing or conversion) the sensor and actuator signals. Thus, for example, data can be stored in a memory storage device, including, for example, a USB device (allowing a wired connection to a computer) or a memory card such as a removable SD card, SDHC card, Micro SDXC card or flash card. Such a memory storage device can be retrieved to allow downloading of data, conveniently at selected special periods of data acquisition, without interfering with the communication network, although wireless communication is an available option.

[0016] The data logger (and more specifically the LAM(s) of the data logger) may be provided with one or more ports that allow flexibility in the selection of memory storage devices that provide accessible memory. For example, the LAM may be provided with ports for USB devices and SD cards, both allowing for data storage and data transfer. Also, the microcontroller contained within each LAM of the data logger may be able to process signals on-board the data logger, allowing it to operate on a stand-alone basis. In some applications, for example, an additional microprocessor may be included to convert large amounts of data, as microprocessors typically have the advantage of large amounts of external RAM, allowing for large amounts of calculations without affecting real-time operation.

[0017] Alternatively or additionally, the memory can be available external to the data logger and communication of data to the external memory storage device can be by using any convenient wired or wireless communication protocol including TCP / IP, short range (preferably Bluetooth (BLE)), long range protocols (preferably LORA or RF), Websockets and / or Ethernet. The data logger can communicate with external communication devices, i.e., networked devices, whether computer systems (including cloud-based servers), or laptops, smartphones, smart devices, or IoT devices, the latter group including user devices, allowing the user to configure the system while on the move or at a fixed location.

[0018] A microcontroller is preferably included within each LAM of the data logger to process signals on-board the data logger. Signals from at least one sensor or actuator may conveniently be processed using a transformation determined by the user of the data logger.

[0019] The data logger may be configured in a number of ways by logic in the form of a state machine and corresponding transformations. For example, the data logger may be configured by scripts loaded into at least one memory storage device. The data logger may additionally or alternatively be configured remotely via scripts downloaded into memory accessible by a web-based user interface or mobile app.

[0020] Data loggers are typically provided with a power source, for example an industrial power supply (conveniently a 9-30 volt industrial power supply), but if such an industrial power supply (or other power supply) is not available, various power options are available. The data logger may be powered, preferably automatically, from a number of power options, including one selected by the controller. Such power options typically include an auxiliary power module, conveniently having the same form factor as the LAM described above. Multiple auxiliary power modules may be included, if desired. Another power option may be Power over Ethernet (PoE), or a similar standard (including IEEE standard 802.3 compliance), allowing for simultaneous transmission of data and power, for example over twisted pair cable. A PoE module may function as a CCM, but may also be provided as a LAM.

[0021] The controller may select the highest available power source to power the data logger. For example, if multiple auxiliary power modules are used, the CCM may enable negotiation between the multiple auxiliary power modules via the above-mentioned serial communication with the LAM(s) to determine which auxiliary power module(s) will power the data logger.

[0022] Further power options may include battery operation using an auxiliary power module including a rechargeable battery. Such an auxiliary power module may receive power, for example, from an energy harvesting system (such as a solar power system) and a battery management system conveniently connected to the data logger. An auxiliary power module is particularly desirable for providing resilience to power outages.

[0023] Power is distributed from the power source through power rails to the CCM and LAM to enable operation of the data logger. In one embodiment, such power rails may include a Vraw power rail to provide the highest available power source available to the data logger, whether from an industrial power source or an auxiliary power module, as described above. The Vraw power rail may provide power to an auxiliary power module, for example, to charge a battery if battery power is used.

[0024] The voltage from the power source to the data logger and its components is regulated as necessary. The data logger may be provided with an uninterruptible power supply (UPS) functionality that includes an auxiliary power module. To that end, the data logger may conveniently be configured with a controller and power rail(s) to allow transition from a preferred power source, such as an industrial power supply, to an auxiliary power source, such as a battery pack.

[0025] The data acquired by the data logger may be processed using software, conveniently web-hosted software, that allows a user to configure the data logger, conveniently via a web-based user interface or mobile app, and customize the data processing of the constructed data logger system, for example for use in process control. Alternatively, a user may process the acquired data within their own software, whether custom developed or "off the shelf", for example via the Office365® platform. The data processing software may be downloaded from a server providing the user with the ability to process the data locally.

[0026] The LAM or CCM preferably allows for a waterproof and dustproof connection of each sensor or actuator cable or wire to each port of the data logger. An IP67, preferably IP68 rating is achievable by the data logger. In such a case, at least one sensor or actuator is connected to the housing of the data logger, the connection providing the data logger with at least an IP67, preferably an IP68 rating. In such an embodiment, at least one sensor or actuator is connected to a housing contained within the data logger by a clamp seal on the sensor or actuator cable, the seal forming a clamp that seals against ingress along the path of the cable and prevents the cable from being pulled out of the housing. The clamp seal may be provided in a wall of the housing, optionally by clamping the sensor or actuator cable.

[0027] A suitable clamp may include a tubular sealing sleeve extending into the port housing the sensor or actuator cable, the sleeve being provided with sealing means to seal the cable to the sleeve and port. Conveniently, the sealing means is a double lip seal. A suitable clamp allows the sleeve and sensor or actuator cable to be clamped in place in the port using a clamp seal. The clamping means may exert a pinching action on the cable as it exits the sleeve inwardly from the port. The clamping means may be a wedge with a slot for engaging the cable, the wedge engaging the tubular sleeve and having an angled back surface which, when pressed into place, forms a seal against the inner surface of the wall of the housing.

[0028] Another embodiment, which may be useful in environments where a seal is not required, allows for standard or "off the shelf" cable connectors to be used with the data logger. A combination of clamp seal connectors, as described above, and standard connectors may be used.

[0029] Data loggers are suitable for use in process control because signals from a sensor(s) connected to the data logger housing can be used as inputs for feedback or feedforward control processes that can be selected from a wide range of options in engineering and scientific applications by the user of the data logger.

[0030] In a further aspect, the present invention provides a data logger system or process control system, the data logger system or process control system comprising: At least one sensor; At least one data logger as described above in communication with the process control unit, a sensor interface for connecting at least one sensor to the housing of the data logger; a memory accessible for storing data received from the at least one sensor; and a controller for controlling the operation of the data logger; a data logger including: at least one actuator controllable by the process control unit in response to signals received from the at least one sensor and logged with the data; Includes.

[0031] Conveniently, the process control unit interfaces with at least one selected sensor that senses an input for control. If the selected sensor input triggers a control response, the process control unit may be conveniently programmed to manage the control response or to continue sampling (at desired time intervals) from another sensor, but not sample data from the selected sensor until the microprocessor flags the control response as complete. This allows for more efficient utilization of computing resources.

[0032] The sampling rate of the sensor inputs may be set by the user via at least one of a web user interface, a mobile app, and a script located on a conveniently accessible memory. The sampling rate may advantageously be greater than the available wireless communication network speed. In this regard, while the sampling rate of conventional data loggers over a network is typically once per second or less, the sensors forming part of the data logging system described herein may be polled at a much higher rate, e.g., hundreds of times per second, which cannot typically be transmitted over a network. The data logger system of the present invention allows for signal processing on-board the data logger, with communication over a wireless network either not provided or optional during logging.

[0033] The data logger conveniently accepts mixed sensor inputs. The process control unit may direct digital and / or analog signals to the LAM(s).

[0034] In an embodiment, the data logger or process control system may include a server capable of communicating with the data logger as described above, and the server may allow a user to configure the data logger. A user may also configure the data logger directly via the server.

[0035] Such a server may be in communication with a memory for storing data, and data from the data logger may be stored in the memory. Conveniently, the server may be in communication with a user network for downloading software and firmware for operating the data logger, and users may conveniently configure the data logger via the user network by way of a user device.

[0036] A server or user network can be in communication with the cloud-based memory for storage of data from the data logger.

[0037] The data logger is easily configurable for edge computing, as described in the following embodiments.

[0038] The data logger, as well as the data logging or process control system utilizing it, are conveniently robust to accommodate a wide range of engineering and scientific applications where environmental factors present a real risk of damage. Potentially significant factors include water and / or dust ingress and damage. To reduce such risk, the modular sensor interface includes a sealing arrangement to reduce or eliminate the risk of water or dust passing through gaps between the data logger housing and the sensor or sensor cable.

[0039] The data logger can be conveniently connected to a variety of sensors, which may include, but are not limited to, temperature sensors, moisture sensors, relative humidity sensors, gas composition sensors, light sensors, acoustic sensors, motion sensors, pressure sensors, current sensors, voltage sensors, position sensors, other environmental parameter sensors, and the like. Desirably, the data logger is connected to multiple sensors sensing different parameters so that the data logger accepts mixed inputs. The data logger can also be conveniently connected to actuators, including flow control valves, switches, stepper motors, and actuators, whether on / off, on or off, by direction or using pulse width modulation. The data logger can be conveniently used in combination with a control system, such as a SCADA control system, where analog and / or digital inputs from the control system are directed to the LAM(s) as described above, and vice versa.

[0040] The data logger conveniently includes on-board sensors such as those mentioned above, which may include an accelerometer for sensing motion, and / or a position sensor such as a GPS or satellite-based navigation sensor (e.g., a GLONASS sensor) to allow positioning over short distances, even to within a few centimetres (using an on-board RTK GPS chipset). The data logger (conveniently a CCM) may include and require air vents for sensors such as barometric pressure and air quality index sensors.

[0041] Data loggers and data logger or process control systems such as those described above are flexible, suitable for use by hobbyists and professionals, including scientists and engineers, allow for a wider range of user configurability than previously possible, and are relatively inexpensive.

[0042] Further features of the present invention will be more fully described in the following description of some non-limiting embodiments thereof. This description is included for the purpose of illustrating the present invention only. It should not be understood as a limitation of the broad summary, disclosure or description of the present invention as set forth above. The description is made with reference to the accompanying drawings. [Brief description of the drawings]

[0043] [Figure 1] FIG. 2 illustrates an orthogonal view of a data logger, according to one embodiment of the present invention. [Diagram 2] FIG. 2 is a schematic orthogonal view of the logging and / or actuation module (LAM) of the data logger of FIG. 1 during assembly. [Diagram 3] FIG. 3 is a schematic partial orthogonal detail cross-sectional view of the data logger shown generally in FIG. 2, showing the connection of the terminal block to the circuit board of the LAM. [Figure 4] FIG. 4 is a further schematic, partially orthogonal, cross-sectional detail view of the LAM of the data logger shown in FIG. [Diagram 5] FIG. 5 is a schematic orthogonal view of the sealing arrangement between the data logger and the base plate of FIGS. 1 to 4. [Figure 6(a)]FIG. 3 is an orthogonal cross-sectional view of a sealing plug for closing a sensor or actuator port as shown in FIGS. 1 and 2. [Figure 6(b)] 5 is an orthogonal cross-sectional view of one embodiment of a sealing clamp element for sealing a sensor cable to a data logger as shown in FIGS. 1, 3 and 4. FIG. [Figure 6(c)] 7A is an orthogonal cross-sectional view of a further embodiment of a seal clamp element for the seal clamp shown in FIG. 6(b). [Figure 7(a)] FIG. 7 is an orthogonal view of a further seal clamp element for use with the seal clamp element shown in FIGS. 6(b) and 6(c). [Figure 7(b)] FIG. 7(b) is a side view of the further closure clamp element shown in FIG. 7(a). [Figure 7(c)] FIG. 8 is a front view of the further closure clamp shown in FIGS. 7(a) and 7(b). [Figure 8] FIG. 3 is a schematic orthogonal view of the data logger of FIG. 2 with the power cable and the sensor cable clamped to the data logger. [Figure 9] 9 is an orthogonal cross-sectional detail view showing clamping of a sensor cable to the data logger of FIG. 8 using the further sealing clamp of FIGS. 7(a)-(c). FIG. [Figure 10] FIG. 9 is a detailed cross-sectional side view showing clamping of a sensor cable to the data logger of FIG. 8 using a combination of the hermetic clamping elements of FIGS. 6(b) and (c) and FIGS. 7(a)-7(c). [Figure 11] FIG. 9 is a schematic orthogonal view of the data logger of FIG. 8 with a retainer plate connected over the sensor ports and power and communication ports. [Figure 12(a)] FIG. 9 is a front orthogonal view of a connector used to connect the LAM of the data logger shown in FIG. 8 to the data logger's Control and Communications Module (CCM) or another LAM. [Figure 12(b)] FIG. 12(b) is a side view of the connector shown in FIG. [Figure 12(c)] FIG. 13 is a side cross-sectional view of the connector shown in FIGS. 12(a) and 12(b). [Figure 13(a)] FIG. 9 is an orthogonal view of a retainer comb for use in connecting the LAM and CCM of the data logger shown in FIG. [Figure 13(b)] FIG. 13(b) is a top view of the retainer comb shown in FIG. [Figure 14] 14 is a top orthogonal view of the LAM of FIG. 8 showing the connector and retainer comb of FIGS. 12 and 13 in place ready for connection of an additional LAM or control and communication module (CCM). [Figure 15] FIG. 15 is a top orthogonal view of the data logger of FIG. 14 with the CCM fixed in place. [Figure 16(a)] FIG. 16 is a partial cross-sectional view of the data logger of FIG. 15 showing the mechanical connection between the CCM and the LAM in one embodiment. [Figure 16(b)] FIG. 16 is a partial cross-sectional view of the data logger of FIG. 15 showing a mechanical connection between the CCM and the LAM in a further embodiment. [Figure 17(a)] FIG. 17 is a further cross-sectional view of the data logger of FIGS. 15 and 16(a). [Figure 17(b)] FIG. 17 is a further cross-sectional view of the data logger of FIGS. 15 and 16(a). [Figure 18] FIG. 18 is a detailed side view showing the connection of the LAM and CCM of the data logger of FIGS. 14 to 17. [Figure 19(a)] FIG. 17 is an orthogonal view of a protective shield used during assembly of the data logger of FIGS. 15 and 16. [Figure 19(b)] FIG. 19(b) is a top orthogonal view of a portion of a first alternative embodiment of a protective shield to that shown in FIG. 19(a). [Figure 19(c)] FIG. 20 is a top orthogonal view of a portion of a protective shield to that shown in FIGS. 19(a) and 19(b). [Figure 20] FIG. 19 is a detailed top orthogonal view showing the power and communication connector block of the data logger of FIGS. 14-18. [Figure 21(a)] FIG. 17 illustrates electrical and communication connections between the LAM and the CCM (or the LAM and a further LAM) of the first embodiment of FIGS. 15 and 16. [Figure 21(b)]FIG. 17 illustrates electrical and communication connections between the LAM and the CCM (or the LAM and a further LAM) of the first embodiment of FIGS. 15 and 16. [Figure 21(c)] FIG. 17 illustrates electrical and communication connections between the LAM and the CCM (or the LAM and a further LAM) of the first embodiment of FIGS. 15 and 16. [Figure 21(d)] FIG. 17(b) is a partial orthogonal view showing how electrical and communication connections are made between the LAM of FIGS. 16(b) and 17(b) and the CCM of the second embodiment. [Figure 21(e)] FIG. 17(b) is a partial orthogonal view showing how electrical and communication connections are made between the LAM of FIGS. 16(b) and 17(b) and the CCM of the second embodiment. [Figure 21(f)] FIG. 17(b) is a cross-sectional side view showing the connection between the LAM of FIG. 16(b) and the CCM of the second embodiment. [Figure 22] FIG. 17 is a partial front orthogonal detail view of the LAM of FIGS. 15 and 16 with the USB and SD card port sealing flaps closed. [Diagram 23] FIG. 17 is a partial front orthogonal detail view of the LAM of FIGS. 15 and 16 with the USB and SD card port sealing flaps removed. [Figure 24] FIG. 24 is a partial top orthogonal cross-sectional view with details hidden showing the front circuit board and indicators of the LAM of FIGS. 15, 16, 22 and 23. [Diagram 25] FIG. 25 is a top orthogonal view showing the front circuit board of FIG. 24 connected to the wall of the LAM. [Figure 26] 26 is a top orthogonal view showing a portion of the protective shield of FIG. 19 in place on the front circuit board shown in FIG. 25. [Figure 27] FIG. 17 is a front orthogonal partial cross-sectional view, with details hidden, showing details of the front wall of the LAM of the data logger shown in FIGS. 15 and 16. [Figure 28] FIG. 29 is an orthogonal detail view of a portion of the front wall of the LAM of the data logger shown in FIGS. 15, 16 and 28, showing the button and hole for directing light from the LAM indicator. [Figure 29]1 is an orthogonal view of a portion of the front wall showing a sealing element and a portion of a diffuser of the LAM indicator in place within a hole to direct light from the LAM indicator. [Diagram 30] FIG. 30 is a top orthogonal view showing details of a portion of the front wall shown in FIG. 29 in relation to other components of the LAM. [Diagram 31] 2 is an orthogonal view showing the data logger of FIG. 1 mated with a mounting bracket for mating with a mounting point, such as a DIN rail, in accordance with one embodiment of the present invention. [Diagram 32] FIG. 32 is a schematic orthogonal view showing the data logger of FIG. 31 mated to a beam attachment point in the form of a DIN rail and mating attachment. [Diagram 33] FIG. 29 is a front orthogonal view of the sealing and diffuser element of FIG. 28. [Diagram 34] FIG. 34 is a rear orthogonal view of the sealing and diffuser element shown in FIG. 33. [Diagram 35] FIG. 35 is a schematic top orthogonal view showing the arrangement of the front circuit board and sealing and diffuser elements of FIGS. 33 and 34. [Diagram 36] FIG. 13 is a top orthogonal view of an additional circuit board of the CCM including sealing and diffuser elements and buttons. [Figure 37] FIG. 11 is a top orthogonal view of a data logger in accordance with a second embodiment of the present invention. [Figure 38] FIG. 38 is a front orthogonal view of the data logger of FIG. 37. [Figure 39] FIG. 39 is a partial cross-sectional view of the data logger of FIGS. 37 and 38. [Diagram 40] FIG. 40 is a first partial top orthogonal view showing the inside of the LAM of FIGS. 37 to 39. [Diagram 41] FIG. 41 is a first schematic top orthogonal view showing the inside of the LAM of FIGS. 37 to 40. [Diagram 42] FIG. 42 is a first partial top orthogonal view showing the inside of the LAM of FIGS. 37 to 41. [Diagram 43] FIG. 43 is a second schematic top orthogonal view showing the inside of the LAM of FIGS. [Diagram 44]FIG. 44 is a partial schematic top view showing details of the connection between the front circuit board and the main circuit board of the LAM of FIGS. 37-43. [Diagram 45] 20(b) is a first partial top orthogonal view showing the relationship between the terminal block and the stacking connector portion of the protective shield of FIG. 19(b). [Diagram 46] FIG. 40 is a partial top orthogonal view showing the connections between the stacking connectors, the flexible circuit board, and the main circuit board of the data loggers of FIGS. 37-39. [Figure 47] FIG. 47 is a top orthogonal view of the connector plate of FIG. 46. [Figure 48] FIG. 48 is a bottom orthogonal view of the connector plate of FIGS. 46 and 47. [Figure 49] FIG. 20 is a second partial top orthogonal view showing the relationship between the terminal block and the stacking connector portion of the protective shield of FIG. 19(b). [Figure 50] FIG. 44 is a partial orthogonal cross-sectional view showing the relationship between the protective shield, retaining plate, and circuit board of the LAM of FIGS. 37-43. [Figure 51] FIG. 44 is a partial top orthogonal view showing the inside of the LAM of FIGS. 37-43, showing a terminal block and a front wall portion. [Figure 52] 44(a) and (b) are orthogonal views of the front circuit board of the LAM of FIGS. [Diagram 53] FIG. 44 is a partial side view of the LAM of FIGS. 37-43, showing the electrical connections to all the functions on the front and main circuit boards of the LAM. [Figure 54] FIG. 44 is a top orthogonal cross-sectional view of the front wall of the LAM of FIGS. 37-43, showing the diffuser and front flap of the SD card and USB ports. [Figure 55] FIG. 13 is a partial front orthogonal view of the front wall showing ports for an SD card and a USB connector along with a button for the LAM. [Figure 56] A partial side cross-sectional view showing a portion of the front flap and the connection to the USB connector port. [Figure 57] FIG. 13 is a front top orthogonal view of the front flap for the SD card and USB ports. [Figure 58]FIG. 13 is a rear top orthogonal view of the front flap for the SD card and USB ports. [Figure 59] FIG. 13 is a partial top orthogonal view of the front wall showing a portion of the front flap and the connection with the USB connector port. [Figure 60] FIG. 39 is a partial orthogonal view showing the relationship between the front flap and the reset button of the data logger of FIGS. 37 and 38. [Figure 61] FIG. 39 is a partial cross-sectional side view showing the relationship between the front flap and the reset button of the data logger of FIGS. 37 and 38. [Figure 62] FIG. 13 is a top perspective view of a partially assembled CCM according to a second embodiment of the present invention. [Figure 63] FIG. 4 is a schematic side view of a CCM according to a second embodiment of the present invention. [Figure 64] FIG. 62 is a partial schematic top orthogonal view of the CCM of FIG. 61 showing ports for sensors requiring air entry. [Figure 65] FIG. 64 is a detailed cross-sectional side view of the CCM of FIG. 63 showing ports for sensors requiring air entry. [Figure 66] FIG. 13 is a top orthogonal view of a partially assembled data logger according to a second embodiment, showing generally the main CCM circuit board and communications module. [Figure 67] FIG. 66 is a first top orthogonal view of the partially assembled data logger, showing the circuit board of FIG. 66 and the auxiliary circuit board for the CCM of FIG. 63. [Figure 68] 67 is a second top orthogonal view of the partially assembled data logger of FIG. 66, showing the circuit board of FIG. 66 and the auxiliary circuit board for the CCM of FIG. 63. [Figure 69] FIG. 13 is a top orthogonal view of a partially assembled CCM with an antenna attached to the top surface, in accordance with a third embodiment of the present invention. [Figure 70] FIG. 13 is a top orthogonal view of a partially assembled CCM with three antennas attached to the top surface in accordance with a fourth embodiment of the present invention. [Figure 71]FIG. 13 is an orthogonal view of a data logger with four antennas mounted on the top surface prior to connecting power, sensor and actuator cables in accordance with a fifth embodiment of the present invention. [Figure 72] FIG. 13 is an orthogonal view of a data logger with four antennas mounted on the top surface prior to connecting power, sensor and actuator cables in accordance with a sixth embodiment of the present invention. [Figure 73] FIG. 13 is a top orthogonal view of a LAM for a battery-powered data logger in accordance with a seventh embodiment of the present invention. [Figure 74] FIG. 74 is a top orthogonal view of the LAM of FIG. 73 with the protective shield of FIG. 19(c) in place. [Figure 75] FIG. 13 is a side view showing a data logger including a stack of LAMs connected to a CCM according to an eighth embodiment of the present invention. [Figure 76] FIG. 76 is a partial cross-sectional side view of the data logger of FIG. 75, showing the mechanical connection between the LAM and CCM. [Figure 77] FIG. 77 is a partial cross-sectional side view of the data logger of FIGS. 75 and 76 showing the electrical connection between the LAM and CCM. [Figure 78] 78 is a partial cross-sectional side view of a data logger having an appearance similar to that of FIGS. 75-77 according to a further embodiment of the present invention. [Figure 79] FIG. 79 is a side orthogonal view showing the electrical and communication connections between the LAM and CCM circuit boards in the data logger of FIG. [Figure 80] FIG. 80 is a top orthogonal view of the LAM circuit board of FIG. [Figure 81] FIG. 80 is a bottom orthogonal view of the LAM circuit board of FIGS. 78 and 79. [Figure 82] FIG. 80 is an orthogonal view of a connector used to make the electrical and communication connections between the LAM and CCM circuit boards of FIG. [Figure 83] FIG. 79 is a top orthogonal view of the bottom LAM in the data logger of FIG. [Figure 84] FIG. 84 is a detailed view of the bottom LAM of FIG. 83 showing the relationship between the vertical circuit board and the protective shield. [Figure 85]1 is a block diagram showing a data logger system according to a first embodiment of the present invention. [Figure 86] FIG. 86 is a block diagram showing a variation of the data logger system of FIG. 85. [Figure 87] FIG. 11 is a block diagram of a data logger system according to a second embodiment of the present invention. [Figure 88] FIG. 88 is a block diagram of a data logger system variation of the data logger system of FIG. [Figure 89] FIG. 13 is a block diagram of a data logger system according to a third embodiment of the present invention. [Figure 90] FIG. 1 is a block diagram of a water network control system using a data logger according to an embodiment of the present invention. [Figure 91] FIG. 91 is a schematic flow diagram showing the logic for operating the water network control system of FIG. 90. [Figure 92] FIG. 1 is a block diagram of an electric vehicle control system using a data logger according to an embodiment of the present invention. [Figure 93] FIG. 93 is a schematic flow diagram showing logic for operating the electric vehicle control system of FIG. 92. [Figure 94] FIG. 80 is a schematic diagram of the electronics and communications architecture for the data logger shown in FIGS. 78 and 79. [Figure 95] A range of exemplary widgets that may be used in the system shown in Figures 90 and 91 are shown. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0044] Referring to FIG. 1, the data logger 100 includes at least two modules: a logging and / or actuation stacking module (LAM) 120; and A control and communication module (CCM) 110; Includes: As shown here for purposes of example, the LAMs 120 and CCM 110 are integrated into a single box 100 to form a data logger. The data logger system including the CCM 110 and LAM(s) 120 will vary depending on the complexity of the system with respect to the sensors and actuators included. The system and its sensor and actuator components are user selectable and configurable, for example using additional LAM(s) 120. However, while in a preferred embodiment a single CCM 110 is provided, multiple LAMs 120 may be provided in a stack as shown in Figures 75-77. In this first embodiment, for purposes of illustration, the LAMs 120 and CCM 110 are integrated into one box or block 100.

[0045] The data logger block 100 includes a top portion as the CCM 110 and a bottom portion as the LAM 120. This division of the data logger block 100, and the ability to remove the top portion 110, allows a user to easily install and work on the data logger block 100 from the top portion only, without affecting any of the cables 150 routed within the LAM 120 of the data logger block 100. For purposes of illustration, one sensor or actuator cable 150 and one power cable 150A are shown in each of Figures 1, 2 and 4, and elsewhere in those figures. Such an arrangement is suitable for simple data monitoring applications where sensor signals are simply acquired for processing.

[0046] The LAM 120, and any additional LAMs (not shown) to which a user's data logging system may need to be connected, may be electrically connected as described below, and is here made from die-cast and painted aluminum, making it robust in terms of resistance to vibration and shock in a variety of applications. Other materials suitable for the manufacture of the LAM 120 may be used as known in the art.

[0047] The LAM 120, and therefore the data logger 100, is fixed in place by screwing it to the base plate 200 using a 100x100mm square array of M4 holes 210, engaged by screws 182. Various base plate designs may be used. The LAM 120 may also be connected by screws or other suitable fasteners to any flat surface provided with threaded holes available for mounting if screws are used. The bottom edge of the LAM 120 is fitted with a rubber O-ring 215 in a groove 213. As shown diagrammatically in FIG. 5, the rubber O-ring 215 extends around the bottom edge of the LAM 120 of the data logger block 100 and seals against the base plate 200 in a manner effective to prevent the ingress of water and dust. Desirably, the rubber O-ring 215 should allow a hard stop between the housing of the LAM 120 and the base plate 200, rather than a volume lock.

[0048] After the LAM 120 is screwed to the base plate 200, the user can wire the desired data logger system (which will vary with each data logging application and can result in anything from simple to complex) with the top of the LAM 120 open and without the CCM 110 in place. The wiring step involves running wires, such as the sensor and actuator cables 150, through a cable enclosure and clamp arrangement as described below. During wiring, the circuit board 122 of the LAM 120 is protected by a protective shield 130, as will be further described below with reference to FIG. 19.

[0049] In the embodiment shown, two cable seal and clamp ports 154A, 154B are provided on the left hand side of the LAM 120 of the data logger block 100 and five ports 155 are provided on the right hand side of the LAM 120. The port arrangement may be different in other embodiments, for example a different number of ports may be selected.

[0050] The left hand side ports 154A, 154B are designated for power and CAN communications (RS485 communications could be used in alternative embodiments) and are conveniently provided by a four-wire cable (power (PWR), ground (GND) over twisted pair for CAN communications) under the control of the microcontroller of the CCM 110. The cable 150A extending through port 154A terminates in one of four pin terminal blocks 126A mounted on the main circuit board 122 inside the data logger block 100. The second left hand side port 154B can be used to "daisy chain" power and the CAN bus to another data logger block (not shown) to expand the user's data logger system, if desired. Such other data logger blocks may be of the type currently described, although "daisy chaining" to other devices or data logger types is not excluded. In the embodiment shown, this "daisy chaining" is not required and so port 154B is closed by a sealing plug 162, as further described below.

[0051] The data logger 100 includes electrical safety circuits to ensure safe connections to power, communications, sensors and actuators and to avoid short circuits caused by accidental misuse.

[0052] In this embodiment, five ports 155 are provided on the right hand side of the LAM 120 of the data logger block 100. A greater or lesser number of ports may be provided. Providing five ports 155 allows for up to five cables to be connected to the data logger block 100 while still providing a complete seal at the ports 155, as described below. It should be understood that in other embodiments, such a complete seal may not be required.

[0053] The ports 155 are intended to be used to interface with various sensors (e.g., moisture or temperature sensors) and / or actuators (e.g., flow control valves or stepper motors or other actuators (whether on / off, on by direction or by pulse width modulation (PWM)) as needed for the convenience of the user, for example, by the user's process control system. The ports 155 allow cables extending therethrough to interface with a desired number of terminal blocks and pins (e.g., 2×10 pin terminal block 126) fitted to the circuit board 122 (subject to space constraints) to provide power and signals to and from the sensors or actuators and to any microprocessor or microcontroller used for process control that may include microcontroller(s) on-board the data logger block 100, one microcontroller provided for the CCM 110 and for each LAM 120. The microprocessors may be used for several applications. If desired, specific pin assignments may be set at the factory or different pin assignments may be presented depending on the application.

[0054] In the embodiment shown, after the cables 150, 150A are physically positioned and electrically terminated within their respective terminal blocks 126, 126A of the LAM 120, the cables 150, 150A are hermetically clamped to the LAM 120 and data logger block 100 using a combination of hermetically clamping elements 160, 165.

[0055] 6(b) and (c) and 7(a)-(c), a seal clamp is shown that includes complementary seal clamp elements 160, 165 that allow connection of cables 150, 150A to the LAM 120 of the data logger block 100 and in some embodiments, such as in field applications, e.g., in process plants, prevent ingress of dust or water into the data logger block 100. The seal clamps 160, 165 allow achievement of at least an IP67 rating, and desirably an IP68 ingress rating, in accordance with IEC standard 60529, the contents of which are incorporated herein by reference. As shown, the cable seal clamp elements include a tubular sleeve 160 and a wedge 165.

[0056] The sleeves 160 have a cylindrical head 160a which, in use, sits on the inner wall 120A of the data logger housing (here the outer wall of the LAM 120, but the same principles apply whether the sleeve 160 is used to clamp and seal a cable in the CCM 110 or the LAM 120), a smaller diameter tube portion 160b to extend through the bore 155a of the port, and a bore 161 for accommodating the end 150a of the sensor or actuator cable 150. The bore 161 of each sleeve 160 is configured to provide a double lip seal of the sleeve 160 on the cable 150, more specifically the cable end 150a, by engagement of the lip 160c with the cable end 150a. The sleeves 160 provide a tolerance for the diameter of the cable end 150a. For example, the bore 161 of the sleeve 160 may conveniently accommodate a nominal difference in cable diameter of 1 mm for sealing different sizes of cables with diameters between 2 mm and 7 mm. If any of the ports 154A, 154B, 155 are not used, a blank sealing element 162 is provided.

[0057] A wedge 165 is provided for each sleeve 160 as shown in Figures 8-10 to complete the seal arrangement. The wedge 165 is pressed down through a slot formed in a side wall 169 of the port 155 over the cable end 150a into the angled wedge cavity 167. The side wall 169 acts as a guide for the wedge 165 and also as a guide for the position of the tubular sleeve 166 and associated cable end 150a. When pressed down, not only does it create a clamping effect on the cable 150, but it also ensures that the seal is forced up against the inner surface of the outer wall 120A of the LAM 120 of the data logger block 100 to complete the sealing of the cable against the inner surface of the outer wall 120A. The angled back surface of the wedge 165 is configured to allow for such sealing. The pinching effect is achieved by providing a slot 166 formed in the wedge 165, with narrow sections 166b and 166c that are smaller than the diameter of the cable end 150a, and a wider section 166a. The narrow section 166b is formed in the thinner section 165b of the wedge 165 so that it can flex and allow the cable end 150a to enter the wider section 166a. As the wedge 165 is pressed further into the wedge cavity 167, the cable is pinched by the wider section 166a, creating a pinching effect that completes the clamping of the cable end 150a at the port 155. The narrow section 166c provides less stiffness to the wedge 166, providing mechanical relief to the primary prongs, allowing the wider section 166a to bend inwardly to pinch the cable.

[0058] With regard to sealing of cable end 150a against LAM 110, this involves the action of wedge 165. Specifically, when wedge 165 with an angled back surface is pressed into place in angled slot 167 in wall 169 (extending toward outer wall 120A of LAM 120), wedge 165 is forced laterally outward toward wall 120A of LAM 120. This causes the annular surface of portion 160a to contact and seal with wall 120A. As described above, this sealing of cable end 150a against LAM wall 120A at ports 154A,B 154,155 allows data logger block 100 to meet IP68 rating using sealing O-ring 213 described above. Sealing of cable end 150a includes sealing against ingress along the path of cable 150 as well as sealing against ingress through the outside of seal and LAM wall 120A.

[0059] It will be appreciated that in the embodiment shown, each cable 150, 150A connected to the data logger 100 is hermetically clamped in place as described above. Each port 155 is configured in the same manner as described above to allow such hermetically clamping to occur. Additionally, the end of cable 150A is hermetically clamped in place at port 154B in the same manner as described above. When clamped in place, cable end 150a cannot actually be pulled out, for example, because someone could trip over cable 150 and disconnect electrical terminal block 126, 126A from circuit board 122, which could be an electrical risk. The clamping and sealing elements as described above do this while eliminating the need for expensive cable connectors. However, in other embodiments, sealing may not be required (e.g., if the data logger is used indoors in a workshop or laboratory type environment). Standard cable connectors may be used instead.

[0060] When ports 154B, 155 are not in use, they can be blocked by sealing plugs 162 as shown in Figure 6(a). In this case, forcing with wedges 165 prevents the sealing plugs 162 from tipping inward. Lubricant may be required during assembly of the sealing clamp to avoid excessive deformation of the tubular sleeve 160 in the wrong direction, i.e., vertically, when the wedges 165 are pressed downward, but rather to provide a lateral force on the tubular sleeve 160 to form an effective seal.

[0061] As shown in Figure 14, retainer plates 168, 168A are fastened to walls 169 of bottom 120 using associated screws 168B, which press wedges 165 downward to secure cables 150, 150A with a clamp seal. In the case of retainer plate 168, screws 168B are tightened within threaded bores 168C as shown in Figures 3, 4, 16 and 17.

[0062] In another embodiment, the CCM 110 may include the sealing and clamping elements described above to accommodate power and CAN communication directly to the CCM 110. However, in such an embodiment, the sealing and clamping elements are assembled from the underside of the CCM 110, rotated 180 degrees, and clamped upwards within the CCM. Such a CCM 110 may be secured directly to the bottom mounting plate 200 rather than to the LAM 120.

[0063] It is convenient to work on the LAM components from above. To assist with the illustrated embodiment, as shown in detail in Fig. 19(a), a plastic protective shield 130 is provided above the main circuit board 122 to shield the electronic components and prevent the user from touching them while assembling the data logger 100, as well as to prevent the cables from rubbing against the electronics during operation. The protective shield 130 is provided with a raised portion 130A to cover the power connection block 128, slots 130B, 130C and 130E to accommodate the terminal blocks 126 and 126A, respectively, a raised portion 130D to protect the front circuit board 191 and associated components as described below, and a slot 130G to accommodate the wall 169 that defines the port 155.

[0064] Alternative forms of plastic protective shields 1130 and 2130 are shown in Figures 19(b) and 19(c), with slots 1130A-G and 2130A-G differing depending on the data logger components to be accommodated, whether a standard cable connector needs to be included and whether the data logger is battery powered as further described below. Figure 19(b) shows a protective shield 1130 suitable for a data logger similar to those already described (and thus the reference numbers are common except for the prefix "3" unless otherwise specified) but using a standard cable connector. Slot 1130B accommodates the terminal blocks 3126 and 3126A of the data logger, further described below with reference to Figures 37-72. Slot 1130H is sector shaped with inwardly curved sloping surfaces that aid in the connection of a standard cable connector.

[0065] 19(c) shows a protective shield 2130 suitable for a data logger, similar to those already described except that it is battery powered (hence the reference numbers are common except for the "2" prefix unless otherwise specified) and uses standard cable connectors. Three slots 2130J accommodate the three batteries 2500 of the data logger whose LAM 2120 is shown in FIGS. 73 and 74.

[0066] The LAM 120 of the data logger block 100 is then ready for either another logging and actuation module or block, or alternatively, as shown here, the control and communications module (CCM) 110, to be positioned and secured in place. In either case, as shown in FIG. 14, this step is accomplished by installing connectors 190, retaining combs 177 within wells 170, and providing comb retainers 176 at each corner of the LAM 120. Screws are convenient fasteners for this purpose, for example, M2.5 pan head screws 171 can be used. Such installation is easily performed by a user working from above the LAM 120. The screws 118 are, for example, M4 cap hex bolts, and for convenience, the screws 118 and 182 for securing the LAM 120 to the base plate 200 are the same.

[0067] Connector 190 is shown in Figure 12 and retaining comb 177 is shown in Figure 13. Connector 190 is a tubular component with an upper 192 and a lower threaded portion 193 with a bore 191 extending therethrough. Retaining comb 177 has tines 177a for securely gripping connector 190 and fits within splines 192A of connector 190. Aperture 177b receives screw 171a for threading retaining comb 177 through bore 171 and securing it within retainer 176, for example as shown in Figure 8.

[0068] The CCM 110 is then positioned over one Logging and Actuation (LAM) module 120 and closes the data logger block 100 as shown in FIG.

[0069] In other embodiments, as shown, for example, in Figures 75-77, further LAMs 120 may be included to form a stack of LAMs, which are collocated in the same footprint as the LAM module 120, but may also be "daisy-chained". It will be appreciated that this allows the data logger system and the process control system with which it is associated to be modularized over time, for example as additional sensors and / or actuators are included. Similarly, a data logger system including data logger 100 may allow modules to be removed over time, perhaps because fewer sensor signals require processing, or because an actuator(s) is found to be obsolete or redundant. This may aid in the testing of prototypes, where at the start of prototype development it may be desirable to monitor some sensors and / or actuators. As the prototype item is understood and progresses towards a production version, it may prove possible to remove sensors and their associated logging and actuation modules. The nature of the controller, whether a microcontroller or microprocessor, can be modified in the same way. This also allows for simplification and cost reduction of the process control system.

[0070] As shown in Figures 16-18, the CCM 110 is then connected to the LAM 120 by fitting the screw 118 through the well 115 into the bore 191 of the connector 190. Again, this is easily accomplished by the user working from above. In this embodiment, an O-ring 215A is placed in a groove 213A in the wall 110A of the CCM 110 to seal the compartment 111 and main circuit board 140 from the ingress of moisture. However, other sealing arrangements are possible, and customized sealing components may be used to specifically facilitate plastic molding of the CCM 110 and LAM 120.

[0071] The CCM 110 of each of Figs. 16(b) and 17(b) differs from the CCM 110 of Figs. 16(a) and 17(b) in that it requires an additional circuit board 140A. The additional circuit board 140A simplifies and becomes robust, especially the combined sealing and diffuser element 238 for the top LEDs 126-129, 131 and 136, and the sealing element 125A for the top button 125, as shown in Fig. 36, although it takes up more space for components. As shown in Fig. 36, the additional circuit board 140A, which is connected to the top wall by a bolt inserted through a hole 141A, is located a short distance (e.g., 4 mm) from the top wall of the CCM 110, allowing the use of flatter sealing elements 238 and 125A. This allows for better sealing and also makes injection molding of the CCM 110 easier. In other embodiments, the additional circuit board 140A is not required, as described below.

[0072] 2, 14 and 20-21, power to the data logger 100 is an industrial 9-30v raw supply provided from cable 150A (including ground and power wires) and port 154A (hermetically clamped as described above) through a power connection block 128 on the adjacent wall 120C of the LAM 120. Power and ground wires are connected from the power connection block 128 to the circuit board 140 of the CCM 110.

[0073] The electrical connection between the CCM 110 and the LAM 120 allows for live power to be transmitted from the LAM 120 to the CCM 110 and in some embodiments is made by a spring pin connector 142 shown in Figures 21(b)-(f), for convenience two such spring pin connectors 142. Figures 21(d) and (e) show an additional circuit board 140A for the CCM 110 described above with reference to Figures 16(b) and 17(b). As shown, the male spring pins 142 extend downward from the above CCM 110 to an array of female electrical pads 144 raised above the top surface 120A of the LAM 120. The female electrical pads 144 are shielded by the same circuit board shield 130 to ensure that the user does not short out any of them while working inside the data logger block 100 (e.g. with a screwdriver). The female electrical pads 144 are connected to the main circuit board 122 by a multi-conductor cable or a flexible circuit board 136 which may be connected directly to the circuit board. Figures 41-46 show an alternative connection of the data logger 3100 in which the spring connector 3142 connects to the female pads 3144 and to the main circuit board 3122 via the interconnects 3142A, 3142B and the flexible circuit board 3136A. The interconnects 3142A are received in a slot 3168E, as shown in Figure 48, formed in a planar body 3168D of the connector plate 3168 in which the female pads 3168a are provided as shown in Figure 45. In an alternative embodiment, a multi-conductor cable connection may be used.

[0074] Additionally, if LAM 120 needs to be connected to another LAM, spring pin connector 122A allows electrical connection to the circuit board of the other LAM, which is accomplished by using spring connector 122A to pick up female pads on the other LAM.

[0075] In the embodiment shown, although alternative arrangements are possible, the electrical connections provided via the above-described electrical connection system for the data logger block 100 are as follows: Industrial power supply 9~30v 2x CAN communication (RS485 communication is an alternative, although it is 5.0V instead of 5.5V due to the nature of the RS485 transceiver chip) 5.5V low power bus

[0076] The 5.5 volt power from the step-down converter is then used by the CCM 110 and the LAM 120 (as well as any additional LAMs 120 in a stack of modules as shown in Figures 75-77). The 5.5 volt power is regulated by the step-down converter to the required voltage, and a dedicated CAN microcontroller (which may be a microprocessor 3199 as shown in Figures 43, 44, 52(a) and 52(b)) located above the main circuit board 122 of the LAM 120 and below the protective shield 130 can be powered up, and CAN communications can begin between the LAM 120, the CCM 110, and any additional LAMs in the data logger block 100.

[0077] CAN communication over CAN lines is carried out between the CCM 110 and the LAM 120 (and any additional LAMs in a stack of LAM modules 120 as shown in Figures 75-77) over two spring pin connectors 142.

[0078] For their on-board power requirements, either the CCM110 or the LAM120 use raw industrial power (V raw ) can be used. V raw Such power provided by may be available after initial power-up of the respective CCM and LAM microcontrollers by the 5.5v power supply and after communication acknowledgement from the CCM 110 microcontroller. If power via Vraw is unavailable, for example due to a power outage, backup power may be provided via a Vcom backup bus that can select power from an auxiliary (AUX) power module, an example of which is described below. The Vcom rail or bus, in an embodiment, is powered by a power protection circuit in the CCM 110. Vcom provided power to each of the CCM 110 and LAM(s) 110 in the stack.

[0079] Battery operation and use of a PoE power source are two examples of power sources that could potentially provide an uninterruptible power supply (UPS) for the data logger 10. The CCM 110 switches power from Vraw to Vcom and in some embodiments can select the "best available" power source from an auxiliary power module, more than one auxiliary power module may be provided. This can be done in a number of ways, for example by a simple diode method that only allows the highest forward voltage to be applied to Vraw, or by a more complex power switching method using a voltage sensing transistor / FET.

[0080] If more than one auxiliary power module is provided, negotiation can occur between them via serial communication mediated by the controller(s) as to which one will power the Vcom rail.

[0081] An alternative power and communication architecture that may be preferred is shown in Figure 94, which shows a power and communication system 910 for a data logger including a CCM 110, a LAM 120 and a stack of further LAMs 120A. The LAMs 120A are auxiliary power modules and can function as a backup power source allowing the data logger 100 to be provided with an uninterruptible power supply (UPS). Other stack arrangements are possible and the auxiliary power module 120A need not be positioned at the bottom of the stack of modules.

[0082] LAM120 is provided with industrial power inputs 9-36VI of 9-36 volts, similar to LAM120A. LAM120A here functions as an auxiliary power module (AUX) with a battery pack 2500 that is chargeable by a battery charger BC. The battery charger may receive energy harvested by a solar cell or the like, but in this embodiment is charged by power from the industrial power inputs 9-36VI and includes a buck / boost regulator VR to regulate the voltage during charging. As above, battery pack 2500 may be controlled by a battery management system (integrated with battery charger BC) as known in the art. Other embodiments of the auxiliary power module are possible.

[0083] The LAM120 and LAM120A are also provided with serial communication capabilities, and for that purpose respective inputs (COMMSI) and outputs (COMMSO) are provided. In this embodiment, COMSI and COMMSO are electrically the same. A Comms bus (here CAN or RS485) allows serial communication through the LAM120, LAM120A and CCM110. The Comms bus is terminated in a Comms bus terminator 920, which includes a termination resistor arrangement that allows the Comms bus to operate in noisy environments, for example where very long cable arrangements are used. The Comms bus may be extended out from the COMMSI and COMMSO ports for daisy-chaining to other modules outside the stack. The Comms bus is electrically connected (without fuses or logic, directly connected to the +ve and -ve rails (COMM+, COMM-) of the Comms bus.

[0084] The industrial power supplies 9-36VI feed the power rail Vraw during normal conditions, i.e. when the power supply is available. The Vraw rail with the ground rail (GND) supplies voltage to each LAM120, LAM120A and CCM110. As mentioned above, the CCM110 allows voltage regulation to 5v or 3.3v via the voltage regulators 5VR and 3v3. The power supply of the LAM120 is the same. If a power supply by a specific charging system is included, it may be necessary to include an auxiliary voltage regulator (AR).

[0085] In the LAM120A, functioning as an auxiliary power module, the buck / boost converter VR is simply required to regulate the voltage to the battery charger BC, so regulators 5VR and 3V3 are not required except in the circumstances described below.

[0086] Regarding fuses 120F and 120AF, electronic fuses, advantageously silicon-based e-fuses, are included in LAM120 and LAM120A, respectively. Conventional fuses, either wired or resettable type, usually take time to switch connected power rails, and their characteristics are also affected by environmental temperature. Secondary connection systems powered through the data logger stack (by stacking or daisy chaining) can potentially cause power loss of the entire system 910 in the event of a fault within the entire system. Electronic fuses 120F and 120AF provide fast, configurable protection that disconnects faulty circuits. Since no physical fuses are present, there is no need to replace parts after a fault, and once the fault is removed, a simple reset (or auto-reset) allows operation of the entire system. e-fuses can also be system endpoints, allowing the data logger (through LAM120 or CCM110) to provide feedback to the user regarding a fault that has occurred.

[0087] The power and communication system 910 further provides a battery power rail (VBATT) capable of supplying battery power from the battery pack 2500 to the LAM 120 and the CCM 110, respectively.

[0088] The CCM 110 and LAM 120 are provided with power supply prioritization controllers 110P and 120P, respectively, with circuitry to enable automatic or instantaneous transfer to a backup or secondary power source (here, battery pack 2500 of LAM 120A). The power supply prioritization controllers 110P and 120P are configured such that a 9-36v industrial power source (9-36VI) is the preferred power source, and the transfer to backup power from battery pack 2500 is performed outside the 9-36v voltage window. All instances of power supply prioritization are intended to include overvoltage protection to protect subsequent circuitry from external voltage transients.

[0089] With respect to the "primary" microcontrollers 3199 for CCM110 and LAM120, these are as described above. However, in this embodiment, LAM120A is "dumb" with no functionality beyond functioning as an auxiliary power module, and does not include a microcontroller. Thus, the primary and secondary microcontrollers 3199 and 3199A of LAM120A are shown in dashed outline. However, LAM120A could also be a smart device in terms of the implementation of the primary and / or secondary microcontrollers 3199, 3199A. In this case, 5VR and 3V3 voltage regulators, and an auxiliary voltage regulator AR, if required, are also included in LAM120A.

[0090] The CCM 110 further comprises, in this embodiment, a secondary microcontroller 930. This is an optional component required if the CCM primary microcontroller 3199 does not have additional communications such as Bluetooth for configuration of the device. The secondary microcontroller 930 is also included if the primary microcontroller 3199 cannot update its own firmware without the interaction of the secondary microcontroller 930.

[0091] In the embodiment shown, the connections between the secondary microcontroller 930 and the primary microcontroller 3199 include the following: - Serial communication (UART / USART, or SPI, or I2C) - Primary microcontroller reset - Erasing the primary microcontroller (optional, may be omitted)

[0092] The Bluetooth module of the secondary microcontroller 930 includes an ARM Cortex processor that controls Bluetooth communications external to the primary microcontroller 3199. In the event of an over-the-air firmware upgrade, the secondary microcontroller 930 may receive new firmware and store it in a dedicated flash memory chip connected to the secondary microcontroller 930 before reflashing the primary microcontroller 930. The secondary microcontroller 930 may keep multiple copies of the firmware of the primary microcontroller 3199. It may also act as a "watchdog" and intervene by "resetting", "erasing" and "reflashing" the primary microcontroller 3199 with the appropriate firmware, if necessary. If necessary, the secondary microcontroller 930 may revert to the original default firmware that was initially functional on the primary microcontroller 3199, for example if a malfunction is detected.

[0093] In other embodiments, the functionality of the secondary microcontroller 930 or 3199A may be integrated with the functionality of the primary microcontroller 3199.

[0094] System 910 also provides the ability to provide a power interrupt signal to all of the stacked CCM and LAM modules 110, 120 and 120A via a power interrupt bus 940. This bus allows the CCM and LAM modules to enable / disable their operation based on the state of push button controller 912, which in turn is determined by whether the user presses or does not press push button 915 (externally available to the user through the casing of CCM 110) or push button 925 of LAMs 120 and 120A (externally accessible to the user for LAMs 120 and 120A).

[0095] The state of the push button controller 912 may be controlled by the push button controller 912 itself or by the microcontroller 3199. In an embodiment, the push button controller controls the device to power on if it is not already on. The push button controller 912 may allow a state that applies a momentary press as an input to the microcontroller 3199 (and thus can be used as a binary sensor input endpoint).

[0096] The push button controller 912 may also be able to detect a long press and not apply a different electrical signal to either directly shut down the power regulators of the entire stack as part of the power prioritization control system 110P, 120P or to allow a controlled shutdown by the microcontrollers 3199, 3199A, 930 in the stack.

[0097] With regard to the operation of the UPS system, if zero voltage is detected in the Vraw rail (conveniently by a battery management system integrated in the battery charger BC, but also seamlessly controlled via, for example, the microcontroller 3199 of the LAM120A, which may include logic for system protection, e.g., the microcontroller 3199 of the LAM120A may cut power to the system 910 if the battery voltage drop is too low or if the temperature rises above a threshold), the microcontroller 3199 may switch the power source to battery power from the battery pack 2500 through the VBATT rail operating in conjunction with the GND rail. In this embodiment, the desired power supply state is an industrial 9-36v power source. Thus, if that source is available, the microcontroller 3199 will drive Vraw accordingly to provide power. However, in other embodiments, this may be reversed.

[0098] The configuration of each module 110, 120, 120A is the same as previously described with respect to memory (SD and USB), reset (RESET) functionality, and on-board sensor (S) capacitance and sensor interface circuit (SC). The CCM 110 is also provided with serial wireless communication (WC) capability via LoRA or other long-range transmission protocols.

[0099] Connections can be made between adjacent LAMs 120, CCMs 110 and AUX power modules so that the data logger 100 knows the order in which the LAM blocks 120 are in the stack, and thus a visual representation of the system can be automatically derived and shown to the user by a mobile or web-based application as further described below. The connection can take the form of a single-ended 3.3v direct to the microcontroller 3199, with a current-limited connection allowing the data logger 100 to understand the stacking order of the LAM blocks 120 via the CCM 110. Verification and communication is by a communication bus. A spare connection may also be provided.

[0100] As shown in Figures 22-28, each LAM 120 has its own removable SD card (not shown) on the main circuit board 122 for configuration and logging of high speed sensor and / or actuator or other endpoint data as accessible memory. The LAM 120 is also provided with a USB-C connector and used to power the LAM microcontroller (mounted on the main circuit board 122 and shown in the second embodiment as Figure 50, item 3199) which performs calculations and communication and accesses only the SD card and offloads the contents of the SD card via wired USB, for example, to a suitable computing device. The SD card and USB-C connector are accessible through a front sealing flap 195 on the front wall 120A of the LAM 120, as shown in Figure 23, through an SD card port 195A and a USB-C port 195B. A further embodiment of the front sealing flap 3195, having generally similar functionality to the front sealing flap 195, is described below with reference to Figures 57-59. Additional microcontrollers or microprocessors may be included to perform functions specific to the LAM 120, but these interface with the primary microcontroller or microprocessor as described above, which provides most of the communication, logging, and control of such LAM.

[0101] The use of an SD card and USB-C connector for storage and transfer of data from the data logger block 100 allows for the avoidance of streaming data, which can constrain a data logging system, however, the data logger block 100 may also be capable of streaming data if desired.

[0102] The front of the LAM 120 is also provided with a button 194 and three RGB LED illumination lamps 196, 197 and 198 for user interaction and feedback, where various information can be communicated by different light colors (provided colors across the visible spectrum), flash and / or strobe routines. The RGB LEDs are assigned to power status 196, CAN communication status 197, and Bluetooth communication, respectively. An additional LED 198 is also provided. The button 194 and LED 198 may be user configurable (i.e., as at least one user configurable input and at least one user configurable output) to enable user actions and provide information based on the data acquisition, processing and / or control strategy in which the data logger 100 is used. Alternatively, the LED 198 may be used to provide the status of additional wireless communication protocols. More than one user configurable button and LED may be provided.

[0103] The LEDs 196-198 reside on a front circuit board 191, as shown in Figs. 24, 25 and 27-29, which is screwed into the wall 120A of the LAM 120 by two countersunk bolts 191A (e.g., M3 type), with the boss 191B of each bolt soldered into the front circuit board 191 and fitting through the threaded bore 191A (one of which is shown in Fig. 29, which is clamped and sealed in place of the optically transparent or opaque silicone seal and diffuser 138, allowing the RGB LEDs 196-198 to emit light through square holes 196a-198a in the front of the LAM wall 120A and illuminate an overlay sticker with an icon indicating the function of each LED 196-198. Portion 130D of the circuit board shield 130 is connected to the front circuit board 191 and the RGB 52(a) and 52(b), the front circuit board 3191 is shown in more detail, but in the second embodiment, it is the same as the front circuit board 191 described in the present invention with threaded bores for connecting bosses (not shown) labeled 3191A. The button mounting portion 3194A is mounted to the front of the front circuit board 3191 shown in FIG. 52(a), as are the RGB LEDs 3196-3198 which interface with the flexible circuit board 3136A. The microprocessor 3199 and button circuitry 3194b are mounted to the rear of the front circuit board 3191, as shown in FIG. 52(b).

[0104] The silicone seal and diffuser 138 is provided as a single sealing part, as shown in Figures 33 and 34, with a sealing surface 138B formed on a protrusion 138A, each of which protrudes through a respective rectangular hole 196a-198a and provides a seal thereto. The sealing surface 138C provides a seal with the inner surface of the wall 120A of the LAM 120 and with the front surface of the front circuit board 191. The cavity 138D allows for the placement of LEDs on the front circuit board 191 which shine through the sealing part, and more specifically the protrusion 138A, through the rectangular holes 196a-198a for illumination as described above. A sealing rib 138E is provided extending around the front edge of the sealing part 138 to ensure contact with the wall 120A and a seal around the sealing part 138.

[0105] A similar silicone seal and diffuser 238 is provided for the LEDs of the CCM 110, as shown in Figure 36. Here, sealing surface 238B provides a seal where protrusions 238A protrude through holes 126-129, 131 and 136 to direct light from the CCM LEDs.

[0106] The button 194 is protected from water and dust ingress, again optimally IP68 rated, by a silicone seal and physical cover 194A that protrudes through the outer wall 120A of the LAM 120, as shown in Figures 27, 28 and 34. A user presses the button 194 to interact with the LAM 120 of the data logger block 100. The button 194 is connected to the main circuit board 122 by a multi-core cable or a flexible circuit board. In the case of the button 3194 of the data logger 3100, shown in Figure 37, the button 3194 is connected to the main circuit board 3122 by a flexible circuit board 3136A that extends from a block 3194A connected to the button 3194 to a block 3136B that is electrically connected to the main circuit board 3122, as shown in Figure 51.

[0107] The CCM 110 is, in an embodiment, made from impact and UV resistant plastic, although aluminum may be preferred if an external antenna is used and an internal RF antenna does not require RF line of sight from the CCM 110. As shown in FIG. 21(a), the CCM 110 has a button 125 and six indication RGB LEDs 126-129, 131 and 136, which utilize the same silicone circuit board sandwich sealing system as described above for both the LEDs 126-131 and the button 125. As with the LAM LED 198, the LED 130 may be configured by the user for at least certain purposes. The LED 130 may conveniently be an output actuator indicating the value of the sensor signal, whether before or after processing (including by conversion or calculation), as described below. In this case, the LED 136 may function as an alarm to warn the user if the parameter sensed by the sensor is outside of acceptable limits.

[0108] The main purpose of the CCM 110 is as a communication mechanism with the controller and the user, as well as to enable CAN communication with each LAM 120 in the stack. Wireless communication is provided and multiple protocols may be provided, including Bluetooth (BLE), Cellular Radio Communication (CELL), LoRa Low Power Wide Area Network (or all of these), as indicated by icons 127, 128 and 131. In other embodiments shown, only Bluetooth (BLE) may be selected, allowing the user to interface with the CCM 110 and data logger 100 via a smartphone, tablet or other communication device via a Bluetooth app. Thus, a Bluetooth chipset is included within the LAM 120. Other forms of communication may also be provided, including a wired connection, e.g., an Ethernet connection. In such an embodiment, the functionality of the LEDs 127, 128 and 131 that are not required for wireless communication may be defined by the user.

[0109] The CCM 110 also contains a microprocessor to host a state machine and set up tasks, if configured by the user. The state machine approach is preferred for control systems using the data logger 100 of this embodiment, regardless of whether the state machine used is deterministic or non-deterministic.

[0110] In further embodiments, an array of blind holes may be provided on the back of the LAM 120 to facilitate other mounting options for the data logger block 100, including stacking of LAMs 120. Additionally, a proprietary DIN mounting system may be included with the LAM 120, allowing the data logger block 100 to be mounted inside an industrial enclosure. Figures 30 and 31 show an embodiment in which the data logger block 100 includes a mounting bracket 305, which may be fitted onto a DIN rail 310 that forms the mounting point for the data logger block 100.

[0111] In some cases, an industrial power source (such as the 9-30 volt power supply mentioned above) may not be available. In such cases, other powering options are available, including battery power and energy harvesting, or Power over Ethernet (PoE), which allows the transmission of both power and data over a twisted pair cable system. Such powering options are provided via an auxiliary power module, which conveniently has the same form factor as the LAM120, 2120 and 3120.

[0112] As shown in Figs. 73 and 74, the LAM2120 (functioning as an auxiliary power module) may comprise, for example, three 18650 lithium batteries 2500 connected in series to power the data logger. Such an arrangement will power up to 2Amp at 11.1 volts. The batteries 2500 may be rechargeable and may be powered from a single solar panel (not shown) wired through a cable sealing and clamp system. On-board battery management includes an MPPT system to draw maximum power from the solar panel and allow charging of the battery through the battery charging circuit. A fuel (state of charge or SOC) gauge is also included for battery balancing and accurate power consumption and run time estimation. Solar power may also be used directly as a power source for the data logger 100, and the power source may be automatically switched to battery power by the CCM110 control system if solar power is not available.

[0113] The LAM 2120 may be connected to other LAM(s) 120 through a CAN communication system as described above.

[0114] Further embodiments of data logger 3100 are shown in Figs. 37-72. Data logger 3100 is similar to data logger 100 as previously described, and reference numbering is the same except for the prefix "3" unless otherwise specified. Data logger 3100 allows for connection of sensor and actuator cables 3150, either by clamp and sealed connector as described above, or by standard connector as shown in Fig. 71. It is also possible to use a single clamp or connector plate 3168 on both sides of the data logger as shown in Figs. 40-48, rather than two clamp plates 168A on the power connection side as described above. Data logger 3100 is suitable for, but not limited to, applications requiring air pressure or air quality sensing, and for these applications, port 3900 allows air access to an air pressure sensor 3930 mounted within the substrate. Other sensors, such as gas composition sensors or air quality index sensors, may be included instead or in addition.

[0115] As shown in Figures 56-58, the front sealing flap 3195 is provided with an outer rib 1195a to provide a seal for the USB and SD card slots 1197a and 1198a of the LAM 1320, and includes one main outer rib 1195a to seal the outer opening, and two secondary seals 1195b to seal the USB-C port 3195B and the SD card port 3195A. The sealing flap 3195 also has a section 1197 that presses into the USB-C port 1195B and provides an additional seal for the USB-C port 3195B by an interference fit. A shorter extension 1198 that serves the same function is provided for the SD card port 3195A.

[0116] The front sealing flap 3195 is removable but needs to be secured to the LAM 3120 during use. The insertion tip 1196, together with the sealing arrangement and central sealing rib 1196b described above, assists in such securing. The insertion tip 1196 desirably includes a partially flexible portion 1196a to allow for insertion and securing, as well as a hole ready for removal. Removal of the front sealing flap 3195 also allows access to the reset button 3210 as shown in Figures 60 and 61. The reset button 3210 allows for a hard reset of the LAM 3120, allowing for reconfiguration, if desired.

[0117] 63-65, a sensor 3930 is connected to the CCM circuit board 3140A and a seal is required from the rest of the CCM 3110. To this end, a port 3900 communicates with the sensor 3930 via a small passageway 3920, allowing air to enter the sensor 3930, such as an air pressure sensor or an air quality index sensor, although other sensors are not excluded. The seal 3910 keeps such air away from the rest of the CCM 3110, as a sealing rib 3915 presses against the inner surface of the top wall 3110A of the CCM 3110 to complete the seal. The seal 3910 utilizes the same kind of silicone circuit board sandwich system as the LEDs 126-129, 131 and 136 and the top button 125. Referring to FIGS. 66-68, the three circuit boards 3122, 3140 and 3140A are shown in conceptual form. It will be appreciated that the electronic configuration of the data logger 3100, or any other embodiment, can vary greatly depending on the application to which it is applied. However, in addition to the on-board sensors 3930 as described above, a position sensor 3400 (in this case a surface mounted active GNSS sensor available from Taoglas, e.g. under part number ASGGB184.A) is provided on the circuit board 3140. Also provided is an inboard mounted wideband antenna 3500, e.g. a Warrior PA.710.A wideband 4G / 3G / 2G SMD PFIA, also available from Taoglas. FIG. 67 shows the LED diffuser 3238B in place along with the air sensor seal 3910 and the CCM button 3125 seal. FIG. 68 shows the air sensor 3930 as well as the RGB LED 3238C for the CCM 3310. Light from RGB LED 3238C is transmitted through slots 3126a, 3127a, 3128a, 3129a, 3131a, and 3136a (shown in FIG. 62) and through diffuser portion 3238B of diffuser 3238 as shown in FIG.

[0118] As mentioned above, an inboard antenna can be fitted inside the CCM 110 to allow wireless communication with the data logger 110. An external antenna 3800 can also be fitted through a cutout 3802 in the circuit board 3140 as shown in FIG. 66 to extend wireless range as needed. Such external antennas 3800 extending through the top surface 3110A of the CCM 3110 can be of a type known in the art and commercially available. Conveniently, any desired number of antennas 3800 can be employed at the user's option. FIG. 69 shows a CCM 3110 with one external antenna 3800. FIG. 70 shows a CCM 3110 with three external antennas, and FIGS. 71 and 72 show a CCM 3110 with four external antennas corresponding to Bluetooth, LORA, cellular and user assigned wireless communication protocols respectively.

[0119] The antenna system of the CCM3110 may be a MIMO (Multiple-In Multiple-Out) dual antenna system. The dual antennas allow for asynchronous transmission and reception of radio signals at slightly different radio frequencies, which facilitates increased data throughput and integrity.

[0120] Referring to Figure 78, there is shown a further embodiment of a data logger 4100 having a similar appearance to the data logger 100 shown in Figure 75. The various components of the data logger 4100 have the same functionality as provided for the data loggers 100 and 3100 as described above, and the reference numbering is generally the same as provided above, with the addition of the numerical prefix "4".

[0121] The data logger 4100 includes one CCM 4110 and two LAMs 4120 and 4120A. LAM 4120A is the top LAM connected to the CCM 4110 and the bottom LAM 4120. The CCM 4110 has four external antennas 4400 in the form of SMA connectors.

[0122] The mechanical connection between each of the LAMs 4120 and CCMs 4110 is made as described above with reference to Figures 8, 12 and 13 by the placement of connectors 190 and retaining combs 177 in wells 170 and comb retainers 176 at each corner of each LAM 4120. Similarly, as shown in Figures 16-18, the CCM 4110 is connected to the top LAM 4120A by engaging threads 118 through wells 115 into bores 191 of connectors 190. Further description of the mechanical connection between the CCM 4110 and the LAMs 4120 and 4120A is provided above.

[0123] However, the electrical and communication connections between the LAM 4120 and the CCM 4110 are simplified from those of the above embodiment. The spring pin connector 142 is replaced with a vertical printed circuit board 4130. This may ensure a more reliable electrical connection and may also eliminate the need for a flexible circuit board or multi-conductor cable for connecting the LAM circuit board 4122 and the CCM circuit board 4140. The LAM circuit board 4122 is positioned at a fixed height above the LAM base 4200, as indicated by the O-ring groove.

[0124] As shown in Figures 79-81, the CCM circuit board 4140 and the LAM circuit board 4122 mate with a circuit board connector 4310 that includes a desired number of plated contacts (e.g., 10 or 20, although the number is flexible). Suitable circuit board connectors 4310 (one is shown in Figure 82) may be obtained from Kyocera under the AVX trademark. The circuit board connector 4310 is electrically connected to the respective CCM and LAM circuit boards 4140 and 4122 via a carrier board 4320.

[0125] A vertical printed circuit board (PCB) 4300 is placed in electrical and communication contact with a circuit board connector 4310 through a carrier board 4320. The vertical PCB 4300 connects the bottom LAM circuit board 4122 to the top LAM circuit board 4122, and connects the top LAM circuit board 4122 to the CCM circuit board 4140.

[0126] 83 and 84, the use of the vertical PCB 4300 requires modifications to the plastic insulating shield 4130 used to protect the electronic components of the circuit board 4122. Thus, the function of the plastic shield 4130 is as described above, but the plastic protective shield 4130 is provided with a pyramidal projection or protrusion 4130A with a slot 4130AA through which the vertical PCB 4300 can extend. The pyramidal projection 4130A also allows for easier alignment of the vertical PCB 4300 to facilitate interfacing with the connector 4310 for the CCM 4110 or the LAM 4120 depending on the placement of the LAM 4120 and CCM 4110 in the data logger 4100.

[0127] Additionally, the CCM 4110 of Figures 78 and 79 does not include the additional circuit board 140A used in the CCM 110 of Figures 16(a) and 17(b) since the CCM 4110 typically houses components such as top LEDs and other components on a CCM circuit board 4140. The same electrical connections can be made as in the previous embodiments.

[0128] In some embodiments, PoE (Power over Ethernet) may be used as a power source for each of the data logger 100, 3100 and 4100 embodiments. A separate PoE module may be provided, in one embodiment having the same form factor as the LAM 120, 3120, 4120 described above, to function as a PoE module (but with the same or similar functionality as the CCM 110, 3110 described above). This allows for the use of a much wider range of voltages, for example in the order of 20v to 52v, in accordance with the new PoE standards, compared to the 9-30v industrial power supplies. Such an additional PoE LAM may desirably allow for Ethernet TCP / IP communication with a cloud server. Furthermore, since it may be assumed that the PoE system has an uninterruptible power supply (UPS) in its power supply, a battery may not be required in the PoE auxiliary power module to provide resilience against power outages.

[0129] In a convenient embodiment, the PoE module may have the same form factor as the CCMs 110, 3110 described above. Such a CCM may have an Ethernet port (RJ-45) on the side, conveniently next to the USB and SD card flaps.

[0130] Exemplary embodiments of the data logger block 100 The data logger block 100 and its constituent LAM(s) 120 or CCM 110 may be used for some exemplary possible applications as follows: (1) General purpose data logging and actuation, e.g. - 1 pair of differential analog inputs - 4 user configurable analog inputs - 4x user configurable digital input or output terminals, - 5x user configurable power pins (PWR), and -5x dedicated ground terminals (GND), General purpose data logging and actuation, including (2) Logging and actuation of digital inputs and outputs, e.g. -10x user configurable digital inputs or outputs or pulse width modulation, - 5x user configurable power pins (PWR), and -5x dedicated ground terminals (GND), Logging and actuation of digital inputs and outputs, including: (3) Analog data logging, e.g. -10x user configurable analog inputs: - Configured in pairs to be differential, or - Single-ended analog, or -4~20mA current loop - 5x configurable power pins (PWR), and -5x dedicated ground terminals (GND), Analog data logging, (4) Differential analog data logging, e.g. -2x differential analog input pins in 2 pairs, -6x configurable analog inputs: - Single-ended analog, or -4~20mA current loop - 5x user configurable power pins (PWR), and -5x dedicated ground terminals (GND), and differential analog data logging, (5) A user-configurable driver, for example, driving a load up to 2Amp, e.g. - 2x sets of 4x configurable pins, -2x stepper motors (all pins in the 2x4x set may be used), - 4x DC motors (paired pins may be used), and -8x relays (switch high or low, single pin available), 2x sets of 4 configurable pins to support any combination of: User configurable drivers, including

[0131] The LAM 120 may also be provided with minimal components, for example excluding a microcontroller or other chip and / or using the LAM main circuit board 122 to perform power and communication functions, simply allowing wiring of power to terminal block 126A and CAN communication to CCM 110 via spring connector(s). Even spring connectors may be avoided if cost needs to be minimized. This embodiment may be used to interface with CCM(s) 110 that include sensors.

[0132] On-Board Sensors The data logger 100 may accommodate a variety of sensor types as described above. Additionally, the CCM 110 or LAM(s) 120 may include on-board sensors, some examples being: -(1) A vibration sensing unit that includes a high speed 2000Hz 12-bit precision 3-axis accelerometer for vibration and motion detection; or (2) An inertial measurement unit (IMU) that includes a 200 Hz 9-axis inertial measurement chipset to calculate G-forces, orientation, and heading, and that includes a 3-axis accelerometer, a 3-axis gyroscope, and a 3-axis magnetometer; or (3) A GPS unit that includes a high-precision GPS that utilizes the GPS and GLONASS satellite systems; or -(4) including the sensors of options (2) and (3); -Precise positioning including dead reckoning, -G force, -direction, -Azimuth, -Motion gestures, -Vehicle stops, turns, road bumps, corrugations, Vehicle GPS and IMU units to enable fusion processing of

[0133] Using the Data Logger Block 100 When the data logger 100 is deployed, a user can log or stream data points from sensors and actuators connected to or contained within the data logger 100. For example, in the case of a plant watering grid system, the sensors may include soil moisture sensors and the actuators may include water flow valves or faucets that can turn on or off depending on the sensed moisture according to logic provided in the LAM microcontroller, which can also perform any necessary calculations or conversions.

[0134] Most conveniently, the sensed data is logged to a memory storage device, such as a USB drive or SD card, as it is acquired, by opening the sealing flap 195 and retrieving the data from the USB drive or SD card through ports 195A or 195B. The advantage of logging data to such memory storage is that it is not hampered by the available wireless network data rate, as would be the case with streaming data wirelessly or off. This allows for very high data rate logging of sensor acquisition and actuator endpoints, where the data at hand may take longer to transfer from the data logger 100 than it does to acquire the data. This may be advantageous to some users in very fast operating systems.

[0135] However, data can be streamed wirelessly from the data logger 100, for example using the TCP / IP protocol. Such a data logger 100 may include all or a combination of the following: -Wi-Fi communication, e.g. 802.11bgn Wi-Fi communication at 10MBps'; - Cellular communication, for example by including a cellular data chipset, from the data logger 100 -GPRS, -3G, -4G, and -Dedicated Cellular IoT Bands: -NB-IoT, and -CAT-M1, cellular communications, which allows for streaming of data; LoRA for long range RF communications using the ISM RF bands, either point-to-point between devices in the system or acting as a base station to remote devices in the system, which may include a LoRA-WAN communications structure for interfacing with retail carriers; -Satellite communications.

[0136] The data acquired from a memory storage device, such as a removable SD card, or wirelessly can then be processed using software, convenient web-hosted software, allowing a user to customize the data processing for a data acquisition system built for use in process control, etc. Alternatively, a user may process the acquired data within their own software, whether custom developed or "off the shelf", for example via the Office platform.

[0137] A data logging system including a data logger block 100 as described above and enabling data processing via web hosting software allows a user to build a control system based on, for example, a state machine, as known in the art of process control, to create and configure tailor made states, sensor and actuator actions within the states, and the necessary transition logic between states appropriate to the process control system the user is building. AND / OR logic may be preferred as the transition logic.

[0138] A "state machine" is at least one, but more generally a collection of states, where each state is a user-selected configuration of endpoints across one or more devices that may be contained within a system or one or more subsystems. An infinite number of state machines are possible, and they are configured as desired by the user. For example, in a soil watering network, a device may include a soil moisture sensor (with an endpoint soil moisture content) and a valve (actuator) to deliver water (endpoint valve goes on or off) when the soil moisture is below a given set point. The two states are: Moisture rises above set point, turning off water tap Moisture falls below set point, turns on water tap

[0139] It will be appreciated that the soil moisture sensor can be effectively polled more frequently when the water valve is turned on to avoid wasting water, and perhaps less frequently when the water valve is turned off, especially if the moisture content is at a level that indicates recent rainfall known to the user and can be programmed into the state machine. The state machine may be much more complex than this simple example.

[0140] States can transition between them if thresholds at one or more endpoints are achieved simultaneously within that state. A variety of different transitions to different states can be achieved if different combinations of thresholds are specified and achieved simultaneously.

[0141] Configuring an endpoint that is a sensor can include issues of how often to poll the sensor and what to do with the data (e.g., logging it to internal memory and / or streaming it to another device in the system or to a connected server for remote logging and display of data).

[0142] The configuration of an endpoint that is an actuator may be to receive input data, perform some action with that actuator, and configure what to do with the resulting output of data indicating what has been done (e.g., log it to internal memory and / or stream it to another device within that device of the system, or to a connected server for remote logging and display of the data).

[0143] In an embodiment, state machines must be specified at least at the device level, and can then optionally be specified at the subsystem and system levels as applicable to user requirements, with device-level state machines taking precedence.

[0144] In an exemplary embodiment, each state includes the following settings: If necessary, -Device power settings - Power on, working - Different levels of sleep for different devices -Communication per communication socket available to the device (i.e. Bluetooth, LoRa, RS485, Wi-Fi, Cellular, Satellite) -Allow or disallow communication from other devices (data logger systems and data logger systems or process control systems using endpoint settings) -Setting the maximum data rate per communication socket Optionally allow or disallow endpoints to stream data at a configurable maximum rate per communication socket Optional -Specific endpoint settings

[0145] In an embodiment, the device, when in a suitable power state, functions as part of a data logger system and is connected via a socket allowing communication over that socket. An exemplary arrangement is shown in the figure.

[0146] The state machine can be set up at a subsystem level whereby one device in the system is assigned the position of controller and other device(s) are notifier(s), as shown in the figure.

[0147] The "controller" then maintains the state machine and issues tasks to the device(s) in the subsystem according to the state machine.

[0148] A "notifier" performs a task and notifies the controller when the task is accomplished.

[0149] A "task" may include configuration of an endpoint with the addition of evaluation of endpoint data against various thresholds. In an embodiment, at least a notifier reports to the controller when a threshold is reached in a flip-flop fashion, minimizing network overhead for communication of tasks.

[0150] A notifier is tasked by the controller and if the threshold combination is reached, the controller may cancel the task on the notifier, change to its next state, and issue a new task to the notifier depending on the threshold required to exit this new state and transition to another state, and the setup of the device-wide endpoint settings.

[0151] Such data logging systems may advantageously create highly autonomous systems of logging and control, minimizing the low data rate limited and potentially high latency network overhead often associated with low power, remote, low cost electronic devices. Such data logging systems may facilitate "edge computing" whereby minimal communication is required to maximize the desired outcome of the data logging system (or process control system based thereon) from the user's perspective.

[0152] The data logging system advantageously includes a server and a web user interface that allows configuration and visualization of the state machines required for the data logging system, the inclusion, and the calculations performed by the transformations on the acquired signal and actuator data. The state machines can be stored by machine code or as scripts created by a graphical user interface, for example a web user interface. The web user interface may be accessed via a web app. Alternatively or additionally, configuration and visualization may be possible via a native mobile app.

[0153] The server then stores the state machine scripts in a database and allows the configuration to be written, updated and downloaded to devices in the field, either by TCP connection to remotely connected devices via the gateway, or by Bluetooth connected devices via a mobile phone application or a Bluetooth enabled internet connected computer. In a particularly preferred embodiment, the data logger 100, 3100, 4100 is equipped with Bluetooth functionality. Such scripts can also be downloaded and transferred to the LAM or CCM, for example by being downloaded to an SD card and plugging the SD card into the SD card port of the LAM.

[0154] Back-end software is provided to take this configuration and convert it into a file that can be read by the System Controller firmware.

[0155] The backend software also allows live two-way interaction between the data logger blocks 100, 3100, 4100 connected to the Internet by TCP / IP or by a Bluetooth proxy (Cranio system and a phone with a Bluetooth connection to the Internet). The backend software includes subsystems for logging sensor and actuation data to a database as well as forwarding such streaming data to the Internet via a suitable web-based application such as web sockets. Backward lookup of data in the database is conveniently made possible by a backend RESTful API. Routing of data between endpoints not located on the same local network (each endpoint being a sensor, actuator, or a translation of data from sensors and / or actuators) is made possible by the backend software routing system, allowing the data logging system to span the wider Internet.

[0156] Advantageously, the data logging system includes the ability to request data stored in the system flash memory(s) for a particular period of time. Assuming the data logger block 100 can interact with the sensors / actuators / endpoints faster than they can be polled and streamed to a web hosting database, it is advantageous to be able to request high speed data for a particular period of time even if it takes time to offload this data.

[0157] This feature is typically made possible by a combination of transforming and streaming "slower" data endpoints into a web-hosted backend database that indicate an event has occurred. The user configures the transform to indicate an event or a logical "TRUE FALSE" expression that may be at a much lower data rate than the raw endpoint of interest. Upon reviewing the data and finding the slower event data, the user can then request high-speed data around that event that provides unique value to the user.

[0158] The data logger system may also provide "dashboard(s)" in the form of visualizations of endpoint data, as described above, optionally forwarded to a server by user-selected devices or subsystems.

[0159] Within a set of states (of a state machine), each endpoint set may be optionally configured to forward its data to the server at a rate that is individually configurable relative to the rate of the endpoint's underlying polling. When forwarded to the server, the endpoint data may be conveniently stored in a server database (or in the cloud) for historical lookup, and may also be displayed retroactively in a live view on the device or subsystem dashboard.

[0160] The dashboard may include "widgets" that show endpoint data or can function as endpoints that may physically reside on a server used by the state machine of the data logger system. Widgets may include buttons, sliders, input fields, charts, graphs, dial faces, indicators, and custom graphic elements that show endpoints or output of data from endpoints (e.g., a graphical representation of an endpoint, such as the rotational position of a stepper motor or a needle on a dial face). A user can configure the dashboard with various widgets according to user preferences by setting and positioning them on a page in a web browser as described above, or by native mobile applications for each device and subsystem.

[0161] Such data logging systems conveniently enable edge computing via a "transformation" system. A transformation is a mathematical or logical function configured on a device, such as a sensor actuator, to convert endpoint data into a new data output. In an embodiment of the data logger system, the transformation is performed by a LAM microcontroller.

[0162] A transformation can be set by a user in the same way as an endpoint, for example an actuator endpoint. A transformation may take data from one or more endpoints, which may be local to the device associated with that endpoint and local to that endpoint. Data may be taken at user configurable intervals (i.e., every n data points from endpoint X) and calculated into a new endpoint that can be treated the same as other endpoints.

[0163] If a translation endpoint is configured by a state machine, its underlying endpoint may conveniently inherit the configuration necessary to achieve a desired data output rate (which may be matched to the network speed). Tasks can be issued to the translation endpoint by the controller and evaluated and processed in the same way as any other endpoint.

[0164] Transformations may be calculated at set time intervals, as defined by the user, or whenever a new sensor data point is acquired. This allows for the creation of logical expressions that allow for the detection of "events" as well as the conversion of raw data into meaningful process information for the user's application. Such events can be used in process control strategies within state machines, or, only if necessary, can be provided over the Internet by data streaming using wireless protocols, as described above. In this way, computer processing power can also be modularized, with additional computer processing resources added on-board to the user device of the data logger 100, 3100, 4100 (such as a personal computer or tablet) being accessed when appropriate.

[0165] The data logger system of an embodiment of the present invention includes the following components, each of which is described above: ·server A system or subsystem of a device - Individual devices - A wired or wireless subsystem that acts as a gateway to the server Each device, system, or subsystem of the device has: - Endpoint - conversion - State Machine - Dashboard(s)

[0166] Each device must be configured with a state machine that defines its endpoint configuration and any tasks that it reports to the larger subsystem.

[0167] The system of devices extends from a single device, a subsystem of communicating devices, and a server.

[0168] The device can only communicate with the server if it is connected to the Internet. This is done by the device having serial socket(s) that allow both serial communication and Internet connectivity through at least one connection to the Internet. Such devices are known as gateways. The gateway can be a mobile phone or a personal computer (tablet, laptop, etc.) or a data logger, as mentioned above, and can be connected to the server via serial and Wi-Fi, cellular or satellite connections.

[0169] 85-89, several data logger system block diagrams illustrating the flexibility of use and configuration of data logger 100 are shown.

[0170] FIG. 85 shows a system 1800 with a server 1810 forming part of a wide area network (WAN) with a direct internet connection 1816 to a single device 1850, in this embodiment a smartphone 2000 with Bluetooth capabilities. The range of Bluetooth, e.g. 10m, allows the user of the smartphone 2000 to configure the data logger 100 as shown in the figure and receive data, conveniently transformed by transformation as described above. Dashboard(s) and desired "widgets" (e.g. as described above) may be provided on the smartphone 2000, allowing quick visualization of data and transformations, whether in real time or retrospectively after data download. It will be understood that the device is not limited to a smartphone, but can be any computing device or IoT device. Also, the widgets can be endpoints that interact with devices in the system 1800 in their own capacity. Some exemplary widgets are described below with reference to FIG. 95.

[0171] The server 1810, in an embodiment, is provided by a third party service provider, is conveniently cloud-based, and has an internet connection 1815 to a user LAN network 1812, which also provides the dashboard(s) 1830 as described above, conveniently in the same format as that displayed on the smartphone 2000, but where necessary, further transformation of the data can also take place within the user LAN network 1812. The user LAN network may include a web app 1820 and a native mobile app 1825 to enable configuration and visualization of the data logger 100. The web app 1820 and the native mobile app 1825 are available from the third party service provider. However, such configuration is transferred via the server 1810 to the smartphone 2000 and then to the data logger 100. In an alternative embodiment, the user may download the configuration to an SD card or USB and transfer it directly to the data logger 100. This option may be more convenient if the user is physically close to the data logger 100.

[0172] In this embodiment, the server 1810 may enable data hosting by a third party service provider.

[0173] FIG. 86 shows an alternative system 1800A for enabling configuration of the data logger 100 by a single device, again a Bluetooth enabled smartphone 2000 via a user server 1860, rather than a third party server 1810. The system 1800A differs from the system 1800 of FIG. 85 only by limiting the role of the third party server 1810 to downloading new software that can be used to configure the data logger 100A. Otherwise, the necessary software and firmware (and data from the data logger 100) are hosted on the user's own server 1860 in the user LAN network 1812A. It will be appreciated that cloud hosting is also possible. Thus, an internet connection 1817 with the smartphone 2000 is sufficient to enable configuration of the data logger 100A. There is no need for configuration data (again, input via a web app 1820 or native mobile app 1825) to be transferred to the data logger 100A via the server 1810.

[0174] Fig. 87 shows a more complex embodiment in which, in contrast to the systems 1800, 1800A of Figs. 85 and 86, the system 1900 includes a system 1970 with multiple data loggers 100. Similar to the system 1800 of Fig. 85 and the system 1800A of Fig. 86, configuration is possible via the user's LAN network 1912, in particular the server 1960, using a web app 1920 or a native mobile app 1925 available, for example, via an internet connection 1915, from a server 1910 of a third party service provider. The server 1910 has respective internet connections 1916 and 1917 to the device system 1950 (here including a single smartphone 2000) and to the system 1970. The smartphone 2000 is also available to transfer the configuration of the data loggers 100 of the system 1970, conveniently by Bluetooth protocol. The data is hosted on the server 1910 of the third party service provider. In alternative embodiments, system 1970 may include multiple devices, not necessarily limited to data logger 100. Other computing devices or IoT devices may be used instead. Additionally, system 1970 may be a subsystem of a more complex system.

[0175] 88 shows a system 1900A in which a user server 1960 is used in the same manner as described above for user server 1860, with the component reference numbers remaining the same with the addition of the prefix "19". A user LAN network 1912 has both the system 1970 and a smartphone 2000 and respective internet connections 1917 and 1918 to the system 1970. Configuration of the data logger 100 in the system 1970 can be accomplished either via the smartphone 2000 or directly by the user without the use of an intermediate device.

[0176] FIG. 89 shows a complex system 5000 which again in this embodiment includes a cloud-based third party server 5010 and its wide area network as well as a further cloud SAAS server 5110.

[0177] The SAAS server 5110 may be an additional cloud server hosted by a third party provider with dedicated resources for use by the system 5000. Instead of users using the available cloud server 5010 (potentially at no cost) or hosting their own server on suitable computer hardware and network 5060, the third party provider can host this server 5110 with dedicated resources that are more than those available from the server 5010. This ensures data integrity, security, and increases resources for data storage, computational requirements for streaming large amounts of data, and even cloud resources that can be used in further embodiments for post-processing of data, such as machine learning or artificial intelligence.

[0178] The SaaS server 5110 allows users to access servers that have more resources than the free third-party server 5010, avoiding the potential complexities associated with deploying and maintaining such resources on the user server 5060.

[0179] The system 5000 may include multiple gateways 5100A and 5100B with multiple data loggers 100 as described above. The gateways 5100A and 5100B enable communication via the LoRA protocol to tertiary systems 5200A and 5200B, each of which includes multiple data loggers 100. This arrangement is particularly suitable when components of the system are located remotely from one another. The gateways 5100A and 5100B as well as the tertiary systems 5200A and 5200B may be enabled to communicate with each other.

[0180] The device 2000, which is again a smartphone in this embodiment, may allow configuration of the gateways 5100A and 5100B and the tertiary systems 5200A and 5200B via Bluetooth protocol when in range. However, configuration may also be done via a user LAN network 5012 and its server 5060 with a Wi-Fi or Ethernet connection 5018A to the gateway 5100A and an Internet connection 5018 to the gateway 5100B. The third party server 5010 serves the same function as a source of updates to the system software and firmware, but in the conceptual system 5000 may also be used to host data.

[0181] An additional feature in the system 5000 allows for cloud hosting of system data in a Software as a Service (SaaS) option, which can be more cost effective than hosting on a third party service provider server 5010 or the user's own server 5060 as described above. The cloud server 5110 has a private Internet connection to the server 5010. Both servers 5010 and 5110 are shown as having respective Internet connections 5016, satellite connections 5019 and cellular connections 5020 to a gateway 5100A and beyond, via the LoRA protocol, to the tertiary system 5200A. These connections are also available to the user LAN network 5012. However, a wide range of connection options are possible.

[0182] In the conceptual system 5000, configuration of the gateways 5100A, 5100B and tertiary systems 5200A and 5200B can be done through either the service provider servers 5010 and 5110 or the user server 5060 using a web app 5020 or a native mobile app 5025. In an embodiment, a user can interact with multiple different servers enabling different functionality, typically dependent on user credentials. It is also possible to have different devices and / or systems linked to different servers with authenticated shifting of responsibility to or between specific servers, typically servers 5010, 5060 and 5110 or other server configurations.

[0183] Referring to Fig. 95, several possibilities are shown that allow a user to visualize system data. Available widgets, by way of example only, are a line graph 8010, a bar graph 8020, a gauge chart 8030, a stacked bar graph 8040 that may cover several systems, and a pie chart 8060. Visualization may be provided for a particular time period, for example a date range shown in a calendar 8070. Other exemplary widgets include a clock face, a numeric output field, a text output field, a numeric input field, a text input field, and a slider input field, although there are many options and some may be user configurable.

[0184] 95 also shows a graphical input widget 8050 dedicated to a stepper motor allowing rotation of the number of steps to rotate left or right, or the angle of rotation, or the absolute position. Such widgets may be configured for other endpoints forming part of the user's system.

[0185] Each output widget can visualize data streamed to a backend server, either via a live stream or by retrospective lookup of streamed data in a database. Each input widget functions as any other endpoint in the system and can be configured in the same way as any other endpoint.

[0186] Example of the system Example 1 FIG. 90 shows a block diagram of a watering network system 6000, useful for watering plants in a garden or horticultural environment. The watering network system 6000 includes two soil moisture sensors SM1 and SM2 as well as a tap T, which provides water when the condition of SM1 and SM2 is lower than the acceptable soil moisture level. The system 6000 includes a user server 6010, which allows the configuration of the component devices of the system and for that purpose has a control module 6075 and an internet connection 6016 of the device to the system. The control module 6075 in turn includes a controller device 6100 (first device) and a notification device 6050 (second device), each with the configuration of the data logger 4100 as described above. The control module 6075 has a connection 6042 to a further device 6040 acting as a notifier for "harvesting" soil moisture signals from the soil moisture sensors SM1 and SM2 via respective connections 6031 and 6032. When, and possibly only when, the notifier 6040 indicates to the control module 6075 (via connection 6042) that soil moisture is low, the controller 6100 initiates a control response to reduce data transmission requirements through the system. The controller 6100 causes the notifier 6050 to change its state from Tap T Off to Tap T On. That task is communicated to Tap T via connection 6052.

[0187] The system 6000 achieves an efficient water network through simple logic and three transitions, as described below with reference to Figure 91. The first state (State 1) is the start-up of the system 6000, which transitions (Transition 1) to the "System Ready State" (first transition). The soil moisture sensors SM1 and SM2 sense moisture at a sampling rate of 1 Hz, in State 2 the tap T is off. It will be appreciated that different sampling rates can be adopted.

[0188] State 2 continues unless transition 2 is triggered. In the embodiment shown, transition 2 is triggered if SM1 and SM2 indicate to the notifier 6040 that their values ​​are <50%, or less than 30% at any given time simultaneously. Under these conditions, the notifier 6040 notifies the control module 6075 accordingly, and the controller 6100 notifies the notifier 6050 of the corresponding task, i.e., turning on the tap T. The system 6000 enters state 3 where the tap T is turned on, and its running status is also monitored at 1 Hz via the notifier 6050. Here the system 6000 allows a dwell time because once the soil moisture falls below a certain level, it needs a certain amount of time to correct it. Here, that time is arbitrarily set to 30 seconds (although this depends on several factors not discussed here).

[0189] If the time on the tap T exceeds 30 seconds, the system 6000 transitions to State 2 by turning off the tap (again indicated by the notifier 6050) and again monitoring the soil moisture (Transition 3).

[0190] During operation of the system, data is harvested at each device and ready to be downloaded when required by the user. Data does not need to be streamed back to the user server 6010 during operation of the system 6000, i.e., the system 6000 is not constrained by the streaming speed over the network via connection 6016.

[0191] Example 2 Figure 92 shows a block diagram of an electric vehicle control system 7000 having a similar setup as shown in Figure 90. However, the electric vehicle control system 7000 includes an electric vehicle inertial management unit (IMU) as well as a battery voltage sensor V and a GPS sensor (GPS) and strain gauges (SG). The SGs are used to monitor the forces acting on an electric vehicle chassis currently under development.

[0192] The IMU operates the electric vehicle under the influence of signals received from the battery voltage sensor V, the GPS sensor and the strain gauges. The system 7000 includes a user server 7010, which allows the configuration of the component devices of the system and for that purpose has a control module 7075 and an internet connection 7016 of the device to the system. The control module 7075 in turn includes a controller device 7100 (first device) and a notification device 7050 (second device), each having the configuration of the data logger 4100 as described above. The control module 7075 has a connection 7042 to a further device 7040 acting as a notifier for "harvesting" the signals (SX, SY, SZ) from the strain gauges SG.

[0193] The notifier 7050 harvests signals from the IMU, the battery voltage sensor V, and the GPS sensor via respective connections 7043, 7044, and 7045. The voltage signal from the battery voltage sensor V can be considered a primary control parameter and is further described below. In response to the signals harvested via the notifier 7050, the controller 7100 sets tasks for the IMU to operate the electric vehicle via connection 7043. In an embodiment, the controller 7100 may set tasks for the electric vehicle when it is stationary.

[0194] The system 7000 achieves efficient operation of the electric vehicle through a state machine with simple logic and four transitions, as described below with reference to Figure 93. The first state (State 1) is the start-up of the system 7000, which transitions to the "System Ready State" (Transition 1), and then enters a "Sleep" state (State 2) where the battery voltage sensor V monitors the voltage (with a sampling rate of 5Hz); if the battery voltage < 25.7v, the sleep state is maintained and the IMU task is unchanged. It will be appreciated that different sampling rates can be adopted.

[0195] In the illustrated embodiment, State 2 continues unless Transition 2 is triggered where the battery voltage sensor detects a battery voltage > 25.7v. Under these conditions, the notifier 7050 notifies the controller 7100, which in turn notifies the notifier 7050 of the corresponding task, i.e., running the electric vehicle under control of the IMU. The system 7000 enters State 3 where the IMU is engaged and operates the electric vehicle. In State 3, the sensor signals from the battery voltage sensor V, GPS, additional speed inputs (not shown in the block diagram), and strain gauges (AX, AY, AZ) are sampled at a sampling rate of 10 Hz with each signal except the battery voltage sensor V, which is sampled at 5 Hz. These sampling rates are user selectable.

[0196] If at any time the battery voltage V sensor detects a battery voltage below 25.7v, for example due to the vehicle being shut off, the system 7000 transitions (Transition 3) to a prepare to sleep state (State 4). The battery voltage is monitored for a selected time (sampling rate 5Hz). If the battery voltage remains below 25.7v, the system 7000 transitions (Transition 5) to "Initiate Sleep" and returns to Sleep State 2. On the other hand, if the battery voltage goes above 25.7v, the system 7000 transitions (Transition 4) back to the working state.

[0197] During operation of the system, data is harvested at each device and ready to be downloaded when required by the user. Data does not need to be streamed back to the user server 7010 during operation of the system 7000, i.e., the system 7000 is not constrained by the streaming speed over the network via connection 7016.

[0198] Structuring the data logging and processing system in this way addresses the problem that networking between devices often becomes the bottleneck of data acquisition and processing systems. In contrast, the data logger block 100 can interface with sensors and actuators at extremely high data rates, sometimes on the order of thousands of times per second. The ability to not only acquire sensor and actuator data at these high rates, but also provide control feedback at this rate, is advantageous. Transmitting sensor and actuator data over a network introduces not only data rate limitations, but also latency. Enabling the data logger block 100, via its microcontroller(s) (and any auxiliary microprocessor(s) as needed), to log and control its connected sensors and actuators at data rates that are not limited by the associated but optionally used network, provides advantages that are usually only offered by systems that are much more expensive and complex than those described here.

[0199] The intended user interaction with a data logging system using the data logger block 100 is as follows: a) A user sets up their data logging system for the first time. b) The user logs or streams all data points from the various sensors and actuators connected to the data logger block 100 to a back-end software for retroactive and detailed analysis within a web-based user interface. Streaming is one option. Another option is to download the data, for example from an SD card where the data is stored at a high-speed sampling rate (i.e., greater than the available internet speed), and download it to a user or third-party server for visualization via a dashboard as described above. This simplifies the system setup as it eliminates the need for streaming data and therefore the need for an internet connection. c) During evaluation, the user creates calculations regarding the logged sensor or actuator signal data that provide meaningful information about the user's application (e.g., a process control system for watering plants) without requiring high-speed streaming of the raw data, or retrospective review of that data. d) Users can validate that their transformations are in fact resulting in the desired outcome or event detection. e) The user may then consider reducing the high speed streaming of samples, or even the high speed logging of samples, to further optimize the data logging system, or related process control system, to reduce power consumption or further increase speed, etc. f) The user may also choose to add other data logger blocks (or possibly LAMs) to the data logging system due to the insight provided to the user by the system, at which point the above process may be repeated to further improve it.

[0200] Such data logging systems provide value to users by providing a complete IoT platform to enable electronic devices to sense and act as fast as possible without network limitations. Such data logging systems also facilitate the iterative process of refining the IoT system with fit-for-purpose data exploration tools and configuring devices in the same web or native app interface.

[0201] Modifications and variations to the data loggers and data logging systems described herein may be apparent to those of ordinary skill in the art upon reading this disclosure, and such modifications and variations are deemed to be within the scope of the present invention.

[0202] Throughout this specification, unless the context requires otherwise, the word "comprise", or variations such as "comprises" or "comprising", will be understood to imply the inclusion of a specified integer or group of integers but not the exclusion of any other integer or group of integers.

Claims

1. 1. A data logger comprising a plurality of free-standing, directly interconnected modules, The plurality of free-standing, directly interconnected modules comprises: at least one module functioning as a logging and / or actuation module (LAM), the module having a housing including a sensor interface for connecting at least one sensor and at least one actuator to the data logger, the housing enclosing a circuit board and a microcontroller mounted on the circuit board for processing signals received from the sensor interface, the LAM module including at least one memory storage device for storing data received as input from the sensor interface, the at least one memory storage device being removable from the at least one LAM module to allow for data downloading; At least one module acting as a control and communication module (CCM), having a housing directly connected to and enclosing said at least one LAM module, and a controller for controlling the operation of said data logger and for hosting a state machine for controlling the operation of said at least one actuator; Including, the housing of the at least one LAM module is electrically and mechanically directly connected to the housing of an adjacent LAM or CCM module via a complementary connector formed or housed within the adjacent LAM or CCM module; A data logger wherein signals from the sensor interface are processable by the microcontroller onboard each LAM module using a transformation determined by a user of the data logger to control operation of the at least one actuator by the state machine.

2. 2. A data logger according to claim 1, wherein the logging and / or actuation module (LAM) is directly connected to at least one further LAM, forming a stack of LAMs.

3. A data logger as described in any one of claims 1 to 2, wherein the LAMs of the same or different data loggers are networked by serial communication over a wireless network, the serial communication being provided by a protocol selected from the group consisting of a short-range protocol (preferably Bluetooth), a long-range protocol (preferably LoRA) and TCP / IP.

4. A data logger as described in claim 3, wherein the serial communication is provided by a protocol selected from the group consisting of a short-range protocol (preferably Bluetooth), a long-range protocol (preferably LoRA) and TCP / IP, and enables serial communication with a user device selected from the group consisting of a mobile phone, a smartphone, a tablet, a portable and a computing device.

5. A data logger according to any preceding claim, comprising at least one user configurable input and at least one user configurable output when selected by a user of the data logger.

6. A data logger as described in any one of claims 1 to 5, wherein the data logger includes multiple memory storage devices, and a port is provided for each memory storage device in each LAM of the data logger.

7. A data logger according to any preceding claim, wherein the data logger stores data at a rate faster than the data can be streamed out from the data logger via an available wireless network.

8. A data logger as described in any one of claims 1 to 7, comprising a plurality of power sources selected from the group including industrial power sources, battery power sources, power sources based on energy harvesting, and power sources that allow simultaneous transmission of data and power.

9. 9. The data logger of claim 8, wherein the power source includes a primary power source and at least one auxiliary power module, a LAM configured as the at least one auxiliary power module, and when multiple auxiliary power modules are used, the CCM enables negotiation between the multiple auxiliary power modules via serial communication to determine which auxiliary power module(s) will supply power to the data logger.

10. 10. A data logger as claimed in any preceding claim, wherein the at least one sensor or actuator is connected to a housing of the data logger, the connection providing the data logger with at least an IP67 rating, preferably an IP68 rating, and the at least one sensor or actuator is connected to a housing contained within the data logger by a sensor or actuator cable clamp seal, the seal forming a clamp that seals against intrusion along the path of the cable and prevents the cable from being pulled out of the housing, the clamp seal being provided within a wall of the housing by clamping the sensor or actuator cable within the wall.

11. A data logger system, at least one sensor; At least one data logger according to any one of claims 1 to 10 in communication with a process control unit; A data logger system comprising: At least one actuator is controllable by the process control unit in response to signals received from the at least one sensor and logged by the data logger.

12. 12. The data logger system of claim 11, wherein the sampling rate of the sensor input is set by a user via at least one of a web user interface, a mobile app, and a script located on the user-accessible memory, and wherein the sampling rate of the sensor input is greater than an available wireless communication network speed.

13. A data logger system, A server capable of communicating with the data logger according to any one of claims 1 to 10. A data logger system comprising: the server allows a user to configure the data logger; A user configures the data logger directly via the server; the server is capable of communicating with a user network to download software and firmware for operating the data logger, and users configure the data logger via the user network; 1. A data logger system, wherein the data logger is configured for edge computing.

14. The data logger system of claim 13, wherein the server or the user network is capable of communicating with a cloud-based memory for storing data from the data logger.

Images