Beiträge von Akriss

Sorry don't know. But That a ingenious idea. =)

A few weeks ago I came upon a German forum posting (http://www.forum-raspberrypi.d…n-wifi-led-controller-udp) detailing how to setup a ESP8266 NodeMCU with Hyperion. (I used Google translate) I was able to setup a ESP8266 ES-12E with a small string of ws2812b as a test and it was working good. So I dismantled it to test some other stuff and ordered some more ESP8266's to setup a bunch of remote pixels. =) And put aside the remote pixel idea till the order arrived.

So I received the Nodemcu's I ordered (Wemos mini's) and sure enough Murphy's law is at work and I can't get it to work on ether of the Nodemcu's type's I have again. And I'm not spotting my error and would greatly appreciate if someone would check my work.

I can run a simple strand test on both board with success with a string of 25 ws2812b's. With ether the Neopixel library or FastLed library. I have attached to this post, some fritzing pictures on the wiring that works for the strand test and for the remote pixel.
The “HyperionRGB.ino” file I have set “#define LED D3” nothing else changed.

The ConfigStatic.h.example is copyed to ConfigStatic.h and edited as such:

/*------------------------------------------------*/
/*Configuration type*/


#define CONFIG_ENABLE_WEBCONFIG 1


//Replaces all values in the webconfig with the ConfigStatic.h values when CONFIG_ENABLE_WEBCONFIG is enabled
#define CONFIG_OVERWRITE_WEBCONFIG 0
/*------------------------------------------------*/
/*Logging level*/


//#define LOGLEVEL LOG_LEVEL_INFOS
//#define LOGLEVEL LOG_LEVEL_DEBUG
#define LOGLEVEL LOG_LEVEL_VERBOSE
/*------------------------------------------------*/
/*Main static configuration*/
//This cannot be changed via web inteface


//#define CONFIG_LED_SPI_CHIPSET WS2801 //Comment out for clockless
#define CONFIG_LED_CLOCKLESS_CHIPSET WS2812B //Comment in for clockless
//#define FASTLED_ALLOW_INTERRUPTS 0 //Comment in if clockless stripe (ex. WS2812B) is flickering
//#define CONFIG_LED_PWM 1 //Comment in if PWM Stripe


#define CONFIG_LED_DATAPIN D1 //Comment out for PWM
//#define CONFIG_LED_CLOCKPIN D2 //Comment out for clockless / PWM
//#define CONFIG_LED_PWM_RED D1 //Comment in for PWM
//#define CONFIG_LED_PWM_GREEN D2 //Comment in for PWM
//#define CONFIG_LED_PWM_BLUE D3 //Comment in for PWM


//Pin order, see FastLED doc. NodeMCU should work with FASTLED_ESP8266_RAW_PIN_ORDER
#define FASTLED_ESP8266_RAW_PIN_ORDER
//#define FASTLED_ESP8266_NODEMCU_PIN_ORDER
//#define FASTLED_ESP8266_D1_PIN_ORDER


#define CONFIG_LED_COLOR_ORDER RGB
#define CONFIG_LED_COUNT 25


//OFF, HYPERION_UDP, STATIC_COLOR, RAINBOW, FIRE2012
#define CONFIG_LED_STANDARD_MODE FIRE2012
#define CONFIG_LED_HYPERION_AUTOSWITCH true
#define CONFIG_LED_STANDARD_MODE_TIMEOUT_MS 5000
/*------------------------------------------------*/
/*Main configuration*/
//You can leave it empty and override it via the web interface on port 80
#define CONFIG_WIFI_SSID "SSIDOFMINE"
#define CONFIG_WIFI_PASSWORD "************"


//#define CONFIG_WIFI_STATIC_IP 1
//const byte CONFIG_WIFI_IP[] = {192, 168, 0, 100};
//const byte CONFIG_WIFI_SUBNET[] = {255, 255, 255, 0};
//const byte CONFIG_WIFI_DNS[] = {192, 168, 0, 1};


#define CONFIG_WIFI_HOSTNAME "ESP8266"


#define CONFIG_PORT_JSON_SERVER 19444
#define CONFIG_PORT_UDP_LED 19446

I have no problems uploading the sketch to ether of the Nodemcu boards, I can log in to the web interface and login with the android app.

However the LED's refuse to work now! And this unskilled hobbyist needs a hand please.

I even tried blowing out the Arduino install and reinstalling it and reinstalling the recommended libraries that SciLor lists in the Git repo as well. =/

I'm lost Help please.

Thank you
Akriss.

If no one here can answer that. I'd bet the good folks on the Arduino forum would know. https://forum.arduino.cc

Doh!!

Seems It was a user mistake. <smacks head.

I had commented out a line in ConfigStatic that shouldn't have been.

#define CONFIG_OVERWRITE_WEBCONFIG 0

Well anyway . . move along nothing to see here...

I realized I should of posted a verbose log level, for clarity.

ets Jan  8 2013,rst cause:2, boot mode:(3,6)


load 0x4010f000, len 1384, room 16
tail 8
chksum 0x2d
csum 0x2d
v3de0c112
~ld
áI:  Start logging
I:  Configuration read at 0x0 with v3
V:    CFG=cfg2ip: 0.0.0.0
V:    CFG=cfg2ip: 0.0.0.0
V:    CFG=cfg2ip: 0.0.0.0
I:  CFG=EEPROM config loaded
D:   CFG Show Config
D:   +WIFI+
D:     ssid=
D:     password=
D:     ip=0.0.0.0
D:     subnet=0.0.0.0
D:     dns=0.0.0.0
D:     hostname=ESP8266
D:   +LED+
D:     idleMode=0
D:     timeoutMs=5000
D:     autoswitch=1
D:   +PORTS+
D:     jsonServer=19444
D:     udpLed=19446
D:   Chipset=Clockless, dataPin=5, clockPin=NONE, colorOrder=66, ledCount=26
I:  Reset Mode
D:   WrapperWiFi(ssid="", password="")
I:  Connecting to WiFi
I:  Using dynamic ip
E: WiFi Connection Failed! Rebooting...

Is it normal for the logs to omit the Wifi SSID and password?

I do have the SSID and password correctly set in ConfigStatic.h.

Thanks.

Hello all,

I have a NodeMcu ESP8266 ES-12E board that I use with the ESP8266 Hyperion LED Controller library. It works very well. And in constructing one pixel bar, it peaked my curiosity in how far I could Bling my Hyperion setup.

So I ordered a bunch of Wemos d1 mini's. In anticipation of fabricating a bunch of remote pixel bar's. However I'm unable to get them to work and could use some advise please.

The sketch I used for the Wemos is the exact same I've used with the 12E board without problems. However it not working properly on the Wemos. The output from the serial console just loops this:

ets Jan  8 2013,rst cause:2, boot mode:(3,0)


load 0x4010f000, len 1384, room 16
tail 8
chksum 0x2d
csum 0x2d
v3de0c112
~ld
øI:  Start logging
I:  Configuration read at 0x0 with v3
I:  CFG=EEPROM config loaded
I:  Reset Mode
I:  Connecting to WiFi
I:  Using dynamic ip
E: WiFi Connection Failed! Rebooting...

I'm lost and seeking some expert advise please. As I'm out of my league and my Google-Fu is failing me.

Many thanks.
Akriss.

So sadly I was unable to find a way to have Hyperion work with my Mythtv setup natively under Linux, with the Hyperion's internal framebuffer grabber. It worked somewhat, however not where it counted, wile watching video content.

So I went with the hdmi splitter, converter Etc. and it's working very well.

Thanks for helping me "Bling" my media center team Hyperion and all who contributed and shared.

Akriss.

Yes. However if you want to make sure the communication between the two is without fault I would install the ide and test an upload or two.

Zitat von ngng

I'm not sure what this would accomplish since I can confirm I am able to upload sketches.

Making sure the Rpi can communicate with the a arduino without issue on /dev/ttyACM0

Zitat von ngng

I am already using the official sketch.

Yup I realized that shortly after posting. My mistake

I have another idea that may resolve the issue. Try the Official sketch. ( https://github.com/hyperion-pr…ino/adalight/adalight.ino)

It may work better for you. I know it did for me.

As a test, would it be possible to install the arduino ide on the Rpi and see if it can upload the sketch without issue?

Are you uploading the sketch via the arduino ide on the Rpi?

Out of curiosity what does " sudo ls -l /dev/ttyACM0 " return on the Rpi?

How many LED's are you using? I ask because the two sketch's have different values. One for 240 and the other for 168.

Zitat von ngng

I don't think I need to ground anything on the RPi.

Yes. you NEED a common ground connection to all attached. However it should be grounded Via the USB connection already.

Zitat von ngng

Could this be the RGB color order?

you would at least see the LED's emitting colors, wrong colors. but colors non the less.

Hope it helps.

I think I found this (See attached) picture on the wiki here. but in any case, it shows the what the connections are.

Hope it helps.

The Arduino picture is missing a ground pin.

Hope it helps.

Ok, you don't use a "sketch" so ignore that bit. Still check the " "colorOrder" : " setting in the config file. I'm not sure what it the correct value it for your type of LED's.

It almost sounds as if you have something else sending the rainbow swirl other then Hyperion. Maybe during you testing you where trying something that auto-starts at boot?

hope it helps

are you using the official "sketch"? https://github.com/hyperion-project/hyperion.ng/tree/master/assets/firmware/arduino/adalight ?
You left out lots of detail on your setup. however I would check that you have the correct values for the " "colorOrder" : " setting in the config file.

hope it helps.

Hi,
I'm no expert. However, I do see a potential problem. You wrote that you have

Zitat von Tjiko

I have 254 leds in my setup

Yet in your .config file you have "#define MAX_LEDS 260". that should match your LED count.

You have to triple check your wiring. People cant help with wiring trouble, above advise that is.

I hope it helps.