Master controller for telematics integration

Abstract

A master controller may be used to provide integrated, centralized, and optimized processing of telematics data in a welding device. The master controller may receive telematics data from other components of the welding device and may apply at least some processing to the telematics data so that the telematics data can be viewed by a remote entity. The telematics data may include data related to an engine used to drive one or more components of the welding device, data related to one or more components of the welding device, or data related to a welding operation performed via the welding device. Processing of the telematics data may include formatting the data according to a single standard format, digitizing analog data, and / or processing the data for transmission to a remote entity. The master controller may provide telematics client and / or host node functionality, for example, based on a controller area network (CAN bus) protocol.

Description

[0001] This application is a divisional application of an invention patent application with an application date of March 16, 2016, an international application number of PCT / US2016 / 022581, a national application number of 201680015823.9, and an invention name of “Main controller for telematics integration”.

[0002] Claim of priority

[0003] This patent application refers to, claims priority to, and claims the benefit of U.S. Provisional Patent Application No. 62 / 134,417, filed on March 17, 2015. The above-identified application is incorporated herein by reference in its entirety. Background Art

[0004] Welding is increasingly common in all industries. Welding can be performed in an automatic manner or manually (e.g., performed by a person). However, while welding can be automatic in some cases, there are still a large number of applications where manual welding operations are used (e.g., where a welding operator uses a welding gun or torch to perform welding). In either mode (automatic or manual), the success of the welding operation depends largely on the correct use of the welding equipment. Summary of the invention

[0005] Implementations of the present disclosure are directed to a master controller for telematics integration, substantially as shown or described in connection with at least one of the accompanying drawings, as more fully set forth in the claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0006] Figure 1 An exemplary system that may be used for welding-type operations according to aspects of the present disclosure is shown.

[0007] Figure 2 An exemplary welding apparatus according to aspects of the present disclosure is shown.

[0008] Figure 3 is a block diagram illustrating an exemplary master controller system for telematics integration according to aspects of the present disclosure.

[0009] Figure 4A is a block diagram illustrating an exemplary configuration for controlling telematics integration using basic third-party telematics, without an engine control unit (ECU).

[0010] Figure 4B is a block diagram illustrating an exemplary configuration for controlling telematics integration using basic third-party telematics, with an engine control unit (ECU).

[0011] Figure 5Ais a block diagram illustrating an exemplary configuration for controlling telematics integration using basic third-party telematics and a telematics module, without an engine control unit (ECU).

[0012] Figure 5B is a block diagram illustrating an exemplary configuration for controlling telematics integration using base third-party telematics and a telematics module with an engine control unit (ECU).

[0013] Fig. 6A is a block diagram illustrating an exemplary configuration for controlling telematics integration using basic third party wireless communication components, without an engine control unit (ECU).

[0014] Figure 6B is a block diagram illustrating an exemplary configuration for controlling telematics integration using basic third-party wireless communication components and an engine control unit (ECU).

[0015] Fig. 7A is a block diagram illustrating an exemplary configuration for controlling telematics integration using an internal wireless communication component, without an engine control unit (ECU).

[0016] Figure 7B is a block diagram illustrating an exemplary configuration for controlling telematics integration using an internal wireless communication component with an engine control unit (ECU). DETAILED DESCRIPTION

[0017] Figure 1 An exemplary system that can be used for welding-type operations according to aspects of the present disclosure is shown. In this regard, "welding-type" operations can include operations according to any known welding technology, including flame welding technology (e.g., oxy-fuel welding), electric welding technology (e.g., shielded metal arc welding (i.e., manual arc welding)), metal inert gas welding (MIG), tungsten inert gas welding (TIG), resistance welding, as well as gouging (e.g., carbon arc gouging), cutting (e.g., plasma cutting), brazing, induction heating, welding, etc. Reference Figure 1 , an exemplary welding device 10 is shown, wherein an operator 18 wears a welding helmet 20 and uses a welding torch 30 to weld a workpiece 24, power is delivered to the welding torch by the device 12 via a pipeline 14, and a welding monitoring device 28 can be used to monitor the welding operation. The device 12 can include a power source, optionally an inert shielding gas source, and wherein a wire feeder will automatically provide welding wire / welding filler material. In addition, in some cases, an engine 32 can be used to drive equipment or components used during the welding operation. For example, the engine 32 can drive a generator, a power source, etc. used during the welding operation.

[0018] Figure 1 The welding apparatus 10 may be configured to form a weld joint using any known welding type technique.

[0019] Optionally, in any embodiment, the welding device 12 can be an arc welding device that provides direct current (DC) or alternating current (AC) to a consumable or non-consumable electrode of a welding torch 30. The electrode delivers the current to a welding point on the workpiece 24. In the welding device 10, the operator 18 controls the position and operation of the electrode by manipulating the welding torch 30 and triggering the start and stop of the current. When the current flows, an arc 26 is formed between the electrode and the workpiece 24. The pipe 14 and the electrode thus deliver a current and voltage sufficient to generate the arc 26 between the electrode and the workpiece. At the welding point between the electrode and the workpiece 24, the arc 26 locally melts the workpiece 24 and the welding wire or welding rod (the electrode in the case of a consumable electrode, and a separate welding wire or welding rod in the case of a non-consumable electrode) provided to the weld joint, thereby forming a weld joint when the metal cools.

[0020] Optionally, in any embodiment, the welding monitoring device 28 can be used to monitor the welding operation. The welding monitoring device 28 can be used to monitor various aspects of the welding operation, particularly in real time (i.e., while welding is occurring). For example, the welding monitoring device 28 can be used to monitor arc characteristics, such as length, current, voltage, frequency, variation, and instability. Data obtained from welding monitoring can be used (e.g., by the operator 18 and / or by an automatic quality control system) to ensure proper welding.

[0021] As shown, device 12 and helmet 20 can communicate via link 25, via which helmet 20 can control the settings of device 12 and / or device 12 can provide information about its settings to helmet 20. Although a wireless link is shown, the link can be wireless, wired, or optical.

[0022] Optionally, in any embodiment, an engine can be utilized to drive equipment or components used during the welding operation. For example, the engine 32 can drive a generator, a power source, etc., used during the welding operation. In some cases, it may be desirable to obtain information related to the engine being used. For example, data related to the engines (and their operation) used during the welding operation can be collected and used (e.g., based on analysis thereof) to monitor and optimize the operation of these engines. The collection and use of such data can be performed in a telematic manner, i.e., the data can be collected locally, at least some processing (e.g., formatting, etc.) can be performed locally, and then the data can be transmitted to a remote management entity (e.g., a centralized management station, engine supplier, etc.) using wireless technology (e.g., cellular, satellite, etc.). In various exemplary embodiments, a dedicated controller (e.g., Figure 134) to control, centralize and / or optimize data processing operations. The controller 34 may include suitable circuitry, hardware, software, or any combination thereof, for performing various aspects of engine-related data processing operations. For example, the controller 34 may be operable to connect to the engine 32 to obtain data related thereto. The connection (or acquisition of data) may be accomplished via analog sensors and / or via an electronic engine control unit (ECU), if present. In addition, the controller 34 may be operable to track or obtain welding-related data (e.g., from the welding monitoring device 28, from the device 12, etc.). The controller 34 may then transmit the data (e.g., engine-related data and welding-related data) via wireless communications to facilitate remote monitoring and / or management. In particular, for example, this may be accomplished using cellular and / or satellite telematics hardware. Reference Figure 3 Exemplary implementations are described in more detail.

[0023] Figure 2 An exemplary welding apparatus according to aspects of the present disclosure is shown. Figure 2 The device 12 includes an antenna 202, a communication port 204, a communication interface circuit 206, a user interface module 208, a control circuit 210, a power circuit 212, a wire feeder module 214 and a gas supply module 216.

[0024] Antenna 202 may be any type of antenna suitable for the frequencies and power levels used by communication link 25 .

[0025] Communication ports 204 may include, for example, a twisted pair Ethernet port, a USB port, an HDMI port, a passive optical network (PON) port, and / or any other suitable port for connecting to a wired or fiber optic cable.

[0026] The communication interface circuit 206 is operable to connect the control circuit 210 to the antenna 202 and / or the port 204 for transmission and reception operations. For transmission, the communication interface 206 can receive data from the control circuit 210 and packetize the data, and then convert the data into a physical layer signal according to the protocol used on the communication link 25. For reception, the communication interface can receive the physical layer signal via the antenna 202 or the port 204, recover the data (demodulate, decode, etc.) from the received physical layer signal, and provide the data to the control circuit 210.

[0027] The user interface module 208 may include electromechanical interface components (e.g., screen, speaker, microphone, button, touch screen, etc.) and associated drive circuits. The user interface 208 may generate electrical signals in response to user input (e.g., screen touch, button press, voice command, etc.). The driver circuit of the user interface module 208 may determine (e.g., amplify, digitize, etc.) signals and send them to the control circuit 210. The user interface 208 may generate auditory, visual, and / or tactile outputs (e.g., via speakers, displays, and / or motors / actuators / servos, etc.) in response to signals from the control circuit 210.

[0028] The control circuit 210 includes the following circuits (e.g., a microcontroller and a memory): it is operable to process data from the communication interface 206, the user interface 208, the power supply 212, the wire feeder 214 and / or the gas supply 216; and output data and / or control signals to the communication interface 206, the user interface 208, the power supply 212, the wire feeder 214 and / or the gas supply 216.

[0029] The power circuit 212 includes circuitry for generating power for delivery to the welding electrode via the pipeline 14. The power circuit 212 may include, for example, one or more voltage regulators, current regulators, inverters, etc. The voltage and / or current output by the power circuit 212 may be controlled by a control signal from the control circuit 210. The power circuit 212 may also include circuitry for reporting the present current and / or voltage to the control circuit 210. In an exemplary implementation, the power circuit 212 may include circuitry for measuring the voltage and / or current on the pipeline 14 (at either or both ends of the pipeline 14) so ​​that the reported voltage and / or current is true, and not just an expected value based on calibration.

[0030] The wire feeder module 214 is configured to deliver a consumable wire electrode to the weld joint. The wire feeder 214 may include, for example, a spool for holding the welding wire, an actuator for pulling the welding wire from the spool for delivery to the weld joint, and a circuit for controlling the speed at which the actuator delivers the welding wire. The actuator may be controlled based on a control signal from the control circuit 210. The wire feeder module 214 may also include a circuit for reporting the current welding wire speed and / or the remaining amount of welding wire to the control circuit 210. In an exemplary implementation, the wire feeder module 214 may include circuits and / or mechanical components for measuring the welding wire speed so that the reported speed is real, not just based on a calibrated expected value.

[0031] The gas supply module 216 is configured to provide shielding gas via the pipeline 14 for use during the welding process. The gas supply module 216 may include an electrically controlled valve for controlling the gas flow rate. The valve may be controlled by a control signal from the control circuit 210 (which may be routed through the wire feeder 214 or directly from the controller 210 (as shown in dashed lines)). The gas supply module 216 may also include a circuit for reporting the current gas flow rate to the control circuit 210. In an exemplary implementation, the gas supply module 216 may include circuits and / or mechanical components for measuring the gas flow rate so that the reported flow rate is real, not just an expected value based on calibration.

[0032] Figure 3 is a block diagram illustrating an exemplary master controller system for telematics integration according to aspects of the present disclosure. Figure 3 Shown are a main controller 300, one or more engine sensors 360, an external third-party communication device 362, an engine control unit (ECU) 364, traditional third-party telematics units 3701 and 3702, an external telematics unit 380, and one or more device add-ons that can use or be affected by telematics information (including, for example, "next generation" devices such as a next generation welding control communication (WCC) unit 392, a next generation welding user interface (UI) 394, a next generation machine user interface (UI) 396, etc.).

[0033] Each of the one or more engine sensors 360 may include suitable hardware, software, or a combination thereof for collecting and / or outputting sensed data related to the engine, its operation, environmental or operating parameters affecting the engine, and / or components used in conjunction with the engine and / or affecting the operation of the engine. For example, the sensors 360 may include an auxiliary power transformer sensor 3601, a battery voltage sensor 3602, and one or more engine sensors 3603 (which may provide sensed readings related to parameters or components such as coolant temperature, level (low) coolant, oil pressure, oil sender, fuel sender, oil sender switch, etc.). The sensors 360 (and the data generated thereby) may be analog.

[0034] The main controller 300 may include suitable hardware, software, or a combination thereof to provide the main control functions for telematics integration. For example, the main controller 300 may include a main processor 310, an internal communication subsystem 320, an external communication interface component 330, a telematics client component 340, and a telematics host component 350.

[0035] The main processor 310 is operable to process data, perform specific tasks or functions (e.g., related to operations performed by the main controller 300), and / or control the operation of other components in the main controller 300. The main processor 310 can be a general-purpose processor (e.g., a CPU), a special-purpose processor (e.g., an ASIC), etc.). However, the present disclosure is not limited to a particular type of processor.

[0036] For example, the main processor 310 can receive data associated with telematics-related functions or operations, and can process the data (e.g., including formatting the data based on applicable formatting standards), such as for wireless communication with a remote telematics monitoring and / or management entity. In this regard, the main controller 300 may include suitable interface components (e.g., circuits, hardware, software, or any combination thereof) to facilitate receiving telematics-related data and / or enabling interaction with components or devices that provide the data. Telematics-related data may include digital and / or analog data, and may include location, machine status, service information, engine sensor data, error codes, and other data available to the main controller 300. The data may include, for example, welding-related data 301, sensing-related data 303, and / or telematics data obtained from an ECU or a third-party telematics unit. In this regard, the telematics client component 340 may be configured to function as a telematics node, such as a controller area network (CAN) bus node, that communicates with an ECU (e.g., an electronic ECU 364). The communication may, for example, use a CAN bus based communication protocol to obtain engine data 341 provided by the electronic ECU 364. The data may then be input into the main processor 310 (as input signal 305).

[0037] Once the telematics-related data is collected and processed (including formatting) for communication, the main processor 310 can utilize available communication components to communicate (e.g., wirelessly) the processed telematics data for communication. For example, in the presence of an internal communication component (e.g., an internal communication subsystem 320), the processed telematics data for communication can be forwarded to the component via a corresponding control signal 311 for transmission. Alternatively, in the case of using external communication components (e.g., an external third-party communication device 362), the processed telematics data for communication can be sent to these components, for example, via an external communication interface component 330. In this case, the external communication component 330 can receive the processed telematics data for communication as a signal 315 and apply any necessary processing (e.g., TCP / IP processing) to facilitate communication with the external device 362.

[0038] The internal communication subsystem 320 may include suitable circuitry operable to handle communications in the main controller 300. The internal communication subsystem 320 may include, for example, a transceiver configured to support various wired or wireless technologies. For example, the internal communication subsystem 320 may be operable to configure, establish and / or use wired and / or wireless connections, such as through a suitable wired / wireless interface and in accordance with wireless and / or wired protocols or standards supported in the device, to facilitate transmission and / or reception of signals (e.g., carrying data). In addition, the internal communication subsystem 320 may be operable to process transmitted and / or received signals according to applicable wired or wireless technologies. Examples of wireless technologies that may be supported and / or used by the internal communication subsystem 320 may include: wireless personal area networks (WPANs), such as Bluetooth (IEEE 802.15); near field communication (NFC); ​​wireless local area networks (WLANs), such as WiFi (IEEE 802.11); cellular technologies, such as 2G / 2G+ (e.g., GSM / GPRS / EDGE, and IS-95 or cdmaOne) and / or 3G / 3G+ (e.g., CDMA2000, UMTS, and HSPA); 4G, such as WiMAX (IEEE 802.16) and LTE; ultra-wideband (UWB); etc. Examples of wired technologies that may be supported and / or used by the internal communication subsystem 320 include: Ethernet (IEEE 802.3), interfaces based on a universal serial bus (USB), etc. Examples of signal processing operations that may be performed by the main controller 300 include, for example, filtering, amplification, analog-to-digital conversion and / or digital-to-analog conversion, upconversion / downconversion of baseband signals, encoding / decoding, encryption / decryption, modulation / demodulation, and the like.

[0039] In conjunction with telematics-related operations in the main controller 300, the internal communication subsystem 320 may preferably support and / or utilize wireless technologies suitable for remote communications with remote peers, including, for example, satellite communications (including two-way point-to-point communications; positioning satellite communications, such as GPS; etc.), cellular communications, etc. In addition, the internal communication subsystem 320 may be used to facilitate the receipt of data related to telematics operations and / or the operation of the main controller 300 as a whole. For example, the internal communication subsystem 320 may allow for the receipt (and provision to the main processor 300) of data such as location information (e.g., location information based on GPS positioning), control signals (e.g., from a telematics server), software updates (e.g., from a supplier, operator, etc.), etc.

[0040] The external third-party communication device 362 can be substantially similar to the internal communication subsystem 320. In this regard, the external third-party communication device 362 may include appropriate circuitry and / or other related hardware for handling wired and / or wireless communications. For example, the external third-party communication device 362 may include a transceiver configured to handle one or more wired and wireless technologies mentioned with respect to the internal communication subsystem 320. However, the external third-party communication device 362 may be a dedicated off-the-shelf system, and may be a traditional third-party system. Nevertheless, the external third-party communication device 362 may provide the same type of communication as the internal communication subsystem 320, particularly with respect to telematics-related operations. The external communication interface component 330 may be used to ensure compatibility and operability of different types of component systems.

[0041] The master controller 300 is operable to interact with local components and / or systems that cooperate with telematics-related operations. In this regard, the telematics host component 350 can be configured to function as a telematics host (e.g., a CAN-bus-based host) to enable the master controller 300 to communicate with other external components or devices (e.g., a traditional third-party telematics unit 3702, an external telematics unit 380, a next-generation WCC unit 392, a next-generation welding UI 394, a next-generation machine UI 396, etc.) using, for example, a CAN-bus-based communication protocol to provide telematics-related data and / or control signals.

[0042] In operation, the master controller 300 can be configured to collect and process (format, process for communication, etc.) digital and analog telematics related data. Telematics related data can include location, machine status, service information, engine sensor data, error codes, and other data available to the master controller 300. The master controller 300 can obtain data from the electronic ECU 364 (connecting to it using the telematics client component 340). In the event that the electronic ECU 364 may not exist or is not available to provide engine data 341, the master controller 300 can collect the information directly (e.g., by interacting with the analog sensor 360). The master controller 300 can provide telematics related data to other local components that would otherwise obtain data from the electronic ECU 364, such as third-party telematics units 3701 and 3702, external telematics units 380. The master controller 300 can also transmit this data to a remote entity (e.g., a telematics server, such as ... Figure 1 server 31).

[0043] In some cases, the master controller 300 can format the telematics data into a single standard format so that a device or apparatus driven by a particular engine can support only a single communication standard. This can avoid the need to enable the device or apparatus to also support telematics units from other suppliers (e.g., third-party telematics units 3701 and 3702). In other words, the master controller 300 can allow reverse compatibility and / or compatibility with solutions from different suppliers by performing the necessary digitization and telematics formatting "translation". For example, by processing telematics data in the master controller 300, key engine-related data (e.g., information related to engine coolant, engine oil, fuel, etc.) can be provided digitally to a third-party CAN bus telematics unit, a third-party telematics unit 3702 in a single standard format, simplifying installation by not requiring splicing to analog sensors. In addition, the master controller 300 has the additional benefit of providing welding-related data 301 in addition to traditional telematics data.

[0044] In the case of using internal communication components (e.g., internal communication subsystem 320), no third-party hardware is required, thereby providing excellent value and reliability through system simplification. However, by incorporating support for external communication devices (e.g., by incorporating external communication interface 330), compatibility with traditional and / or third-party vendor communication components can be ensured in a cost-effective manner. Therefore, third-party communication devices 362 can be easily and economically integrated using standard universal communications such as TCP / IP, wherein external communication interface 330 provides the necessary TCP / IP processing to connect to a modem. The third-party communication device 362 can then allow remote connection via satellite, cellular, WiFi, or any other wireless means, such as over the Internet.

[0045] Apart from Figure 3 In addition to the configuration shown in Figure 3 Some of the elements shown may be used or implemented in other configurations (eg, based on availability, user or vendor preference, etc.). FIG. 4A to FIG. 7B Other different configurations that can be used to provide control of integrated telematics are shown, which only utilize Figure 3 Some components or devices described or shown in the.

[0046] Figure 4A is a block diagram illustrating an exemplary configuration for controlling telematics integration using basic third-party telematics, without an engine control unit (ECU). Figure 4A A main controller 400, a sensor 360, and a conventional third-party telematics unit 3701 are shown.

[0047] The main controller 400 may be similar to the main controller 300. However, the main controller 400 may have a minimal implementation including only the main processor 310. Figure 4A In the configuration shown, the main processor 310 can receive welding related data 401 (similar to Figure 3 In addition, the main processor 310 may receive telematics input 403, which may include only some of the telematics-related sensing information generated by the sensors 360. For example, the telematics input 403 may include only the sensing information corresponding to the auxiliary power transformer sensor 3601. The remaining telematics sensing data 461 (e.g., corresponding to the battery voltage sensor 3602 and the engine sensor 3603) may be provided to the traditional third-party telematics unit 3701 as analog input.

[0048] Figure 4B is a block diagram illustrating an exemplary configuration for controlling telematics integration using basic third-party telematics, with an engine control unit (ECU). Figure 4B The main controller 400 is shown. Figure 3 Sensors 360, traditional third-party telematics unit 3701 and electronic ECU 364 in.

[0049] and Figure 4A As in the configuration shown, the main processor 310 can receive welding-related data 301 and telematics input 303, which includes at least some of the telematics-related sensed data generated by the sensor 360. However, the remaining telematics sensed data 361 can be sent to the electronic ECU 364, which can generate corresponding data for input to a conventional third-party telematics unit 3701 (e.g., as a CAN bus signal).

[0050] Figure 5A is a block diagram illustrating an exemplary configuration for controlling telematics integration using basic third-party telematics and a telematics module, without an engine control unit (ECU). Figure 5A Shown are a main controller 500 , a sensor 360 , a legacy third party telematics unit 3702 , an external telematics unit 380 , a next generation WCC unit 392 , a next generation welding UI 394 , and a next generation machine UI 396 .

[0051] The main controller 500 may be similar to the main controller 300. However, the main controller 500 may have a minimal implementation, including only the main processor 310, the telematics client component 340, and the telematics host component 350. In other words, Figure 5A In the configuration shown (similarly, in Figure 5B In the configuration shown), the master controller 500 lacks the communication resources (e.g., internal communication subsystem 320 and external communication interface component 330) required to send telematics-related information to a remote entity, whether using internal components or external devices. However, the master processor 310 can receive welding-related data 301 and telematics-related sensing data 303 (from all sensors 360). Therefore, the master controller 500 is operable to act as a telematics host to provide telematics data (including welding-related information) and related messages (after processing and formatting) to a local device or equipment (e.g., a traditional third-party telematics unit 3702, an external telematics unit 380, a next-generation WCC unit 392, a next-generation welding UI 394, and a next-generation machine UI 396).

[0052] Figure 5B is a block diagram illustrating an exemplary configuration for controlling telematics integration using basic third-party telematics, with an engine control unit (ECU). Figure 5B The main controller 500 is shown. Figure 3 Sensors 360 in, legacy third-party telematics unit 3702, external telematics unit 380, next-generation WCC unit 392, next-generation welding UI 394, next-generation machine UI 396, and electronic ECU 364.

[0053] and Figure 5A As in the configuration shown, the main processor 310 can receive welding-related data 301. However, only some telematics sensing information (e.g., sensing information corresponding to the auxiliary power transformer sensor 3601) can be directly provided to the main processor (as input signal 521). However, the remaining telematics sensing data 523 (e.g., corresponding to the battery voltage sensor 3602 and the engine sensor 3603) can be sent to the electronic ECU 364, which can generate corresponding data (e.g., as a CAN bus signal) as input signal 525 input to the main controller 500 via the telematics client component 340.

[0054] Fig. 6A is a block diagram illustrating an exemplary configuration for controlling telematics integration using basic third party wireless communication components, without an engine control unit (ECU). Fig. 6A Shown are a main controller 600, a sensor 360, an external third party communication device 362, a legacy third party telematics unit 3702, an external telematics unit 380, a next generation WCC unit 392, a next generation welding UI 394, and a next generation machine UI 396.

[0055] The main controller 600 may be similar to the main controller 300. However, the main controller 600 may be a simplified implementation including only the main processor 310, the external communication interface component 330, the telematics client component 340, and the telematics host component 350. In other words, Fig. 6A In the configuration shown (similarly, in Figure 6B In the configuration shown), the master controller 600 lacks the internal / integrated communication resources (e.g., internal communication subsystem 320) required to autonomously send telematics related information to remote entities and / or autonomously receive data (e.g., location, control, software updates, etc.). Instead, communication can only be accomplished using external communication resources such as external third-party communication devices 362, and the master controller 600 can interact with the external communication resources using the external communication interface component 330. The main processor 310 can receive welding-related data 301 and telematics-related sensing data 303 (from all sensors 360). The master controller 600 is operable to act as a telematics host to provide telematics data (including welding-related information) and related messages (after processing and formatting) to local devices or equipment (e.g., traditional third-party telematics units 3702, external telematics units 380, next-generation WCC units 392, next-generation welding UI 394, and next-generation machine UI 396).

[0056] Figure 6B is a block diagram illustrating an exemplary configuration for controlling telematics integration using basic third-party wireless communication components and an engine control unit (ECU). Figure 6B Shown are a main controller 600, a sensor 360, an external third party communication device 362, a legacy third party telematics unit 3702, an external telematics unit 380, a next generation WCC unit 392, a next generation welding UI 394, a next generation machine UI 396, and an electronic ECU 364.

[0057] and Fig. 6A As in the configuration shown, the main processor 310 can receive welding-related data 301. However, only some telematics sensing information (e.g., sensing information corresponding to the auxiliary power transformer sensor 3601) can be directly provided to the main processor (as input signal 621). However, the remaining telematics sensing data 623 (e.g., corresponding to the battery voltage sensor 3602 and the engine sensor 3603) can be sent to the electronic ECU 364, which can generate corresponding data (e.g., as a CAN bus signal) as input signal 625 to the main controller 500 via the telematics client component 340.

[0058] Fig. 7Ais a block diagram illustrating an exemplary configuration for controlling telematics integration using an internal wireless communication component, without an engine control unit (ECU). Fig. 7A Shown are a main controller 700, a sensor 360, an external third party communication device 362, a legacy third party telematics unit 3702, a next generation WCC unit 392, a next generation welding UI 394, and a next generation machine UI 396.

[0059] The main controller 700 may be similar to the main controller 300. However, the main controller 700 may be a simplified implementation including only the main processor 310, the external communication interface component 330, the telematics client component 340, and the telematics host component 350. In other words, Fig. 7A In the configuration shown (similarly, in Figure 7B In the configuration shown in FIG. 1 , the master controller 700 lacks the ability to support the use of external communication resources (e.g., external third-party communication devices 362). Instead, the master controller 700 only supports the use of integrated communication resources (i.e., internal communication subsystem 320), so it can still achieve autonomous transmission of telematics related information to remote entities and / or autonomous reception of data (e.g., location, control, software updates, etc.).

[0060] The main processor 310 may receive welding related data 301 and telematics related sensed data 303 (from all sensors 360). The main controller 700 may be operable to act as a telematics host, providing telematics data (including welding related information) and related messages (after processing and formatting) to local devices or equipment (e.g., legacy third party telematics units 3702, external telematics units 380, next generation WCC units 392, next generation welding UI 394, and next generation machine UI 396).

[0061] Figure 7B is a block diagram illustrating an exemplary configuration for controlling telematics integration using an internal wireless communication component with an engine control unit (ECU). Figure 7B Shown are a main controller 700, a sensor 360, an external third party communication device 362, a legacy third party telematics unit 3702, an external telematics unit 380, a next generation WCC unit 392, a next generation welding UI 394, a next generation machine UI 396, and an electronic ECU 364.

[0062] and Fig. 7AAs in the configuration shown, the main processor 310 can receive welding-related data 301. However, only some telematics sensing information (e.g., sensing information corresponding to the auxiliary power transformer sensor 3601) can be directly provided to the main processor (as input signal 721). However, the remaining telematics sensing data 723 (e.g., corresponding to the battery voltage sensor 3602 and the engine sensor 3603) can be sent to the electronic ECU 364. The ECU 364 can generate corresponding data (e.g., as a CAN bus signal) that is input to the main controller 700 via the telematics client component 340 as input signal 725.

[0063] The method and system of the present invention can be implemented in hardware, software or a combination of hardware and software. The method and / or system of the present invention can be implemented in at least one computing system in a centralized manner, or in a distributed manner in which different elements are distributed in multiple interconnected computing systems. Any type of computing system or other device suitable for executing the method described herein is suitable. A typical combination of hardware and software may include a general computing system with a program or other code, and when the program or other code is loaded and executed, the computing system is controlled so that it executes the method described herein. Another typical implementation may include a dedicated integrated circuit or chip. Some implementations may include a non-temporary machine-readable (e.g., computer-readable) medium (e.g., a flash drive, an optical disk, a magnetic storage disk, etc.) having one or more lines of code executable by a machine stored thereon, so that the machine performs the processing as described herein.

[0064] Although the method and / or system of the present invention may be described with reference to certain implementations, it will be appreciated by those skilled in the art that various changes and equivalent substitutions may be made without departing from the scope of the method and / or system of the present invention. In addition, many modifications may be made to adapt specific circumstances or materials to the teachings of the present disclosure without departing from the scope thereof. Therefore, the method and / or system of the present invention is not intended to be limited to the specific implementation disclosed, but the method and / or system of the present invention will include all implementations falling within the scope of the appended claims.

[0065] As used herein, the term "circuit" refers to physical electronic components (i.e., hardware) and any software and / or firmware ("code") that can configure hardware, be executed by hardware, and / or otherwise be associated with hardware. As used herein, for example, when executing a first set of one or more lines of code, a specific processor and memory may include a first "circuit", and when executing a second set of one or more lines of code, a second "circuit" may be included. As used herein, "and / or" represents one or more of the items connected by "and / or" in a list. As an example, "x and / or y" represents any element in a three-element set {(x), (y), (x, y)}. In other words, "x and / or y" represents "one or both of x and y". As another example, "x, y and / or z" represents any element in a seven-element set {(x), (y), (z), (x, y), (x, z), (y, z), (x, y, z)}. In other words, "x, y and / or z" represents "one or more of x, y and z". As used herein, the term "example" means serving as a non-limiting example, case, or illustration. As used herein, the term "for example" leads to a list of one or more non-limiting examples, cases, or illustrations. As used herein, a circuit is "operable" to perform a function as long as the circuit includes the necessary hardware and code (if necessary) for performing the function, regardless of whether the performance of the function is disabled or not enabled (e.g., by user-configurable settings, factory settings, etc.).

Claims

1. A system for a welding type operation, the system comprising: a welding supply configured to provide a welding output to drive a welding torch, the welding output comprising at least one of a power source or a welding material; an engine configured to drive the system; as well as A controller, the controller being configured to: obtaining telematics data, the telematics data comprising at least data related to at least one component of the system; as well as processing the telematics data so that the telematics data can be used by a remote entity to at least one of remotely monitor or manage at least one component of the system, wherein the processing includes modifying or configuring the telematics data to match a single standard; The controller is configured to function as both a telematics client node and a telematics host node.

2. The system according to claim 1, wherein: The controller is operable to obtain at least a portion of the telematics data from one or more analog sensors.

3. The system according to claim 1, wherein: The controller is operable to obtain at least a portion of the telematics data from an engine control unit (ECU) of the engine.

4. The system according to claim 1, wherein: The telematics data includes engine-related data including information related to at least one of engine coolant, engine oil, or engine fuel.

5. The system according to claim 1, wherein: The controller processes the telematics data by formatting the telematics data according to a single standard format, regardless of the source or type of data obtained.

6. The system according to claim 1, wherein: The controller processes the telematics data by digitizing the obtained analog data.

7. The system according to claim 1, wherein: The controller processes the telematics data by processing the telematics data according to a wired or wireless interface, protocol, or standard to communicate with the remote entity.

8. The system according to claim 1, wherein: The controller is operable to communicate telematics-related messages to at least one of the engine, a component of the engine, or one or more other components according to a communication protocol.

9. The system according to claim 8, wherein: The communication protocol includes a Controller Area Network (CAN) bus protocol.

10. A system for processing telematics data associated with welding-type equipment, comprising: A controller, the controller comprising: an interface component operable to receive telematics data; a telematics host component, the telematics host being operable to perform telematics host node functions; a telematics client component, the telematics client being operable to perform telematics client node functions; and processing circuitry operable to process the telematics data so that the telematics data is usable by a remote entity; wherein: The telematics data includes at least data related to one or more components of the welding-type equipment; and The processing includes modifying or configuring the telematics data to match a single standard supported or used by the remote entity.

11. The system according to claim 10, wherein: The processing circuitry is operable to format the telematics data according to a single standard format regardless of the source or type of data obtained.

12. The system according to claim 10, wherein: The processing circuitry is operable to digitize the acquired analog data.

13. The system according to claim 10, wherein: The controller includes at least one of the following: an internal communication component operable to at least one of configure, establish, or utilize at least one of a wired or wireless connection to the remote entity; as well as An external communication interface component is operable to connect the controller to an external communication device that provides at least one of a wired or wireless connection to the remote entity.

14. The system according to claim 13, wherein: At least one of the processing circuitry, the communication component, or the external communication interface component is operable to process the telematics data for transmission to the remote entity via the wired or wireless connection.

15. The system according to claim 10, wherein: The controller includes a telematics communication component operable to process telematics-related messages according to a specific telematics communication protocol.

16. The system of claim 15, wherein: The telematics communication protocol includes a Controller Area Network (CAN) bus protocol.

17. A method comprising: processing telematics data associated with a welding-type device in a controller of the welding-type device, the processing comprising: obtaining telematics data, wherein during obtaining the telematics data, the controller functions simultaneously as a telematics client node and a telematics host node; processing the telematics data, including formatting the telematics data according to a single standard so that the telematics data can be used by a remote entity; and transmitting said telematics data to said remote entity, The telematics data at least includes data related to one or more components of the welding equipment. 18 . The method of claim 17 , wherein processing the telematics data comprises formatting the telematics data according to a single standard format regardless of the source or type of data obtained.

19. The method of claim 17, further comprising processing the telematics data in accordance with a wired or wireless interface, protocol, or standard to communicate with the remote entity.

20. The method of claim 17, wherein the telematics data comprises analog data, and wherein processing the telematics data comprises digitizing the analog data.

Images