NeoPixel with 272/273 on Pico 2 W Bright White

[b-blake]

Hello,
Versions prior to 272 drive the NeoPixel properly.
Starting with 272/273 the NeoPixel goes to bright white with very minor flicker.
Going back to 267 all is good again.
Bad = RPI_PICO2_W-20250208-v1.25.0-preview.273.gb2ce9b6fb.uf2
Bruce

[scruss]

Sorry, can't confirm with v1.25.0-preview-273/272/270*/172. One NeoPixel on GPIO 0 and this code:

from machine import Pin
from neopixel import NeoPixel
from time import sleep

pin = Pin(0, Pin.OUT)  # set GPIO0 to output to drive NeoPixels
np = NeoPixel(pin, 1)

while True:
    np[0] = (64, 0, 0)
    np.write()
    sleep(1)
    np[0] = (0, 64, 0)
    np.write()
    sleep(1)
    np[0] = (0, 0, 64)
    np.write()
    sleep(1)

cycles between red, green and blue as expected.

What is your code doing?

*: NB - the RPI_PICO2_W-20250207-v1.25.0-preview.267.ge44a2c692.uf2 image (sha1sum 911536199e599b7dcf66fb5775c7e43f220edaf9) is preview-270. This is its boot banner:

MicroPython v1.25.0-preview.270.gd76733d05 on 2025-02-07; Raspberry Pi Pico 2 W with RP2350

[b-blake]

Hello, Your test code works with build 283. I had to move the GPIO to pin 28 to work with the *Maker Pi Pico V1.2*. I have my RPi Pico 2 W plugged into a Maker Pi Pico board. The NeoPixel is on GPIO28 I also have a DS3231 on I2C #1 (not #0) Pins 6 & 7. Should detect missing DS3231 and adapt for it. I tried *RPI_PICO2_W-20250210-v1.25.0-preview.283.g11c9656fa.uf2* with the same result. Max white on the NeoPixel My main.py is attached. 270 does not exist for the 2 W Bruce

…

On Sun, Feb 9, 2025 at 3:08 PM Stewart Russell ***@***.***> wrote: Sorry, can't confirm with v1.25.0-preview-273/272/270*/172. One NeoPixel on GPIO 0 and this code: from machine import Pinfrom neopixel import NeoPixelfrom time import sleep pin = Pin(0, Pin.OUT) # set GPIO0 to output to drive NeoPixelsnp = NeoPixel(pin, 1) while True: np[0] = (64, 0, 0) np.write() sleep(1) np[0] = (0, 64, 0) np.write() sleep(1) np[0] = (0, 0, 64) np.write() sleep(1) cycles between red, green and blue as expected. What is your code doing? *: *NB* - the RPI_PICO2_W-20250207-v1.25.0-preview.267.ge44a2c692.uf2 image (sha1sum 911536199e599b7dcf66fb5775c7e43f220edaf9) is preview-270. This is its boot banner: MicroPython v1.25.0-preview.270.gd76733d05 on 2025-02-07; Raspberry Pi Pico 2 W with RP2350 — Reply to this email directly, view it on GitHub <#16723 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AWCPQOKJ5ZQDUSX3EBH2BQL2O6YSTAVCNFSM6AAAAABWX6HUTWVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEMJRGA4DOMY> . You are receiving this because you authored the thread.Message ID: ***@***.*** com>

[scruss]

I'm confused: you said my code both did and didn't work with preview.283?. I still can't replicate on a Pico 2 W

As regards 270, I was pointing out that the UF2 marked for download as "preview.267" has an actual build ID of preview.270

[b-blake]

Your test code works fine under build 238 using GPIO 28. I had to change the GPIO port, but your code still works.

The code I attached previously does not work under build 238 using GPIO 28. The NeoPixel on the Maker Pi Pico is hard wired.

[b-blake]

###################################
##      picow_ntp_client.py      ##
###################################
# Raspberry Pi Pico W with RP2040

import gc
import os
import sys
import time
import machine
import network
import ntptime
import neopixel
import ubinascii

#import socket
#import struct
#import urequests

led = machine.Pin('LED', machine.Pin.OUT, value=True)

# Source: Electrocredible.com, Language: MicroPython.
# Default A UART(0, baudrate=115200, bits=8, parity=None, stop=1, tx=0, rx=1, txbuf=256, rxbuf=256, timeout=0, timeout_char=1, invert=None)
# Default B UART(1, baudrate=115200, bits=8, parity=None, stop=1, tx=4, rx=5, txbuf=256, rxbuf=256, timeout=0, timeout_char=1, invert=None)

print('Start')
# https://github.com/pangopi/micropython-DS3231-AT24C32
try:
    import ds3231
    i2c_ID = 1           # I/O Port
    SDA = machine.Pin(6) # Serial Data  # ID0 0,1, 4,5,  8, 9, 12,13, 16,17, 20,21
    SCL = machine.Pin(7) # Serial Clock # ID1 2,3, 6,7, 10,11, 14,15, 18,19,        26,27
    ds_i2c = machine.I2C(id=i2c_ID, sda=SDA, scl=SCL)
    DS_3231 = ds3231.DS3231(ds_i2c)
    print('DS3231.datetime is:', DS_3231.datetime())
    rtc = machine.RTC()
    Maker_Pi = True
except:
    Maker_Pi = False
else:
    pass # code block
finally:
    pass # code block
print('Is DS3231 Active? ', Maker_Pi)
    
if Maker_Pi:
    # https://docs.micropython.org/en/latest/esp8266/tutorial/neopixel.html
    np = neopixel.NeoPixel(machine.Pin(28), 1)
    np[0] = (64, 0, 0) # red Green Blue
    led.toggle()
    np.write()
    time.sleep(0.5)
    led.toggle()
    np[0] = (0, 64, 0)
    np.write()
    led.toggle()
    time.sleep(0.5)
    np[0] = (0, 0, 64)
    led.toggle()
    np.write()
    time.sleep(0.5)
    np[0] = (0, 32, 0)
    led.toggle()
    np.write()
    time.sleep(0.5)
# Seeed Studio Precision RTC Module for Raspberry Pi Pico, 6, 7
# https://gr.mouser.com/new/seeed-studio/seeed-precision-rtc-module-raspberry-pi-pico/

# 2**0=1, 2**1=2, 2=4, 3=8, 4=16, 5=32, 6=64, 7=128, 8=256, 9=512, 10=1024, 11=2048, 12=4096, 13=8192, 14=16384
#           9,600 813 *
# 0       115,200 67  *
# 1       230,400 33
# 2       460,800 16
# 3       921,600  8  *
# 4     1,843,200  4
# 5     3,686,400  2
# 6     7,372,800  1  *
# 7    14,745,600  1
# 8    29,491,200  1
# 9    58,982,400  1
#10   117,964,800  1
#11   235,929,600  1
#12   471,859,200  1
#13   943,718,400  1
#14 1,887,436,800  1
BitRate  = int(115200*(2**6))
DataBits = 8
Parity   = None
StopBits = 1
Buffer   = 256
TimeOut  = 0
TO_Char  = 2
Invert   = False
OneTenth = 0.1

uarta = 0
txA   = machine.Pin(0) # PCB 1
rxA   = machine.Pin(1) # PCB 2
ctsA  = machine.Pin(2) # PCB 4
rtsA  = machine.Pin(3) # PCB 5
uartA = machine.UART(uarta, tx=txA, rx=rxA)
uartA.init(rts=rtsA, cts=ctsA)
uartA.init(baudrate=BitRate, bits=DataBits, parity=Parity, stop=StopBits)
uartA.init(txbuf=Buffer, rxbuf=Buffer, timeout=TimeOut, timeout_char=TO_Char, invert=Invert)
print('A', uartA)
time.sleep(0.125)

uartb = 1
txB   = machine.Pin(8)  # PCB 11
rxB   = machine.Pin(9)  # PCB 12
ctsB  = machine.Pin(10) # PCB 14
rtsB  = machine.Pin(11) # PCB 15
uartB = machine.UART(uartb, tx=txB, rx=rxB)
uartB.init(rts=rtsB, cts=ctsB)
uartB.init(baudrate=BitRate, bits=DataBits, parity=Parity, stop=StopBits)
uartB.init(txbuf=Buffer, rxbuf=Buffer, timeout=TimeOut, timeout_char=TO_Char, invert=Invert)
print('B', uartB)
time.sleep(0.125)
print('')

fudge = 32
Diag  = False
count = 1
# Send a character or text line
def UART_TX(ab, data_tx_ab):
    if ab == 'a': uartA.write(data_tx_ab)
    if ab == 'b': uartB.write(data_tx_ab)
    if Diag: print(d , len(data_tx_ab))
    delay = ((fudge / BitRate) * (len(data_tx_ab) * 1.25)) # 1 Start Bit, 8 Data Bits, 1 Stop Bit = 10 
    time.sleep(delay) # bitrate
    led.toggle()
    pass
# Receive a character or text line
def UART_RX(ab):
    if ab=='a': _ = uartA.any()
    if ab=='b': _ = uartB.any()
    if  Diag:
        if ab=='a': print(uartA, _, count)
        if ab=='b': print(uartB, _, count)
    if _:
        try:
            if ab == 'a':
                data_rx_ab = uartA.read(_).decode('utf-8')
                if Diag: print('data A read! = ', end='')
            if ab == 'b':
                data_rx_ab = uartB.read(_).decode('utf-8')
                if Diag: print('data B read! = ', end='')
            if Diag: print(data_rx_ab)
        except:
            return 'Rx Failure'
    led.toggle()
    return(data_rx_ab)
    pass
Diag = False
if  True:
    for count in range(1, 36, 1):
        # Send character(s) from a to b
        data_tx_a = (chr(48 + count) * count) + (chr(64 + count) * count)
        UART_TX('a', data_tx_a)
        # Receive character(s) from a
        data_rx_b = UART_RX('b')
        # Echo character(s) from b to a
        UART_TX('b', data_rx_b)
        # Receive character(s) from b
        data_rx_a = UART_RX('a')
Diag = False
print('UART0_BASE + UARTIBRD', machine.mem32[0x40034024])  # UART0_BASE + UARTIBRD # Find UART setting
print('UART1_BASE + UARTIBRD', machine.mem32[0x40038024])  # UART1_BASE + UARTIBRD # Find UART setting
#print('Pause')
#while True: pass
txpwr      = int(63/(2**1)) # 0=63mw, 1=31mw, 2=15mw, 3=7mw, 4=3mw, 5=1mw, 6=0.5mw, 7=0.25mw
flag       = None
wifi_reset = False
DST        = False # Daylight Saving Time
SecPerHr   = 60 * 60 # Offset for DST in seconds (Second Sunday in Mar to First Sunday in Nov)

print("\t"+"#"*21)
print("\t##  Program Start  ##")
print("\t"+"#"*21)
for x in range(3, -1, -1): print("\t\t ", x, end='\r')
print("\t##   Run Program   ##")
print("\t"+"#"*21)
try:
  from secrets import secrets
except ImportError:
  print("All your secret keys are kept in secrets.py,\n\tplease add them there!")
  raise

host  = secrets['ntp_server'] #'pool.ntp.org'
#host2 = 'https://nghttp2.org/httpbin/anything'
print("\t##    NTP Clock    ##")
print("\t" + "#"*21)
time.sleep(OneTenth)

UTC  =   0 # Universal Coordinated Time, UTC, No Daylight Saving Time
EST  =  -5 # Eastern  Standard Time, EDT -4
CST  =  -6 # Central  Standard Time, CDT -5
MST  =  -7 # Mountain Standard Time, MDT -6
PST  =  -8 # Pacific  Standard Time, PDT -7
AKST =  -9 # Alaska   Standard Time, ADT -8
HST  = -10 # Hawaii   Standard Time, No Daylight Saving Time

Zone = 'EST'
if   Zone == 'UTC':  LocalZone = UTC
elif Zone == 'EST':  LocalZone = EST
elif Zone == 'CST':  LocalZone = CST
elif Zone == 'MST':  LocalZone = MST
elif Zone == 'PST':  LocalZone = PST
elif Zone == 'AKST': LocalZone = AKST
elif Zone == 'HST':  LocalZone = HST

led.on()
#################################### Start of Defined Functions
def set_local():
  global UTC, DST, Zone, TimeZone, USA_Time_Zones, tm_zoneoff, SecPerHr
  USA_Time_Zones = ['UTC', 'EDT', 'CDT', 'MDT', 'PDT', 'AKDT', 'HST'] if DST else ['UTC', 'EST', 'CST', 'MST', 'PST', 'AKST', 'HST']
  TimeZone       = ['Zulu', 'Eastern', 'Central', 'Mountain', 'Pacific', 'Alaska', 'Hawaii']
  time.sleep(OneTenth)
  tm_zoneoff  = -((LocalZone + (int(DST))) * SecPerHr) # Time Zone Offset in seconds
  if(TimeZone == ' Zulu'): tm_zoneoff = 0
  DELTA       = (((1970-1900)*365)+(int((1970-1900)/4)))*24*SecPerHr # 2208986640 Seconds 1/1/1900 to 1/1/1970 ???
  NTP_DELTA   = DELTA + tm_zoneoff # 2208988800 Seconds 1970-1900 + Time_Zone_offset
  if((LocalZone == HST) or (LocalZone == UTC)): DST = False 
  Zone        = '  UTC ' if LocalZone == UTC else 'Local'
####################################
def set_time(flag=False):
  try:
    flag_ = ntptime.settime()
    _ = time.localtime()
    #print(' ~ Set to:', _)
    set_ds3231(_)
    time.localtime(int(time.time()-(5 * SecPerHr)))
    flag = True if (flag_ == None) else False
  except Exception as exception:
    print(' ^^^ Exception:', str(exception), end="\r")
    flag = False
  time.sleep(OneTenth)
  return(flag)
####################################
def SET_TIME(flag):
  flag = False
  _ = 0
  while not flag:
    try:
      _ += 1
      print(" Setting Time using NTP via:", wifi.config('ssid'), _, end='') # aka essid
      time.sleep(OneTenth)
      flag = set_time(flag)
      if flag: print(" >>> Time was set to:\a", time.localtime(), 'UTC', time.mktime(time.localtime()))
      time.sleep(OneTenth)
    except OSError as exc:
      print("set_time error:", exc, end="\r") # [Errno 110] ETIMEDOUT
      time.sleep(OneTenth)
  return(flag)  
####################################
def set_ds3231(datetime):
#    dstetime = DS_3231.datetime()
    if Maker_Pi: DS_3231.datetime(datetime)
    return
####################################
def CPU_temp():
  conversion_factor = 3.3 / (2**16 - 1)
  if  True:
     return(27-( (((machine.ADC(4)).read_u16() * conversion_factor) - 0.706) / 0.001721) )
  else:
    sensor_temp = machine.ADC(4)
    reading     = sensor_temp.read_u16() * conversion_factor 
    tempC       = 27 - ((reading - 0.706) / 0.001721) # * 581.0575247)
    return(tempC)
####################################
def ordinal(n: int):
    if 11 <= (n % 100) <= 13: # or 4 <= 20
        suffix = 'th'
    else:
        suffix = ['th', 'st', 'nd', 'rd', 'th'][min(n % 10, 4)]
    return suffix # str(n) + suffix
#ordinal = lambda n: "%d%s" % (n,"tsnrhtdd"[(n//10%10!=1)*(n%10<4)*n%10::4])
####################################
def bbbordinal(___day):
  if ___day > 0:
    __day  = ___day%100 # 0 to 99
    if(10 <= __day <= 20): # 10 to 20
      ordinal = 'th'
      return(ordinal)
    _day = __day%10  # 0 to 9
    if   (4 <= _day <= 10): ordinal = 'th' # 4th to 20th
    elif (_day == 1): ordinal = 'st'
    elif (_day == 2): ordinal = 'nd'
    elif (_day == 3): ordinal = 'rd'
    else: ordinal = 'th' # n4 to n9 e.g. 54th
  else:
    ordinal = 'NA'
  return(ordinal)
####################################
def scan_wifi():
  y = 0
  print("\t      Available  CYW43439KUBG   WiFi  networks:")
  print('No.\tSSID\t\t MAC Address\tChan  Pwr  sec  hid')
  # 0=SSID, 1=MAC, 2=Chan, 3=Power, 4=???, 5=???
  # (ssid, bssid, channel, RSSI, security, hidden)
  # security: 0 – open, 1 – WEP, 2 – WPA-PSK, 3 – WPA2-PSK, 4 – WPA/WPA2-PSK, 5, 6, 7
  # hidden:   0 – visible, 1 – hidden, 2, 3
  for net in sorted(wifi.scan(), key=lambda x: x[3], reverse=True):#radio.start_scanning_networks():
    s = "."*(18-len(str(net[0], "utf-8")))
    t = ''
    y += 1
    if (len(s) == 0):
      t = "...Hidden.SSID...."
      #print("%2d %s" % (y, t))
      print("%2d %s%s %s %3d   %3d %3d  %3d" % (y, t, s,
        ubinascii.hexlify(net[1],':').decode(), net[2], net[3], net[4], net[5]))
    else:
      print("%2d %s%s %s %3d   %3d %3d  %3d" % (y, str(net[0], "utf-8"), s,
        ubinascii.hexlify(net[1],':').decode(), net[2], net[3], net[4], net[5]))
  print('#'*60)
  time.sleep(1)
####################################
def power_management():
  # CYW43439
  # m  Low  4 bits, 1 slice : 0: Disabled, 1: Aggressive savings low throughput, 2: Power savings with high throughput
  # rr Next 8 bits, 2 slices: Awake time before next sleep in units of 10ms
  # b  Next 4 bits, 1 slice : Wake Period in beacon periods
  # d  Next 4 bits, 1 slice : Wake interval in DTIMs
  # a  Next 4 bits, 1 slice : Wake interval sent to access point
  #                        adbrrm
  MP_PM_NONE           = 0x000010 # MicroPython
  MP_PM_POWERSAVE      = 0x000011 # MicroPython
  MP_PM_PERFORMANCE    = 0xA11142 # MicroPython
  #
  CYW43_NONE_PM        = 0xA11140
  CYW43_DEFAULT_PM     = 0xA11142
  CYW43_AGGRESSIVE_PM  = 0xA11C82
  CYW43_PERFORMANCE_PM = 0x111022
  # The difference between the default 0xA11142 and not low power 0xA11140 is that it changed from
  # "Powersave mode on specified interface with High throughput" to "No Powersave mode". All other parameters stayed the same.
  PM_DISABLED          = 0xa11140 # No Power Management
  PM_STANDARD          = 0xa11142 # Balanced Power Management
  PM_AGGRESSIVE        = 0xa11c82 # Max Power Saving
  PM_PERFORMANCE       = 0x111022 # High Performance
  PM_MAX_IMPACT        = 0x111141 # BBB
  wifi.config(pm=PM_PERFORMANCE)
  #print(wifi.config.getpm)
  return
####################################
def connect_wifi(ssidx, passwordx):
  global wifi, wifi_reset
  if(wifi_reset):
    print('WiFi Reset')
    wifi_reset = False
    wifi.reset()
  wifi = network.WLAN(network.STA_IF)
  wifi.active(True)
  scan_wifi()
  wifi.config(txpower=txpwr%64) # Default 31mw=50%
  time.sleep(0.25)
  print('      Connecting To:', ssidx, end='\r')
  wifi.connect(ssidx, passwordx)
  time.sleep(0.25)
  power_management()
  return()
####################################
def holiday(yr, mo, da): # Year, Month, Day of Month
  global _hday
  _hday = False
  if     (mo ==  1): # January
    if   (da ==  1): prn("New Year's Day, "+ str(yr))
    elif (da == 20) and (((yr-1) % 4) == 0): prn('Inauguration Day')
    #else: eol()
  elif   (mo ==  2): # February
    yrs_ = str(yr - 2022) + str(ordinal(yr - 2022))
    if   (da ==  1): prn('NGC Retired, 2010')
    elif (da ==  2): prn('Groundhog Day, 700cc, 2006')
    elif (da ==  4): av_ = yrs_ + ' Aniv. Quadrupal Bypass, 2022'; prn(av_)
    elif (da == 14): prn("Valintine's Day")
    elif (da == 29): prn('Leap Day')
    #else: eol()
  elif   (mo ==  3): # March
    if   (da == 14): prn("Pi Day * 3.141_592_653_589_793_238_462_643_383_279_50")
    elif (da == 17): prn("St. Patrick's Day")
    elif (da == 25): prn('Happy Birthday Bruce, 1947')
    elif (da == 27): prn('Happy Birthday Todd, 1975')
    #else: eol()
  elif   (mo ==  4): # April
    if   (da ==  1): prn('April Fools Day')
    #else: eol()
  elif   (mo ==  5): # May
    if   (da ==  5): prn('Cinco de Mayo')
    #else: eol()
  elif   (mo ==  6): # June
    if   (da == 19): prn('Juneteenth')
    pass
    #else: eol()
  elif   (mo ==  7): # July
    if   (da ==  4): prn('Independance Day')
    elif (da == 26): prn('Happy Birthday Ben, 1972')
    #else: eol()
  elif   (mo ==  8): # August
    if   (da == 10): prn('Happy Birthday Jackie, 1950')
    elif (da == 23): prn('Happy Birthday Aaron, 1977')
    #else: eol()
  elif   (mo ==  9): # September
    pass
    #else:  eol()
  elif   (mo == 10): # October
    if   (da ==  6): prn('350cc, 2004')
    elif (da == 31): prn('Holloween')
    #else: eol()
  elif   (mo == 11): # November
    if   (da ==  1): prn('USAF Retired, 1987')
    if   (da == 11): prn('Armistis Day')
    #else: eol()
  elif   (mo == 12): # December
    yrs_ = str(yr - 1970) + str(ordinal(yr - 1970))
    if   (da ==  7): prn('Pearl Harbor Day, 1941')
    elif (da == 12): av_ = yrs_ + ' B&J Anniversary'; prn(av_)
    elif (da == 23): prn('Festivus')
    elif (da == 24): prn('Christmas Eve')
    elif (da == 25): prn('Christmas Day')
    elif (da == 31): prn("New Year's Eve")
    #else: eol()
  eol()
  return(_hday)
####################################
def prn(_):
    global _hday
    _hday = True
    print(' *', _, '*', end='')
def eol():
    print('\r', end='')
####################################
def detect_dst(tm_year, tm_mon, tm_mday, tm_weekday):
    #print('\timport cedargrove_dst_adjuster')
    """Determines if the North American Standard Time (xST) input is
    within the Daylight Saving Time (DST) window. Input to this function is
    expressed as a structured time object in Standard Time (xST).
    The function returns:
    ``True``  if the datetime object is within  the DST window,
    ``False`` if the datetime object is outside the DST window.
    The helper cannot detect DST for a structured time object that was encoded as DST.
    
    January and February: Standard Time (2)
    March:    Transition from Standard Time to Saving Time on Second Sunday (2:00 >> 1:00)
    April through October: Daylight Saving Time (7)
    November: Transition from Saving Time to Standard Time on First  Sunday (2:00 >> 3:00)
    December: Standard Time (1)

    :param structured_time datetime: The Standard Time structured time input value.
    Can be any structured time value within the specified date calculation range of
    CircuitPython, currently January 1, 2000 00:00:00 to January 19, 2038 03:14:07.
    https://www.nist.gov/pml/time-and-frequency-division/popular-links/daylight-saving-time-dst
    No default value."""
    # Fix weekday and yearday structured time errors
    #datetime = time.localtime(time.mktime(datetime))
    # Convert Python time structure from Monday-origin to Sunday-origin.
    #weekday = (datetime.tm_wday + 1) % 7
    # Check for Standard Time window
    March    =  3
    November = 11
    if tm_mon < March or tm_mon > November: return False  # xST # Jan, Feb, & Dec: xST
    # Check for Saving Time window
    if March < tm_mon < November: return True # Apr, May, Jun, Jul, Aug, Sep, Oct: DST
    """ Test for *March* window opening threshold: **Second Sunday** occurs on the
    8th through 14th of the month at 02:00 Standard Time (xST)."""
    # Get the date of the previous Sunday or today's date if Sunday.
    prev_sunday_date = tm_mday - tm_weekday
    if tm_mon == March:
        if prev_sunday_date <= 7: return False  # xST  # First Sunday of month or before
        if prev_sunday_date <= 14:  # Second Sunday of month
            # Determine current DST threshold
            # year, March, previous Sunday date, 02 hours xST, 00 min, 00 sec
            dst_thresh = time.mktime([tm_year, tm_mon, prev_sunday_date, 2, 0, 0, 0, -1, -1])
            if time.mktime(time.localtime()) < dst_thresh: return False  # xST
        return True  # DST
    """Test for *November* window closing threshold: **First Sunday** occurs on the
    1st through 7th of the month at 02:00 Standard Time (xST) = 03:00 Daylight
    Saving Time (xDT)."""
    if tm_mon == November:
        if prev_sunday_date <= 0: return True  # DST # Before first Sunday of month
        if prev_sunday_date <= 7:  # First Sunday of month (First 7 days of November)
            # Determine current xST threshold
            #  year, November, previous Sunday date, 02 hours xDT, 00 min, 00 sec
            xst_thresh = time.mktime( [tm_year, 11, prev_sunday_date, 2, 0, 0, 0, -1, -1] )
            if time.mktime(time.localtime()) < xst_thresh: return True  # DST
        return False  # xST
    print('Calendar Error:', tm_year, tm_mon, tm_mday, tm_weekday)
    while True: pass
####################################
def checkSum(sentence):
    # Calculate the checksum.
    actual = 0
    for i in range(0, len(sentence)):
        actual ^= ord(sentence[i])
    return actual
#################################### End of Defined Functions
led.off()
'''   ['bblake',    'adafruit',  'Verizon_RFB79', 'Ubiquiti',  'TestNet',   'aristotle']  '''
sec = ['ssid0',     'ssid1',     'ssid2',         'ssid3',     'ssid4',     'ssid5']
pas = ['password0', 'password1', 'password2',     'password3', 'password4', 'password5']
bblake    = 0
adafruit  = 1
Verizon   = 2
Ubiquiti  = 3
TestNet   = 4
aristotle = 5
_         = TestNet # SSID Selected
_loop = False
while not _loop:
  _ = _ % 6
  try:
    ssid = secrets[sec[_]]
    password = secrets[pas[_]]
    print(_, ssid, password)
    connect_wifi(ssid, password)
    _loop = True
  except Exception as exc:
    print(Exception, ssid, exc)
    _ += 1
    time.sleep(1)
led.toggle()
time.sleep(OneTenth)
osn = os.uname( )
#print('\t      Sysname:', osn[0]) # rp2
#print('\t     Nodename:', osn[1]) # rp2
#print('\t      Release:', osn[2]) # 1.24.0-preview
print('  MicroPython Version:', osn[3])
print('    Hardware Platform:', osn[4])
mac = ubinascii.hexlify(network.WLAN().config('mac'),':').decode()
print('\t  MAC Address:', mac)
print('\t     TX Power: ' + str(wifi.config('txpower')) + 'mw')
print('\t      Channel:', wifi.config('channel'))
print('\t\t SSID:', wifi.config('ssid')) # aka essid
####################################
max_wait = 10
while max_wait:
  if (wifi.status() < 0) or (wifi.status() >= 3): break
  print('\tWaiting for Connection...', max_wait, end=' \r')
  max_wait -= 1
  time.sleep(1)
if max_wait != 10: print("")
####################################
time.sleep(0.250)
flag = False
while not flag:
  if wifi.status() == 3:
    ifc = wifi.ifconfig( )
    print('\t\t   IP: ' + ifc[0])
    print('\t\t Mask: ' + ifc[1])
    print('\t\tDGate: ' + ifc[2])
    print('\t\t  DNS: ' + ifc[3])
    print('#'*60)
    flag = True
  else:
    print("Raise RuntimeError('WiFi network connection failed')", max_wait)
    time.sleep(OneTenth)
    sys.exit() # Ctrl-D
    machine.reset() # Power Restart
    raise RuntimeError('WiFi network connection failed')
####################################
led.toggle()
SET_TIME(None)
if LocalZone == 0: zz = 0
else: zz = abs(LocalZone) -4 # Zone EST = -5
Year, Month, Day,  Hour, Minute, Second,  DoW, DoY = 0, 1, 2,  3, 4, 5,  6, 7
spinner = ('|/-\\')
####################################
oldSecond = None
DOW = ("Mon", "Tues", "Wednes", "Thurs", "Fri", "Satur", "Sun", "Beer")
MON = ("Beer", "Jan", "Febr", "March", "April", "May", "June", "July", "August", "Septem", "Octo", "Novem", "Decem", "Beer")
led.toggle()
####################################
dtg = time.localtime()# Year, Month, Day, Hour, Minute, Second, DoW, DoY
DST = (detect_dst(dtg[Year], dtg[Month], dtg[Day], dtg[DoW]))
set_local()
#DST = False
_ = '' if DST else ' '
banner = (' CPU Temperature * yyyy/mm/dd hh:mm:ss  DST' + _ + '  Zone  DoY DoW  DoW' + '     ' + TimeZone[zz] + ' Time Zone')
print(banner)
diag = False
while True:
  if wifi.status() != 3:
    print("Crash! ", end='')
    connect_wifi(ssid, password)
    SET_TIME(None)
  dtg = time.localtime(time.time() - tm_zoneoff)# Year, Month, Day, Hour, Minute, Second, DoW, DoY
  if ((dtg[Hour]%3==0) and (dtg[Minute]==59) and (dtg[Second]==33)):
    print("")
    SET_TIME(None)
    print(banner)
  if (oldSecond != dtg[Second]):
    oldSecond    = dtg[Second]
    Tick_ms      = time.ticks_ms()
    Day_ord      = ordinal(dtg[Day])
    DoY_ord      = ordinal(dtg[DoY])
    spin         = spinner[time.time()%len(spinner)]
    tempC        = CPU_temp()
    tempF        = tempC*1.8+32
    _ab = ''
    if(dtg[Month] <= 2): _ab = 'uary'
    if(dtg[Month] >= 9): _ab = 'ber'
    if(Zone == "Local"): Zone = "  " + USA_Time_Zones[zz]
    #           CPU Temperature   Spinner
    format0 = " {:.2f}°C {:.2f}°F {:} "
    line0 = format0.format (tempC, tempF, spin)
    print(line0, end='')
    #          yyyy / mm  / dd    HH :  MM :  SS Zone
    format1 = "{:4}/{:02}/{:02} {:02}:{:02}:{:02} {}{}  "
    line1 = (format1.format (dtg[Year], dtg[Month], dtg[Day], dtg[Hour], dtg[Minute], dtg[Second], DST, Zone))
    print(line1, end='')
    #           DoY  DoW ord
    format2 = "{:03}{:2} {} "
    line2 = (format2.format (dtg[DoY], DoY_ord, dtg[DoW]))
    print(line2, end='')
    #          DoW     Mon  DoMOrd  Year
    format3 = "{:}day, {:} {:}{:}, {:}CE "
    line3 = (format3.format (DOW[dtg[DoW]], MON[dtg[Month]]+_ab, dtg[Day], Day_ord, dtg[Year]))
    print(line3, end='')
    if holiday(dtg[Year], dtg[Month], dtg[Day]): pass
    else:
      data_tx = line0 + line1 + line2 + line3
      #Send characters from a to b
      data_tx_a = data_tx
      UART_TX('a', data_tx_a)
      #Receive characters from a
      data_rx_b = UART_RX('b')
      #Send characters from b to a
      UART_TX('b', data_rx_b)
      #Receive characters from b
      data_rx_a = UART_RX('a')
      _ = ' ' if len(hex(checkSum(data_tx))) > 3 else '  '
      s = str(hex(checkSum(data_tx))) + _ + str(hex(checkSum(data_rx_a))) + _
      print(data_rx_a, 'UART A>B~B>A CS:', s, end='')
      if Maker_Pi: print('~ DS3231 Time:', DS_3231.datetime(), end='     \r')
      else: print(' ~ No DS3231 RTC     ', end='\r')
      if (hex(checkSum(data_tx)) == hex(checkSum(data_rx_a))): pass
      else:
        print('\n\n UART IN vs OUT CheckSum Error!!!\a\n')
        time.sleep(OneTenth)
  hb = 1000/6 # ms
  Bri, Dim = 64, 16
  tick_diff = (time.ticks_diff(time.ticks_ms(), Tick_ms))
  if   (tick_diff < (hb*0)):
      if Maker_Pi: np[0] = (0, Dim, 0)
      else: led.off()
  elif (tick_diff < (hb*1)):
      if Maker_Pi: np[0] = (0, Bri, 0)
      else: led.on()
  elif (tick_diff < (hb*2)):
      if Maker_Pi: np[0] = (0, Dim, 0)
      else: led.off()
  elif (tick_diff < (hb*3)):
      if Maker_Pi: np[0] = (0, Bri, 0)
      else: led.on()
  elif (tick_diff < (hb*4)):
      if Maker_Pi: np[0] = (0, Dim, 0)
      else: led.off()
  #elif (tick_diff < (hb*5)): led.toggle()
  else: pass
  if Maker_Pi: np.write()
  gc.collect()
  time.sleep(2**-10) # 2**-10 = 0.000_976_562_500
####################################

[b-blake]

My error for finding an icon <> saying Code and clicking on it.
I should no better.

[b-blake]

I agree it is long, but it fails near the beginning. The user would only be looking for the NeoPixel code initially. It may be other code that is clobbering the neopixel code. The code checks if there is a DS3231. If not it turns off the DS3231 and Neopixel.

Were there any changed to the NeoPixel code internal to MicroPython?

[b-blake]

267/270 is the last working version

[b-blake]

OK, I went back to the start.

Below is the latest test code. The user can move back and forth by changing line 7.
Both chunks work with Build 267/270
Neither chunk works with Build 295

The schematic shows GPIO28 going to the WS2812B pin 4 (Page 1), and a Resistor/Diode/FET/LED. (Q19, BSS138), (Page 2)
MAKER-PI-PICO v1.2.0 Schematic.pdf

I don't see any magic there.

It looks to go max at the first np.write().
The NeoPixel is at full brightness and looks like it may be dimming the colored LEDs one at a time as the code cycles.
It is so bright it is hard to see what is going on.

Has there been a change the the internal neopixel library?

Bruce

from time import sleep
import time

GPIOPin = 28
noPixels = 1

if not True: # your setup (True)
    from machine import Pin
    from neopixel import NeoPixel
    pin = Pin(GPIOPin, Pin.OUT)  # set GPIO0 to output to drive NeoPixels
    np = NeoPixel(pin, noPixels)
else: # my setup (not True)
    import machine
    import neopixel
    np = neopixel.NeoPixel(machine.Pin(GPIOPin), noPixels)
    np[0] = (0, 0, 0)
    np.write()
    time.sleep(1)

print('Start')
while True:
    np[0] = (64, 0, 0)
    np.write()
    print('Red')
    sleep(1)

    np[0] = (0, 64, 0)
    np.write()
    print('Green')
    sleep(1)
    
    np[0] = (0, 0, 64)
    np.write()
    print('Blue')
    sleep(1)

[scruss]

Thanks for the cut-down version. Using

MicroPython v1.25.0-preview.295.g30acb16ad on 2025-02-11; Raspberry Pi Pico 2 W with RP2350

with a Maker Pi Pico, I get reasonable reds/greens/blues cycling each second. No blowout to white. Same goes with a regular RP2040 Pico.

The only thing I could see as a possible error in the full code: did you mean to set the baud rate to int(115200 * (2**6)), or nearly 7.4 MBps? That seems a little high

[b-blake]

I don't know what to say. For you 295 100% good. For me 295 100% bad.

I'll try 295 with the SD card pulled. I'll also try with the DS3231 removed.
Those seem to be longshots, but that is all we have left.

The UART baud rates (which are truly bit rates) are the result of "Let's see how fast can they go?"
The 7.4 Mbps is the fastest 100% reliable speed over very short wire paths, 3 inches.
This value was validated in the RP2040. I'll have to test the RP2350 to see if it can handle 2**7.

P.S. My training was that baud rate was when 2 or more bits were encoded into one information packet by phase shift, frequency shift, Quadra-Phase, etc.
If 1 bit is in each information packet, it is bit rate.
I will return the soapbox to its place in the corner.

[b-blake]

No joy in Mudville after removing the SD card and DS3231.

There have been preview releases before that did not work on my MCUs.
But then I waited two to four releases, and things straitened themselves out.
That is not happening this time.

Other than the NeoPixel, 295 works just fine.

What was changed between build 270 and 272? Would having me test 271 be of help?

I have Maker Pi Pico Rev1.2. That says there was a 1.0, and 1.1 before 1.2. Do you have 1.2?

[ricksorensen]

Do you have a way of checking the bit-banging for the neopixel data line? That might help. The default micropython neopixel.py uses the bitstream module (rp2/machine_bitstream.c) to send the pulses.

[scruss]

I have Maker Pi Pico Rev1.2. That says there was a 1.0, and 1.1 before 1.2. Do you have 1.2?

I tested with a 1.2 as well. As a former Cytron reseller, the one(s) I have are fairly early release. If earlier versions were released, they may have been for domestic educational distribution in Malaysia.

[b-blake]

Stewart,

More strange results.

My O'Scope shows no signal on pin 28.. That cannot be true. It is not a fancy scope. Logic probe fails too.

More strange. Running the cycle code below. Basically your version.

with 270 I get Red, Green, Blue, Red, . . . (1 second intervals)

With 259 I get Red, White, Blue, White, Green, White, Red, . . . (I believe 1/2 second interval for color, then 1/2 second for white)
The color order is not the same. I am dying to hear you explain that!?!?

I tried to reproduce the above by loading 270 then 295. Now I get.
Yellow white orange white magenta white cyan white blue white other colors white ...
I have not been able to find a pattern

I am having a hard time typing because the brilliant white is burning a big dot in my retina..
I out a white bread tag over the NeoPixel helps some.

No matter what happens, when I go back to 270, all works correctly. O'Scope and Logic Probe still fails.

from time import sleep

GPIOPin = 28
noPixels = 1

if  True: # your setup
    from machine import Pin
    from neopixel import NeoPixel
    pin = Pin(GPIOPin, Pin.OUT)  # set GPIO0 to output to drive NeoPixels
    np = NeoPixel(pin, noPixels)
else: # my setup
    import machine
    import neopixel
    np = neopixel.NeoPixel(machine.Pin(GPIOPin), noPixels)
    np[0] = (0, 0, 0)
    np.write()
    sleep(1)
print('Start')
while True:
    np[0] = (64, 0, 0)
    np.write()
    print('Red')
    sleep(1)

    np[0] = (0, 64, 0)
    np.write()
    print('Green')
    sleep(1)
    
    np[0] = (0, 0, 64)
    np.write()
    print('Blue')
    sleep(1)

[b-blake]

If I increase the number of NeoPixels to more than 1, my O'Scope and Logic Probe show signals in and out of the NeoPixel.
The pulses look the same from 270 or 295. Most are 3.3 volts tall. A few are about half that.

No guess from here.

[ricksorensen]

The IO Pin to the neopixel should be one way - the Pin should be an output on the RP2350/RP2040. The pulse bit for the neopixel color is a high-low pair, of fixed length with the ratio of high to low time determining 1 or 0, and there are 24bits sent per pixel. An extended low time is used to mark end of the bit sequence. The high value should be at VCC (3.3 V) and the low at GND (0V). Default timing in neopixel.py is 1250 ns/bit with high for a '1' bit at 800ns and for a '0' bit at 400 ns

…

On Wed, Feb 12, 2025 at 5:17 PM b-blake ***@***.***> wrote: If I increase the number of NeoPixels to more than 1, my O'Scope and Logic Probe show signals in and out of the NeoPixel. No guess from here. — Reply to this email directly, view it on GitHub <#16723 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA5QPQD4COXLGXNLMS5WGBT2PPJA5AVCNFSM6AAAAABWX6HUTWVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEMJYGA3TSNI> . You are receiving this because you commented.Message ID: ***@***.*** com>

-- Rick Sorensen ***@***.*** 651-470-5511

[b-blake]

Rick,

I am referring to the input (4) and output (2) pins of the NeoPixel WS2812B. If I confused you into thinking I was referring to the same pin, I apologize.
Pin 1 ~ Vdd (3v3), Pin 4 ~ Data In.
Pin 2 ~ Data Out, Pin 3 ~ Vss (Ground)

As to the timing of the pulses, my oscilloscope is not of the finest quality. I have yet to figure out how to resolve to the multi-nanosecond, and get the triggering right.. Again I apologize.

Right now we are playing the "600 mile screwdriver game". You guys are turning the handle right and left. I am the screwdriver tip reporting what I see with the tools I have available.

My confusion comes from things working with build 144 - 270 and not working with build 272 - 295. It looks to me like something changed between build 270 and build 272 that impacts the NeoPixel data stream formation. What that change is, is not visible to me on my scope. I could guess, but I would be doing it through complete ignorance as to what is happening in the source code.

Would any of the bugs in the RP2350 chip impact this? Is GPIO 28 any different from the other pins?

Bruce

[scruss]

It looks to me like something changed between build 270 and build 272 that impacts the NeoPixel data stream formation.

The last change to rp2/machine_bitstream.c was made on 2025-01-10. v1.25.0-preview.267 (so before 270 and 272) was built on 2025-02-07, so it is likely that the underlying driver code is the same on all of your versions.

Would any of the bugs in the RP2350 chip impact this?

Unlikely. Erratum RP2350-E9 affects a GPIO pin configured as a pull-down with input buffer enabled. WS2812B LEDs are write-only, so use Pin.OUT

Is GPIO 28 any different from the other pins?

Not markedly so, according to §1.2.3. GPIO Functions (Bank 0) of the RP2350 datasheet.

[b-blake]

I tried build 301. No change.

[robert-hh]

The last change to rp2/machine_bitstream.c was made on 2025-01-10. v1.25.0-preview.267

This change causes the timing to be changed marginally.

Before the change: 380ns T0H, 800ns T0L, 1:780 ns T1H, 400ns T1L
After the change: 415 T0H, 845 T0L 1: 820 T1H, 440ns T1L

Actually there are different value for that in the two data sheet copies I have. I get from the first WS2812B Mini:

T0H0 code, high voltage time 220ns~380ns
T1H1 code, high voltage time 580ns~1µs
T0L0 code, low voltage time  580ns~1µs
T1L1 code, low voltage time  220ns~420ns

From the second, WS2812B:

T0H0 code ,high voltage time 0.4us±150ns
T1H1 code ,high voltage time 0.8us±150ns
T0L0 code , low voltage time 0.85us±150ns
T1L1 code ,low voltage time0.45us±150ns

Do you know which version is at the board?

[b-blake]

I do not have a true build 267. The file name I have says 267, but the os.name()[3] says it is 270.
v1.25.0-preview.270.gd76733d05 on 2025-02-07 (GNU 13.2.0 MinSizeRel)

[robert-hh]

That's build 270.

[scruss]

yes, but the filename says it's 267, as I noted last week:

picotool info RPI_PICO2_W-20250207-v1.25.0-preview.267.ge44a2c692.uf2
File RPI_PICO2_W-20250207-v1.25.0-preview.267.ge44a2c692.uf2 family ID 'rp2350-arm-s':

Program Information
 name:            MicroPython
 version:         v1.25.0-preview.270.gd76733d05
 features:        thread support
                  USB REPL
 frozen modules:  aioble/security, aioble/l2cap, aioble/client, aioble/central,
                  aioble/server, aioble/peripheral, aioble/device, aioble/core,
                  aioble, urequests, webrepl_setup, webrepl, ssl, ntptime, mip,
                  requests, neopixel, dht, ds18x20, onewire, uasyncio,
                  asyncio/stream, asyncio/lock, asyncio/funcs, asyncio/event,
                  asyncio/core, asyncio, _boot_fat, _boot, rp2
 binary start:    0x10000000
 binary end:      0x100ceaa8
 target chip:     RP2350
 image type:      ARM Secure

[robert-hh]

@b-blake: maybe if you still get the bright whites with this, there's a vague chance that your board has a 400 kHz WS2812B. Try timing=0 if so

Isn't it the opposite: using a "fast" WS2812 with the slow timing=0 results in all white, while using a "slow" WS2812 with the fast timing=1 would result in all black?

[b-blake]

timing=0 ~ Solid bright white.
Fast loop.

timing=1 ~ flickering bright white
It flickers because I have it looping as fast as possible. Waiting a FULL second is too long to see a result.

[robert-hh]

If the timing is the problem, you can try to directly set it with the timing argument, e.g. as timing=(300,800,800,360)
With that setting I get a real timing of (340, 760, 820, 360).

[scruss]

... looping as fast as possible

Huh? Please use the repeatable test code I linked to. If you're doing your own thing, we have no chance of converging on an answer that will help you.

I have tried exactly the same hardware, with exactly the same firmware as you. I can't repeat your issue with any code posted here unless I set timing=0. Therefore, I can only see these options:

1. you have an intermittent hardware issue that unfortunately somehow correlates to the firmware loading process;
2. you aren't running the code you're showing us; or
3. you are trolling and deliberately wasting our time.

[robert-hh]

It flickers because I have it looping as fast as possible.

If it is looping too fast with all colors alternatively on you will see a flickering White. So you need a sleep in between. Just verified.

[b-blake]

Below is the code I am using for testing When I slow it down to 1 second per color I get a color, white, color, white... Each lasts about a second. The colors change each time ~ green, red, blue, *magenta*, red, blue, green, red, blue, *orange*, *cyan*, blue, green, red, blue... I have seen yellow too. As far as I can tell there is no pattern to the color replacing green, red, blue in the sequence It should be noted with 267 I get red, green, blue, as the code says, with no white between each color. It looks like the RGB are in the reverse order for 301. No guess on the random, random color. ``` from time import sleep GPIOPin = 28 noPixels = 1 if True: # Stewart's setup from machine import Pin from neopixel import NeoPixel pin = Pin(GPIOPin, Pin.OUT) # set GPIO0 to output to drive NeoPixels np = NeoPixel(pin, noPixels, bpp=3, timing=1) sleep(0.1) np[0] = (0, 0, 0) np.write() sleep(1) else: # Bruce's setup import machine import neopixel np = neopixel.NeoPixel(machine.Pin(GPIOPin), noPixels, bpp=3, timing=1) sleep(0.1) np[0] = (0, 0, 0) np.write() sleep(1) print('Start') i = 1 p = noPixels - 1 while True: np[p] = (64, 0, 0) np.write() print('Red') sleep(i) np[p] = (0, 64, 0) np.write() print('Green') sleep(i) np[p] = (0, 0, 64) np.write() print('Blue') sleep(i) ```

…

On Sat, Feb 15, 2025 at 3:11 PM Robert Hammelrath ***@***.***> wrote: It flickers because I have it looping as fast as possible. If it is looping too fast with all colors you will see a flickering White. — Reply to this email directly, view it on GitHub <#16723 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AWCPQOMJ5Y4ALSQ74GHW3BL2P6NOVAVCNFSM6AAAAABWX6HUTWVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEMRRGE3DSOI> . You are receiving this because you were mentioned.Message ID: ***@***.*** com>

[b-blake]

Stewart, 1. you have an intermittent hardware issue that unfortunately *somehow* correlates to the firmware loading process; 2. you aren't running the code you're showing us; or 3. you are trolling and deliberately wasting our time. I am running the code in the previous post. I have added diagnostic code to assist me. I will not address item 3.

…

On Sat, Feb 15, 2025 at 3:44 PM Bruce Blake ***@***.***> wrote: Below is the code I am using for testing When I slow it down to 1 second per color I get a color, white, color, white... Each lasts about a second. The colors change each time ~ green, red, blue, *magenta*, red, blue, green, red, blue, *orange*, *cyan*, blue, green, red, blue... I have seen yellow too. As far as I can tell there is no pattern to the color replacing green, red, blue in the sequence It should be noted with 267 I get red, green, blue, as the code says, with no white between each color. It looks like the RGB are in the reverse order for 301. No guess on the random, random color. ``` from time import sleep GPIOPin = 28 noPixels = 1 if True: # Stewart's setup from machine import Pin from neopixel import NeoPixel pin = Pin(GPIOPin, Pin.OUT) # set GPIO0 to output to drive NeoPixels np = NeoPixel(pin, noPixels, bpp=3, timing=1) sleep(0.1) np[0] = (0, 0, 0) np.write() sleep(1) else: # Bruce's setup import machine import neopixel np = neopixel.NeoPixel(machine.Pin(GPIOPin), noPixels, bpp=3, timing=1) sleep(0.1) np[0] = (0, 0, 0) np.write() sleep(1) print('Start') i = 1 p = noPixels - 1 while True: np[p] = (64, 0, 0) np.write() print('Red') sleep(i) np[p] = (0, 64, 0) np.write() print('Green') sleep(i) np[p] = (0, 0, 64) np.write() print('Blue') sleep(i) ``` On Sat, Feb 15, 2025 at 3:11 PM Robert Hammelrath < ***@***.***> wrote: > It flickers because I have it looping as fast as possible. > > If it is looping too fast with all colors you will see a flickering White. > > — > Reply to this email directly, view it on GitHub > <#16723 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AWCPQOMJ5Y4ALSQ74GHW3BL2P6NOVAVCNFSM6AAAAABWX6HUTWVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEMRRGE3DSOI> > . > You are receiving this because you were mentioned.Message ID: > ***@***.*** > com> >

[b-blake]

Robert, I do not understand what you are saying with: *If the timing is the problem, you can try to directly set it with the timing argument, e.g. as timing=(300,800,800,300)* Do you want me to pass the tuple you show in your statement? If so, how should I vary the numbers to find a workable number?

…

On Sat, Feb 15, 2025 at 3:50 PM Bruce Blake ***@***.***> wrote: Stewart, 1. you have an intermittent hardware issue that unfortunately *somehow* correlates to the firmware loading process; 2. you aren't running the code you're showing us; or 3. you are trolling and deliberately wasting our time. I am running the code in the previous post. I have added diagnostic code to assist me. I will not address item 3. On Sat, Feb 15, 2025 at 3:44 PM Bruce Blake ***@***.***> wrote: > Below is the code I am using for testing > > When I slow it down to 1 second per color I get a color, white, color, > white... > Each lasts about a second. > The colors change each time ~ green, red, blue, *magenta*, red, blue, > green, red, blue, *orange*, *cyan*, blue, green, red, blue... > I have seen yellow too. > > As far as I can tell there is no pattern to the color replacing green, > red, blue in the sequence > > It should be noted with 267 I get red, green, blue, as the code says, > with no white between each color. > It looks like the RGB are in the reverse order for 301. No guess on the > random, random color. > > ``` > from time import sleep > > GPIOPin = 28 > noPixels = 1 > > if True: # Stewart's setup > from machine import Pin > from neopixel import NeoPixel > pin = Pin(GPIOPin, Pin.OUT) # set GPIO0 to output to drive NeoPixels > np = NeoPixel(pin, noPixels, bpp=3, timing=1) > sleep(0.1) > np[0] = (0, 0, 0) > np.write() > sleep(1) > else: # Bruce's setup > import machine > import neopixel > np = neopixel.NeoPixel(machine.Pin(GPIOPin), noPixels, bpp=3, > timing=1) > sleep(0.1) > np[0] = (0, 0, 0) > np.write() > sleep(1) > print('Start') > i = 1 > p = noPixels - 1 > while True: > np[p] = (64, 0, 0) > np.write() > print('Red') > sleep(i) > > np[p] = (0, 64, 0) > np.write() > print('Green') > sleep(i) > > np[p] = (0, 0, 64) > np.write() > print('Blue') > sleep(i) > ``` > > On Sat, Feb 15, 2025 at 3:11 PM Robert Hammelrath < > ***@***.***> wrote: > >> It flickers because I have it looping as fast as possible. >> >> If it is looping too fast with all colors you will see a flickering >> White. >> >> — >> Reply to this email directly, view it on GitHub >> <#16723 (comment)>, >> or unsubscribe >> <https://github.com/notifications/unsubscribe-auth/AWCPQOMJ5Y4ALSQ74GHW3BL2P6NOVAVCNFSM6AAAAABWX6HUTWVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEMRRGE3DSOI> >> . >> You are receiving this because you were mentioned.Message ID: >> ***@***.*** >> .com> >> >

[b-blake]

Robert, You found the nail. * timing=(300,800,800,300) *made it work under 301 It works under 267 also. What does this tell us. Well you guys, I have no idea.

…

On Sat, Feb 15, 2025 at 3:54 PM Bruce Blake ***@***.***> wrote: Robert, I do not understand what you are saying with: *If the timing is the problem, you can try to directly set it with the timing argument, e.g. as timing=(300,800,800,300)* Do you want me to pass the tuple you show in your statement? If so, how should I vary the numbers to find a workable number? On Sat, Feb 15, 2025 at 3:50 PM Bruce Blake ***@***.***> wrote: > Stewart, > > > 1. you have an intermittent hardware issue that unfortunately > *somehow* correlates to the firmware loading process; > 2. you aren't running the code you're showing us; or > 3. you are trolling and deliberately wasting our time. > > I am running the code in the previous post. I have added diagnostic code > to assist me. > > I will not address item 3. > > > On Sat, Feb 15, 2025 at 3:44 PM Bruce Blake ***@***.***> wrote: > >> Below is the code I am using for testing >> >> When I slow it down to 1 second per color I get a color, white, color, >> white... >> Each lasts about a second. >> The colors change each time ~ green, red, blue, *magenta*, red, blue, >> green, red, blue, *orange*, *cyan*, blue, green, red, blue... >> I have seen yellow too. >> >> As far as I can tell there is no pattern to the color replacing green, >> red, blue in the sequence >> >> It should be noted with 267 I get red, green, blue, as the code says, >> with no white between each color. >> It looks like the RGB are in the reverse order for 301. No guess on the >> random, random color. >> >> ``` >> from time import sleep >> >> GPIOPin = 28 >> noPixels = 1 >> >> if True: # Stewart's setup >> from machine import Pin >> from neopixel import NeoPixel >> pin = Pin(GPIOPin, Pin.OUT) # set GPIO0 to output to drive NeoPixels >> np = NeoPixel(pin, noPixels, bpp=3, timing=1) >> sleep(0.1) >> np[0] = (0, 0, 0) >> np.write() >> sleep(1) >> else: # Bruce's setup >> import machine >> import neopixel >> np = neopixel.NeoPixel(machine.Pin(GPIOPin), noPixels, bpp=3, >> timing=1) >> sleep(0.1) >> np[0] = (0, 0, 0) >> np.write() >> sleep(1) >> print('Start') >> i = 1 >> p = noPixels - 1 >> while True: >> np[p] = (64, 0, 0) >> np.write() >> print('Red') >> sleep(i) >> >> np[p] = (0, 64, 0) >> np.write() >> print('Green') >> sleep(i) >> >> np[p] = (0, 0, 64) >> np.write() >> print('Blue') >> sleep(i) >> ``` >> >> On Sat, Feb 15, 2025 at 3:11 PM Robert Hammelrath < >> ***@***.***> wrote: >> >>> It flickers because I have it looping as fast as possible. >>> >>> If it is looping too fast with all colors you will see a flickering >>> White. >>> >>> — >>> Reply to this email directly, view it on GitHub >>> <#16723 (comment)>, >>> or unsubscribe >>> <https://github.com/notifications/unsubscribe-auth/AWCPQOMJ5Y4ALSQ74GHW3BL2P6NOVAVCNFSM6AAAAABWX6HUTWVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEMRRGE3DSOI> >>> . >>> You are receiving this because you were mentioned.Message ID: >>> <micropython/micropython/repo-discussions/16723/comments/12211699@ >>> github.com> >>> >>

[b-blake]

FYI ~ *timing=(400,800,800,400)* returns to brilliant white. A quick search does not explain what is happening.

…

On Sat, Feb 15, 2025 at 4:03 PM Bruce Blake ***@***.***> wrote: Robert, You found the nail. * timing=(300,800,800,300) *made it work under 301 It works under 267 also. What does this tell us. Well you guys, I have no idea. On Sat, Feb 15, 2025 at 3:54 PM Bruce Blake ***@***.***> wrote: > Robert, > > I do not understand what you are saying with: > > *If the timing is the problem, you can try to directly set it with the > timing argument, e.g. as timing=(300,800,800,300)* > > Do you want me to pass the tuple you show in your statement? If so, how > should I vary the numbers to find a workable number? > > On Sat, Feb 15, 2025 at 3:50 PM Bruce Blake ***@***.***> wrote: > >> Stewart, >> >> >> 1. you have an intermittent hardware issue that unfortunately >> *somehow* correlates to the firmware loading process; >> 2. you aren't running the code you're showing us; or >> 3. you are trolling and deliberately wasting our time. >> >> I am running the code in the previous post. I have added diagnostic >> code to assist me. >> >> I will not address item 3. >> >> >> On Sat, Feb 15, 2025 at 3:44 PM Bruce Blake ***@***.***> wrote: >> >>> Below is the code I am using for testing >>> >>> When I slow it down to 1 second per color I get a color, white, color, >>> white... >>> Each lasts about a second. >>> The colors change each time ~ green, red, blue, *magenta*, red, blue, >>> green, red, blue, *orange*, *cyan*, blue, green, red, blue... >>> I have seen yellow too. >>> >>> As far as I can tell there is no pattern to the color replacing green, >>> red, blue in the sequence >>> >>> It should be noted with 267 I get red, green, blue, as the code says, >>> with no white between each color. >>> It looks like the RGB are in the reverse order for 301. No guess on >>> the random, random color. >>> >>> ``` >>> from time import sleep >>> >>> GPIOPin = 28 >>> noPixels = 1 >>> >>> if True: # Stewart's setup >>> from machine import Pin >>> from neopixel import NeoPixel >>> pin = Pin(GPIOPin, Pin.OUT) # set GPIO0 to output to drive >>> NeoPixels >>> np = NeoPixel(pin, noPixels, bpp=3, timing=1) >>> sleep(0.1) >>> np[0] = (0, 0, 0) >>> np.write() >>> sleep(1) >>> else: # Bruce's setup >>> import machine >>> import neopixel >>> np = neopixel.NeoPixel(machine.Pin(GPIOPin), noPixels, bpp=3, >>> timing=1) >>> sleep(0.1) >>> np[0] = (0, 0, 0) >>> np.write() >>> sleep(1) >>> print('Start') >>> i = 1 >>> p = noPixels - 1 >>> while True: >>> np[p] = (64, 0, 0) >>> np.write() >>> print('Red') >>> sleep(i) >>> >>> np[p] = (0, 64, 0) >>> np.write() >>> print('Green') >>> sleep(i) >>> >>> np[p] = (0, 0, 64) >>> np.write() >>> print('Blue') >>> sleep(i) >>> ``` >>> >>> On Sat, Feb 15, 2025 at 3:11 PM Robert Hammelrath < >>> ***@***.***> wrote: >>> >>>> It flickers because I have it looping as fast as possible. >>>> >>>> If it is looping too fast with all colors you will see a flickering >>>> White. >>>> >>>> — >>>> Reply to this email directly, view it on GitHub >>>> <#16723 (comment)>, >>>> or unsubscribe >>>> <https://github.com/notifications/unsubscribe-auth/AWCPQOMJ5Y4ALSQ74GHW3BL2P6NOVAVCNFSM6AAAAABWX6HUTWVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEMRRGE3DSOI> >>>> . >>>> You are receiving this because you were mentioned.Message ID: >>>> <micropython/micropython/repo-discussions/16723/comments/12211699@ >>>> github.com> >>>> >>>

[robert-hh]

Lacking knowledge of the exact timing at your WS2812B chip it's hard to find a reason. We do not know if the boards send wrong times or if the WS2812B is out of spec. Most likely it's the latter. The only thing we observed is, that shortening the H phase for a 0 bit solves the problem. @scruss pointed at commit 7964a43 which caused the bit times to be extended a little bit. That could be the change you have seen between working and failing.

[b-blake]

I have done some playing with the first number. It works with 399, and fails with 400. That is a very, very close miss.
Ref: @scruss comment, if it was a one nanosecond extension it would fit what I am seeing.

After reading four different discussions about WS2812 timing I settled on (350, 750, 800, 400).
50 Nanoseconds down from the spec sheet for all four values.

The WS2812B specification sheet I found says (400, 800, 850, 450) is the center value +/- 150 nanoseconds.
That would look like (250 to 550, 650 to 950, 700 to 1000, 300 to 600) are allowable.

Knowing that commit 7964a43 has extended the NeoPixel timing, does the MicroPython NeoPixel code need to be adjusted?
I would expect that I am not the only person who has NeoPixels that are at the edge of the specifications.

Please advise if the MicroPython code is adjusted so I can test with the change.

[robert-hh]

The bitstream implementation of the various ports differs in granularity. As far as I recall, it is 20ns for RP2. So changing from 399 to 400 could be an effective change by 20ns.
In my tests, the ws2812 seemed pretty forgiving about the timing. So, I assume that it is something in your hardware that requires different timing configurations. But there must be a measurement to get further.
The MicroPython code does not need changes. The timing it creates is, according to my tests, perfectly fine.

[robert-hh]

Knowing that commit 7964a43 has extended the NeoPixel timing,

This commit extended the timing for RP2350 only to better match the NeoPixel specification. Before, the timing was slightly to low, but still within the NeoPixel tolerance.

[b-blake]

@robert-hh, I understand.

I have been looking on the internet for the documentation for the NeoPixel timing=(400,800,800,400) option.
I have not been able to find it. Can someone point me to the documentation?
I want to better understand what the impacts are to changes.

[robert-hh]

Here are copies of various data sheet variants: https://www.alldatasheet.com/view.jsp?Searchword=WS2812B
It's interesting that newer versions of the chip require a shorter timing for a 0 bit, 220ns~380ns, instead of 400ns +/- 150ns found in the older data sheets. That might explain why the older firmware worked with your Neopixel, since the older one had 380µs for the T0H phase.
The voltage range is 3.7-5.3 V at the newer datasheet, compared to 3.5 - 5.3 for the older. In any case 3.3V is out of spec.

[b-blake]

@robert-hh,

I agree. 4 out of 5 say the first state should be 220ns to 380ns. The first data sheet numbers may have been rounded. .350 will round to .400 even though that is not in the range of .220 to .380. The data sheet with a 2020 in its title is the one I have most confidence in.

3.7 volts minus 5% is 3.515 volts. 3.5 volts minus 5% is 3.325 volts. Both are above the 3.3 nominally available on microprocessors and microcontrollers, again out of spec. I would think a slightly lower voltage would impact timing. Which way I am not sure. I doubt the timing inside a NeoPixel is crystal controlled. Most likely an R-C triple inverter oscillator. Very susceptible to voltage and temperature influence.