WO2025179407A1 - Control interface system to operably couple a databus and actuatable devices - Google Patents

Abstract

A programmable control interface system is provided for interfacing between a first network bus and multiple actuatable devices that are not compatible with the first network bus. A network transceiver is configured to exchange digital messages with the first network bus. An interface system (IS) controller operably connected to the network transceiver and each of the interface components. The IS controller is operable to: individually assign interface components from the set of interface components to each of the multiple actuatable devices during a configuration of the programmable control interface system; and process command messages received by the network transceiver from the first network bus to cause the assigned interface component to provide a control signal to the target actuatable device to perform the command indicated in the received command message.

Description

CONTROL INTERFACE SYSTEM TO OPERABLY COUPLE A DATABUS AND ACTUATABLE DEVICES

RELATED APPLICATIONS

[0001] This application claims priority to and benefit of United States Provisional Patent Application No. 63/560,356 filed March 1 , 2024, the contents of which are incorporated herein by reference.

FIELD

[0002] This disclosure relates generally to the road transportation industry. More specifically, the disclosure is directed towards a control interface system to operably couple a databus and actuatable devices.

BACKGROUND

[0003] In heavy trucking, tractors and trailers have many manual, pneumatic, hydraulic, and electrical accessories. Also, many existing tractors are equipped with one or more carrier area network (CAN) or other types of vehicle data buses (as specified in SAE J 1939). More modern trailers have one or more CAN vehicle networks interconnecting devices such as wheel hub temperature sensors or tire pressure monitoring sensors. In the future, it is likely that tractors and trailers will be equipped with 1000BASE-T1 automotive ethernet networks (as specified in IEEE 802.3bp) for transmitting video from 360 bird’s eye view camera systems or rear trailer backup cameras, or even trailer interior cargo cameras.

[0004] Currently, the traditional/legacy accessories, such as lights, landing legs, sliders, doors, etc. are either manual, or switched directly by electrical or pneumatic switches in the vehicle cab or via relayed circuits, for example, a switch in the vehicle cab completes a relay-coil circuit which, in turn, switches a high powered circuit to control an accessory, the starter motor circuit is such a circuit and is switched by an electrical switch integrated into the ignition key mechanism. Accessory manufacturers currently have little to no impetus or, in some cases, competency, to move away from traditional device actuation strategies. [0005] In contrast, some manufacturers are innovating and making what were once manually operated systems to be powered in some fashion. However, these manufacturers are proceeding without consideration for how these systems may be actuated remotely or by autonomous systems because, currently, autonomous systems are not prevalent and trailers and tractors are generally not connected for data transmission.

[0006] Accordingly, a solution is desirable that enables vehicle network and data connection to span between tractor and trailer well as electrical power and pneumatics to power and control on-trailer devices from the cab, as well as to receive data from distributed devices from the trailer.

SUMMARY

[0007] According to example aspects, a programmable control interface system is provided for interfacing between a first network bus and multiple actuatable devices that are not compatible with the first network bus, the system comprising: a network transceiver configured to exchange digital messages with the first network bus, the digital messages including command messages received from the first network bus that each indicate a command for a respective target actuatable device of the multiple actuatable devices; a set of interface components, the interface components each being respectfully configured for connection to a respective one of the multiple actuatable devices; an interface system (IS) controller operably connected to the network transceiver and each of the interface components. The IS controller is operable to: individually assign interface components from the set of interface components to each of the multiple actuatable devices during a configuration of the programmable control interface system; and process command messages received by the network transceiver from the first network bus to: (i) identify, for each received command message, the interface component assigned to the target actuatable device that is the target of the received command message, and (ii) cause the assigned interface component to provide a control signal to the target actuatable device to perform the command indicated in the received command message.

[0008] The programmable control interface system can be included as part of a trailer includes the first network bus, and the multiple actuatable devices, wherein the first network bus is operably coupled to a vehicle network bus of a vehicle that is configured to tow the trailer, the vehicle comprising a vehicle controller operably coupled to the vehicle network bus; and the programable control interface system is configured to: receive the command messages from the vehicle controller via the first network bus and the vehicle network bus.

BRIEF DESCRIPTION OF DRAWINGS

[0009] In the figures, which illustrate example embodiments,

[0010] Figure 1 is a schematic side view showing a vehicle (e.g., a tractor) and a vehicle connector (e.g., a trailer) that incorporates a control interface system according to an example embodiment.

[0011] Figure 2 is a schematic block diagram showing the control interface system of Figure 1 in greater detail, according to an example embodiment.

[0012] Figure 3 shows an example of an enclosure that contains the control interface system of Figure 2.

DETAILED DESCRIPTION

[0013] Figure 1 depicts a towing vehicle 13 that is coupled to a vehicle connector, namely a trailer 12. The towing vehicle 13 is configured to tow the trailer 12. In some embodiments, for example, the towing vehicle 13 is a tractor, a yard shifter, or a converter dolly. In some embodiments, for example, the towing vehicle 13 is an autonomous vehicle, such as an autonomous tractor, yard shifter, or converter dolly. In some embodiments, for example, the towing vehicle 13 includes a fifth wheel assembly 16 configured for slidably receiving, and coupling with a corresponding kingpin of the trailer 12.

[0014] In the illustrated example, towing vehicle 13 includes an on-board vehicle controller 20 that is operably connected to a set or electrical or electromechanical components of the vehicle 13, including for example a sensor configuration 22, and a user interface 24 (e.g., a human machine interface (HMI)). The vehicle controller 20 can, for example, include a processor or a central processing unit (CPU), a memory such as a ROM, RAM, persistent memory, or flash memory for storing data, and input or output peripherals. In some embodiments, for example, the vehicle controller 20 acts as a central controller for controlling various components and devices of vehicle 13 and the trailer 12. In an example implementation, the towing vehicle 13 is equipped with a vehicle on-board digital communications network 25 (also referred to herein as vehicle databus 25) that is operably coupled to on-board vehicle controller 20 and used for communicating digital messages between the vehicle controller 20 and other communications- enabled components and devices of vehicle 13 and the trailer 12. By way of example, the vehicle databus 25 can be implemented by communications network that is complaint with a communications protocol such as Controller Area Network (CAN), Automotive Ethernet, or Gigabit Multimedia Serial Link (GMSL).

[0015] As shown in Figure 1 , trailer 12 is similarly equipped with a trailer on-board digital communications network 1802 (also referred to herein as trailer databus 1802) is used for communicating digital messages between communications-enabled components and devices of of the trailer 12 and vehicle 13. In example implementations, the trailer databus 1802 can be implemented by communications network uses the same communications protocol as vehicle databus 25, for example, Controller Area Network (CAN), Automotive Ethernet, or Gigabit Multimedia Serial Link (GMSL).

[0016] In the illustrated example, the vehicle 13 is equipped with a first adapter counterpart 302 that functions as an interface to vehicle databus 25, and the trailer 12 is equipped with a second adapter counterpart 350 that functions as an interface to trailer databus 1802. When the towing vehicle 13 is coupled to the trailer 12, the first adapter counterpart 302 and second adapter counterpart 350 are configured to couple and operatively connect the vehicle databus 25 and the trailer databus 1802 such that digital messages can be exchanged, via a data path through the first adapter counterpart 302 and second adapter counterpart 350, between the vehicle databus 25 and the trailer databus 1802.

[0017] In addition to providing a data communications network connection between vehicle databus 25 and the trailer databus 1802, coupling of the respective adapter counterparts 302, 350 can, in some examples, also establish other system connections between the towing vehicle 13 and the trailer 12, including for example, fluid system connections and electrical (e.g., power) system connections.

[0018] In example embodiments, the interconnection of the vehicle databus 25 and the trailer databus 1802 provided by coupling of the adapter counterparts 302, 350 enables digital messages to be transmitted from the vehicle controller 20 for communications-enabled devices of the trailer 12. In some examples, some of these devices can be configured with a network complaint interface that permits the device to be connected directly to the vehicle databus 25 to receive digital messages originating from the vehicle controller 20. However, in many use cases, at least some devices of the trailer 12 may not have a network complaint interface, and thus are not able to be directly connected directly to the trailer databus 1802 to receive digital messages that are sent using the trailer databus 1802, including messages from the vehicle controller 20. This situation can, by way of non-limiting example, occur in a retrofit situation where a trailer 12 includes legacy devices that are not forward compatible with a trailer databus 1802 that has been installed on the trailer 12.

[0019] By way of example, in Figure 1 , the trailer 12 comprises an actuatable device 1804 that is not trailer databus 1802 compatible such that there is an absence of operable coupling (e.g. data communication) of the databus 1802 and the actuatable device 1804. This can cause a lack of utility of the databus 1802, and prevent some of the benefits that could otherwise be realized by equipping a trailer 12 with a databus 1802, including for example, the benefit of having the actuatable device 1804 controlled by messages originating from the vehicle controller 20. Illustrative examples of actuatable devices can, by way of illustrative example, include (i) a lock actuator for a locking device that can be used to lock a sliding bogie 1704 of the trailer 12; and (ii) an actuator device for raising and lowering landing legs 1764 or the trailer 12.

[0020] In this regard, the present disclosure describes a control interface system 1806 that is configured to enable devices, such as actuatable device 1804, that are not compatible with trailer databus 1802 to be operably coupled to the databus 1802, thereby enabling such devices to be controllable by vehicle controller 20. In example embodiments, control interface system 1806 is configured to function as a configurable and programmable network interface device for controlling various accessories and subsystems (e.g., devices) of a trailer via commands communicated over a CAN bus or similar vehicle network.

[0021] In some embodiments, for example, the control interface system 1806 can be provided as part of a trailer upgrade kit for modifying an existing trailer 12 for trailer databus compatibility. In the illustrated example, as illustrated in Figures 1 and 2, the control interface system 1806 comprises an interface system (IS) controller 1808, configured to be operably coupled various accessories and subsystems such as the actuatable device 1804, a network transceiver 1810, configured to operably couple the IS controller 1808 to the databus 1802, and one or more device interface components 1820 that, configured to operably couple the IS controller 1808 to respective devices, including actuatable device 1804.

[0022] In some embodiments, for example, similar to the controller 20 of the vehicle 13, as shown in Figure 2, the IS controller 1808 includes a processor 202 such as central processing unit (CPU) or microcontroller unit (MCU), and a memory 204 such as a ROM, RAM, persistent memory, or flash memory for storing data and executable instructions that configure the operation of processor 202. In some embodiments, for example, the IS controller 1808 includes an interface 223 for operably coupling with the network transceiver 1810.

[0023] In an example embodiment, as shown in Figure 2, the electronic components of control interface system 1806 are all mounted to a common printed circuit board 210, which in turn is mounted, as shown in Figure 3, within a rigid housing or enclosure 300 that includes a set of ports that support a set of electrical connectors 302 that can be accessed externally of the enclosure 300 an enable connecting wires and cables to be connected to the respective device interface components 1820 of the control interface system 1806. The enclosure 300 can be provided with mounting hardware for mounting the enclosure to trailer 12 at a location that is within a body of the trailer 12 or on the trailer 12.

[0024] The control interface system 1806, shown in Figure 2, is connected by a power management module 226 to a power source (e.g., a trailer 12 or vehicle 13 power system, either to battery power, ignition switched power, or both). The device interface components 1820 can include a variety of types input and/or output interface components, including for example: a plurality of motor drivers 228, a plurality of solenoid drivers 230, a plurality of relays 232, and sets of other types of analog I/O interface components 234 and digital I/O interface components 236. Digital I/O interface components 236 can, for example, include a plurality of protocol specific (e.g., RS 232) and generic digital I/O interfaces. Analog I/O interface components 234 can for example include a plurality of insulated-gate bipolar transistor (IGBT) drivers, as well as analog input components, among other things.

[0025] The set of electrical connectors 302 shown in Figure 3 can, with reference to Figure 2, include, among other things, a CAN connector 220; a power connector 240; and the following device interface component connectors: motor driver output connectors 210; solenoid driver output connectors 212; relay output connectors 214; and analog and digital I/O connectors 222. [0026] In the illustrated example, the IS controller 1808 can be pre-configured through a set-up programming to selectively communicate individually (e.g., send and/or receive signals) with each of the device interface components 1820, such that the control interface system 1806 allows programmatic control of existing automatic or powered devices of trailer 12 and the databus 1802 to allow for remote and or autonomous actuation of those devices ( e.g., remote control from vehicle controller 20 and interface components such as vehicle user interface 24 that are coupled to the vehicle controller 20. In this regard, the device interface components 1802 can be assigned through a configuration process to specific trailer and vehicle devices. For example, a specific solenoid driver 230 can be assigned to a specific device such as actuatable device 1804. In some examples, the IS controller 1808 is preconfigured through programing and configuration data (e.g. a set of one or more mapping tables) stored in a local on-chip memory of IS controller or in memory 204. The configuration data can map each of the device interface components to a respective output pin (or set of pins) of the processor 202. Furthermore, the configuration data can map each of the device interface components to a respective assigned device, together with a trailer network identifier for that device. The configuration data can also map each device to set of device-specific processing instructions that specify what actions the processor 202 must take when processing incoming or outgoing data messages or signals that are routed to or from the trailer devices. These actions can include for example converting a digital command into an analog signal, changing data from a first format to a second format, as well as other signal or data transformations or conversions.

[0027] By way of example, command messages received by the processor 202 for a target actuatable device 1804 via the trailer databus 1802 can include a pre-assigned trailer network identifier that uniquely identifies the device and command data for the device. Based on the configuration data, processor 202 can determine, based on the pre-assigned trailer network identifier, which device interface component 1820 is associated with the target actuatable device and format and/or content of the signal that the IS controller 1808 needs to provide for that device interface component 1820 to provide the device interface component 1820 output signal for the target actuatable device 1804 to carry out the function instructed in the command data.

[0028] In addition to routing data commands received via the trailer databus 1802, in example implementations the device interface component 1820 can also be configured through programming to route input commands received from an input device that is connected to an assigned device interface component 1820 to target device that is connected to a further device interface component 1820 that is connected to a target actuatable device 1804. In this regard, the configuration data can also include mapping data that maps assigned device interface components 1820 as input sources for one or more other assigned device interface components 1820.

[0029] In some examples, the configuration can also include data that maps assigned device interface components 1820 that are input as input sources to CAN network addresses such that information received via a specific device interface component 1820 can mapped to a destination network address and converted by processor 202 to a databus 1802 complaint format and sent as a data message using databus 1802.

[0030] In some examples, the Control Interface System 1806 can be configured by configuration data to selectively place actuatable devices under control from commands issued through the vehicle/trailer databus 25,1802, or under control of commands issued through a human controlled interface. By way of example, actuatable device 1804 can be connected to an output terminal of a relay interface component 232 that has a first input terminal and a control terminal connected to IS Controller 1808 and a second input terminal connected to a legacy human interface device (e.g., an on-off switch). The IS Controller 1808 can be configured to selectively control the relay so that: (i) in a first mode, the legacy human interface device is isolated from the actuatable device 1804 and is coupled to an assigned signal output of the IS Controller 1808, while (ii) in a second mode, the legacy human interface device is coupled to the actuatable device 1804 in place of the assigned signal output of the IS Controller 1808. This configuration can enable hybrid human and machine control: for example, in the case of subsystems and accessories (e.g., actuatable devices 1804) controlled directly or indirectly by driver input, the control interface system 1806 can enable commands from input devices that are controlled by human operator commands to pass through as expected, but in the presence of an autonomous controller, when control is ceded to the autonomous controller, the autonomous controller may command the same actuatable devices 1804 by sending commands over the vehicle/trailer network databus 25, 1802.

[0031] Thus, device interface component 1820 provides ubiquitous device that can be programmed route and transform data signals: (i) from network databus 1802 to legacy devices (e.g., actuatable devices 1804); (ii) from legacy devices (e.g., sensors and command input devices) to network databus 1802 compliant devices; and (iii) between legacy devices (e.g., from legacy command input device to a legacy actuatable device). In some examples, the same actuatable device 1804 can be controlled from commands received via data messages sent over network databus 1802 as well as commands received from legacy devices.

[0032] Furthermore, multiple device interface components 1820 can be located at different locations and tied to different access points to a network databus 25 and 1802 to provide an intermediate network path between network non-compliant input devices and actuatable devices.

[0033] Among other things, the control system interface 1806 can programmed to receive control inputs from human operated input devices that are not compatible with databus 1802 (e.g., a legacy on/off switch control interface located in vehicle 12 or on the trailer 12) that is electrically connected to a respective devices interface component 1820, and then cause those commands to be passed through to a target actuatable device 1804.

[0034] In example embodiments, the control system interface 1806 can: 1) allow remote or autonomous operation, actuation, engaging, or disengaging, by human operator interfacing through a driver-machine interface (DM I) or autonomous command by autonomous system of any existing or future electrical, pneumatic, or hydraulic accessory, and 2) given current vehicle state as communicated by other on-board sensors, determine safe operation of the connected accessory.

[0035] In some embodiments, for example, when the control interface system 1806 is installed on the trailer 12, the IS controller 1808 is operably coupled to the actuatable device 1804 and the network transceiver 1810 is operably coupled to the databus 1802, such that the databus 1802 and the actuatable device 1804 are operably coupled via the control interface system 1806. In some embodiments, for example, the operable coupling of the IS controller 1808 and the actuatable device 1804 is with effect that the actuatable device 1804 is controllable by the IS controller 1808, for example, in response to control commands from the IS controller 1808. In some embodiments, for example, the operable coupling of the IS controller 1808 and the actuatable device 1804 is effectuated via a wired connection interface. In some embodiments, for example, the operable coupling of the IS controller 1808 and the actuatable device 1804 is effectuated wirelessly (e.g. via a wireless network using a wireless communication protocol).

[0036] In some embodiments, for example, in addition to the control system interface 1806, the trailer upgrade kit can also include the second adapter counterpart 350 together with the databus 1802, such the second adapter counterpart 350 together with the databus 1802 and the control system interface 1806 can be operabily coupled together and installed on trailer 12 together. In some embodiments, for example, the trailer upgrade kit includes the second adapter counterpart 350 without the databus 1802 ( which may for example have been previously installed in tailer 12), such that the second adapter counterpart 350 and the control system interface 1806 and the control system interface 1806 can be operabily coupled installed on trailer 12 together and operably coupled with an existing databus 1802.

[0037] In some embodiments, for example, the actuatable device 1804 comprises a sensor configuration 1812, configured to detect a parameter of the actuatable device 1804 (e.g. speed of a component of the device, temperature of a component of the device, pressure of a component of the device, position of a component of the device, state of a component of the device, force applied to the device, weight on the device, configuration of a component of the device, etc.). In some embodiments, for example, the sensor configuration 1812 comprises a sensor, for example, a position sensor, a displacement sensor, a mechanical sensor, an optical sensor, speed sensor, a load sensor, a temperature sensor, and the like, for detecting the parameter of the actuatable device 1804. In some embodiments, for example, the IS controller 1808 is configured to determine an operability of the actuatable device 1804, based at least in part on the detected parameter of the actuatable device 1804. In some embodiments, for example, the determination of the operability of the actuatable device 1804 includes a determination that it is safe to operate the actuatable device 1804. In some embodiments, for example, the determination of the safety for operating the actuatable device 1804 meets the functional safety standard as defined in ISO 26262.

[0038] In some embodiments, for example, the vehicle 13 and the modified trailer 12 are cooperatively configured such that, while the first adapter counterpart 302 and the second adapter counterpart 350 are connected, the control interface system 1806 and the actuatable device 1804 becomes operably coupled to controller of the vehicle 13, for example, for communicating the parameter of the actuatable device 1804 and the operability of the actuatable device 1804 to the controller. In some embodiments, for example, the parameter of the actuatable device 1804 and the operability of the actuatable device 1804 are communicated to the vehicle controller via the databus of the trailer 12, the counterparts 302, 350, and the databus of the vehicle 13.

[0039] In some embodiments, for example, the vehicle 13 and the modified trailer 12 are cooperatively configured such that, while the first adapter counterpart 302 and the second adapter counterpart 350 are connected, a graphical representation of the parameter of the actuatable device 1804 and the operability of the actuatable device 1804 are rendered on the user interface 24 of the vehicle 13. In some embodiments, for example, in response to communication of the parameter of the actuatable device 1804 and the operability of the actuatable device 1804 to the vehicle controller 20, the vehicle controller 20 sends a control command to the user interface to render the graphical representation of the parameter of the actuatable device 1804 and the operability of the actuatable device 1804 on the user interface. In some embodiments, for example, the vehicle 13 and the trailer 12 are co-operatively configured such that, while the first adapter counterpart 302 and the second adapter counterpart 350 are connected, a graphical representation of instructions for controlling the actuatable device 1804 is rendered on the user interface.

[0040] In some embodiments, for example, the vehicle 13 and the trailer 12 are co-operatively configured such that, while the first adapter counterpart 302 and the second adapter counterpart 350 are connected, the controlling of the actuation of the actuatable device 1804 is based at least in part on the detected parameter of the actuatable device 1804. In some embodiments, for example, based on the detection by the sensor configuration 1812 that there is an opposition to the actuation of the actuatable device 1804, for example, by a foreign object such as dirt or a rock, the controlling of the actuation of the actuatable device 1804 is such that the actuatable device 1804 is not actuated, as actuation of the actuatable device 1804 while such opposition to the actuation of the actuatable device 1804 is present may damage the actuatable device 1804. In some embodiments, for example, based on the detection by the sensor configuration 1812 that there is an absence of opposition to the actuation of the actuatable device 1804, for example, by a foreign object such as dirt or a rock, the controlling of the actuation of the actuatable device 1804 is such that the actuatable device 1804 is actuated, it may be safe to actuate the actuatable device 1804 while such opposition to the actuation of the actuatable device 1804 is absent.

[0041] In some embodiments, for example, the trailer 12 comprises a sensor configuration 1814, configured to detect a parameter of the trailer 12 (e.g. speed of a component of the trailer 12, temperature of a component of the trailer 12, pressure of a component of the trailer 12, position of a component of the trailer 12, state of a component of the trailer 12, force applied to the trailer 12, weight on a component of the trailer 12, configuration of a component of the trailer 12, etc.). In some embodiments, for example, the sensor configuration 1814 comprises a sensor, for example, a position sensor, a displacement sensor, a mechanical sensor, an optical sensor, speed sensor, a load sensor, a temperature sensor, and the like, for detecting the parameter of the trailer 12. In some embodiments, for example, the IS controller 1808 is configured to determine an operability of the actuatable device 1804, based at least in part on the detected parameter of the trailer 12. In some embodiments, for example, the determination of the operability of the actuatable device 1804 includes a determination that it is safe to operate the actuatable device 1804. In some embodiments, for example, the determination of the safety for operating the actuatable device 1804 meets the functional safety standard as defined in ISO 26262.

[0042] In some embodiments, for example, while the trailer 12 is established, the IS controller 1808 and the sensor configuration 1814 are operably coupled, for example, via the databus 1802, such that the detected parameter of the trailer 12 is communicated to the IS controller 1808, and the operability of the actuatable device 1804 is determined by the IS controller 1808.

[0043] In some embodiments, for example, the vehicle 13 and the trailer 12 are co-operatively configured such that, while the first adapter counterpart 302 and the second adapter counterpart 350 are connected, the control interface system 1806 and the actuatable device 1804 becomes operably coupled to controller of the vehicle 13, for example, for communicating the parameter of the trailer 12 and the operability of the actuatable device 1804 to the controller. In some embodiments, for example, the parameter of the trailer 12 and the operability of the actuatable device 1804 are communicated to the vehicle controller via the databus of the trailer 12, the adapter 300, and the databus of the vehicle 13.

[0044] In some embodiments, for example, the vehicle 13 and the trailer 12 are co-operatively configured such that, while the first adapter counterpart 302 and the second adapter counterpart 350 are connected, a graphical representation of the parameter of the trailer 12 and the operability of the actuatable device 1804 are rendered on the user interface, for example, of the vehicle 13. In some embodiments, for example, in response to communication of the parameter of the trailer 12 and the operability of the actuatable device 1804 to the vehicle controller, the vehicle controller sends a control command to the user interface to render the graphical representation of the parameter of the trailer 12 and the operability of the actuatable device 1804 on the user interface. In some embodiments, for example, the vehicle 13 and the trailer 12 are co-operatively configured such that, while the first adapter counterpart 302 and the second adapter counterpart 350 are connected, a graphical representation of instructions for controlling the actuatable device 1804 is rendered on the user interface. [0045] In some embodiments, for example, the vehicle 13 and the trailer 12 are co-operatively configured such that, while the first adapter counterpart 302 and the second adapter counterpart 350 are connected, the controlling of the actuation of the actuatable device 1804 is based at least in part on the detected parameter of the trailer 12. In some embodiments, for example, based on the detection by the sensor configuration 1814 that a wheel of the trailer 12 is moving (e.g. indicating that the trailer 12 is being displaced, for example by the vehicle 13) the controlling of the actuation of the actuatable device 1804 is such that the actuatable device 1804 is not actuated, as actuation of the actuatable device 1804 while the trailer 12 is moving may damage the actuatable device 1804. In some embodiments, for example, based on the detection by the sensor configuration 1814 that a wheel of the trailer 12 is not moving (e.g. indicating that the trailer 12 is not being displaced), the controlling of the actuation of the actuatable device 1804 is such that the actuatable device 1804 is actuated, it may be safe to actuate the actuatable device 1804 while the trailer 12 is not moving.

[0046] In some embodiments, for example, the vehicle 13 comprises a sensor configuration, configured to detect a parameter of the vehicle (e.g. speed of a component of the vehicle 13, temperature of a component of the vehicle 13, pressure of a component of the vehicle 13, position of a component of the vehicle 13, state of a component of the vehicle 13, force applied to the vehicle 13, weight on a component of the vehicle 13, configuration of a component of the vehicle 13, etc.). In some embodiments, for example, the sensor configuration comprises a sensor, for example, a position sensor, a displacement sensor, a mechanical sensor, an optical sensor, speed sensor, a load sensor, a temperature sensor, and the like, for detecting the parameter of the vehicle 13. In some embodiments, for example, the sensor configuration of the vehicle 13 is operably coupled to controller of the vehicle 13 for communicating the parameter to the vehicle controller. In some embodiments, for example, the parameter is communicated to the vehicle controller via the databus of the vehicle 13. In some embodiments, for example, the sensor configuration of the vehicle 13 is operably coupled to the first adapter counterpart 302, for example, via the controller of the vehicle 13 or the databus of the vehicle 13.

[0047] In some embodiments, for example, the IS controller 1808 is configured to determine an operability of the actuatable device 1804, based at least further in part on the detected parameter of the vehicle 13. In some embodiments, for example, the determination of the operability of the actuatable device 1804 includes a determination that it is safe to operate the actuatable device 1804. In some embodiments, for example, the determination of the safety for operating the actuatable device 1804 meets the functional safety standard as defined in ISO 26262.

[0048] In some embodiments, for example, the vehicle 13 and the trailer 12 are co-operatively configured such that, while the first adapter counterpart 302 and the second adapter counterpart 350 are connected, the controller and the sensor configuration of the vehicle become operably coupled to the IS controller 1808, for example, for communicating the parameter of the vehicle 13 to the IS controller 1808, such that the determination of the operability of the actuatable device 1804 is based at least further in part on the parameter of the vehicle 13. In some embodiments, for example, the parameter of the vehicle is communicated to the IS controller 1808 via the databus of the trailer 12, the adapter 300, and the databus of the vehicle 13.

[0049] In some embodiments, for example, a graphical representation of the trailer parameter is rendered on the user interface of the vehicle 13. In some embodiments, for example, the vehicle controller sends a control command to the user interface to render the graphical representation of the parameter of the vehicle 13 on the user interface.

[0050] In some embodiments, for example, the vehicle 13 and the trailer 12 are co-operatively configured such that, while the first adapter counterpart 302 and the second adapter counterpart 350 are connected, the controlling of the actuation of the actuatable device 1804 is based at least in part on the detected parameter of the vehicle 13. In some embodiments, for example, based on the detection by the sensor configuration that a wheel of the vehicle 13 is moving (e.g. indicating that the trailer 12 is being displaced, for example by the vehicle 13) the controlling of the actuation of the actuatable device 1804 is such that the actuatable device 1804 is not actuated, as actuation of the actuatable device 1804 while the trailer 12 is moving may damage the actuatable device 1804. In some embodiments, for example, based on the detection by the sensor configuration 1814 that a wheel of the vehicle 13 is not moving (e.g. indicating that the trailer 12 is not being displaced), the controlling of the actuation of the actuatable device 1804 is such that the actuatable device 1804 is actuated, it may be safe to actuate the actuatable device 1804 while the trailer 12 is not moving.

[0051] In some embodiments, for example, the controlling of the actuation of the actuatable device 1804 is based at least in part on the operability of the actuatable device 1804, which is based at least in part on the detected parameter of the actuatable device 1804, the detected parameter of the trailer 12, and/or the detected parameter of the vehicle 13. [0052] In some embodiments, for example, the controlling of the actuatable device 1804 is effectuated automatically (e.g. the vehicle 13 is an autonomous vehicle). In some embodiments, for example, while communication between the vehicle controller and the IS controller 1808 is established, for example, while the first adapter counterpart 302 and the second adapter counterpart 350 is connected, the vehicle controller sends a control command to the IS controller 1808. In some embodiments, for example, in response to the control command from the vehicle controller, the IS controller 1808 sends a control command to the actuatable device 1804, based on the determination of the operability of the actuatable device 1804, to control the actuatable device 1804. In some embodiments, for example, in response to the control command from the vehicle controller, and a determination by the IS controller 1808 that the actuatable device 1804 is safe to operate, the IS controller 1808 sends a control command to the actuatable device 1804 to control the actuatable device 1804 (e.g. actuate the device to operate the device). In some embodiments, for example, in response to the control command from the vehicle controller, and a determination by the IS controller 1808 that the actuatable device 1804 is not safe to operate, the IS controller 1808 sends a control command to the actuatable device 1804 to control the actuatable device 1804 (e.g. actuate the device to dispose the device in a non-operating configuration).

[0053] In some embodiments, for example, the controlling of the actuatable device 1804 is effectuated in response to an input by a user, such as an operator, via the user interface of the vehicle 13. In this respect, in some embodiments, for example, the vehicle 13 and the modified trailer 12 are co-operatively configured such that, while the first adapter counterpart 302 and the second adapter counterpart 350 are connected, the controlling of the actuatable device 1804 is based at least in part on the input from the user. In some embodiments, for example, while communication between the vehicle controller and the IS controller 1808 is established, for example, while the first adapter counterpart 302 and the second adapter counterpart 350 is connected, the vehicle controller sends a control command to the user interface of the vehicle 13 to render the graphical representation of the operability of the actuatable device 1804, the parameter of the actuatable device 1804, and/or the parameter of the trailer 12. At this point, the user sends a control command to the vehicle controller via the user interface, and in response, the vehicle controller sends a control command to the IS controller 1808. In some embodiments, for example, in response to the control command from the vehicle controller, the IS controller 1808 sends a control command to the actuatable device 1804, based on the determination of the operability of the actuatable device 1804, to control the actuatable device 1804. In some embodiments, for example, in response to the control command from the vehicle controller, and a determination by the IS controller 1808 that the actuatable device 1804 is safe to operate, the IS controller 1808 sends a control command to the actuatable device 1804 to control the actuatable device 1804 (e.g. actuate the device to operate the device). In some embodiments, for example, in response to the control command from the vehicle controller, and a determination by the IS controller 1808 that the actuatable device 1804 is not safe to operate, the IS controller 1808 sends a control command to the actuatable device 1804 to control the actuatable device 1804 (e.g. actuate the device to dispose the device in a non-operating configuration).

[0054] In some embodiments, for example, the actuatable device 1804 comprises an actuator 1816 for actuating the actuatable device 1804. In some embodiments, for example, the actuator 1816 includes a solenoid. In some embodiments, for example, the actuator 1816 includes a valve. In some embodiments, for example, the actuator 1816 includes a cylinder, for example, a pneumatic or hydraulic cylinder.

[0055] In some embodiments, for example, the IS controller 1808 is operably coupled to the actuator 1816 of the actuatable device 1804 and the network transceiver 1810 is operably coupled to the databus 1802, such that the databus 1802 and the actuator 1816 of the actuatable device 1804 are operably coupled via the control interface system 1806.

[0056] in some embodiments, for example, the controller 20 of the vehicle 13 is operably coupled to the actuator 1816 of the actuatable device 1804, for example, via the databus of the vehicle 13, the adapter 300, the databus of the trailer 12, and the control interface system 1806, for controlling the actuation of the actuatable device 1804.

[0057] In some embodiments, for example, the actuator 1816 is operably coupled to an energy source or energy storage device (e.g. fluid or electrical energy source or fluid or electrical energy storage device) of the trailer 12 for actuating the actuator 1816. In some embodiments, for example, while the first adapter counterpart 302 and the second adapter counterpart 350 are connected, the actuator 1816 is operably coupled to an energy source or energy storage device of the vehicle 13 for actuating the actuator 1816.

[0058] In some embodiments, for example, the actuatable device 1804 comprises a device controller 1818 for controlling actuation of the actuatable device 1804. In some embodiments, for example, the device controller 1818 or the controller of the vehicle 13, the device controller 1818 includes a processor or a central processing unit (CPU), a memory such as a ROM, RAM, persistent memory, or flash memory for storing data, and input or output peripherals, in some embodiments, for example, the device controller 1818 is operably coupled to the sensor configuration 1812 and the actuator 1816 for controlling actuation of the actuatable device 1804.

[0059] In some embodiments, for example, the IS controller 1808 is operably coupled to the device controller 1818 of the actuatable device 1804 and the network transceiver 1810 is operably coupled to the databus 1802, such that the databus 1802 and the device controller 1818 of the actuatable device 1804 are operably coupled via the control interface system 1806.

[0060] in some embodiments, for example, the vehicle 13 and the modified trailer 12 are cooperatively configured such that, while the first adapter counterpart 302 and the second adapter counterpart 350 are connected, the controller of the vehicle 13 becomes operably coupled to the device controller 1818 of the actuatable device 1804, for example, via the databus of the vehicle 13, the adapter 300, the databus of the trailer 12, and the control interface system 1806, for controlling the actuation of the actuatable device 1804.

[0061] In some embodiments, for example, the trailer 12 includes more than one actuatable device 1804, and while the trailer adaptor components are installed on the trailer with effect that the trailer 12 is established, the IS controller 1808 is operably coupled to each one of the actuatable devices 1804, such that the databus 1802 and each one of the actuatable devices 1804 are operably coupled via the control interface system 1806. In some embodiments, for example, the trailer 12 includes more than one actuatable device 1804, and while the trailer adaptor components are installed on the trailer with effect that the trailer 12 is established, the IS controller 1808 is operably coupled to a plurality of the actuatable devices 1804, such that the databus 1802 and the plurality of the actuatable devices 1804 are operably coupled via the control interface system 1806.

[0062] In some embodiments, for example, by operably coupling the actuatable device 1804 to the databus 1802, for example, via the control interface system 1806, the actuatable device 1804 is controllable remotely, for example, via the controller of the vehicle 13, while the first adapter counterpart 302 and the second adapter counterpart 350 are connected. This allows for a user or operator to control the actuation or operation of the actuatable device 1804 without leaving the vehicle 13. In some embodiments, for example, this improves safety for the user, as: (i) the user avoids having to step out of the vehicle 13 and manually operating the actuatable device 1804 (e.g. via a hand crank, lever, or button), which reduces risk of physical injury, such as slips and falls and injuries to joints and muscles, and (ii) the user does not have to step out onto a road and actuate or operate the actuatable device 1804 while standing nearby oncoming vehicles, which reduces risk of injury from a collision with one of the oncoming vehicles.

[0063] In some embodiments, for example, since the controlling of the actuation of the actuatable device 1804 is effectuated via controllers, for example, the vehicle controller and the IS controller 1808, the controlling of the actuation of the actuatable device 1804 is more accurate and precise.

[0064] In the preceding description, for purposes of explanation, numerous details are set forth in order to provide a thorough understanding of the embodiments; however the specific details are not necessarily required. In other instances, well-known electrical structures and circuits are shown in block diagram form in order not to obscure the understanding. For example, specific details are not provided as to whether the embodiments described herein are implemented as a software routine, hardware circuit, firmware, or a combination thereof.

[0065] The steps and/or operations in the flowcharts and drawings described herein are for purposes of example only. There may be many variations to these steps and/or operations without departing from the teachings of the present disclosure. For instance, the steps may be performed in a differing order, or steps may be added, deleted, or modified.

[0066] The coding of software for carrying out the above-described methods described for execution by a controller (or processor) of the apparatus 100 is within the scope of a person of ordinary skill in the art having regard to the present disclosure. Machine readable code executable by one or more processors of one or more respective devices to perform the abovedescribed method may be stored in a machine readable medium such as the memory of the data manager. The terms “software” and “firmware” are interchangeable within the present disclosure and comprise any computer program stored in memory for execution by a processor, comprising RAM memory, ROM memory, erasable programmable ROM (EPROM) memory, electrically EPROM (EEPROM) memory, and non-volatile RAM (NVRAM) memory. The above memory types are example only, and are thus not limiting as to the types of memory usable for storage of a computer program.

[0067] All values and sub-ranges within disclosed ranges are also disclosed. Also, although the systems, devices and processes disclosed and shown herein may comprise a specific plurality of elements/components, the systems, devices and assemblies may be modified to comprise additional or fewer of such elements/components. For example, although any of the elements/components disclosed may be referenced as being singular, the embodiments disclosed herein may be modified to comprise a plurality of such elements/components. The subject matter described herein intends to cover and embrace all suitable changes in technology.

[0068] Although the present disclosure is described, at least in part, in terms of methods, a person of ordinary skill in the art will understand that the present disclosure is also directed to the various components for performing at least some of the aspects and features of the described methods, be it by way of hardware (DSPs, ASIC, or FPGAs), software or a combination thereof. Accordingly, the technical solution of the present disclosure may be embodied in a non-volatile or non-transitory machine readable medium (e.g., optical disk, flash memory, etc.) having stored thereon executable instructions tangibly stored thereon that enable a processing device (e.g., a data manager) to execute examples of the methods disclosed herein.

[0069] The term “processor” may comprise any programmable system comprising systems using micro- or nano-processors/controllers, reduced instruction set circuits (RISC), application specific integrated circuits (ASICs), logic circuits, and any other circuit or processor capable of executing the functions described herein. The term "database" may refer to either a body of data, a relational database management system (RDBMS), or to both. As used herein, a database may comprise any collection of data comprising hierarchical databases, relational databases, flat file databases, object-relational databases, object oriented databases, and any other structured collection of records or data that is stored in a computer system. The above examples are example only, and thus are not intended to limit in any way the definition and/or meaning of the terms "processor" or “database”.

[0070] The present disclosure may be embodied in other specific forms without departing from the subject matter of the claims. The described example embodiments are to be considered in all respects as being only illustrative and not restrictive. The present disclosure intends to cover and embrace all suitable changes in technology. The scope of the present disclosure is, therefore, described by the appended claims rather than by the foregoing description. The scope of the claims should not be limited by the embodiments set forth in the examples, but should be given the broadest interpretation consistent with the description as a whole.

Claims

WHAT IS CLAIMED IS:

1. A programmable control interface system for interfacing between a first network bus and multiple actuatable devices that are not compatible with the first network bus, the system comprising: a network transceiver configured to exchange digital messages with the first network bus, the digital messages including command messages received from the first network bus that each indicate a command for a respective target actuatable device of the multiple actuatable devices; a set of interface components, the interface components each being respectfully configured for connection to a respective one of the multiple actuatable devices; an interface system (IS) controller operably connected to the network transceiver and each of the interface components, the IS controller being operable to: individually assign interface components from the set of interface components to each of the multiple actuatable devices during a configuration of the programmable control interface system; and process command messages received by the network transceiver from the first network bus to: (i) identify, for each received command message, the interface component assigned to the target actuatable device that is the target of the received command message, and (ii) cause the assigned interface component to provide a control signal to the target actuatable device to perform the command indicated in the received command message.

2. The programmable control interface system of claim 1 wherein the IS controller is operable to, during the configuration of the programmable control interface system, store configuration data that indicates any processing required to be performed by IS controller in respect of command messages to cause assigned interface component to provide control signals.

3. The programmable control interface system of claim 1 or 2 wherein the programmable control interface system is also for interfacing between the first network bus and multiple input devices that are not compatible with the first network bus, the interface system (IS) controller being further operable to: during the configuration of the programmable control interface system, individually assign interface components from the set of interface components to each of the multiple input devices; and receive inputs from the interface components assigned to the input devices, and for each received input generate a respective digital message for sending over the first network bus, the respective digital message including an indication of the identity of the input device that caused the interface component to provide the input to the interface system (IS) controller.

4. The programmable control interface system of claim 3 wherein the multiple input devices include one or more sensing devices for sensing a parameter, and the respective digital message includes an indication of the sensed parameter.

5. The programmable control interface system of claim 3 or 4 wherein the multiple input devices include one or more human interface input devices for sensing a parameter, and the respective digital message includes an instruction corresponding to the input.

6. The programmable control interface system of any one of claims 1 to 5 wherein the programmable control interface system is also for interfacing between a first input device and a first actuatable device, the IS controller being further operable to: during the configuration of the programmable control interface system, individually assign interface components from the set of interface components to each of the first input device and the first actuatable device; and receive a first input that is provided by the interface component assigned to the first input device in response to a first signal from the first input device; and responsive to receiving the first input, cause the interface component assigned to the first actuatable device to provide a control signal, based on the first signal, to the first actuatable device.

7. The programmable control interface system of any one of claims 1 to 5 wherein the set of interface components includes a relay component that includes a first input connection that is connected to an output of the IS controller, a second input connection that is assignable to an input device and an output connection that is assignable to an actuatable device, wherein the IS controller is further operable to: during the configuration of the programmable control interface system, assign the second input connection of the relay component to a first input device and assign the output connection of the relay component to a first actuatable device; selectively cause the relay component to operate in one of a first mode and a second mode, wherein in the first mode the relay component is caused to route any inputs received on the first input connection to the output connection of the relay component and in the second mode the relay component is caused to route any inputs received on the second input connection to the output connection of the relay component, thereby enabling the IS controller to selectively enable control of the first actuatable device either by, in the first mode, messages received via the network transceiver, and, in the second mode, inputs from the first input device.

8. The programmable control interface system of any one of claims 1 to 7 wherein programmable control interface system is implemented by a set of electronic components that are housed within an enclosure that includes a set of externally accessible electrical connectors that enable external devices, including the actuatable devices, to be electrically connected to the interface components.

9. A trailer comprising: the programmable control interface system of any one of claims 1 to 8; the first network bus; and the multiple actuatable devices, wherein: the first network bus is operably coupled to a vehicle network bus of a vehicle that is configured to tow the trailer, the vehicle comprising a vehicle controller operably coupled to the vehicle network bus; and the programable control interface system is configured to: receive the command messages from the vehicle controller via the first network bus and the vehicle network bus.

10. A trailer comprising: a databus; an actuatable device a control interface system, comprising: a system controller, configured to be operably coupled to the actuatable device; and a network transceiver, configured to be operably coupled to the databus; wherein: the system controller is operably coupled to the actuatable device and the network transceiver is operably coupled to the databus, such that the databus and the actuatable device are operably coupled via the control interface system.

11. The trailer of claim 10 wherein the trailer comprises a trailer-defined connection counterpart, operably coupled to the databus, and wherein trailer is configured to co-operate with a vehicle, the vehicle comprising: a controller; and a vehicle-defined connection counterpart, operably coupled to the controller; such that: while the vehicle-defined connection counterpart and the trailer-defined connection counterpart are connected, the controller is operably coupled to the actuatable device for controlling the actuation of the actuatable device.

12. The trailer of claim 11, wherein: the actuatable device comprises a sensor configuration configured to detect a parameter of the actuatable device; the system controller is configured to determine an operability of the actuatable device, based at least in part on the parameter of the actuatable device; wherein: the system controller and the sensor configuration are operably coupled, and the operability of the actuatable device is determined by the controller; while the vehicle-defined connection counterpart and the trailer-defined connection counterpart are connected, the controlling of the actuation of the actuatable device is based at least in part on the operability of the actuatable device.

13. The trailer of claim 12, wherein: the vehicle further comprises a user interface, operably coupled to the controller; wherein: while the vehicle-defined connection counterpart and the trailer-defined connection counterpart are connected, a graphical representation of the parameter of the actuatable device is rendered on the user interface.

14. The trailer of claim 12 wherein: the trailer comprises a sensor configuration, operably coupled to the databus, and configured to detect a parameter of the trailer; the system controller is configured to determine an operability of the actuatable device, based at least in part on the parameter of the trailer; wherein: the system controller and the sensor configuration are operably coupled, and the operability of the actuatable device is determined by the controller; and while the vehicle-defined connection counterpart and the trailer-defined connection counterpart are connected, the controlling of the actuation of the actuatable device is based at least in part on the operability of the actuatable device.

15. The trailer of claim 14, wherein: the vehicle further comprises a user interface, operably coupled to the controller; wherein: while the modified trailer is established: while the vehicle-defined connection counterpart and the trailer-defined connection counterpart are connected, a graphical representation of the parameter of the trailer is rendered on the user interface.

16. The trailer of claim 15, wherein: the user interface is further configured to receive an input from a user; wherein: while the vehicle-defined connection counterpart and the trailer-defined connection counterpart are connected, the controlling of the actuation of the actuatable device is based at least in part on the input from the user.

17. The trailer of any one of claims 10 to 16, wherein: the actuatable device comprises an actuator for actuating the actuatable device; wherein: the system controller and the actuator are operably coupled, such that the databus and the actuator are operably coupled via the control interface system.

18. The trailer of claim 17, wherein: while the vehicle-defined connection counterpart and the trailer-defined connection counterpart are connected, the controller becomes operably coupled to the actuator for controlling the actuation of the actuatable device.