[9fans] node-red

[Bakul Shah <bakul@iitbombay.org>]

[-- Attachment #1: Type: text/plain, Size: 3941 bytes --]

I saw a comment on Hackaday by someone who uses 25 Pis (all running node-red) on a manufacturing line 24/7, producing ~60K parts a day. Another commenter talked about a setup involving 100 or so Pis on shop floor. Lots of people using pi+node-red combination for all sorts of things. Looks like one can work around Pi's shortcomings if there is a real app!

Something like node-red would be a fun project for plan9. With a graph editor as a frontend - I suspect sure such a thing doesn't exist for plan9. 

https://www.youtube.com/watch?v=GeN7g4bdHiM
https://en.wikipedia.org/wiki/Node-RED
https://nodered.org/

> On Nov 22, 2020, at 2:48 AM, hiro <23hiro@gmail.com> wrote:
> 
> i should not have said anything
> 
> [11561053.235151] xhci_hcd 0000:01:00.0: @000000001ed0c6e0 00000000
> 00000000 0e000000 02048000
> [11572206.218075] Under-voltage detected! (0x00050005)
> [11572207.738154] bcmgenet fd580000.genet eth0: Link is Down
> [11572211.898285] bcmgenet fd580000.genet eth0: Link is Up -
> 1Gbps/Full - flow control off
> [11572212.458226] Voltage normalised (0x00000000)
> [11585621.202242] xhci_hcd 0000:01:00.0: ERROR Transfer event for
> disabled endpoint slot 2 ep 3
> 
> gonna move back to my seagate dockstar (kirkwood) for this thing :(
> at least then the rpi is free for a stateless 9front terminal again
> (easier to reboot when there's problems like the above :()
> 
> On 11/14/20, hiro <23hiro@gmail.com <mailto:23hiro@gmail.com>> wrote:
>> well they have FCC compliance, so i'd hope it's just internal
>> interference due to lack of rf separation on the board. unless the fcc
>> test is so busted that they were able to activate a less-problematic
>> pixel clock and never tried the full possible range? :D
>> 
>> since i don't have a github account i don't think they will listen to
>> me about my issues with the device.
>> 
>> but anyway they should hire an RF engineer and not me. if they tried
>> the common combinations at all they should have noticed themselves, no
>> ?
>> 
>> i have been using 4k@60hz when i experienced my problem, bluetooth
>> cannot be switched to 5ghz.
>> 
>> i'm just happy it works at all, i was just gonna return it otherwise
>> like i did with the earlier rpi version. don't have time to make
>> bug-wishlists for future raspberry christmas trees (took them 8 years
>> already to make the first rpi with working ethernet+usb).
>> 
>> On 11/14/20, Bakul Shah <bakul@iitbombay.org> wrote:
>>> There were reports of 2560x1440 res generating RF noise in the 2.4GHz
>>> band
>>> wifi channel 1. The proposed solution (by Eben Upton) was to use channel
>>> 4
>>> or higher or use 5GHz wifi band at this res. And supposedly there is a
>>> firmware fix for this. No idea about the bluetooth issue. You should
>>> report
>>> these issues either on their forum or one of their github repos.
>>> 
>>>> On Nov 14, 2020, at 7:14 AM, hiro <23hiro@gmail.com> wrote:
>>>> 
>>>> well, for me hdmi reliably stops working when i turn on the bluetooth
>>>> keyboard and versa.
>>>> clearly RF interference was none of their concern when they made this
>>>> chip.
>>>> if your monitor suggests a different pixel clock you might get lucky
>>>> and it's just good enough, but your signal quality is gonna suffer no
>>>> matter what
> 
> ------------------------------------------
> 9fans: 9fans
> Permalink: https://9fans.topicbox.com/groups/9fans/Te91377223453b8c0-M3206bd878f444f406e0fb927 <https://9fans.topicbox.com/groups/9fans/Te91377223453b8c0-M3206bd878f444f406e0fb927>
> Delivery options: https://9fans.topicbox.com/groups/9fans/subscription <https://9fans.topicbox.com/groups/9fans/subscription>

------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T44e63b084a86351b-Md515e2e941ef3e09ff71e1ff
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

[-- Attachment #2: Type: text/html, Size: 21847 bytes --]