DUET2 Wifi LED control



  • Hello Duett fans,
    I updated my duett 2 Wifi to new RepRap Release 3.2-RC1
    To control a 24V LED bar, i used in old firmware (1.2.1) this code in config.g:
    ; LEDs
    M307 H2 A-1 C-1 D-1 ; disable the heater functionality
    M42 P2 S255 ; control P2 with PWM values

    to control my LED Light.
    Since i updated to new Reprap 3.x ,i changed the code to:
    M950 P2 C"exp.heater2" Q500 ; allocate GPIO port 2 to heater2 on expansion connector, 500Hz
    M42 P2 S255 ; control P2 with PWM values
    but it did not work....
    Have you any ideas what i did wrong?
    What do i need to do?
    Thank you for your help. 🙂



  • Where are your leds connected? Looks like E1 heater or?


  • Moderator

    Can you provide the results of M122 and M98 P"config.g"?



  • Sorry my Printer is closed and i need to check ... but this needs a lot of work.
    All i can say now is that:


    M307 H2 A-1 C-1 D-1 ; disable the heater functionality
    M42 P2 S255 ; control P2 with PWM values


    worked well ... so it should be the "H2"



  • @Phaedrux

    M122
    === Diagnostics ===
    RepRapFirmware for Duet 2 WiFi/Ethernet version 3.0 running on Duet WiFi 1.02 or later
    Board ID: 08DGM-956GU-DGMSN-6JKF2-3SD6T-TVRVG
    Used output buffers: 3 of 24 (12 max)
    === RTOS ===
    Static ram: 30516
    Dynamic ram: 91888 of which 12 recycled
    Exception stack ram used: 568
    Never used ram: 8088
    Tasks: NETWORK(ready,640) HEAT(blocked,1240) MAIN(running,3700) IDLE(ready,156)
    Owned mutexes:
    === Platform ===
    Last reset 00:05:46 ago, cause: power up
    Last software reset time unknown, reason: User, spinning module GCodes, available RAM 7592 bytes (slot 2)
    Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
    Error status: 0
    Free file entries: 10
    SD card 0 detected, interface speed: 20.0MBytes/sec
    SD card longest block write time: 2.1ms, max retries 0
    MCU temperature: min 35.4, current 37.2, max 37.8
    Supply voltage: min 1.5, current 24.1, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes
    Driver 0: standstill, SG min/max 0/325
    Driver 1: standstill, SG min/max 0/291
    Driver 2: standstill, SG min/max 0/1023
    Driver 3: standstill, SG min/max not available
    Driver 4: standstill, SG min/max not available
    Date/time: 2020-12-21 20:59:31
    Cache data hit count 913639565
    Slowest loop: 62.65ms; fastest: 0.07ms
    I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
    === Move ===
    Hiccups: 874360(0), FreeDm: 169, MinFreeDm: 166, MaxWait: 24318ms
    Bed compensation in use: mesh, comp offset 0.000
    === MainDDARing ===
    Scheduled moves: 58, completed moves: 58, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
    === AuxDDARing ===
    Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
    === Heat ===
    Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
    === GCodes ===
    Segments left: 0
    Stack records: 2 allocated, 0 in use
    Movement lock held by null
    http is idle in state(s) 0
    telnet is idle in state(s) 0
    file is idle in state(s) 0
    serial is idle in state(s) 0
    aux is idle in state(s) 0
    daemon is idle in state(s) 0
    queue is idle in state(s) 0
    autopause is idle in state(s) 0
    Code queue is empty.
    === Network ===
    Slowest loop: 85.66ms; fastest: 0.00ms
    Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
    HTTP sessions: 1 of 8

    • WiFi -
      Network state is running
      WiFi module is connected to access point
      Failed messages: pending 0, notready 0, noresp 0
      WiFi firmware version 1.23
      WiFi MAC address 84:0d:8e:b2:78:c7
      WiFi Vcc 3.36, reset reason Turned on by main processor
      WiFi flash size 4194304, free heap 24664
      WiFi IP address 192.168.178.36
      WiFi signal strength -57dBm, reconnections 0, sleep mode modem
      Socket states: 0 0 0 0 0 0 0 0


  • @Phaedrux said in DUET2 Wifi LED control:

    M98 P"config.g"
    98 P"config.g"
    HTTP is enabled on port 80
    FTP is disabled
    TELNET is disabled
    Warning: M307: heater 0 appears to be over-powered. If left on at full power, its temperature is predicted to reach 365C.

    Error: M950: Unknown pin name 'exp.heater2'
    Warning: M307: heater 0 appears to be over-powered. If left on at full power, its temperature is predicted to reach 365C.

    Warning: M307: heater 1 appears to be over-powered. If left on at full power, its temperature is predicted to reach 435C


  • Moderator

    @Frank-Liewald said in DUET2 Wifi LED control:

    C"exp.heater2"

    There is no exp.heater2

    See here for the available pin names.
    https://duet3d.dozuki.com/Wiki/RepRapFirmware_3_overview#Section_Pin_names_for_Duet_2_WiFi_Ethernet

    One of these names may work assuming that's the pin you're actually connected to.

    exp.heater3, exp.8, !duex.e2heat, !duex.pwm1



  • @Phaedrux said in DUET2 Wifi LED control:

    exp.heater3, exp.8, !duex.e2heat, !duex.pwm1

    M98 P"config.g"
    HTTP is enabled on port 80
    FTP is disabled
    TELNET is disabled
    Warning: M307: heater 0 appears to be over-powered. If left on at full power, its temperature is predicted to reach 365C.

    Error: M950: exactly one of FHPS must be given
    Warning: M307: heater 0 appears to be over-powered. If left on at full power, its temperature is predicted to reach 365C.

    Warning: M307: heater 1 appears to be over-powered. If left on at full power, its temperature is predicted to reach 435C.



  • Thanks, i figured out, that the pin was "e1heat "....

    So..
    M950 P2 C"e1heat"
    M42 P2 S1 ; control P2 with PWM values

    works 🙂


Log in to reply