Automated Flagpole System, Apparatus and Method

Description

CROSS REFERENCE TO RELATED APPLICATION

This application claims priority to provisional application Ser. No. 63/678,612 filed Aug. 2, 2024, and titled “Automated Flagpole System, Apparatus and Method” which is hereby incorporated by reference in its entirety.

FIELD OF THE DISCLOSURE

This disclosure relates generally to flagpoles. More specifically and without limitation, this disclosure relates to automated systems to raise and lower flags on a flagpole.

Overview of the Disclosure

The United States Flag Code stipulates that that flag of the United States should be lowered from time-to-time to a position known as “half-staff”. This refers to the flag being flown at half of the distance to the top of the staff on which it is displayed. An extensive list of preauthorized dates on which this half-staff hoisting occurs is written into the U.S. Code. However, the U.S. President and Governors of individual states may order the flag to be lowered to half-staff.

For the vast majority of traditional flagpoles in the U.S., each time the flag is ordered to half-staff a physical interaction with the flagpole is required. An individual must lower the flag to half-staff, or, if the flag has not yet been raised for the day, first raise the flag to the peak of the staff and then lower it to half-staff. As the U.S. flag is seen as a literal representation of the American spirit and written in code to be treated as a living being, the promptness of execution and adherence to governmental order is of great importance. Therefore, a system, method and apparatus to quickly receive the order to lower the flag and the means to automatically execute that order is needed.

In one or more arrangements the automated flagpole system includes a flag, a flagpole having a lifting mechanism configured to raise or lower the flag when the flag is attached to the flagpole. The flagpole may also include an actuator operably connected to the lift mechanism and configured to raise or lower the lift mechanism. The automated flagpole system includes a controller module configured to receive user input to raise or lower the flag on the flagpole. The controller module is operably connected to the actuator and configured to instruct the actuator to move the lifting mechanism to raise or lower the flag to a position. The system also includes a remote device operatively connected to the controller module and configured to send at least a raise the flag command, a lower the flag command or a half-staff command.

In one or more arrangements, for example, an automated flagpole apparatus is disclosed. The flagpole apparatus includes a flagpole having a lifting mechanism configured to raise or lower the flag when the flag is attached to the flagpole. The flagpole may also include an actuator operably connected to the lift mechanism and configured to raise or lower the lift mechanism. The automated flagpole system includes a controller module configured to receive user input to raise or lower the flag on the flagpole. The controller module is operably connected to the actuator and configured to instruct the actuator to move the lifting mechanism to raise or lower the flag to a position.

In one or more arrangements, a method for using the automated flagpole system is disclosed. The method includes determining a position of a flag on a flagpole by a controller module of the flagpole. The method may also include communicating by the controller module with a remote device to determine if the flag must be at half-staff. The method further includes communicating with the remote device to the controller module that the flag must be at half-staff. The method may also include providing instructions to an actuator interface of the flagpole by the controller module to raise the flag from the bottom of the flagpole to half-staff or to lower the flag from a top position of the flagpole to half-staff.

As such, for all these reasons existing flagpole systems are too difficult to set up, they are too time consuming to set up and they are too easy to improperly set-up.

Therefore, for all the reasons stated above, and the reasons stated below, there is a need in the art for a flagpole system that improves upon the state of the art.

Another object of the disclosure is to provide a flagpole system that provides improved functionality over prior art systems.

Yet another object of the disclosure is to provide a flagpole system that provides improved features over prior art systems.

Another object of the disclosure is to provide a flagpole system that is relatively inexpensive.

Yet another object of the disclosure is to provide a flagpole system that is easy to use.

Another object of the disclosure is to provide a flagpole system that is intuitive to use. Yet another object of the disclosure is to provide a flagpole system that is strong and robust.

Another object of the disclosure is to provide a flagpole system that can be used in many applications.

Yet another object of the disclosure is to provide a flagpole system that improves efficiencies.

Another object of the disclosure is to provide a flagpole system that provides unique functionality.

Yet another object of the disclosure is to provide a flagpole system that is fast to use and fast to set up.

Another object of the disclosure is to provide a flagpole system that is safe to use. Yet another object of the disclosure is to provide a flagpole system that saves time. Another object of the disclosure is to provide a flagpole system that has a compact size. Yet another object of the disclosure is to provide a flagpole system that has a long useful life.

Another object of the disclosure is to provide a flagpole system that is high quality. These and other objects, features, or advantages of the disclosure will become apparent from the specification, figures and claims.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 is a perspective view of an automated flagpole system, in accordance with one or more arrangements; the view showing a flag flying at half-staff attached to a flagpole.

FIG. 2A is a side view of an automated flagpole system, in accordance with one or more arrangements; the view showing the flagpole and the securing mechanism.

FIG. 2B is another side view of an automated flagpole system, in accordance with one or more arrangements; the view showing the flagpole and the securing mechanism.

FIG. 2C is another side view of an automated flagpole system, in accordance with one or more arrangements; the view showing the flagpole and the securing mechanism

FIG. 3 is a view of an automated flagpole system, in accordance with one or more arrangements; the view showing the flagpole, the automated flagpole system housing, the controller module, the central board, the motor and actuator, the pulley and coupler, the tensioner, and the lifting mechanism.

FIG. 4 is a view of an automated flagpole system, in accordance with one or more arrangements; the view showing the flagpole, the automated flagpole system housing, the controller module, the central board, the motor and actuator, the pulley and coupler, the tensioner, and the lifting mechanism.

FIG. 5 is a view of an automated flagpole system, in accordance with one or more arrangements; the view showing the flagpole, the automated flagpole system housing, the controller module, the central board, the motor and actuator, the pulley and coupler, the tensioner, and the lifting mechanism.

FIG. 6A is a view of an automated flagpole system, in accordance with one or more arrangements; the view showing the flagpole, an internal lifting mechanism, the securing mechanism, the shaft, the interior of the flagpole and the exterior of the flagpole.

FIG. 6B is a view of an automated flagpole system, in accordance with one or more arrangements; the view showing the cleat

FIG. 6C is a view of an automated flagpole system, in accordance with one or more arrangements; the view showing the cleat.

FIG. 7 is a side view of an automated flagpole system, in accordance with one or more arrangements; the view showing the flagpole, the winch, the top flag position, the bottom flag position, the mounting height, the flag securing members, the securing mechanism, the cleat, the ground sleeve and the ground.

FIG. 8 is a view of an internal lifting mechanism of an automated flagpole system, in accordance with one or more arrangements; the view showing the trunk and the pulley.

FIG. 9 is another view of an internal lifting mechanism of an automated flagpole system, in accordance with one or more arrangements; the view showing the pulley, the actuator, the internal side of the flagpole, the external side of the flagpole and a door to the inside of the flagpole.

FIG. 10 is a view of an automated flagpole system, in accordance with one or more arrangements; the view showing the power source, the solar panel and the battery.

FIG. 11 is a flowchart of an example process performed by the communication system of an automated flagpole system, in accordance with one or more arrangements.

FIG. 12. Is a chart showing an example communication system for an automated flagpole system, in accordance with one or more arrangements; the view showing the controller module, the user interface, the memory, the storage, the actuator interface, the communications module, the transceiver, the safety and redundancy system, the microcontroller, the sensor interface, the remote control logic, the mobile application, the cloud, the could-based and/or edge computing system, the alert and notification system, the graphical user interface and the sensors including the position sensor, the voltage sensor, the time sensor, the obstruction detection sensor.

FIG. 13 is a picture of an automated flagpole system, in accordance with one or more arrangements; the view showing the solar panel, the user inputs, the status indicators, the lifting mechanism and the flagpole.

FIG. 14 is a picture of an automated flagpole system, in accordance with one or more arrangements.

FIG. 15 is a picture of an automated flagpole system, in accordance with one or more arrangements.

FIG. 16 is a picture of an automated flagpole system, in accordance with one or more arrangements.

DETAILED DESCRIPTION OF THE DISCLOSURE

In the following detailed description of the embodiments, reference is made to the accompanying drawings which form a part hereof, and in which is shown by way of illustration specific embodiments in which the disclosure may be practiced. The embodiments of the present disclosure described below are not intended to be exhaustive or to limit the disclosure to the precise forms in the following detailed description. Rather, the embodiments are chosen and described so that others skilled in the art may appreciate and understand the principles and practices of the present disclosure. It will be understood by those skilled in the art that various changes in form and details may be made without departing from the principles and scope of the invention. It is intended to cover various modifications and similar arrangements and procedures, and the scope of the appended claims therefore should be accorded the broadest interpretation so as to encompass all such modifications and similar arrangements and procedures. For instance, although aspects and features may be illustrated in or described with reference to certain figures or embodiments, it will be appreciated that features from one figure or embodiment may be combined with features of another figure or embodiment even though the combination is not explicitly shown or explicitly described as a combination. In the depicted embodiments, like reference numbers refer to like elements throughout the various drawings.

It should be understood that any advantages and/or improvements discussed herein may not be provided by various disclosed embodiments, or implementations thereof. The contemplated embodiments are not so limited and should not be interpreted as being restricted to embodiments which provide such advantages or improvements. Similarly, it should be understood that various embodiments may not address all or any objects of the disclosure or objects of the invention that may be described herein. The contemplated embodiments are not so limited and should not be interpreted as being restricted to embodiments which address such objects of the disclosure or invention. Furthermore, although some disclosed embodiments may be described relative to specific materials, embodiments are not limited to the specific materials or apparatuses but only to their specific characteristics and capabilities and other materials and apparatuses can be substituted as is well understood by those skilled in the art in view of the present disclosure.

It is to be understood that the terms such as “left, right, top, bottom, front, back, side, height, length, width, upper, lower, interior, exterior, inner, outer, and the like as may be used herein, merely describe points of reference and do not limit the present invention to any particular orientation or configuration.

As used herein, the term “or” includes one or more of the associated listed items, such that “A or B” means “either A or B”. As used herein, the term “and” includes all combinations of one or more of the associated listed items, such that “A and B” means “A as well as B.” The use of “and/or” includes all combinations of one or more of the associated listed items, such that “A and/or B” includes “A but not B,” “B but not A,” and “A as well as B,” unless it is clearly indicated that only a single item, subgroup of items, or all items are present. The use of “etc.” is defined as “et cetera” and indicates the inclusion of all other elements belonging to the same group of the preceding items, in any “and/or” combination(s).

As used herein, the singular forms “a,” “an,” and “the” are intended to include both the singular and plural forms, unless the language explicitly indicates otherwise. Indefinite articles like “a” and “an” introduce or refer to any modified term, both previously-introduced and not, while definite articles like “the” refer to a same previously-introduced term; as such, it is understood that “a” or “an” modify items that are permitted to be previously-introduced or new, while definite articles modify an item that is the same as immediately previously presented. It will be further understood that the terms “comprises,” “comprising,” “includes,” and/or “including,” when used herein, specify the presence of stated features, characteristics, steps, operations, elements, and/or components, but do not themselves preclude the presence or addition of one or more other features, characteristics, steps, operations, elements, components, and/or groups thereof, unless expressly indicated otherwise. For example, if an embodiment of a system is described as comprising an article, it is understood the system is not limited to a single instance of the article unless expressly indicated otherwise, even if elsewhere another embodiment of the system is described as comprising a plurality of articles.

It will be understood that when an element is referred to as being “connected,” “coupled,” “mated,” “attached,” “fixed,” etc. to another element, it can be directly connected to the other element, and/or intervening elements may be present. In contrast, when an element is referred to as being “directly connected,” “directly coupled,” “directly engaged” etc. to another element, there are no intervening elements present. Other words used to describe the relationship between elements should be interpreted in a like fashion (e.g., “between” versus “directly between,” “adjacent” versus “directly adjacent,” “engaged” versus “directly engaged,” etc.). Similarly, a term such as “operatively”, such as when used as “operatively connected” or “operatively engaged” is to be interpreted as connected or engaged, respectively, in any manner that facilitates operation, which may include being directly connected, indirectly connected, electronically connected, wirelessly connected or connected by any other manner, method or means that facilitates desired operation. Similarly, a term such as “communicatively connected” includes all variations of information exchange and routing between two electronic devices, including intermediary devices, networks, etc., connected wirelessly or not. Similarly, “connected” or other similar language particularly for electronic components is intended to mean connected by any means, either directly or indirectly, wired and/or wirelessly, such that electricity and/or information may be transmitted between the components.

It will be understood that, although the ordinal terms “first,” “second,” etc. may be used herein to describe various elements, these elements should not be limited to any order by these terms unless specifically stated as such. These terms are used only to distinguish one element from another; where there are “second” or higher ordinals, there merely must be a number of elements, without necessarily any difference or other relationship. For example, a first element could be termed a second element, and, similarly, a second element could be termed a first element, without departing from the scope of example embodiments or methods.

Similarly, the structures and operations discussed herein may occur out of the order described and/or noted in the figures. For example, two operations and/or figures shown in succession may in fact be executed concurrently or may sometimes be executed in the reverse order, depending upon the functionality/acts involved. Similarly, individual operations within example methods described below may be executed repetitively, individually or sequentially, to provide looping or other series of operations aside from single operations described below. It should be presumed that any embodiment or method having features and functionality described below, in any workable combination, falls within the scope of example embodiments.

As used herein, various disclosed embodiments may be primarily described in the context of flagpole systems. However, the embodiments are not so limited. It is appreciated that the embodiments may be adapted for use in various other applications, which may be improved by the disclosed structures, arrangements and/or methods. The system is merely shown and described as being used in the context of flagpole systems for ease of description and as one of countless examples.

In one or more arrangements, for example as shown, the automated flagpole system is a comprehensive Internet of things (“IoT”) system designed to modernize and automate the management of a physical flagpole. In one or more arrangements, for example, the automated flagpole system combines a custom-built Arduino controller with a powerful cloud backend to provide a wide range of control options, from manual button presses to fully automated, data-driven actions. This automated flagpole system ensures the flag is displayed properly and respectfully with minimal human intervention, handling daily routines and special protocols automatically.

System 10

With reference to the figures, a flagpole system 10 (or simply system 10) is presented. System 10 is formed of any suitable size, shape and design and is configured to facilitate raising flag 14 to a certain height off the ground for a desired duration, such as at a top of the flagpole, to half-staff and lowering the flag to half-staff 16 or to remove the flag. In the arrangement shown, as one example, system 10 includes a flagpole 12, a flag 14, an actuator 66, a coupler 42, a tensioner 40, a lifting mechanism 18, a user interface 92, sensors 78, a securing system 22, flag securing members 30, as well as other components.

In one or more arrangements, for example, system 10 may automatically hoist a flag 14 to half-staff 16. Modern technology offers multiple means by which to receive wireless or remote notifications. Electronic power systems can efficiently monitor the status of flag 14 upon the flagpole 12. Electric motors 44 can move the flag 14 up and down a flagpole 12 via the same rope or lifting mechanism 18 in which a human would interact. The intent of system 10 is to remove the need for human interaction with flagpole 12 in order to comply with government orders to fly flag 14 at half-staff 16.

Flag 14:

With reference to the figures, in one or more arrangements, as shown for example, flag 14 is formed of any suitable design, shape, or size and is configured to be attached to flagpole 12. Flag 14 is provided for display on flagpole 12, wherein one or more flag securing members 30 are configured to affix the flag 14 to the flagpole 12 in a stable, secure, and weather-resistant manner. The flag securing members 30 may include, but are not limited to, clips, hooks, carabiners, grommets, snap fasteners, or loop-and-cord arrangements, which may be formed from metal, polymer, textile, or composite materials. In one embodiment, flag securing members 30 are operatively coupled to a peripheral edge or header portion of the flag 14 and are adapted to engage corresponding retaining features on flagpole 12, such as eyelets, rings, tracks, or channels. The flag securing members 30 may be adjustable, tensionable, or elastically biased to maintain tautness of the flag 14 and to prevent excessive flapping or detachment under wind load. In some embodiments, the flag securing members 30 are integrally formed with the flagpole 12 or removably attachable thereto for ease of assembly, replacement, or reconfiguration. The configuration may allow for vertical or rotational adjustment of the flag 14 relative to the flagpole 12, enabling user customization and ensuring proper flag orientation under various environmental conditions. Flag securing members 30 may be any suitable size, shape, and design to facilitate affixing flag 14 to flagpole 12.

Flagpole 12:

With reference to the figures, flagpole 12 is formed of any suitable size, shape and design and is configured to hold a flag 14. In one or more arrangements, as shown, for example, flagpole 12 is a residential flagpole 12. In other arrangements, as shown, for example, flagpole is a commercial flagpole 12. Flagpole 12 has shaft 20 that may be made of wood, fiberglass, aluminum, metal, plastics or steel or any other material capable of supporting a flag 14 at a mounting height 34 above the ground 48. Flagpole 12 has an internal side 52 of flagpole 12 and an external side of the flagpole 12. Truck 26 sits at the top 36 of flagpole 12 and houses the pulley 24 for the lifting mechanism 18 to facilitate raising and lowering flag 14. Flagpole 12 may be 10 to 30 feet in height, 3 to 5 inches in diameter, and/or a static truck. In other arrangements, for example, the height or diameter may be smaller or larger, and the truck may be rotating. In one or more arrangements, as shown, for example flagpole 12 is configured to be installed within a ground sleeve 32, which is embedded in the ground 48 or a foundation structure and serves to receive and support the lower end of the flagpole 12, thereby providing a stable, upright mounting arrangement while also allowing for removal or repositioning of the flagpole as needed. Flagpole 12 may be any suitable size, shape, and design to facilitate holding flag 14.

Lifting Mechanism 18:

With reference to the figures, system 10 includes a lifting mechanism 18. Lifting mechanism 18 is formed of any suitable size, shape, and design and is configured to raise or lower flag 14 on flagpole 12. The lifting mechanism 18 may be halyard, rope, or cable or any other mechanism sufficient to raise or lower a flag 14 or other item on the flagpole 12 connected to one or more pulleys 24. Pulleys 24 may be located at a top flag position 54 and/or a bottom flag position 56. The lifting mechanism 18 may be on an external side 50 of flagpole 12 or shaft 20, or inside an interior side 52 of shaft 20 or flagpole 12. External lifting mechanism 18 or halyard may utilize the traditional method for raising and lowering flags 14. The lifting mechanism 18 may be a rope that runs up and down the outside of flagpole 12. It is easier to use and costs less than an internal lifting mechanism 18 flagpole 12. Standard is a 360° revolving truck 26 at top 36, 54 with a pulley 24 and a cleat 58 to tie the lifting mechanism 18, such as the halyard, to at the bottom 56. Because the lifting mechanism 18 is tied at the bottom 56 there is limited rotation of the truck 26 at top 36. An internal lifting mechanism 18 or internal halyard may include a rope-based system that has a less expensive internal rope and cleat 58 mechanism concealed by a locking door 60. It is an excellent choice for flagpoles with a height of 40′ or less where additional security is desired. The lifting mechanism 18 runs up the inside of the flagpole and out at the revolving truck 26 and is held to the flagpole by a securing system 22 and down by a weight or positioning sensor 84. The flag or flags 14 are installed above the weight. This system 10 is simple to use and has low maintenance. The cost is less than the cable based internal lifting mechanism 18 system. Lifting mechanism 18 may be any suitable size, shape, and design to facilitate raising and lowering flag 14.

Securing System 22:

With reference to the figures, system 10 may have a securing system 22. Securing system 22 is formed of any suitable size, shape, and design and is configured to secure the lifting mechanism 18 to the flagpole 12. In one or more arrangements, as shown, for example, securing system 22 includes a cleat or other mechanism configured to secure the lifting mechanism 18 to flagpole 12 to secure flag 14 at a specific height on the flagpole 12. A winch 28 of flagpole 12 facilitates raising or lowering flag 14 on flagpole 12. Winch 28 may be fixed or moveable. The securing system 22 may be a cleat 58 such as a static “saddle-like” fixture mounted externally to the flagpole 12, a retaining ring, or a ratchet-type pinching lever cleat on an interior of the shaft 20 or any other type of securing mechanism that is capable of securing the lifting mechanism 18 to flagpole 12. In one or more arrangements, for example, securing system 22 may utilize the existing mounting holes for the traditional cleat. The cleat may be removed and replaced with a mounting plate adapter. In one or more arrangements, as shown, for example, the cleat 58 may be comprised of a motorized cleat 58 configured for engagement and disengagement with lifting mechanism 18. The cleat 58 may also include a low-power stepper motor operable to rotate a gripping component between open and closed positions. In one or more arrangements, for example, cleat 58 comprises a servo-motor actuated locking pin, selectively engageable to lock the cleat in the closed position to prevent unintentional release of the lifting mechanism 18. The securing system 22 may include a winch 28 assembly, wherein the winch 28 may be fixed to the flagpole 12 or removably mounted, enabling both static and dynamic rope management configurations. The combination of stepper motor control and servo-actuated locking provides precise, energy-efficient operation suitable for remote or automated flag handling applications. In one or more arrangements, as shown, for example, the securing system 22 may include using existing cleat 58 mounting holes for external lifting mechanisms 18 halyards. The securing system 22 may include straps, pipe clamp-like straps around the flagpole, magnets, weights, retaining rings, external halyard cleat mounting bolt adapter or any other securing system 22 that facilitates securing the flag 14 to the flagpole 12 or at a specific position on the flagpole 12. Securing system 22 may be any suitable size, shape, and design to facilitate securing the lifting mechanism 18 to flagpole 12.

Housing 38:

With reference to the figures, system 10 may include a housing 38 that is formed of any suitable size, shape, and design and is configured to store components of system 10, such as lighting systems, sensors 78, controllers 102, or communication systems 100 in an interior 64 of the housing 38. The interior 64 of the housing 38 opposes an exterior side 62 of housing 38. The housing 38 may be configured for outdoor use and is constructed from weather-resistant materials such as UV-stabilized polymer, powder-coated metal, or composite materials to withstand prolonged exposure to environmental conditions including rain, snow, humidity, temperature extremes, and UV radiation. The housing 38 may include sealing features such as gaskets, O-rings, or conformal coatings to achieve a desired ingress protection (IP) rating, thereby preventing the intrusion of moisture, dust, or debris. In some embodiments, the housing 38 is ventilated or thermally managed through passive or active cooling systems, such as heat sinks, vents with hydrophobic membranes, or low-power fans, to prevent overheating of internal components. The housing 38 may be mounted directly to flagpole 12, to a support structure adjacent to flagpole 12, or positioned at a remote but operatively connected location, and may include access panels or ports to facilitate maintenance, wiring, or replacement of internal components. Housing 38 may be any suitable size, shape, and design to facilitate securing the storing components of system 10.

Actuator 66:

With reference to the figures, system 10 may include an actuator 66. Actuator 66 is formed of any suitable size, shape, and design and is configured to raise or lower flag 14 on flagpole 12 utilizing the lifting mechanism 18. In one or more arrangements, as shown, for example, actuator 66 may include one or more optional actuators 66 selected from a 24V DC brushed motor, a 12V DC stepper motor, or an electronically controlled motor, which may be powered by either AC or DC current. In other arrangements, for example, actuator 66 may include brushless DC (BLDC) motors, AC induction motors, servo motors, linear actuators, and coreless or gear-reduced motors, depending on torque, speed, and control needs of system 10. In one or more arrangements, for example, the actuator 66 is powered directly from a microcontroller's 120 onboard voltage output. In other arrangements, for example the actuator 66 is not directly powered from the microcontroller's 120 onboard voltage output, as this may result in insufficient power delivery or damage to system 10 components. The actuator 66 may be powered from a separate power supply. In one or more arrangements, motors 44 may support closed-loop feedback using encoders, Hall-effect sensors, or potentiometers for positional accuracy. Motors 44 may also incorporate integrated driver electronics, thermal protection, or environmental sealing including but not limited to IP65-rated enclosures for use in harsh or outdoor conditions. Actuation may involve rotary or linear output, and motors 44 may be configured in direct drive, geared, or belt/chain-driven arrangements depending on the mechanical interface. Actuator 66 may be disposed of within an interior 64 of the housing 38. A user may access the actuator 66 through door 60 that opens to interior 64 of housing 38. Actuator 66 may be any suitable size, shape, and design to facilitate raising or lowering flag 14.

Power Source 70:

With reference to the figures, system 10 includes a power source 70. Power source 70 is formed of any suitable size, shape, and design and is configured to power the system 10 or one or more components of system 10, such as but not limited to lifting mechanism 18. System 10 may be configured to be powered by a versatile and adaptable power source 70, which may include a range of optional configurations to suit various environmental and operational conditions. In one or more arrangements, for example, as shown, the power source 70 is a 24V DC supply derived from a solar panel 72 and battery 74 combination. In other arrangements, for example, a 12V DC configuration using a similar solar 72 and battery 74 arrangement may be used to power system 10. In other arrangements, the power source 70 may include one or more renewable energy sources such as a solar panel 72 and/or wind generator. The renewable power source 70 may operate in conjunction with a rechargeable battery 74 to provide energy storage and continuous operation. In one or more arrangements, for example, power source 70 may be hard-wired to an AC power source, either as a primary or backup supply. When connected to an AC source, a transformer or voltage regulation circuitry may be required to ensure the output voltage is compatible with the system's operating requirements. Additional power input options may include fuel cells, diesel or gas-powered generators, or uninterruptible power supplies (UPS) for backup scenarios. The power source 70 may further include power conditioning circuitry, such as charge controllers, inverters, voltage monitoring, and overcurrent protection, to ensure stable and safe delivery of electrical power across various conditions. Power source 70 may be operable connected to the controller module 102 or the microcontroller 120, or a central board 46 of the microcontroller 120 or controller module 102. This flexible power source architecture enables deployment in both off-grid and grid-connected environments. Power source may be any suitable size, shape, and design to facilitate powering system 10.

Coupler 42:

With reference to the figures, system 10 includes at least one coupler 42. Coupler 42 is formed of any suitable size, shape, and design and is configured to transmit a mechanical force to the lifting system 18 from the actuator 66. Coupler 42 may take various forms depending on the specific actuator 66 type and lifting mechanism 18. In one or more arrangements, as shown for example, coupler 42 comprises a winch 24 port interface, wherein the actuator engages a rotating drum or spool to wind or unwind a cable, thereby raising or lowering the lifting mechanism 18. In other arrangements, for example a geared direct-drive coupler 42 may be employed, wherein the actuator's 66 output shaft is mechanically interfaced with the lifting mechanism 18 through a gear train to provide torque multiplication and controlled linear motion. In other arrangements, for example coupler 42 may include but are not limited to: belt drives, chain drives, spline shafts, keyed connections, or magnetically coupled systems, allowing for tailored integration with a variety of lifting mechanisms 18. The coupler 42 may be rigid or flexible and may incorporate safety features such as torque limiters, overload clutches, or quick-disconnect elements. This modular coupler 42 enables the lifting system 18 to be adapted to a range of actuator 66 types and operational requirements while maintaining structural integrity and motion precision. Coupler 42 may be any suitable size, shape, and design to facilitate transmitting a mechanical force from motor to lifting mechanism 18.

Tensioner 40:

With reference to the figures, system 10 may include a tensioner 40. Tensioner 40 is formed of any suitable size, shape and design and is configured to facilitate the lifting mechanism 18 remaining taunted throughout the hoisting process and may remain securely fixed on the flag 14 is in position. In one or more arrangements, for example, where a cable-driven lifting mechanism 18 is employed, the tensioner 40 serves to compensate for slack, elasticity, thermal expansion, or mechanical stretch, all of which can induce positional errors and degrade actuator effectiveness. In other arrangements, for example, tensioners 40 may include, but are limited to, externally mounted counterweights, preloaded spring-arms, or spring-loaded pulleys that apply constant or variable force to the cable or belt path to maintain appropriate tension. Tensioner 40 may be passive or active and may optionally incorporate feedback sensors to monitor cable displacement, tension force, or system deflection. Tensioner 40 may be located at fixed or movable anchor points, along guide rails, or integrated directly into the actuator or coupler assembly. This adaptable tensioning architecture is essential for maintaining consistent lifting behavior, preventing backlash or drift, and extending the operational lifespan of both the actuator and the lifting medium. Tensioner 40 may be any suitable size, shape, and design to facilitate keeping the lifting system 18 taunt.

Position Sensors 84:

With reference to the figures, system 10 may have one or more position sensors 84. Position sensors 84 are formed of any suitable size, shape, and design and are configured to detect the location of flag 14 on flagpole 12. Position sensors 84 configured to monitor and report the position, movement, or status of lifting mechanism 18, flag 14, actuator 66, pulley 24 or any other component of system 10 with respect to a reference point or travel range. These position sensors 84 ensure accurate control, repeatability, and safety during lifting, lowering, and load positioning operations. In one or more arrangements, for example, the positioner sensors 84 may include but are not limited to Hall-effect sensors in conjunction with permanently mounted magnets on the moving components, allowing for non-contact detection of linear or rotary position. The Hall-effect sensor is a solid-state device that responds to changes in magnetic fields by producing a corresponding electrical signal, typically a voltage. These position sensors 84 may be mounted on a stationary part of system 10, such as the shaft 20, flagpole, or housing 38 and are configured to detect the proximity, presence, or passing of a magnetic field generated by one or more discrete magnets mounted to a moving part of the lift, such as a cable carriage, actuator arm, or winch drum. For example, position sensors 84 may be located at the top flag position 54 and/or the bottom flag position 56, or at half-staff 16. The magnets may be of various types, including rare-earth (e.g., neodymium), ferrite, or alnico compositions, and may be embedded, surface-mounted, or otherwise affixed to the moving component at specific locations to correspond with known positions in the mounting height 34. The positioner sensors 84 may include multiple magnets spaced at calibrated intervals for multi-point position tracking or a single magnet for limit or reference detection. By sensing magnetic field transitions as magnets pass near the Hall-effect sensors, system 10 can determine absolute or relative position, movement direction, and speed. In other arrangements, for example, digital Hall-effect sensors can provide binary on/off signals, while analog Hall-effect sensors may be used to estimate continuous displacement based on magnetic field strength.

In one or more arrangements, for example, the position sensors 84 may include Hall-effect sensors, which may be employed, for example, as standalone solid-state components that detect changes in magnetic fields induced by ferrous materials or internally generated electromagnetic conditions. These sensors may be integrated into housing 38, shaft 20 or flagpole 12 to provide non-contact position feedback, particularly suitable for rotary or linear actuators with embedded magnetic field variations, such as those using motor shaft feedback or encoded rotor positions.

In other arrangements for example, the position sensors 84 may include magnet-based sensors, such as but not limited to reed switches or magnetic proximity sensors, that rely on the movement of a discrete permanent magnet affixed to a moving component of system 10. As the magnet position sensor 84 approaches or passes by a fixed position sensor 84, it triggers a signal that can be used to define limit positions, intermediate checkpoints, or positional changes. The magnet position sensor 84 and positioner sensor 84 may be placed at predefined intervals to enable multi-point detection or travel tracking.

These position sensor 84 options, Hall-effect or magnet-based, may be implemented individually or in combination with other technologies such as step-counting, optical encoders, distance sensors, or mechanical limit switches, depending on the required resolution, environmental conditions, and control strategy. This modular approach allows for high configurability of the position detection system based on application-specific needs.

In other arrangements, for example, the position sensor 84 is a stepper motor actuator and the position of flag 14 is tracked. When a stepper motor actuator is used, position may also be tracked via a step-counting algorithm, wherein each discrete motor step is monitored to estimate displacement, either independently or with feedback correction. Alternatively, or additionally, the lift mechanism 18 may incorporate distance tracking position sensors 84, such as ultrasonic, infrared, or laser rangefinders, which provide continuous measurement of position relative to a fixed frame or ground plane. For example, the stepper motor amplifier, configured as a position sensor 84, may exhibit an initial spike when the flag is positioned at the top of the flagpole 12, typically due to transient response, followed by a stepwise progression corresponding to elapsed time as flag 14 is lowered. Each step represents a fixed time interval, allowing system 10 to measure time based on the number of steps completed while the flag is lowered. This allows the system to track flag 14 position and the time it takes to lower flag 14.

In other arrangements, for example, the lift mechanism 18 may utilize a calibrated electronic timer as a position sensor 84, particularly in systems where motion occurs at a consistent, known rate over time. This approach estimates the position of a moving component, such as but not limited to lifting mechanism 18, flag 14, pulley 24, or actuator 66, by tracking the elapsed time during powered movement and correlating it with pre-characterized speed profiles. The timer is initialized at a known reference point (e.g., a home or zero position) and begins counting when the actuator 66, or pulley 24 is engaged. Based on prior calibration data, which may include actuator speed, gear ratios, load conditions, and direction of travel, the system 10 can infer the approximate position of the lift element at any given time.

This system 10 is particularly well-suited for use with stepper motors, DC motors with known RPMs, or geared drives where speed and direction are tightly controlled. To improve accuracy, the time-based position sensor 84 may periodically reset or synchronize its internal count using independent reference signals, such as limit switches, Hall-effect sensors, or encoder pulses. In some implementations, software compensation may be applied to correct for drift, load variation, or wear over time. The calibrated electronic timer position sensor 84 may function as a primary, secondary, or redundant position sensing system, and is advantageous in low-cost, space-constrained, or sealed environments where physical sensors are impractical or undesirable.

In other arrangements, for example system 10 or lift mechanism 18 includes one or more limit switches as position sensors 84 to define physical endpoints of travel, establish reference positions, such as at the top flag position 54 and the bottom flag position 56. These switches act as discrete position indicators that signal when flag 14 has reached a predefined limit or boundary. Limit switches can be used to prevent overtravel, initiate homing routines, or serve as safety interlocks to halt motion when thresholds are exceeded. System 10 may incorporate various types of limit switches as position sensors 84 depending on environmental conditions, required precision, and mechanical constraints. In one or more arrangements, for example, the limit switch may be a 3-wire limit switch that is connected to Signal, VCC (High), and GND. If 2-wire switches are used (connected only to Signal and VCC (High)), a “slow drain” effect on the power source, which may include Arduino's input pins, can occur. This may cause a delay in detecting the switch trigger, leading to inaccurate positioning or failure to stop the motor at the correct time.

In other arrangements, for example mechanical limit switches utilize a physical actuator 66, such as a lever arm, plunger, or roller, that is directly engaged by the moving lift mechanism 18. These switches are commonly used due to their simplicity, reliability, and ease of integration. Variants may include snap-action switches, which provide a fast and distinct switching response, or slow-break/make types for applications where contact bounce must be minimized. Magnetic limit switches operate based on proximity to a magnet affixed to the moving part. These may include reed switches, which are sealed in glass enclosures and close or open in response to a nearby magnetic field. Magnetic switches are advantageous in dusty, wet, or chemically aggressive environments where mechanical wear or exposure may degrade conventional contacts. Optical limit switches, including reflective or through-beam photoelectric sensors, may be integrated into the lift mechanism for high-speed, non-contact position detection. These are particularly useful where no physical contact is permissible.

Each limit switch may be mounted to a fixed frame or moving carriage and may operate in normally open (NO) or normally closed (NC) configurations, depending on the control logic. The system may also employ redundant limit switches for fault tolerance, adjustable trip points for customizable travel limits, or programmable electronic limit switches as part of a more advanced motion control system. These switches may interface directly with the actuator interface, or a centralized logic controller, ensuring that the lifting system operates within defined mechanical and safety boundaries at all times. Position sensor 84 may be any suitable size, shape, or design that facilitates the detection of the location of flag 14 on flagpole 12.

Voltage Sensor 86:

With reference to the figures, system 10 may have one or more voltage sensors 86. Voltage sensors 86 are formed of any suitable size, shape and design and are configured to monitor electrical conditions at critical points within the system, including the motor power supply and the controller module 102 input. These voltage sensors 86 provide real-time feedback on voltage levels to support diagnostics, performance optimization, fault detection, and protective shutdowns. In other arrangements, for example, voltage sensor 86 may include but is not limited to a voltage divider circuit, wherein a pair of resistors or impedance elements are configured to scale the monitored voltage down to a level suitable for analog-to-digital conversion by a microcontroller or processor. This method is particularly effective for monitoring high-voltage motor supplies (e.g., 12V, 24V, or higher), allowing system 10 to detect undervoltage, overvoltage, or brownout conditions that could compromise actuator performance or safety.

In other arrangements the voltage sensor 86 may include but is not limited to dedicated voltage monitoring ICs, isolation amplifiers, or analog front-end circuits designed to provide accurate measurements with enhanced stability, noise immunity, and protection from transient spikes. For AC-powered systems, RMS voltage sensors or zero-crossing detectors may also be incorporated to characterize line voltage conditions. Voltage data may be sampled continuously or at predefined intervals, and may be used to adjust control parameters dynamically, log operational status, or trigger alerts when thresholds are exceeded. The voltage sensor 86 may monitor one or more nodes in the power system, including but not limited to, the motor terminals, motor driver output, controller input rail, battery output, or auxiliary power lines. In some implementations, the voltage sensor 86 may interface directly with battery management systems (BMS), power conditioning circuits, or energy harvesting modules, enabling the lift mechanism to operate safely and efficiently under a wide range of electrical supply scenarios. Voltage sensor 86 may be any suitable size, shape, or design that facilitates the monitoring of electrical currents.

Time Sensor 88:

With reference to the figures, system 10 may include one or more time sensors 88 or time keeping modules 88. Time sensors 88 and time keeping modules 88 are formed of any suitable size, shape, and design and are configured to maintain accurate clock time, enabling time-dependent operations, data logging, and event tracking even when the system is operating offline or without network connectivity. In one or more arrangements, for example, timekeeping is achieved using a real-time clock (RTC) module as the time sensor 88, which may include a crystal oscillator and dedicated integrated circuit capable of maintaining time with high accuracy over extended periods. The RTC module may be powered by a secondary power source, such as a coin-cell battery, supercapacitor, or onboard backup supply, ensuring continuity of timekeeping even during power interruptions or system shutdowns. In other arrangements, the time sensor 88 or time keeping modules 88 are powered by the power source 70. In other arrangements, for example, time sensors 88 may include GPS-based time receivers, network time synchronization modules (e.g., NTP clients), or microcontroller-based counters calibrated against a known oscillator reference. When online connectivity is available, system 10 may synchronize periodically with external time sources, and store a calibrated offset or timestamp locally for future reference. In fully offline conditions, the onboard RTC or equivalent time sensor 88 ensures continuity of accurate time data, which may be critical for features such as scheduled operations, system wake/sleep cycles, maintenance alerts, audit trails, or event timestamping.

In other arrangements, for example the timekeeping module 88 may also track elapsed runtime, power-on hours, or cycle counts, and may interface with non-volatile memory to preserve time and date information across power losses. The time sensor 88 may be integrated into the controller module 102, housed as a discrete module, or implemented in software using watchdog timers, tick counters, or hardware clocks available within the microcontroller 120. This resilient and flexible time sensing architecture supports both real-time and historical functionality, ensuring robust system performance in both connected and standalone operational environments. Time sensors 88 or time keeping modules 88 may be any suitable size, shape, or design that facilitates maintaining an accurate clock time.

Obstruction Detection Sensor 90:

With reference to the figures, system 10 may have at least one obstruction detection sensor 90, which is formed of any suitable size, shape, and design, and is configured to detect obstacles along the lifting mechanism 18 that may prevent the raising or lowering of flag 14 or may damage flag 14 or any other component of system 10. The obstruction detection sensors 90 may detect the presence of foreign objects, structural interference, or unintended blockages along the lift path. These obstruction detection sensors 90 may be used to monitor the movement of the flag 14, lifting mechanism 18, pulley 24, actuator 66, or any other component of system 10 and may trigger automatic responses, such as, but not limited to, halting movement, reversing direction, or issuing an alert, when an obstruction is detected. In one or more arrangements, for example, proximity sensors, such as ultrasonic, infrared (IR), or laser-based distance sensors, are positioned along flagpole 12 as obstruction detection sensors 90 to continuously scan for unexpected objects within a defined travel corridor. These obstruction detection sensors 90 sensors can provide real-time distance measurements and are capable of detecting stationary or moving obstructions.

In other arrangements, for example, the obstruction detection sensors may be mechanical contact sensors, such as pressure-sensitive bump strips, micro-switches, or flexure triggers, may be mounted on the flagpole 12 or lifting mechanism 18 or any other component of system 10 to physically detect contact with an obstruction. Obstruction detection sensor 90 may be used alone or in combination with position sensors 84 and safety interlocks and may be integrated into the system's controller module 102 for coordinated decision-making. In some cases, the obstruction detection sensor 90 may include but is not limited to current monitoring or motor load sensing may be used as an indirect method of obstruction detection, wherein an unexpected spike in torque or stall current indicates resistance due to physical blockage. This obstruction detection sensor 90 may also support fail-safe routines, such as emergency braking or load release, and may log obstruction events for diagnostics or maintenance purposes. The flexible architecture of the obstruction detection sensor 90 allows for adaptation to a wide range of lift configurations, environments, and safety requirements. Obstruction detection sensor 90 may be any suitable size, shape, or design that facilitates detecting objects that may prevent the raising or lowering of flag 14 or damage to one or more components of system 10.

User Interface 92:

With reference to the figures, system 10 may have a user interface 92. User interface 92 is formed of any suitable size, shape, design and is configured to provide both status feedback and manual control for operating system 10. User interface 92 may be integrated into the system housing 38, mounted remotely, or implemented on a connected device 132 such as a touchscreen, mobile application 134, or any remote device 132 in communication with controller module 102, such as a desktop console. In certain embodiments, the user interface 92 includes one or more buttons 94 or input controls 94 for raising and lowering flag 14, as well as additional input controls 94 including but not limited to buttons, switches, or soft keys, or microphones to receive verbal commands for selecting predefined lift positions (e.g., “ground level,” “top level” and “half-staff” etc.). The preset position input controls 94 may correspond to stored actuator positions or encoded step counts and may be programmed or adjusted by the user as needed.

The user interface 94 may also feature status indicators 96, such as visual status indicators 96, including but not limited to, LEDs, LCDs, OLED displays, e-ink panels, to show the current system status, including but not limited to lift position, power availability, system faults, obstruction alerts, motor temperature, battery charge level, or communication link status. In one or more arrangements, for example the user interface 94 may have three push buttons 94 and four status LEDs 96. The LEDS 96 may include a first LED 96A for flag 14 being located at the bottom flag position 56, a second LED 96B for flag 14 being located at the top flag position 54, a third LED 96C for the flag 14 being at half-staff 16, and a fourth LED 96D to indicate that system 10 is calibrating. If the flag 14 is in transit, the LED 96 corresponding to its destination may have a first flashing pattern, such as flashing quickly, flashing slowly, flashing at specific time intervals, a specific pattern, or remain solid. When the flag is holding steady at a position, the corresponding LED 96 may flash with a second flashing pattern, such as flash quickly, flashing slowly, flashing at specific time intervals, a specific pattern, or remain solid. The “calibrating” LED 96 may have a third flashing pattern, such as flash quickly, flash slowly, flashing at specific time intervals, a specific pattern, or remain solid, during the calibration sequence. The other LEDs 96 will follow the rules above as the flag moves during calibration. The flashing patterns for each LED 96 may be the same or different. In other arrangements the status indicators may be auditory using a speaker of system 10 or tactile.

To raise flag 14, a user may press and hold the “raise” button 94A for a specific time period, such as but not limited to less than or greater than 1 second. To lower flag 14, a user may press the “lower” button 94B for a specific time period such as but not limited to for less than or greater than 1 second. To move the flag 14 to half-staff 16, a user may press and hold the “half-staff” button 94C for a specific time period such as but not limited to less than or greater than 1 second or any other time interval. To calibrate system 10, the user may push one or more buttons 94, or a combination of one or more buttons 94 for a specific time period such as but not limited to greater than or less than 1 second. Other actions that system 10 may take may be activated by pressing one or more buttons 94 or user controls 94 on the user interface 92.

In other arrangements, for example the user interface 92 may include a graphical display 98 showing real-time flag 14 position, status of other components of system 10, diagnostic messages, or interactive menus for configuring operational parameters. In one or more arrangements for example, the graphical display 98 may include but is not limited to touchscreens, rotary encoders, capacitive buttons, voice command modules or other interface as input mechanisms, while status feedback may be provided via visual signals, audible tones, or haptic feedback.

The user interface 92 may also include security features, such as PIN-based access control, RFID authorization, or remote lockout functionality to prevent unauthorized operation. In networked versions, the user interface may sync with external devices to allow remote monitoring, logging, or command issuance via web interface or mobile application 134. The interface may be wired or wireless, and may be designed for rugged, waterproof, or industrial conditions where environmental durability is required. This configurable and accessible user interface enables intuitive interaction with system 10 while supporting safe, flexible, and efficient operation across a wide range of use cases. The user interface 92 may be any suitable size, shape, or design that facilitates monitoring or manually operating system 10.

Communication System 100:

With reference to the figures, system 10 may have a communication system 100. The communication system is formed of any suitable size, shape, or design and is configured to send commands to the flagpole lifting mechanism 18 commanding flag 14 be raised or lowered. Communication system 100 may include a controller module 102, a transceiver 104, a Cloud or Edge-Based System 106, an actuator interface 108, a remote control logic 110, a safety and redundancy system 112, an alert and notification system 138, a sensor interface 122, and a communications module 124.

In one or more arrangements for example, the communication system 100 is configured to interface with external calendar-based scheduling services, government half-staff flag order, and geofencing technologies to enable automated, context-aware flag movement. The controller module 102 includes logic for periodically querying, at predefined time intervals (e.g., every 30 seconds or configurable), one or more remote data sources to determine whether a lift or lower operation is scheduled or requested. Communication system 100 communicates with a cloud-based calendar service via secure API protocols, or may sync with one or more user's calendars, or internet calendars, enabling it to retrieve scheduled federal holidays or governmental orders where the flag 14 needs to be flown at half-staff 16. When the current time aligns with a scheduled calendar event, the controller module 102 initiates a system readiness check and, if conditions are met, automatically executes the operation. Furthermore, the communication system 100 may accept asynchronous command requests from third-party platforms such as inventory control systems, building automation networks, or logistics software. Communication systems 100 can transmit structured instructions, such as a request to lower the flag to half-staff 16 via authenticated API messages. The controller module 102 processes such requests, validates their authorization, and executes the operation accordingly. This combined use of scheduled events, location-based triggers, and third-party integrations allows the lifting system to function autonomously while maintaining strict safety and operational compliance.

In one or more arrangements, for example, communication system 100 may have integration capabilities with Internet of Things (IOT) platforms and popular voice-controlled virtual assistants, including but not limited to Google Assistant, Amazon Alexa, and Apple Siri. Through these integrations, the controller module 102 is configured to receive user commands, operational instructions, and system status queries via voice input or IoT device triggers. Communication system 100 may connect to these platforms through cloud-based APIs and standardized communication protocols, enabling seamless interoperability within smart buildings, industrial automation, or home automation environments. Users can issue voice commands to initiate raising or lowering the flag, adjust settings, or request status updates, enhancing hands-free control and accessibility. Communication system 100 may also participate in coordinated automation routines or scenes defined within IoT ecosystems, allowing it to operate in conjunction with other connected devices such as sensors, alarms, or environmental controls. These integrations facilitate enhanced user experience, remote accessibility, and intelligent automation while ensuring compliance with safety and authorization requirements.

Controller Module 102:

With reference to the figures, one or more arrangements, as shown, for example, the controller module 102 manages system 10, flagpole 12, lifting mechanism 18, actuator 66, user interface 92, or any other component, interprets commands (local or remote), and ensures safe and precise movement of the lifting mechanism 18. The controller module 102 comprises a processing unit 120 or microcontroller 120 programmed with control logic for executing lift and lower commands based on received input signals. The processing unit 120 is communicatively linked to motor or actuator interface 108, which regulates power and directional control to one or more lift actuators 66 or motors 44. The controller module 102 further includes a sensor interface 122 configured to receive real-time input from various sensors 78, including but not limited to position sensors 84, voltage sensors 86, time sensors 88, obstruction detection sensors 90 and any other sensors, such as but not limited to temperature or pressure sensors. A communication module 124, within the controller module 102 enables bi-directional data exchange, using transceiver 104 with a remote operator interface 92 or one or more components of the communication system 100 that are remote, and may support wireless protocols such as Wi-Fi, 5G, Bluetooth, or industrial communication standards such as CAN bus or Modbus. In one or more arrangements, for example, the controller module 102 includes safety and redundancy system 112 comprising embedded fault detection logic and emergency stop protocols, which override active commands in the event of overload conditions, system instability, or communication failure. Non-volatile memory 128 is also provided within the controller module 102 for storing firmware, lift commands, historical operational data, and scheduled task routines. In one or more arrangements, for example, the controller module 102 may also include a local user interface 92 or diagnostic display panel 98 for manual operation, system status indication 96, or maintenance access. In one or more arrangements, for example, the processing unit 120 or microcontroller 120 may include a central “board” 46 for signal management, power distribution, temperature control, and system monitoring. The microcontroller 120 may be an integrated PCB 46 (printed circuit board) with the necessary components. In other arrangements, for example the microcontroller 120 may be an Arduino-compatible board with WiFi capabilities (e.g., Arduino Uno R4 WiFi). Central board 46 may be located within the housing 38 of system 10. The housing 38 may be inside flagpole 12 or an adjacent housing that houses one or more components of system 10, such as the microcontroller 120, the one or more components of power source 70, the coupler 42 and any other components of system 10. The controller module 102 may report the current flag 14 position or current system voltage to cloud 130 through communication system 100. The controller module 102 may be configured to synchronize an internal time with time provided from a remote server or cloud 130. The controller module 130 may be configured to connect to the IoT Cloud such as the Arduino IoT Cloud. The controller module 102 may be any suitable size, shape, or design that facilitates monitoring or operating system 10.

Actuator Interface 108:

With reference to the figures, one or more arrangements, as shown, for example, system 10 includes actuator interface 108 that is formed of any suitable size, shape, and design and is configured to regulate and control the operation of one or more motors 44 or actuators 66. The actuator interface 108 comprises power control circuitry that interfaces directly with the actuator 66 components, including electric motors depending on the specific lift mechanism 18 configuration. The power control circuitry may include motor drivers, H-bridge circuits, a dual H-bridge motor driver, or variable frequency drives (VFDs) capable of modulating current, voltage, and frequency to the actuator 66. The actuator interface 108 is operatively connected to the microcontroller 120 of the controller module 102 and receives control signals, such as through the transceiver 104, based on operator input, automated routines, or sensor feedback. The actuator interface 108 may further include feedback lines to monitor actuator 66 status, such as current draw, actuator temperature, speed, or actuator position, enabling closed-loop control. In other arrangements, for example, the actuator interface 108 may incorporate protective elements such as overcurrent protection, thermal cutoffs, and short-circuit detection to prevent damage during abnormal operation. The actuator interface 108 may also be modular to support various actuator types and voltage levels, allowing adaptability for different lifting mechanisms 18. The actuator interface 108 may be any suitable size, shape, or design that facilitates monitoring or operating system 10.

Sensor Interface 122:

With reference to the figures, in one or more arrangements, as shown, for example, controller module 102 may include a sensor interface 122 formed of any suitable size, shape, and design, and is configured to receive and process data from a plurality of sensors 78 associated with system 10. The sensor interface 122 includes analog and digital signal processing circuits adapted to interface with various sensor types, including but not limited to position sensors 84, voltage sensors 86, time sensors 88, obstruction detection sensors 90 and other sensors including temperature sensors, and mechanical or electronic limit switches. The limit switches are operably positioned along flagpole 12 and are configured to detect predefined upper and lower travel limits of the lift mechanism 18. Upon actuation, the limit switches generate a signal that is transmitted to the controller to initiate a control response, such as halting further lift movement or triggering a safe stop condition. The sensor interface 122 may include signal conditioning components such as voltage dividers, filters, and isolation circuits to ensure accurate sensor readings and protection against noise or voltage spikes. In one or more arrangements, for example, the sensor interface 122 supports real-time polling or interrupt-based signal acquisition to ensure rapid response to critical changes in sensor states. The sensor interface 122 communicates directly with the microcontroller 120, enabling closed-loop feedback control and fault detection based on the sensor data. The sensor interface 122 may also store or timestamp sensor events, such as limit switch activations, for diagnostic or logging purposes. The sensor interface 122 may be any suitable size, shape, or design that facilitates monitoring or operating system 10.

Communications Module 124:

With reference to the figures, communication system 100 includes a communication module 124 that is formed of any suitable size, shape, and design, and is configured to manage both local and remote data exchange between the flagpole 12, local components of system 10 and external or remote components of system 10. Communication module 124 comprises hardware and software components that support a plurality of communication protocols, including wired interfaces including but not limited to Ethernet, RS-485, CAN bus, and wireless protocols including but not limited to Wi-Fi, Bluetooth, LTE, 5G). In one or more arrangements, for example, communication module 124 may respond to web-based notifications. Communication module 124 facilitates local communication with nearby devices 132 such as but not limited to operator control panels, safety interlocks, diagnostic tools, mobile applications 134, and embedded edge controllers. For remote communication, communication module 124 establishes secure, bidirectional connectivity with operator terminals, monitoring systems, mobile applications 134, or cloud-based platforms over public or private networks. In one or more arrangements, for example, the communication module 124 includes an Application Programming Interface (API) forwarding service that enables external software platforms to send and receive structured control commands, telemetry data, and system status updates through standardized protocols such as REST, MQTT, or WebSocket. This API forwarding service may include authentication, data validation, and rate-limiting functions to ensure secure and reliable access to the lift control system. In one or more arrangements, for example, the communication module 124 may be operably connected to a cloud 130 platform, where operational data is logged, analyzed, and used for real-time monitoring, predictive maintenance, user account management, or firmware updates. Communication module 124 may also support over-the-air (OTA) update capabilities, enabling authorized administrators to deploy software or configuration updates remotely without physical access to the lift apparatus. In some embodiments, communication module 124 may include encryption, redundancy, and failover mechanisms to maintain continuous and secure system connectivity under variable network conditions. In one or more arrangements, the user is able to trigger the “Raise”, “Lower”, “Half-Staff”, and “Calibrate” functions remotely via the cloud dashboard. The communication module 124 may be any suitable size, shape, or design that facilitates monitoring or operating system 10.

In one or more arrangements, for example, communication module 124 is further configured to interface with a mobile application 134 executed on a user device 132, such as a smartphone or tablet. This mobile application 134 provides a graphical user interface 98 (GUI) through which an operator can remotely monitor and control the lift mechanism 18. Communication between the controller module 102 and the mobile application 134 is established via wireless protocols, including but not limited to Wi-Fi, Bluetooth, or cellular networks (e.g., 4G, 5G), and may be secured using encryption protocols such as TLS. The mobile application 134 is configured to transmit user-initiated control commands-such as lift, lower, half-staff, pause, or emergency stop—to the controller module 102 in real time, and to receive feedback data including flag position, system status, system diagnostics, and sensor alerts. In one or more arrangements, for example, the mobile application 134 communicates with the controller module 102 directly over a local connection or indirectly through an internet-based API gateway. The mobile application 124 may also include user authentication features, access controls, and logging functionality to ensure secure and auditable interaction with the lift system. Additionally, the mobile application 134 may synchronize with cloud-based 130 services for data backup, performance analytics, remote notifications, and scheduled maintenance alerts, thereby extending the functional reach of the lifting system beyond the immediate vicinity of the equipment. The communication module 124 may be any suitable size, shape, or design that facilitates monitoring or operating system 10.

Safety and Redundancy System 112:

With reference to the figures, in one or more arrangements, for example, the controller module 102 or communication system 100 further comprises a safety and redundancy system 112 formed of any design and configured to monitor operational parameters and system conditions in real time, and to initiate corrective or protective actions in response to actual or anticipated fault conditions. The safety and redundancy system 112 is implemented in both hardware and software and is operatively connected to critical sensors 78, including but not limited to position sensors 84, voltage sensors 86, time sensors 88, obstruction detection sensors 90 and any other sensors and communication status indicators. In response to predefined fault thresholds, such as overload, excessive tilt, actuator malfunction, unauthorized access, or loss of communication, the safety and redundancy system 112 triggers automated responses, including halting actuator movement, engaging braking mechanisms, or activating an emergency stop sequence. The safety and redundancy system 112 may include a dedicated emergency stop input that can be manually activated by a remote or local operator via a physical switch or mobile application 134 interface, with immediate priority override over ongoing operations. In one or more arrangements, for example, the safety and redundancy system 112 includes fail-safe routines that place the lift into a secure state in the event of power failure, firmware error, or signal interruption. In certain embodiments, the safety subsystem continuously logs fault events and system responses, enabling diagnostic review and regulatory compliance. Redundancy mechanisms, such as dual-sensor validation or watchdog timers, may be employed to increase fault tolerance and prevent unsafe operations in high-risk environments. In one or more arrangements, for example, the actuator 66 will automatically shut down if it runs continuously for five minutes. This can happen if a limit switch fails to trigger. An error is logged to the cloud dashboard when this timeout occurs. The safety and redundancy system 112 may be any suitable size, shape, or design that facilitates monitoring or operating system 10

Memory 128 and Storage 136:

With reference to the figures, in one or more arrangements the communication system 100 and/or the controller module 102 includes one or more memories 128 and storages 136 formed of any design configured to support both operational functionality and system data management. Memory 128 may comprise a combination of volatile memory (e.g., RAM) for temporary data processing and non-volatile memory (e.g., flash storage, EEPROM, or solid-state drive) for long-term data retention. The non-volatile memory 128 is used to store firmware, lift control algorithms, configuration parameters, and user-defined profiles, including lift height presets, load thresholds, and system timeout settings. In one or more arrangements, for example, the storage 136 maintains logs of system activity, including sensor readings, user commands, fault conditions, maintenance events, and emergency responses. These logs may be timestamped and indexed for retrieval, diagnostic review, regulatory compliance, or integration with cloud-based analytics platforms. In arrangements, for example, supporting over-the-air (OTA) updates, memory 128 also includes a secure partition for staging and validating incoming firmware packages prior to deployment. The storage 136 may implement data redundancy, checksums, or error correction protocols to ensure the integrity and reliability of critical operational data. Furthermore, access to stored data may be controlled through encryption and role-based authentication mechanisms to prevent unauthorized modification or access. In one or more arrangements, for example, the stored data may include when the system 10 takes an action such as but not limited to raising or lowering the flag or calibrating the system, the event shall be logged. In one or more arrangements, for example, each log entry may include time, date, position of flag, status of system 10, action taken, and/or reason for the action, as well as any other information that may be logged. Memory 128 and storage 136 may be any suitable size, shape, or design that facilitates monitoring or operating system 10.

Remote Control Logic 110:

With reference to the figures, in one or more arrangements, for example, as shown, the controller module 102 or communication system 100 includes a remote control logic 110 formed of any design, shape, and size and is configured to receive, validate, interpret, and execute operational commands originating from a remote operator interface, such as a mobile application 134, web-based control panel, or centralized command system. The remote control logic 110 is implemented through a combination of firmware and embedded software algorithms that manage the secure transmission and parsing of command data via communication module 124. The remote control logic 110 continuously monitors the state of the system 10 and evaluates each received command against a set of safety, authorization, and operational readiness criteria prior to execution. The remote control logic 110 supports a wide range of functions, including initiation of lift or lower sequences, emergency stop activation, position presets, and status queries. In one or more arrangements, for example, the remote control logic 110 operates within a priority queue or real-time command buffer, ensuring deterministic behavior and safe concurrency management, particularly in multi-user. The remote control logic 110 may also include timeout routines, heartbeat monitoring, and command acknowledgment protocols to ensure that commands are acted upon within a safe operational window or otherwise disregarded to prevent improper flag handling. In one or more arrangements, for example, the remote control logic 110 may integrate with cloud-based APIs to allow scheduled, conditional, or automated command execution based on external triggers such as calendar events, sensor thresholds, predictive maintenance alerts or national, state, county, or city half-staff flag orders. Remote control logic 110 may be any suitable size, shape, or design that facilitates monitoring or operating system 10.

Cloud-based and/or Edge-based Computing System 106:

With reference to the figures, in one or more arrangements, for example, further comprises a cloud-based and/or edge-based computing system 106 formed of any design and configured to support extended data processing, remote monitoring, and system-wide management functions. The cloud or edge-based system 106 is communicatively linked to the controller module 102 via the communication module 124 and is configured to receive operational data including sensor telemetry, user commands, event logs, and system diagnostics in real time or at defined intervals. The cloud-based and/or edge-based computing system 106 includes a secure data storage platform for long-term archival of system logs, user interaction history, and maintenance records, and may provide web-based dashboards or APIs for access by authorized users. In one or more arrangements, for example, cloud-based and/or edge-based computing system 106 may incorporate data analytics engines capable of performing trend analysis, fault prediction, load usage profiling, and optimization recommendations using historical and real-time data streams. In one or more arrangements, for example, an edge computing layer may be deployed locally at or near the lift installation site to handle latency-sensitive tasks such as initial data filtering, alarm generation, and real-time decision-making, thereby reducing dependence on high-latency cloud communication. The cloud or edge-based computing system 106 may also support over-the-air (OTA) updates for controller firmware, configuration files, and machine learning models. Furthermore, cloud-based and/or edge-based computing system 106 may interface with external enterprise systems, such as calendar scheduling tools, asset management platforms, or IoT integration hubs, enabling automated workflows and system-wide coordination across distributed lifting units. Cloud-based and/or edge-based computing system 106 may be any suitable size, shape, or design that facilitates monitoring or operating system 10.

Alert and Notification System 138:

With reference to the figures, in one or more arrangements, for example, the communication system may include an alert and notification system 138 formed of any design and configured to provide real-time alerts and status notifications to operators, maintenance personnel, and other authorized users. Alert and notification system 138 monitors critical parameters such as load conditions, limit switch status, system faults, communication interruptions, and safety events, generating alerts upon detection of abnormal or predefined threshold conditions. Alert and notification system 138 also notify users when a lift operation has been successfully completed, such as when a load has been raised or lowered, as well as when a command or order to raise or lower a flag 14, has been received and is being executed. Notifications may be delivered through multiple channels including mobile applications, email, SMS, push notifications, and voice alerts via integrated voice assistant platforms. Alert and notification system 138 supports customizable notification rules and escalation protocols to ensure timely response and may include acknowledgment and logging features for audit trails. In one or more arrangements, for example, alert and notification system 138 can provide predictive maintenance alerts based on trend analysis of sensor data, enabling proactive servicing to reduce downtime. Integration with cloud-based management platforms allows centralized monitoring and coordination of alerts across multiple lift units within a facility or distributed locations. The alert and notification system thereby enhances operational safety, responsiveness, and overall system reliability. Alert and notification system 138 may be any suitable size, shape, or design that facilitates monitoring or operating system 10.

In Operation:

With reference to the figures, in one or more arrangements, for example, system 10 is powered off. First the user ensures that the flag 14 is not fully lowered. The user then connects power to flagpole 12. Flag 14 automatically raises to the top position 54 using the lift mechanism 18. The user interface 92 may have one or more status indicators 96, such as the “top” LED blink to indicate position. The status of flag 14 may be obtained from the cloud system 130 or mobile application 134 where the last known position of flag 14 was logged.

In one or more arrangements, for example, when flag 14 is at the bottom position 56, the user may press a button 94 or switch 94 to raise the flag 14. The user may continue to hold the button 94 until they observe the flag 14 moving up or until flag 14 is in the designated position. If the designated position is not the top 54, the user may press the lower button 94 once the flag 14 reaches the top position 54 until the flag reaches the designated position, such as half-staff 16. The user may be informed of the flag's 14 action using one or more status indicators 96.

In one or more arrangements, for example, system 10 is calibrated. When system 10 is being calibrated the flag 14 may be in any position or the flag may need to start in a specific position. The user commands system 10 to calibrate. A status indicator 96 may inform the user through an interface 92 or notification that the system 10 is calibrating. Flag 14 may move to the top position 54 and then the bottom position 56. This motion may repeat until system 10 is calibrated. After a certain number of cycles, a half-staff 16 time or new half-staff time, which may be 50% of the lowering time, is calculated or saved. The flag 14 then moves to a designated position.

For example, the user may be able to initiate a calibration sequence by pressing and holding both the “Raise” and “Lower” buttons simultaneously for three seconds. The calibration sequence may be comprised of raising the flag 14 to the top and lowering it too the bottom three consecutive times. The controller module 102 may measure the time it takes to lower the flag 14 during each cycle. The half-staff duration may be calculated as 50% of the average of the three measured lowering times. The calculated half-staff duration is saved to non-volatile memory. After a successful calibration, the flag 14 shall automatically move to the new half-staff position.

In one or more arrangements, for example, when calibration is completed and the flag 14 is at the bottom position 56. The user may want to raise the flag to half-staff; the user may command system 10 to raise the flag to half-staff by pressing and holding the “Half-Staff” button for over 1 second. Flag 14 first rises to the top 54. The flag then lowers for the pre-calibrated duration and stops. The “Half-Staff” LED blinks slowly.

In one or more arrangements, for example, when calibration is completed and the 14 flag is at the top position. The user may want to lower the flag 14 to half-staff 16. In one or more arrangements, the user commands system 10 to lower the flag 14 by pressing and holding the “Lower” button for over 1 second. Flag 14 first rises to the top 54. After reaching the top 54, flag 14 immediately begins to lower to the bottom 56. The “Bottom” LED blinks slowly.

In one or more arrangements the system is connected to cloud 130, such as the Arduino IoT Cloud. From the cloud dashboard, the user triggers one of the “Raise”, “Lower”, “Half-Staff”, and “Calibrate” functions. The user observes the flag 14 position and voltage variables in the dashboard. Each cloud command triggers the corresponding action on the device. The flag 14 position and voltage variables update in near real-time.

In one or more arrangements for example, the user may want to test system 10 to make sure system 10 is functioning appropriately. The user has completed calibration, and flag 14 is positioned at half-staff 16. The user disconnects and reconnects power. After flag 14 returns to the top 54, the user presses the “Half-Staff” button. System 10 should remember the calibration value. The flag should move correctly to the half-staff 16 position, demonstrating that the value was saved.

In one or more arrangements, the user may need to test the reraising of the flag 14. The controller module 102 is connected to cloud 130 and the flag is in the top position 54. From the cloud dashboard, the user may trigger the “Reraise” command. The user may initiate the test with flag 14 starting at the half-staff position 16. The user may repeat the test with flag 14 starting at the bottom position. When starting from the top 54 or half-staff 16, the flag 14 should raise completely then lower completely, then raise back to the top 54. When starting from the bottom 56, the flag 14 should not move.

In one or more arrangements for example, upon startup, the controller module 102 shall raise the flag 14 to the top position if not already at top 54 or bottom 56 positions. The controller module 102 may persist the half-staff calibration value across power cycles. If no calibration value is present, the half-staff feature shall be disabled. The user shall be able to raise the flag 14 by pressing and holding the “Raise” button 96 for more than 1 second. The user shall be able to lower the flag 14 by pressing and holding the “Lower” button for more than 1 second. The flag 14 shall automatically stop when it reaches the top limit switch (when raising). The flag 14 shall automatically stop when it reaches the bottom limit switch (when lowering). In some arrangements, the flag 14 must be raised to the top before it can be lowered. In other arrangements, flag 14 does not need to be raised to the top before it can be lowered. The flag 14 may be raised briskly and lowered slowly (e.g., at 50% speed) or any other pattern of speed.

In one or more arrangements, for example, the user shall be able to command the flag 14 to the half-staff position 16 by pressing and holding the “Half-Staff” button for more than 1 second. In one or more arrangements, to move to half-staff 16, the controller module 102 first raises the flag 14 to the top, then lowers it for a pre-calibrated duration. In one or more arrangement, if a “Lower” command is issued while flag 14 is at half-staff 16, the controller module 102 first raises the flag 14 to the top and then lowers it completely to the bottom.

It will be appreciated by those skilled in the art that other various modifications could be made to the device without parting from the spirit and scope of this disclosure. All such modifications and changes fall within the scope of the claims and are intended to be covered thereby.

From the above discussion it will be appreciated that the automated flagpole system and related method of use, presented herein improves upon the state of the art.

Specifically, the automated flag pole system presented: provides improved functionality over prior art systems; provides improved features over prior art systems; is relatively inexpensive; is easy to use; is intuitive to use; is strong and robust; provides unique functionality; is fast to use and fast to set-up; is safe to use; saves time; has a compact size; is adjustable, has a long useful life; is high quality; and/or improves efficiencies, among countless other advantages and improvements.

SELECT REFERENCE NUMBERS

• • 10-Automated Flagpole System
  • 12-Flagpole
  • 14-Flag
  • 16-Half-staff
  • 18-Lifting Mechanism
  • 20-Shaft
  • 22-Securing System
  • 24-Pulley
  • 26-Trunk
  • 28-Winch
  • 30-Flag Securing Members
  • 32-Ground Sleeve
  • 34-Mounting Height
  • 36-Top of Flagpole
  • 38-Housing
  • 40-Tensioner
  • 42-Coupler
  • 46-Central Board
  • 48-Ground
  • 50-External Side of Flagpole
  • 52-Internal Side of Flagpole
  • 54-Top Flag Position
  • 56-Bottom Flag Position
  • 58-Cleat
  • 60-Door to Housing
  • 62-External Side of Housing
  • 64-Internal Side of Housing
  • 66-Actuator
  • 70-Power Source
  • 72-Solar Panel
  • 74-Battery
  • 78-Sensors
  • 84-Position Sensors
  • 86-Voltage Sensors
  • 88-Time Sensors
  • 90-Obstruction Detection Sensors
  • 92-User Interface
  • 94-Input Controls
  • 96-Status Indicators
  • 98-Graphical Display
  • 100-Communication System
  • 102-Controller Module
  • 104-Transceiver
  • 106-Cloud-based and/or Edge-based Computing System
  • 108-Actuator Interface
  • 110-Remote Control Logic
  • 112-Safety and Redundancy System
  • 120-Processing Unit/Microcontroller
  • 122-Sensor Interface
  • 124-Communication Module
  • 128-Memory
  • 130-Cloud
  • 132-Devices
  • 134-Mobile Application
  • 136-Storage
  • 138-Alert and Notification System