Programmatic control of LG-07 progressive automation modular lifting column for rail / arm combo

[sgbaird]

Several options for programmatic control (see also the usage in parent issue videos)

[sgbaird]

1. FLTCON → Home automation (pinouts, K1–K4, wiring examples)

   • FLTCON Control Box to Home Automation Compatibility (Progressive Automations blog)
   • Same article mirrored as an Instructable (has the pinout photos)

2. Control box products + manuals (Hall effect, duty cycle, reset behavior)

   • FLTCON-2 Hall Effect Control Box (includes user manual link)
   • FLTCON-1 Hall Effect Control Box
   • FLTCON-2 datasheet PDF (reset, errors, memory, duty cycle)
   • Applications for FLTCON-2 & FLTCON-4 (conceptual overview)

3. Remotes and wireless options (RT-11, RT-BT1, Progressive Motion app)

   • RT-11 Hand Remote (Progressive Automations)
   • RT-11 Hand Remote (Progressive Desk)
   • RT-BT1 Bluetooth Dongle (product page)
   • RT-BT1 Bluetooth Dongle + Progressive Motion app overview
   • Progressive Motion app (App Store – requires RT-BT1)

4. General resources hub (for PDFs, 3D models, manuals)

   • Progressive Automations resources page (datasheets, 3D files, diagrams)

[Daniel0813]

https://youtube.com/shorts/5tUAfDhCdks?si=KUqTg0A5H0qw6H03

Video of testing out the short circuiting to move the lift, voltages were about 3.3 volts.

[Daniel0813]

https://youtu.be/7kGC231InBI?feature=shared

[sgbaird]

@Daniel0813 uploaded a video above showing the latest test, but to recap, we got some basic programmatic control working. While using an optocoupler or relay would probably be ideal to avoid damaging electronics on the Pi (I guess?), I followed this transcript in a workaround where we never set the GPIO pin to high, instead using GPIO.PUD_OFF and GPIO.LOW in BCM mode. Noting that the "UP" and "DOWN" pins seem to have been reversed compared to the datasheet we found.

Copying that script below, also committed to https://github.com/AccelerationConsortium/progressive-automations-python/blob/main/scripts/test_up.py:

# test_up.py
import time
import RPi.GPIO as GPIO

UP_PIN = 17  # BCM numbering, physical pin 11

GPIO.setmode(GPIO.BCM)

def release_up():
    # High-impedance: "button not pressed"
    GPIO.setup(UP_PIN, GPIO.IN, pull_up_down=GPIO.PUD_OFF)

def press_up():
    # Drive low: "button pressed"
    GPIO.setup(UP_PIN, GPIO.OUT, initial=GPIO.LOW)

try:
    # Make sure we're released at start
    release_up()
    print("Ready. Desk should NOT move yet.")
    
    input("Press Enter to move UP for 2 seconds...")

    print("Moving UP...")
    press_up()
    time.sleep(2.0)   # adjust if you want a shorter/longer test
    release_up()
    print("Released UP. Test finished.")

finally:
    # Ensure we leave the line released
    release_up()
    GPIO.cleanup()

Pinout per https://chatgpt.com/share/69168c09-25e4-8007-8020-1e1174defa74:

---

Here’s the pinout in one place, with your actual wire colors and the Pi 5 mapping.

RJ-45 (FLT control box) → Ethernet cable colors (T568B)

• Pin 1 – white/orange
• Pin 2 – orange
• Pin 3 – white/green → GND
• Pin 4 – blue
• Pin 5 – white/blue
• Pin 6 – green
• Pin 7 – white/brown → UP (empirically)
• Pin 8 – brown → DOWN (empirically)

RJ-45 → Raspberry Pi 5 header

Use 1 kΩ series resistors on the two signal lines.

Function	RJ45 pin	Cable color	Series resistor	Pi 5 header pin (physical)	Pi signal (BCM)
GND	3	white/green	none	6	GND
UP	7	white/brown	1 kΩ	11	GPIO17
DOWN	8	brown	1 kΩ	13	GPIO27

Software convention

• Use BCM numbering in GPIO libraries:

  • UP_PIN = 17
  • DOWN_PIN = 27

• Behavior:

  • “Released” → configure pin as input, no pull (high-Z).
  • “Pressed” → configure pin as output, LOW.
  • Never drive these pins HIGH.

---

Will probably move these issues over to https://github.com/AccelerationConsortium/progressive-automations-python

[sgbaird]

Immediate next steps:

• connect the other pin
• test out a workflow that homes each time and then moves to a desired position

Important, less urgent:

• creating a class
• decorating class methods with Prefect
• publish to PyPI
• update docs
• better wiring
• careful control to stay within duty cycle limits (i.e., not holding it for more than ~15 seconds at a time)

Maybe worth trying, not urgent:

• position feedback (could be a long journey, maybe best to reach out to progressive automations first)

[sgbaird]

Electronics looking slightly better (thanks Amazon)

PXL_20251114_235535304.mp4

[sgbaird]

From Kelvin:

this should be enough information to figure out feedback

Looked into it a bit; in case we explore more - https://chatgpt.com/share/6917d2e8-0814-8007-83bb-8010361e7530. Seems that an optocoupler (or preferably, a logic-level shifter, which I don't remember if we have on hand or not) is necessary.

[Daniel0813]

FLTCON-1 Error Codes

https://f.hubspotusercontent40.net/hubfs/7717445/PDFs/Control%20Systems/FLTCON-1%20datasheet.pdf?utm_source=chatgpt.com

E01: Overcurrent Protection
Triggered when the actuator draws too much current (overload, mechanical obstruction, jammed column, or wiring fault).
Fix: Reduce load, ensure nothing is blocking travel, reseat the actuator cable, then run the reset procedure.
Avoid: Keep load within spec, avoid side-loading the column, and check alignment before long movements.

E07: Hall Sensor Error
Controller isn’t receiving valid position feedback (loose connector, damaged sensor wire).
Fix: Inspect/secure the actuator cable at both ends, power-cycle, then reset.
Avoid: Prevent cable strain, make sure the column connector clicks fully into the FLTCON.

H01: Overheat / Duty-Cycle Protection
Motor/controller overheated due to exceeding the duty cycle (≈2 minutes total motion per 20-minute window).
Fix: Let the system rest 15–20 minutes to cool down.
Avoid: Break large movements into shorter segments, avoid back-to-back adjustments, reduce load, and ensure good airflow around the control box.

Other indicators

RST: Run full reset (hold DOWN until column bottoms out + rebounds slightly).

HOT: Same as H01; allow cooling.

General best practices

• Keep load well below the column’s max rating.
• Ensure travel path is clear.
• Avoid rapid repeated micro-adjustments.
• Check all cables are fully seated and undamaged.
• Keep the FLTCON ventilated / unobstructed.

[sgbaird]

Prefect integration: https://youtu.be/RfYhE3h7Pug?si=9E7GM6TevBEeSHJA

[sgbaird]

A semi-final electrical setup. Changing so that down is gpio 17 and up is gpio 18, to make it a bit easier to make the electrical connections, though it adds some confusion if we don't correct this consistently.

PXL_20251118_182758391.mp4