Hello,

I got the Mosquitto and paho-mqtt testing on my BBBW and BBGW. I can run a 
broker on each of them so far. I can also run some extra scripts in python 
to make them "almost work." 

...

Should I be using the BBGW/BBBW as a broker or should I use a larger 
computer as the broker?

Seth

P.S. I started to use this idea w/ websockets too.

On Sunday, August 16, 2020 at 1:45:16 PM UTC-5 [email protected] wrote:

> You could use something like MQTT where you run the Mosquitto MQTT server 
> on one of the BBBW and then publish and subscribe to shared topics between 
> the two.  I believe Node-RED might be another option.
>
>
>
> On Sun, Aug 16, 2020 at 8:56 AM Dennis Lee Bieber <[email protected]> 
> wrote:
>
>> On Sat, 15 Aug 2020 20:47:51 -0700 (PDT), in
>> gmane.comp.hardware.beagleboard.user set_
>> <[email protected]> wrote:
>>
>> >
>> >I mean, I can test UART connections b/t the two boards. This is not my 
>> >concern. I am trying to use one script to control both boards. I mean, I 
>> >can break them up and try that setup too. 
>> >
>> >I would rather have _________ work to make one script compiled 
>> communicate 
>> >my interests to the boards at my disposal. 
>> >
>>
>>         I believe you are going to have to define some sort of distributed
>> communication protocol, and run some sort of command interpreter on the
>> second board. The first board would then have to format and send commands
>> over the link to the second board for execution. The command definitions
>> will have to cover all operation categories you want to perform on the
>> second board (set motor speed, or whatever it is supposed to do), and
>> probably include return values too.
>>
>>         Depending upon how you create this protocol library, it may be 
>> possible
>> to, say, run the command processor on each board using TCP/IP and 
>> listening
>> on "commandport", and your master script would open sockets to
>> "localhost:commandport" and "otherhost:commandport". This way, you use the
>> same command sequences for both boards (and can expand if needed --
>> "anotherhost:commandport").
>>
>>         Your top-level control script only needs to know the IP/port for 
>> each
>> controller board. You run the same processor code as a server on each
>> board.
>>
>>
>>
>> -- 
>> Dennis L Bieber
>>
>> -- 
>> For more options, visit http://beagleboard.org/discuss
>> --- 
>> You received this message because you are subscribed to the Google Groups 
>> "BeagleBoard" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to [email protected].
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/beagleboard/36lijf9tr63qecfjj9j982oom5snk9apqu%404ax.com
>> .
>>
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/c7c8ea82-41d4-4244-bb08-7f13fb8d4742n%40googlegroups.com.

Reply via email to