Not outputting to leds #50
Replies: 19 comments 23 replies
-
|
https://github.com/awawa-dev/HyperSPI?tab=readme-ov-file#performancedebug-output |
Beta Was this translation helpful? Give feedback.
-
|
I'll have to wait till I'm home to try the screen debug. |
Beta Was this translation helpful? Give feedback.
-
|
That's not proper HyperSPI log. Read the manual (link posted above) again. |
Beta Was this translation helpful? Give feedback.
-
and maybe read the entire manual here https://github.com/awawa-dev/HyperSPI/ because you even chose the wrong driver in HyperHDR. HyperSPI will not forgive any mistake and these are the basics |
Beta Was this translation helpful? Give feedback.
-
|
That was the only spi ws2812spi driver I saw. Is the rp2040 and rpi 4 suppose to be connected? |
Beta Was this translation helpful? Give feedback.
-
|
you have even a screenshot on the main page |
Beta Was this translation helpful? Give feedback.
-
|
I tried screen /dev/ttyACM0 115200 Nothing is happening or shows up in the console. |
Beta Was this translation helpful? Give feedback.
-
|
And HyperHDR is running then after you fixed LED driver configuration? |
Beta Was this translation helpful? Give feedback.
-
|
im not positive what is the command line to start HyperHDR? |
Beta Was this translation helpful? Give feedback.
-
|
Is HyperHDR running? If so there wont be any output in the |
Beta Was this translation helpful? Give feedback.
-
|
also last line may be helpful: https://github.com/awawa-dev/HyperHDR/wiki/Installation#Linux |
Beta Was this translation helpful? Give feedback.
-
|
I stopped the service with the command. When I use screen the cursor just
blinks till I exit
…On Mon, Jul 15, 2024, 4:09 PM Awawa ***@***.***> wrote:
Is HyperHDR running? If so there wont be any output in the screen
terminal as per manual says
—
Reply to this email directly, view it on GitHub
<#50 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ANUAZLVIGKPPE5VZH7EKC2DZMQ27ZAVCNFSM6AAAAABK4GAIOCVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTAMBVGU2TIMI>
.
You are receiving this because you modified the open/close state.Message
ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
if there is no output then either: wrong COM port used for screen (/dev/ttyACM0 is not a pico), the pico is dead or you made a mistake with flashing firmware |
Beta Was this translation helpful? Give feedback.
-
|
connect it to the windows and use putty, check if com port disapears when you disconnect the pico and appears again after you connect it |
Beta Was this translation helpful? Give feedback.
-
|
I'd what tou said the company port disappears after I unplug and will
reappear if I plug it back in.
…On Mon, Jul 15, 2024, 4:26 PM Awawa ***@***.***> wrote:
connect it to the windows and use putty, check if com port disapears when
you disconnect the pico and appears again after you connect it
—
Reply to this email directly, view it on GitHub
<#50 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ANUAZLT2LYR2CJJAUYFQKDDZMQ5BLAVCNFSM6AAAAABK4GAIOCVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTAMBVGU3DIMI>
.
You are receiving this because you modified the open/close state.Message
ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Stupid autocorrect. The com port recognizes it when it's plugged in and
doesn't recognize it when I unplug it. It recognizes when I plug it again
too
…On Mon, Jul 15, 2024, 4:50 PM Luke Parnell ***@***.***> wrote:
I'd what tou said the company port disappears after I unplug and will
reappear if I plug it back in.
On Mon, Jul 15, 2024, 4:26 PM Awawa ***@***.***> wrote:
> connect it to the windows and use putty, check if com port disapears when
> you disconnect the pico and appears again after you connect it
>
> —
> Reply to this email directly, view it on GitHub
> <#50 (reply in thread)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/ANUAZLT2LYR2CJJAUYFQKDDZMQ5BLAVCNFSM6AAAAABK4GAIOCVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTAMBVGU3DIMI>
> .
> You are receiving this because you modified the open/close state.Message
> ID: ***@***.***>
>
|
Beta Was this translation helpful? Give feedback.
-
|
OK, then you should have some output if you connect using putty. |
Beta Was this translation helpful? Give feedback.
-
|
I relashed the pico with the hyperSPI_Pico_ws2812.uf2 firmware.
…On Mon, Jul 15, 2024, 4:52 PM Luke Parnell ***@***.***> wrote:
Stupid autocorrect. The com port recognizes it when it's plugged in and
doesn't recognize it when I unplug it. It recognizes when I plug it again
too
On Mon, Jul 15, 2024, 4:50 PM Luke Parnell ***@***.***>
wrote:
> I'd what tou said the company port disappears after I unplug and will
> reappear if I plug it back in.
>
> On Mon, Jul 15, 2024, 4:26 PM Awawa ***@***.***> wrote:
>
>> connect it to the windows and use putty, check if com port disapears
>> when you disconnect the pico and appears again after you connect it
>>
>> —
>> Reply to this email directly, view it on GitHub
>> <#50 (reply in thread)>,
>> or unsubscribe
>> <https://github.com/notifications/unsubscribe-auth/ANUAZLT2LYR2CJJAUYFQKDDZMQ5BLAVCNFSM6AAAAABK4GAIOCVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTAMBVGU3DIMI>
>> .
>> You are receiving this because you modified the open/close state.Message
>> ID: ***@***.***
>> com>
>>
>
|
Beta Was this translation helpful? Give feedback.
-
|
This is what shows when I first load hyperhdr. So now I should set a color
and disable hyperhdr then use screen?
…On Mon, Jul 15, 2024, 4:58 PM Luke Parnell ***@***.***> wrote:
I relashed the pico with the hyperSPI_Pico_ws2812.uf2 firmware.
On Mon, Jul 15, 2024, 4:52 PM Luke Parnell ***@***.***>
wrote:
> Stupid autocorrect. The com port recognizes it when it's plugged in and
> doesn't recognize it when I unplug it. It recognizes when I plug it again
> too
>
> On Mon, Jul 15, 2024, 4:50 PM Luke Parnell ***@***.***>
> wrote:
>
>> I'd what tou said the company port disappears after I unplug and will
>> reappear if I plug it back in.
>>
>> On Mon, Jul 15, 2024, 4:26 PM Awawa ***@***.***> wrote:
>>
>>> connect it to the windows and use putty, check if com port disapears
>>> when you disconnect the pico and appears again after you connect it
>>>
>>> —
>>> Reply to this email directly, view it on GitHub
>>> <#50 (reply in thread)>,
>>> or unsubscribe
>>> <https://github.com/notifications/unsubscribe-auth/ANUAZLT2LYR2CJJAUYFQKDDZMQ5BLAVCNFSM6AAAAABK4GAIOCVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTAMBVGU3DIMI>
>>> .
>>> You are receiving this because you modified the open/close state.Message
>>> ID: ***@***.***
>>> com>
>>>
>>
|
Beta Was this translation helpful? Give feedback.
-
|
Still no output. The only eps32 I have is the esp32-c6 and there's no firmware for that. |
Beta Was this translation helpful? Give feedback.
-
|
Please ignore the lack of logs for now. Does the LEDs work? Whats in your current HyperHDR now after you fixed the configuration? |
Beta Was this translation helpful? Give feedback.
-
|
No the leds aren't working but I know they work cause I used them on other projects. Same hardware. Pi 4. Ms2130. FEzcoo EZ-SP12HAS rp2040 pico. |
Beta Was this translation helpful? Give feedback.
-
|
Tomorrow I have a esp32 s2 mini. Part number is ESP32-S2FN4R2 so I won't need level shifter right? |
Beta Was this translation helpful? Give feedback.
-
|
rpi, esp32 s2 or rp2040 doesnt matter...all have 3.3V GPIO and level shifter is needed. And logs? |
Beta Was this translation helpful? Give feedback.
-
|
2024-07-17T21:54:51.076Z [CORE] TTY is not attached to the log output |
Beta Was this translation helpful? Give feedback.
-
|
Switched to esp32 s2 but still having issues with no led output. Does the esp32 usb cable have to be connected to the pi all the time? |
Beta Was this translation helpful? Give feedback.
-
ws2812spi??? You still havent configured LED device in HyperHDR properly and you are using wrong driver. In this case there is no chance it will work. |
Beta Was this translation helpful? Give feedback.
-
|
yes, and before that you should use rp2040 for pico. |
Beta Was this translation helpful? Give feedback.
-
|
Alright. I'll probably put my rp2040 pico back in then. How do you power the pico just through the usb cable to the pi? |
Beta Was this translation helpful? Give feedback.
-
|
Do you power the pico with usb connection to pi 4? |
Beta Was this translation helpful? Give feedback.
-
|
Yes, you can use usb for that purpose and for debugging using 'screen' console |
Beta Was this translation helpful? Give feedback.
-
|
if you connect everything again, set correct driver in HyperHDR and run it. Also connect 'screen' console at the same time. In HyperHDR run some effect and in the remote tab enable and disable the |
Beta Was this translation helpful? Give feedback.
-
|
Here's my log and screen. Only the first two leds light up for some reason. |
Beta Was this translation helpful? Give feedback.
-
|
so you test it with esp32 not rp2040, no spi communication, logs doesn't corresponded to the test procedure, no pics etc |
Beta Was this translation helpful? Give feedback.
-
|
I tried hyperserialpico today and still no luck. Screen shows same thing. I'm getting no leds to light up. Here's my log https://pastebin.com/5qh7EVTU
|
Beta Was this translation helpful? Give feedback.
-
if you have this in the log after disabling the LED driver, it means that Pico was receiving data and rendering frames before it was disabled. If there was no response from the LED strip, there is something wrong between the Pico and the LED strip. |
Beta Was this translation helpful? Give feedback.
-
|
There was no reply from led strip. |
Beta Was this translation helpful? Give feedback.
-
I'm using raspberry pi 4 as hyperhdr host. Wired to rp2040 zero as per your diagrams. Flashed hyper pico spi firmware. Ms2130 grabber and a an Ezcoo EZ-SP12HAS. I've wired everything up including using Level Shifter (SN74AHCT125N) with WS2812B leds. In remote everything is green except Forwader. I just get no output to my leds even though there getting 5volts.
Beta Was this translation helpful? Give feedback.
All reactions