Open mhoffma opened 7 years ago
It should work fine on the NodeMCU the only concern may be the NTSC signal itself may be interfering with the wifi. Please trying to run cnping against it and see if you get a see-saw effect.
I got it working my setup was not flashed right on the ESP01 module, your work is absolutely amazing.
On Fri, Apr 28, 2017 at 10:26 PM, CNLohr notifications@github.com wrote:
It should work fine on the NodeMCU the only concern may be the NTSC signal itself may be interfering with the wifi. Please trying to run cnping against it and see if you get a see-saw effect.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/cnlohr/channel3/issues/9#issuecomment-298141567, or mute the thread https://github.com/notifications/unsubscribe-auth/AQEAUxJOEX1sBzx9Aq1rl4RehjspaqUrks5r0p_vgaJpZM4NHbDw .
Can you be more specific about what you did? I know this is a common problem for people.
Yes. I moved to node mcu and added -fm dio to the esptool writeflash command applying it by hand. Then I just did make burnweb.
I plan to try it again on esp01. If you want I can add my notes to your project wiki. On Sat, Apr 29, 2017 at 3:40 PM CNLohr notifications@github.com wrote:
Can you be more specific about what you did? I know this is a common problem for people.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/cnlohr/channel3/issues/9#issuecomment-298190096, or mute the thread https://github.com/notifications/unsubscribe-auth/AQEAU0xWt1hw_7puJf7Rbbw4OHraZJM-ks5r05IagaJpZM4NHbDw .
Using -fm dio where exactly? It should either /just work/ or just /not work/
It was crashing for me the inf crash loop On Sat, Apr 29, 2017 at 6:15 PM CNLohr notifications@github.com wrote:
Using -fm dio where exactly? It should either /just work/ or just /not work/
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/cnlohr/channel3/issues/9#issuecomment-298197854, or mute the thread https://github.com/notifications/unsubscribe-auth/AQEAU47l7BMe5RLXjZNUV6fGyaGuzNe9ks5r07ZpgaJpZM4NHbDw .
But, it was getting far enough to load the webpage?
yes I had a similar problem with your colorchord where it was unstable but that turned out I believe to be a short on my board. The performance Hz was all over the place and then it would become totally unresponsive dropping connection. I wired TX so I could see the terminal text and I noticed the reboot sequence happening. I'm not sure if the two things are the same issue but my setup for channel3 has no wires just the breakout board so its not my wiring as an issue.
It really is odd that web page loads and displays and you could even thumb through the different pages on occasions and then it would die, it was pretty frustrating. I was just about to put trace into the code to figure out where it was dying when I reflashed it. woops I just realized I did change the code.
I don't see how this could be related but I made this change too.
--- a/user/user_main.c : +++ b/user/user_main.c @@ -363,15 +363,16 @@ void ICACHE_FLASH_ATTR user_init(void)
uart0_sendStr("\r\nesp8266 ws2812 driver\r\n");
-// int opm = wifi_get_opmode();
+#define FORCE_SSID 1
-#define SSID "" -#define PSWD "" +#define SSID "hoff" +#define PSWD "xxxxxxx"
//Override wifi.
diff --git a/web/page.mpfs b/web/page.mpfs index d4015cc..8cef52b 100644 Binary files a/web/page.mpfs and b/web/page.mpfs differ :
On Sat, Apr 29, 2017 at 9:36 PM, CNLohr notifications@github.com wrote:
But, it was getting far enough to load the webpage?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/cnlohr/channel3/issues/9#issuecomment-298205209, or mute the thread https://github.com/notifications/unsubscribe-auth/AQEAU6avMm4brYonxXe8k-XrPRqvxA2Yks5r0-WagaJpZM4NHbDw .
I don't see that either. I guess we'll just have to chalk it up to an unknown cause/effect :(. If you want we can close the issue
yes
On Sat, Apr 29, 2017 at 9:57 PM, CNLohr notifications@github.com wrote:
I don't see that either. I guess we'll just have to chalk it up to an unknown cause/effect :(. If you want we can close the issue
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/cnlohr/channel3/issues/9#issuecomment-298205860, or mute the thread https://github.com/notifications/unsubscribe-auth/AQEAU2f3OsxAYSzJpiQ9nEh1fsTJTF0Wks5r0-qZgaJpZM4NHbDw .
I'm having this issue, too. Takes forever to load the page, then when it does, the Hz hits 0 and I get Comms Lost.
I have noticed that what can happen is if your antenna is too short, or (unknown other details) the NTSC signal itself seems to interfere with the carrier detect for the 2.4 GHz wifi and prevents the ESP from sending any packets causing comms to fail. I strongly recommend trying a longer wire length.
Hi, I have same issue on Wemos D1 mini. From 10 tries I got once connection and after page loading takes forever. And if I am lucky the system speed descending from ie. 40Hz to 0Hz and after few seconds and goes to offline. Video output working without any interruption.
How did you get 800Hz?
Whitch wire leght do you recommend (lambda/4 1.2m)? At the moment I am using 1pcs dupoint cable.
EDIT: I have tested 1.2m wire as well and with other PSU nothing has been changed regarding connection :(
I do not have any specific recommended length. You can also try place something metallic near the antenna to mute it. This is way more janky than you may have previously expected :-p
Once the system boots and connects and loads web page up I can see all the nice widgets in my browser. however my Hz fluctuations go from like 6 to 0 and once I get 0 it loses connection.
I'm using a nodemcu module USB powered, nothing connected. Is the intended target esp01?
Any hints appreciated