SPI PINS - Githubissues

awawa-dev / HyperSerialEsp8266

High speed 2Mb USB serial port LED strip HyperHDR driver using Esp8266 device.

https://hyperhdr.blogspot.com

MIT License

38 stars 69 forks source link

SPI PINS #2

Closed 5vi5t closed 3 years ago

5vi5t commented 3 years ago

what pins to use for spi? data pin and clock pin? in neopixelbus the software spi method is selected, not the hardware method. Why?) D5 and D7 is simple

awawa-dev commented 3 years ago

Hi In HyperSerialEsp8266 conventional NeoPixelBus' constructor is used (with only led number is passed as an argument) so standard pin should be selected. You can try to change DotStarMethod to DotStarSpiMethod in the code but I didn't test that method.

5vi5t commented 3 years ago

Ok, thank you What pins are standart for software spi?

awawa-dev commented 3 years ago

On my Wemos d1 mini pins: D5 and D7

5vi5t commented 3 years ago

D5 and D7 are hardware SPI pins, and don't work with DotStarMethod =(

awawa-dev commented 3 years ago

As I have no longer any SPI led strip I debug it today to make sure it still works. On screenshot D5 & D7 captured by the analyzer, output starts when HyperHDR is starting sending data, otherwise it's flat zero: obraz If you have no output on these pins then probably there is some other cause.

awawa-dev commented 3 years ago

Software method allows to redefine default pins. I don't change them. On Esp8266 you can't redefine them anyway so always hardware pins are used.

5vi5t commented 3 years ago

Ok, I understood But dont work with SK9822 and WEMOS D1 mini. I changed to DotStarSpiMethod and dont work too. I tested with FastLED sketch and all good

awawa-dev commented 3 years ago

Did you check if HyperSerialEsp8266 is receiving any data (in statistics)?

5vi5t commented 3 years ago

I checked with a basic sketch adalight (https://github.com/hyperion-project/hyperion.ng/blob/master/assets/firmware/arduino/adalight/adalight.ino), the data is received, the highlight is working.

awawa-dev commented 3 years ago

There are some specific aspects for HyperSerialEsp8266 that can cause not receiving the data and no output on led in result: different, rigorous protocol not compatible with the sketch you provided and 2Mb speed that can be unsupported by hardware serial chip . So checking these statistics should be first step in the diagnostic because the sketch you used unfortunately tells us nothing about it.

5vi5t commented 3 years ago

how can I do it?

awawa-dev commented 3 years ago

Please follow guide from other case: https://github.com/awawa-dev/HyperSerialEsp8266/issues/1

In short:

configure HyperHDR properly for using AWA protocol & HyperSerialEsp8266 and try to run it for at least one minute.
stop and close HyperHDR to release COM port
using any serial port client listen to that COM and wait for statistics. They are sent every few seconds when HyperHDR is not sending led data to the device. For example: screen /dev/ttyUSB0 2000000 under Linux.
if HyperSerialEsp8266 received at least one valid frame there will be a trace of that.

But first verify what serial chip is on your ESP8266 board.