Problem with multiple Master bricks

[Cathodion]

Hey fellas,

 

I'm running into trouble connecting multiple master bricks over USB to my PC. I have 3 master bricks installed in different rooms in my attic, and connect those with USB cables to a powered USB Hub, which is connected to my PC. However, if I connect more then 3 master bricks to the HUB brickv can no longer connect to brickd. If I attach 2 master bricks, then connect with brickv, and then connect the 3rd master brick to the USB Hub, I can see the third brick appear in brickv less then a second after plugging it in. But If I then disconnect brickv and try to reconnect it fails, and keeps failing until I disconnect one of the bricks.

 

If i remember correctly I also get problems if I connect 2 master bricks with USB cables to 2 different USB ports on my Macbook.

 

Are there any such problems known to you?

These use-cases are quite important to my setup, so I would be more then happy to give more details on this problem in a Google Hangout or something.

 

Kind regards,

Geert Schuring.

[photron]

However, if I connect more then 3 master bricks to the HUB brickv can no longer connect to brickd.

 

If brickv fails to connect to brickd then this might be a problem in brickd itself. Assuming that you mean that brickv is really complaining about connection problems with a message box. There is known problem like this related to the number of connected Bricks.

 

Are you using the latest version of brickd and the firmwares on the Bricks?

 

What operating system are you using on the PC?

 

Does it matter which of the Bricks you connect as third one that will then trigger the problem? Does this only happen with one of them?

 

What USB cables are you using? Is the problem related to a specific cable?

 

Could you take a look at the brickd log file? On Windows you can use eventlog.exe from the brickd installation directory. eventlog.exe allows to store the log to file. On Linux and Mac the log file is stored in /var/log/brickd.log. Could you attach the log file here on a post, so I can have a look at it?

[raphael_vogel]

Hi Geert

I remeber that you wanted to use quite long USB cables? Am I right ?

How long are your USB cables?

[photron]

Yes, too long or too low quality USB cables might result in broken/flaky USB communication. That's something to check too.

 

But this should not stop brickd from accepting TCP/IP connection attempts from brickv.

[Cathodion]

Thanks for your replies. I'm trying out several different setups to be able to answer your questions. I have a couple of answers already:

 

- I'm seeing the problem on linux only. If I connect 3 master bricks using long (5m) usb cables and a USB hub to my Macbook Pro I have no problems at all!

- The linux PC that I want to use is an Odroid U3.

- The problem is not related to a particular cable or brick.

- I can connect as much bricks as I want to the Odroid which all works fine... until I disconnect brickv from brickd and try to reconnect. So it looks like there's a problem in the brick/bricklets discovery mechanism on linux when a client connects.

 

I have a Windows 8 laptop in the house (ugh) so I'll test on that one too.

 

I'll have more answers in the coming days.

[photron]

So, if you have brickv connected to brickd before you connect any Bricks then it works. But If you try to connect brickv to brickd while there are already Bricks connected to USB then it doesn't work.

 

Odroid U3 can run XUbuntu 13.10 or Android 4.x according to their website. I assume you're using XUbuntu. Are you running brickv on the Odroid U3 if the problem occurs? If yes you might be affected by this bug in PyQwt. You can check your PyQwt version like this:

 

apt-cache show python-qwt5-qt4

 

If it's older than 5.2.1~cvs20091107+dfsg-6+b3build2.1 you should probably update it.

 

You can also test if the problem doesn't occur if you run brickv on a different computer than the Odroid U3, for example your Macbook, while the Bricks are still connected to the Odroid U3.

 

This all assumes that the problem is related to the PC you run brickv on. If that's not the case and the problem is only related to the PC brickd is running on then I'm following a red herring here

[Cathodion]

This is the log of brickd running on the Odroid:

 

2014-03-17 23:14:41.512984 <I> <network|network.c:94> Added new client (socket: 15, peer: 192.168.1.116)
2014-03-17 23:15:01.129551 <I> <usb|usb.c:144> Added USB device (bus: 1, device: 51) at index 0: Master Brick [6QHQQb]
2014-03-17 23:15:14.699561 <I> <usb|usb.c:144> Added USB device (bus: 1, device: 52) at index 1: Master Brick [6DbrcQ]
2014-03-17 23:15:28.269694 <I> <usb|usb.c:144> Added USB device (bus: 1, device: 53) at index 2: Master Brick [6jEWkb]
2014-03-17 23:15:35.442208 <I> <network|client.c:74> Client (socket: 15, peer: 192.168.1.116) disconnected by peer
2014-03-17 23:15:37.095135 <I> <network|network.c:94> Added new client (socket: 15, peer: 192.168.1.116)
2014-03-17 23:15:37.098579 <E> <network|client.c:255> Could not send response to client (socket: 15, peer: 192.168.1.116), disconnecting it: EAGAIN (11)
2014-03-17 23:15:37.214632 <I> <network|network.c:94> Added new client (socket: 15, peer: 192.168.1.116)
2014-03-17 23:15:37.378739 <E> <network|client.c:255> Could not send response to client (socket: 15, peer: 192.168.1.116), disconnecting it: EAGAIN (11)
2014-03-17 23:15:37.536632 <I> <network|network.c:94> Added new client (socket: 15, peer: 192.168.1.116)
2014-03-17 23:15:37.598215 <E> <network|client.c:255> Could not send response to client (socket: 15, peer: 192.168.1.116), disconnecting it: EAGAIN (11)
2014-03-17 23:15:37.706233 <I> <network|network.c:94> Added new client (socket: 15, peer: 192.168.1.116)
2014-03-17 23:15:37.745932 <E> <network|client.c:255> Could not send response to client (socket: 15, peer: 192.168.1.116), disconnecting it: EAGAIN (11)
2014-03-17 23:15:37.874373 <I> <network|network.c:94> Added new client (socket: 15, peer: 192.168.1.116)
2014-03-17 23:15:38.004635 <E> <network|client.c:255> Could not send response to client (socket: 15, peer: 192.168.1.116), disconnecting it: EAGAIN (11)

 

You can see what I'm doing:

• Connect brickv running on my Mac to brickd running on Odroid
  
• Attach 3 bricks using 5m usb cables
  
• Disconnect Brickv and try to reconnect
  

 

See the attachement for a screenshot of the brickv error message.

 

Now the following is the log output of brickd running on my Mac. I've simply attached the same bricks setup to my mac, which is now running both brickd and brickv:

 

2014-03-17 23:26:08.477154 <I> <network|network.c:94> Added new client (socket: 13, peer: 127.0.0.1)
2014-03-17 23:26:15.523401 <I> <usb|usb.c:144> Added USB device (bus: 26, device: 5) at index 0: Master Brick [6QHQQb]
2014-03-17 23:26:15.845647 <I> <usb|usb.c:144> Added USB device (bus: 26, device: 6) at index 1: Master Brick [6DbrcQ]
2014-03-17 23:26:15.907285 <I> <usb|usb.c:144> Added USB device (bus: 26, device: 7) at index 2: Master Brick [6jEWkb]
2014-03-17 23:26:30.675503 <I> <network|client.c:74> Client (socket: 13, peer: 127.0.0.1) disconnected by peer
2014-03-17 23:26:35.006954 <I> <network|network.c:94> Added new client (socket: 13, peer: 127.0.0.1)

 

No problem whatsoever...

[photron]

That's interesting:

 

2014-03-17 23:15:37.098579 <E> <network|client.c:255> Could not send response to client (socket: 15, peer: 192.168.1.116), disconnecting it: EAGAIN (11)

 

This means that brickd cannot send data to the socket. This only happens if you reconnect brickv while the the Bricks are connected.

 

Brickv requests an enumerate on connect. If no Bricks are connected then there is no enumerate response. If you connect a Brick it sends enumerate responses for its stack only. But if you reconnect Brickv while all the Bricks are connected then all Bricks send their enumerate response at once resulting in a burst. This could explain the problem you're seeing there.

 

I've added a send queue to brickd to deal with this situation. I attached an .deb package for armhf, assuming that the right things for the Odroid.

 

If you didn't install from a package you can find the source code on GitHub:

https://github.com/Tinkerforge/brickd

 

Could you test this version to see if it fixes your problem?

brickd-2.1.0-dfef064fc11f415b926aa82ba77f6f63a8c7b375_armhf.deb

[Cathodion]

YES that worked! Awesome.

I can now hook a whole bunch of bricks and bricklets to my odroid. GREAT!

 

Thanks a lot for taking the time to look into my problem. Its very much appreciated!

 

[photron]

Nice! This send queue feature will be part of the next release.

[Cathodion]

Nice! This send queue feature will be part of the next release.

 

Thanks again. And congrats on your 1k forum posts.

[fridolin11]

Dear all,

I have been running into the same problem as Cathodion and have trouble connecting two masterbrick stacks to the same raspberry pi 4. Following picture displays the entire setup when both stack are connected via USB:

My problem is, that not always both stacks show up and if they both show up then I am having troubles when using the individual bricklets and they are having timeouts. Following questions came up while I tried to troubleshoot this issue:

• Is the fix mentioned by photron already implemented in the version of brickviewer which I am using (2.4.25)?
• If no, is the version posted in this thread compatible with my raspberry pi?
• Where can i access the log file from brickd?

Any input is greatly appreciated.

Kind regards,

Fridolin

[fridolin11]

I just found the log files. This is what shows up when I try to connect over brickv:

2024-02-26 16:22:36.039557 <W> <usb_transfer.c:428> Read transfer 0x1967858 (handle: 0x1964e38, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:22:36.039807 <W> <usb_transfer.c:428> Read transfer 0x1967878 (handle: 0x1969d40, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:22:36.039912 <W> <usb_transfer.c:428> Read transfer 0x19678b8 (handle: 0x19682b8, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:22:36.040000 <W> <usb_transfer.c:428> Read transfer 0x19678d8 (handle: 0x19674e0, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:22:36.040650 <I> <usb_stack.c:103> Cleared read endpoint stall for Master Brick [6tdoWM]
2024-02-26 16:22:38.838728 <I> <network.c:304> Added new client (N: 127.0.0.1:43914, T: plain-socket, H: 20/20, B: 0, P: 0, A: disabled)
2024-02-26 16:22:39.977974 <W> <usb_transfer.c:428> Read transfer 0x1967898 (handle: 0x19514c0, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:22:39.978205 <W> <usb_transfer.c:428> Read transfer 0x19678f8 (handle: 0x1967570, submission: 8185) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:22:39.980536 <I> <usb_stack.c:103> Cleared read endpoint stall for Master Brick [6tdoWM]
2024-02-26 16:22:44.588868 <W> <usb_transfer.c:428> Read transfer 0x19677d8 (handle: 0x1967740, submission: 8290) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:22:44.589047 <W> <usb_transfer.c:428> Read transfer 0x19678d8 (handle: 0x19674e0, submission: 8288) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:22:44.590777 <I> <usb_stack.c:103> Cleared read endpoint stall for Master Brick [6tdoWM]
2024-02-26 16:22:46.513998 <W> <usb_transfer.c:428> Read transfer 0x19677f8 (handle: 0x1969408, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:22:46.515795 <I> <usb_stack.c:103> Cleared read endpoint stall for Master Brick [6tdoWM]
2024-02-26 16:22:54.639888 <I> <usb.c:506> Removing USB device (bus: 1, device: 19) at index 1: Master Brick [6kLrqd]
2024-02-26 16:22:54.998130 <I> <usb.c:273> Added USB device (bus: 1, device: 20) at index 1: Master Brick [6kLrqd]
2024-02-26 16:22:54.998368 <W> <network.c:509> Broadcasting response (U: 6kLrqd, L: 33, F: 255, S: 1, E: 0, I: 0, packet: 30 31 F1 D0 21 FF 18 00 36 6B 4C 72 71 64 00 00 30 00 00 00 00 00 00 00 30 03 02 00 02 05 02 0D 00) because no client/zombie has a matching pending request
2024-02-26 16:22:59.334920 <W> <usb_transfer.c:428> Read transfer 0x19677d8 (handle: 0x1967740, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:22:59.334942 <W> <usb_transfer.c:428> Read transfer 0x19677f8 (handle: 0x1969408, submission: 8510) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:22:59.334946 <W> <usb_transfer.c:428> Read transfer 0x1967818 (handle: 0x19655c8, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:22:59.334951 <W> <usb_transfer.c:428> Read transfer 0x1967838 (handle: 0x1963458, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:22:59.334954 <W> <usb_transfer.c:428> Read transfer 0x1967858 (handle: 0x1964e38, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:22:59.334963 <W> <usb_transfer.c:428> Read transfer 0x1967878 (handle: 0x1969d40, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:22:59.334966 <W> <usb_transfer.c:428> Read transfer 0x1967898 (handle: 0x19514c0, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:22:59.334970 <W> <usb_transfer.c:428> Read transfer 0x19678b8 (handle: 0x19682b8, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:22:59.334973 <W> <usb_transfer.c:428> Read transfer 0x19678d8 (handle: 0x19674e0, submission: 8512) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:22:59.334977 <W> <usb_transfer.c:428> Read transfer 0x19678f8 (handle: 0x1967570, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:22:59.335758 <I> <usb_stack.c:103> Cleared read endpoint stall for Master Brick [6tdoWM]
2024-02-26 16:23:00.469956 <W> <usb_transfer.c:428> Read transfer 0x19677d8 (handle: 0x1967740, submission: 8513) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:23:00.470414 <I> <usb_stack.c:103> Cleared read endpoint stall for Master Brick [6tdoWM]
2024-02-26 16:23:00.470467 <W> <usb_transfer.c:428> Read transfer 0x195abc8 (handle: 0x1964600, submission: 8369) for Master Brick [6kLrqd] aborted by stall condition
2024-02-26 16:23:00.470472 <W> <usb_transfer.c:428> Read transfer 0x195abe8 (handle: 0x1964690, submission: 8371) for Master Brick [6kLrqd] aborted by stall condition
2024-02-26 16:23:00.470476 <W> <usb_transfer.c:428> Read transfer 0x195ac08 (handle: 0x1964720, submission: 8373) for Master Brick [6kLrqd] aborted by stall condition
2024-02-26 16:23:00.470480 <W> <usb_transfer.c:428> Read transfer 0x195ac28 (handle: 0x1967160, submission: 8355) for Master Brick [6kLrqd] aborted by stall condition
2024-02-26 16:23:00.470483 <W> <usb_transfer.c:428> Read transfer 0x195ac48 (handle: 0x19671f0, submission: 8357) for Master Brick [6kLrqd] aborted by stall condition
2024-02-26 16:23:00.470487 <W> <usb_transfer.c:428> Read transfer 0x195ac68 (handle: 0x1966160, submission: 8359) for Master Brick [6kLrqd] aborted by stall condition
2024-02-26 16:23:00.470490 <W> <usb_transfer.c:428> Read transfer 0x195ac88 (handle: 0x19661f0, submission: 8361) for Master Brick [6kLrqd] aborted by stall condition
2024-02-26 16:23:00.470493 <W> <usb_transfer.c:428> Read transfer 0x195aca8 (handle: 0x1966280, submission: 8363) for Master Brick [6kLrqd] aborted by stall condition
2024-02-26 16:23:00.470512 <W> <usb_transfer.c:428> Read transfer 0x195acc8 (handle: 0x1966310, submission: 8365) for Master Brick [6kLrqd] aborted by stall condition
2024-02-26 16:23:00.470520 <W> <usb_transfer.c:428> Read transfer 0x195ace8 (handle: 0x1964ad8, submission: 8367) for Master Brick [6kLrqd] aborted by stall condition
2024-02-26 16:23:00.471146 <I> <usb_stack.c:103> Cleared read endpoint stall for Master Brick [6kLrqd]
2024-02-26 16:23:03.608132 <W> <usb_transfer.c:428> Read transfer 0x19677f8 (handle: 0x1969408, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:23:03.608153 <W> <usb_transfer.c:428> Read transfer 0x1967818 (handle: 0x19655c8, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:23:03.608157 <W> <usb_transfer.c:428> Read transfer 0x1967838 (handle: 0x1963458, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:23:03.608161 <W> <usb_transfer.c:428> Read transfer 0x1967858 (handle: 0x1964e38, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:23:03.608164 <W> <usb_transfer.c:428> Read transfer 0x1967878 (handle: 0x1969d40, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:23:03.608167 <W> <usb_transfer.c:428> Read transfer 0x1967898 (handle: 0x19514c0, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:23:03.609345 <I> <usb_stack.c:103> Cleared read endpoint stall for Master Brick [6tdoWM]
2024-02-26 16:23:03.609456 <W> <usb_transfer.c:428> Read transfer 0x195abc8 (handle: 0x1964600, submission: 8524) for Master Brick [6kLrqd] aborted by stall condition
2024-02-26 16:23:03.609466 <W> <usb_transfer.c:428> Read transfer 0x195abe8 (handle: 0x1964690, submission: 8525) for Master Brick [6kLrqd] aborted by stall condition
2024-02-26 16:23:03.609471 <W> <usb_transfer.c:428> Read transfer 0x195ac08 (handle: 0x1964720, submission: 8526) for Master Brick [6kLrqd] aborted by stall condition
2024-02-26 16:23:03.609478 <W> <usb_transfer.c:428> Read transfer 0x195ac28 (handle: 0x1967160, submission: 8527) for Master Brick [6kLrqd] aborted by stall condition
2024-02-26 16:23:03.609482 <W> <usb_transfer.c:428> Read transfer 0x195ac48 (handle: 0x19671f0, submission: 8528) for Master Brick [6kLrqd] aborted by stall condition
2024-02-26 16:23:03.610073 <I> <usb_stack.c:103> Cleared read endpoint stall for Master Brick [6kLrqd]
2024-02-26 16:23:06.531701 <W> <usb_transfer.c:428> Read transfer 0x195ac68 (handle: 0x1966160, submission: 0) for Master Brick [6kLrqd] aborted by stall condition
2024-02-26 16:23:06.531727 <W> <usb_transfer.c:428> Read transfer 0x195ac88 (handle: 0x19661f0, submission: 0) for Master Brick [6kLrqd] aborted by stall condition
2024-02-26 16:23:06.531731 <W> <usb_transfer.c:428> Read transfer 0x195aca8 (handle: 0x1966280, submission: 0) for Master Brick [6kLrqd] aborted by stall condition
2024-02-26 16:23:06.531734 <W> <usb_transfer.c:428> Read transfer 0x195acc8 (handle: 0x1966310, submission: 0) for Master Brick [6kLrqd] aborted by stall condition
2024-02-26 16:23:06.532989 <I> <usb_stack.c:103> Cleared read endpoint stall for Master Brick [6kLrqd]
2024-02-26 16:23:06.533076 <W> <usb_transfer.c:428> Read transfer 0x19677d8 (handle: 0x1967740, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:23:06.533086 <W> <usb_transfer.c:428> Read transfer 0x19677f8 (handle: 0x1969408, submission: 8534) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:23:06.533090 <W> <usb_transfer.c:428> Read transfer 0x1967818 (handle: 0x19655c8, submission: 8535) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:23:06.533094 <W> <usb_transfer.c:428> Read transfer 0x19678b8 (handle: 0x19682b8, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:23:06.533097 <W> <usb_transfer.c:428> Read transfer 0x19678d8 (handle: 0x19674e0, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:23:06.533101 <W> <usb_transfer.c:428> Read transfer 0x19678f8 (handle: 0x1967570, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:23:06.534223 <I> <usb_stack.c:103> Cleared read endpoint stall for Master Brick [6tdoWM]
2024-02-26 16:23:10.477011 <W> <usb_transfer.c:428> Read transfer 0x19677d8 (handle: 0x1967740, submission: 8549) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:23:10.477060 <W> <usb_transfer.c:428> Read transfer 0x19677f8 (handle: 0x1969408, submission: 8550) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:23:10.477104 <W> <usb_transfer.c:428> Read transfer 0x1967818 (handle: 0x19655c8, submission: 8551) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:23:10.477114 <W> <usb_transfer.c:428> Read transfer 0x1967838 (handle: 0x1963458, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:23:10.477123 <W> <usb_transfer.c:428> Read transfer 0x1967858 (handle: 0x1964e38, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:23:10.477132 <W> <usb_transfer.c:428> Read transfer 0x1967878 (handle: 0x1969d40, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:23:10.477140 <W> <usb_transfer.c:428> Read transfer 0x1967898 (handle: 0x19514c0, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:23:10.477148 <W> <usb_transfer.c:428> Read transfer 0x19678b8 (handle: 0x19682b8, submission: 8552) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:23:10.477157 <W> <usb_transfer.c:428> Read transfer 0x19678d8 (handle: 0x19674e0, submission: 8553) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:23:10.477165 <W> <usb_transfer.c:428> Read transfer 0x19678f8 (handle: 0x1967570, submission: 8554) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:23:10.479322 <I> <usb_stack.c:103> Cleared read endpoint stall for Master Brick [6tdoWM]
2024-02-26 16:23:10.479637 <W> <usb_transfer.c:428> Read transfer 0x195abc8 (handle: 0x1964600, submission: 0) for Master Brick [6kLrqd] aborted by stall condition
2024-02-26 16:23:10.479660 <W> <usb_transfer.c:428> Read transfer 0x195abe8 (handle: 0x1964690, submission: 0) for Master Brick [6kLrqd] aborted by stall condition
2024-02-26 16:23:10.479670 <W> <usb_transfer.c:428> Read transfer 0x195ac08 (handle: 0x1964720, submission: 0) for Master Brick [6kLrqd] aborted by stall condition
2024-02-26 16:23:10.479679 <W> <usb_transfer.c:428> Read transfer 0x195ac28 (handle: 0x1967160, submission: 0) for Master Brick [6kLrqd] aborted by stall condition
2024-02-26 16:23:10.479687 <W> <usb_transfer.c:428> Read transfer 0x195ac48 (handle: 0x19671f0, submission: 0) for Master Brick [6kLrqd] aborted by stall condition
2024-02-26 16:23:10.479696 <W> <usb_transfer.c:428> Read transfer 0x195ac68 (handle: 0x1966160, submission: 8545) for Master Brick [6kLrqd] aborted by stall condition
2024-02-26 16:23:10.479705 <W> <usb_transfer.c:428> Read transfer 0x195ac88 (handle: 0x19661f0, submission: 8546) for Master Brick [6kLrqd] aborted by stall condition
2024-02-26 16:23:10.479713 <W> <usb_transfer.c:428> Read transfer 0x195aca8 (handle: 0x1966280, submission: 8547) for Master Brick [6kLrqd] aborted by stall condition
2024-02-26 16:23:10.479721 <W> <usb_transfer.c:428> Read transfer 0x195acc8 (handle: 0x1966310, submission: 8548) for Master Brick [6kLrqd] aborted by stall condition
2024-02-26 16:23:10.479729 <W> <usb_transfer.c:428> Read transfer 0x195ace8 (handle: 0x1964ad8, submission: 0) for Master Brick [6kLrqd] aborted by stall condition
2024-02-26 16:23:10.482042 <I> <usb_stack.c:103> Cleared read endpoint stall for Master Brick [6kLrqd]
2024-02-26 16:23:13.895063 <W> <usb_transfer.c:428> Read transfer 0x195abc8 (handle: 0x1964600, submission: 8565) for Master Brick [6kLrqd] aborted by stall condition
2024-02-26 16:23:13.895088 <W> <usb_transfer.c:428> Read transfer 0x195abe8 (handle: 0x1964690, submission: 8566) for Master Brick [6kLrqd] aborted by stall condition
2024-02-26 16:23:13.895092 <W> <usb_transfer.c:428> Read transfer 0x195ac08 (handle: 0x1964720, submission: 8567) for Master Brick [6kLrqd] aborted by stall condition
2024-02-26 16:23:13.895096 <W> <usb_transfer.c:428> Read transfer 0x195ac28 (handle: 0x1967160, submission: 8568) for Master Brick [6kLrqd] aborted by stall condition
2024-02-26 16:23:13.895100 <W> <usb_transfer.c:428> Read transfer 0x195ac48 (handle: 0x19671f0, submission: 8569) for Master Brick [6kLrqd] aborted by stall condition
2024-02-26 16:23:13.895103 <W> <usb_transfer.c:428> Read transfer 0x195ac68 (handle: 0x1966160, submission: 8570) for Master Brick [6kLrqd] aborted by stall condition
2024-02-26 16:23:13.897043 <I> <usb_stack.c:103> Cleared read endpoint stall for Master Brick [6kLrqd]
2024-02-26 16:23:14.447729 <W> <usb_transfer.c:428> Read transfer 0x19677d8 (handle: 0x1967740, submission: 8555) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:23:14.447756 <W> <usb_transfer.c:428> Read transfer 0x19677f8 (handle: 0x1969408, submission: 8556) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:23:14.447761 <W> <usb_transfer.c:428> Read transfer 0x1967818 (handle: 0x19655c8, submission: 8557) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:23:14.447765 <W> <usb_transfer.c:428> Read transfer 0x1967838 (handle: 0x1963458, submission: 8558) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:23:14.447768 <W> <usb_transfer.c:428> Read transfer 0x1967858 (handle: 0x1964e38, submission: 8559) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:23:14.447777 <W> <usb_transfer.c:428> Read transfer 0x1967878 (handle: 0x1969d40, submission: 8560) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:23:14.447780 <W> <usb_transfer.c:428> Read transfer 0x1967898 (handle: 0x19514c0, submission: 8561) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:23:14.447784 <W> <usb_transfer.c:428> Read transfer 0x19678b8 (handle: 0x19682b8, submission: 8562) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:23:14.447787 <W> <usb_transfer.c:428> Read transfer 0x19678d8 (handle: 0x19674e0, submission: 8563) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:23:14.447790 <W> <usb_transfer.c:428> Read transfer 0x19678f8 (handle: 0x1967570, submission: 8564) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:23:14.448334 <I> <usb_stack.c:103> Cleared read endpoint stall for Master Brick [6tdoWM]
2024-02-26 16:23:16.998961 <W> <usb_transfer.c:428> Read transfer 0x19677d8 (handle: 0x1967740, submission: 8581) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:23:16.998986 <W> <usb_transfer.c:428> Read transfer 0x19677f8 (handle: 0x1969408, submission: 8582) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:23:17.001342 <I> <usb_stack.c:103> Cleared read endpoint stall for Master Brick [6tdoWM]
2024-02-26 16:23:21.968506 <W> <usb_transfer.c:428> Read transfer 0x1967818 (handle: 0x19655c8, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:23:21.968531 <W> <usb_transfer.c:428> Read transfer 0x1967838 (handle: 0x1963458, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:23:21.968536 <W> <usb_transfer.c:428> Read transfer 0x1967858 (handle: 0x1964e38, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:23:21.968539 <W> <usb_transfer.c:428> Read transfer 0x1967878 (handle: 0x1969d40, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:23:21.970349 <I> <usb_stack.c:103> Cleared read endpoint stall for Master Brick [6tdoWM]
2024-02-26 16:23:27.074464 <W> <usb_transfer.c:428> Read transfer 0x1967898 (handle: 0x19514c0, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:23:27.074693 <W> <usb_transfer.c:428> Read transfer 0x19678b8 (handle: 0x19682b8, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:23:27.074795 <W> <usb_transfer.c:428> Read transfer 0x19678d8 (handle: 0x19674e0, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:23:27.074884 <W> <usb_transfer.c:428> Read transfer 0x19678f8 (handle: 0x1967570, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:23:27.075741 <I> <usb_stack.c:103> Cleared read endpoint stall for Master Brick [6tdoWM]
2024-02-26 16:23:30.551991 <W> <usb_transfer.c:428> Read transfer 0x19677d8 (handle: 0x1967740, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:23:30.552168 <W> <usb_transfer.c:428> Read transfer 0x19677f8 (handle: 0x1969408, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:23:30.554533 <I> <usb_stack.c:103> Cleared read endpoint stall for Master Brick [6tdoWM]
2024-02-26 16:23:31.892155 <W> <usb_transfer.c:428> Read transfer 0x1967818 (handle: 0x19655c8, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:23:31.893216 <I> <usb_stack.c:103> Cleared read endpoint stall for Master Brick [6tdoWM]
2024-02-26 16:23:35.293526 <W> <usb_transfer.c:428> Read transfer 0x1967838 (handle: 0x1963458, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:23:35.293964 <W> <usb_transfer.c:428> Read transfer 0x1967858 (handle: 0x1964e38, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:23:35.294744 <I> <usb_stack.c:103> Cleared read endpoint stall for Master Brick [6tdoWM]
2024-02-26 16:23:37.031052 <W> <usb_transfer.c:428> Read transfer 0x1967878 (handle: 0x1969d40, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:23:37.033476 <I> <usb_stack.c:103> Cleared read endpoint stall for Master Brick [6tdoWM]
2024-02-26 16:23:38.273910 <W> <usb_transfer.c:428> Read transfer 0x1967898 (handle: 0x19514c0, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:23:38.276154 <I> <usb_stack.c:103> Cleared read endpoint stall for Master Brick [6tdoWM]
2024-02-26 16:23:41.525715 <W> <usb_transfer.c:428> Read transfer 0x19677d8 (handle: 0x1967740, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:23:41.526106 <W> <usb_transfer.c:428> Read transfer 0x19678b8 (handle: 0x19682b8, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:23:41.526365 <W> <usb_transfer.c:428> Read transfer 0x19678d8 (handle: 0x19674e0, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:23:41.526623 <W> <usb_transfer.c:428> Read transfer 0x19678f8 (handle: 0x1967570, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:23:41.529114 <I> <usb_stack.c:103> Cleared read endpoint stall for Master Brick [6tdoWM]
2024-02-26 16:23:42.695988 <W> <usb_transfer.c:428> Read transfer 0x19677f8 (handle: 0x1969408, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:23:42.697747 <I> <usb_stack.c:103> Cleared read endpoint stall for Master Brick [6tdoWM]
2024-02-26 16:23:45.254975 <W> <usb_transfer.c:428> Read transfer 0x1967818 (handle: 0x19655c8, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:23:45.256603 <I> <usb_stack.c:103> Cleared read endpoint stall for Master Brick [6tdoWM]
2024-02-26 16:23:49.002708 <W> <usb_transfer.c:428> Read transfer 0x1967838 (handle: 0x1963458, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:23:49.003121 <W> <usb_transfer.c:428> Read transfer 0x1967858 (handle: 0x1964e38, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:23:49.003435 <W> <usb_transfer.c:428> Read transfer 0x1967878 (handle: 0x1969d40, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:23:49.003688 <W> <usb_transfer.c:428> Read transfer 0x1967898 (handle: 0x19514c0, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:23:49.005626 <I> <usb_stack.c:103> Cleared read endpoint stall for Master Brick [6tdoWM]
2024-02-26 16:23:50.503097 <W> <usb_transfer.c:428> Read transfer 0x19677d8 (handle: 0x1967740, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:23:50.504328 <I> <usb_stack.c:103> Cleared read endpoint stall for Master Brick [6tdoWM]
2024-02-26 16:23:52.795155 <W> <usb_transfer.c:428> Read transfer 0x19678b8 (handle: 0x19682b8, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:23:52.797160 <I> <usb_stack.c:103> Cleared read endpoint stall for Master Brick [6tdoWM]
2024-02-26 16:23:54.399587 <W> <usb_transfer.c:428> Read transfer 0x19678d8 (handle: 0x19674e0, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:23:54.401883 <I> <usb_stack.c:103> Cleared read endpoint stall for Master Brick [6tdoWM]
2024-02-26 16:23:56.665937 <W> <usb_transfer.c:428> Read transfer 0x19677f8 (handle: 0x1969408, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:23:56.666353 <W> <usb_transfer.c:428> Read transfer 0x1967818 (handle: 0x19655c8, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:23:56.666602 <W> <usb_transfer.c:428> Read transfer 0x1967838 (handle: 0x1963458, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:23:56.666618 <W> <usb_transfer.c:428> Read transfer 0x1967858 (handle: 0x1964e38, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:23:56.666629 <W> <usb_transfer.c:428> Read transfer 0x19678f8 (handle: 0x1967570, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:23:56.668704 <I> <usb_stack.c:103> Cleared read endpoint stall for Master Brick [6tdoWM]
2024-02-26 16:23:59.781103 <W> <usb_transfer.c:428> Read transfer 0x19677d8 (handle: 0x1967740, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:23:59.781588 <W> <usb_transfer.c:428> Read transfer 0x1967878 (handle: 0x1969d40, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:23:59.781851 <W> <usb_transfer.c:428> Read transfer 0x1967898 (handle: 0x19514c0, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:23:59.782101 <W> <usb_transfer.c:428> Read transfer 0x19678b8 (handle: 0x19682b8, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:23:59.782347 <W> <usb_transfer.c:428> Read transfer 0x19678d8 (handle: 0x19674e0, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:23:59.783631 <I> <usb_stack.c:103> Cleared read endpoint stall for Master Brick [6tdoWM]
2024-02-26 16:24:00.815429 <W> <usb_transfer.c:428> Read transfer 0x19677f8 (handle: 0x1969408, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:24:00.815481 <W> <usb_transfer.c:428> Read transfer 0x1967818 (handle: 0x19655c8, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:24:00.816269 <I> <usb_stack.c:103> Cleared read endpoint stall for Master Brick [6tdoWM]
2024-02-26 16:24:03.179621 <W> <usb_transfer.c:428> Read transfer 0x19677d8 (handle: 0x1967740, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:24:03.179673 <W> <usb_transfer.c:428> Read transfer 0x1967838 (handle: 0x1963458, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:24:03.179686 <W> <usb_transfer.c:428> Read transfer 0x1967858 (handle: 0x1964e38, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:24:03.179696 <W> <usb_transfer.c:428> Read transfer 0x1967878 (handle: 0x1969d40, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:24:03.179707 <W> <usb_transfer.c:428> Read transfer 0x19678f8 (handle: 0x1967570, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:24:03.181098 <I> <usb_stack.c:103> Cleared read endpoint stall for Master Brick [6tdoWM]
2024-02-26 16:24:04.824835 <W> <usb_transfer.c:428> Read transfer 0x1967898 (handle: 0x19514c0, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:24:04.825779 <I> <usb_stack.c:103> Cleared read endpoint stall for Master Brick [6tdoWM]
2024-02-26 16:24:07.243762 <W> <usb_transfer.c:428> Read transfer 0x19678b8 (handle: 0x19682b8, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:24:07.243786 <W> <usb_transfer.c:428> Read transfer 0x19678d8 (handle: 0x19674e0, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:24:07.244616 <I> <usb_stack.c:103> Cleared read endpoint stall for Master Brick [6tdoWM]
2024-02-26 16:24:10.748589 <W> <usb_transfer.c:428> Read transfer 0x19677d8 (handle: 0x1967740, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:24:10.748641 <W> <usb_transfer.c:428> Read transfer 0x19677f8 (handle: 0x1969408, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:24:10.748654 <W> <usb_transfer.c:428> Read transfer 0x1967818 (handle: 0x19655c8, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:24:10.749654 <I> <usb_stack.c:103> Cleared read endpoint stall for Master Brick [6tdoWM]
2024-02-26 16:24:12.664740 <W> <usb_transfer.c:428> Read transfer 0x1967838 (handle: 0x1963458, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:24:12.666422 <I> <usb_stack.c:103> Cleared read endpoint stall for Master Brick [6tdoWM]
2024-02-26 16:24:13.733181 <W> <usb_transfer.c:428> Read transfer 0x1967858 (handle: 0x1964e38, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:24:13.733232 <W> <usb_transfer.c:428> Read transfer 0x1967878 (handle: 0x1969d40, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:24:13.733244 <W> <usb_transfer.c:428> Read transfer 0x19678f8 (handle: 0x1967570, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:24:13.735072 <I> <usb_stack.c:103> Cleared read endpoint stall for Master Brick [6tdoWM]
2024-02-26 16:24:15.247072 <W> <usb_transfer.c:428> Read transfer 0x1967898 (handle: 0x19514c0, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:24:15.247796 <I> <usb_stack.c:103> Cleared read endpoint stall for Master Brick [6tdoWM]
2024-02-26 16:24:19.285848 <W> <usb_transfer.c:428> Read transfer 0x19678b8 (handle: 0x19682b8, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:24:19.285881 <W> <usb_transfer.c:428> Read transfer 0x19678d8 (handle: 0x19674e0, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:24:19.286817 <I> <usb_stack.c:103> Cleared read endpoint stall for Master Brick [6tdoWM]
2024-02-26 16:24:20.301689 <W> <usb_transfer.c:428> Read transfer 0x19677d8 (handle: 0x1967740, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:24:20.301741 <W> <usb_transfer.c:428> Read transfer 0x19677f8 (handle: 0x1969408, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:24:20.303510 <I> <usb_stack.c:103> Cleared read endpoint stall for Master Brick [6tdoWM]
2024-02-26 16:24:27.646882 <W> <usb_transfer.c:428> Read transfer 0x1967818 (handle: 0x19655c8, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:24:27.646913 <W> <usb_transfer.c:428> Read transfer 0x1967838 (handle: 0x1963458, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:24:27.649018 <I> <usb_stack.c:103> Cleared read endpoint stall for Master Brick [6tdoWM]
2024-02-26 16:24:35.566066 <W> <usb_transfer.c:428> Read transfer 0x1967858 (handle: 0x1964e38, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:24:35.566092 <W> <usb_transfer.c:428> Read transfer 0x1967878 (handle: 0x1969d40, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:24:35.566944 <I> <usb_stack.c:103> Cleared read endpoint stall for Master Brick [6tdoWM]
2024-02-26 16:24:46.094333 <W> <usb_transfer.c:428> Read transfer 0x1967898 (handle: 0x19514c0, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:24:46.094358 <W> <usb_transfer.c:428> Read transfer 0x19678f8 (handle: 0x1967570, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:24:46.096610 <I> <usb_stack.c:103> Cleared read endpoint stall for Master Brick [6tdoWM]
2024-02-26 16:24:55.395694 <W> <usb_transfer.c:428> Read transfer 0x19677d8 (handle: 0x1967740, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:24:55.395967 <W> <usb_transfer.c:428> Read transfer 0x19678b8 (handle: 0x19682b8, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:24:55.396060 <W> <usb_transfer.c:428> Read transfer 0x19678d8 (handle: 0x19674e0, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:24:55.398419 <I> <usb_stack.c:103> Cleared read endpoint stall for Master Brick [6tdoWM]
2024-02-26 16:25:00.414345 <W> <usb_transfer.c:428> Read transfer 0x19677f8 (handle: 0x1969408, submission: 0) for Master Brick [6tdoWM] aborted by stall condition
2024-02-26 16:25:00.415597 <I> <usb_stack.c:103> Cleared read endpoint stall for Master Brick [6tdoWM]

What I did:

• connect over brickv
• -> only one stack shows up initially
• wait
• -> second stack shows up

Does anybody know what is going on and what might cause my problem?

[photron]

@fridolin11 Your problem seem to have a different cause.

On 2/26/2024 at 5:15 PM, fridolin11 said:

Is the fix mentioned by photron already implemented in the version of brickviewer which I am using (2.4.25)?

There was no fix in Brick Viewer, but a change in Brick Daemon to handle the message burst created by the enumeration of the whole system.

There is no need to test any old version that might have been mentioned in this thread. Please only test the latest versions of Brick Daemon and Brick Viewer. I assume that is what you already have installed.

From the brickd.log I can see that you get a lot stalled USB read transfers making the communication with the Bricks and Bricklets unreliable.

On 2/26/2024 at 5:27 PM, fridolin11 said:

2024-02-26 16:24:46.094358 <W> <usb_transfer.c:428> Read transfer 0x19678f8 (handle: 0x1967570, submission: 0) for Master Brick [6tdoWM] aborted by stall condition

As long as you continue to see this kind of message in brickd.log the problem persists. You can open brickd.log in a console/terminal like this to get a live view:

tail -f /var/log/brickd.log

Then try plugging and unplugging the Bricks from USB and see what messages you get.

Do the stall messages only appear when you connect two Bricks to USB? Is one Brick alone okay?

In the Raspberry Pi 2 era many problems where caused by insufficiant power supplies. How do you power the Raspberry Pi 4? Could you try a "stronger" power supply?

Du you directly connect the Bricks to the Raspberry Pi, or is there another USB hub in between? Does it make a difference if you remove any USB hub? You can also try to add a powered USB hub.

[fridolin11]

Dear photron

Thank you so much for your reply! I just checked ther version of brickd: 2.4.5

The live view was very helpful, and I was able to identify the problem. The stack which is directly next to my raspberry works fine all the time. The other stack, which is connected over a 1.5 m long usb cable causes the stall condition messages. They only occur though once I turn on some larger loads with the industrial relay bricklets. I routed all the signal cables seperately from the power lines but the noise occures nonetheless.

Regarding the powersupply of the raspberry:

• Both stacks have a Tinkerforge Step-Down PSU which are powered by two 24V 60W PSUs.
• The raspberry is connected over the usb-c port to the 5V output from one of the Step-Down PSUs
• The output from the Step-Down Bricks is rated for 5V 3A, which matches the PSU which Raspberry recommends
• The bricks are directly connected to the Raspberry Pi and I currently don't have a powered USB-hub to test out other possible connections

I most definitely will just remove the second seperate stack and will just include all of the bricklets into the first stack. Instead of an USB cable I will then have the cables from the bricklets routed over the 1.5 m. Most of those cables are not subsceptible to noise except for maybe one RS485 connection. I will have to test that tough.

[photron]

The power supply looks okay. For now I don't expect it to the an issue.

On 2/27/2024 at 7:50 AM, fridolin11 said:

The other stack, which is connected over a 1.5 m long usb cable causes the stall condition messages.

Does the USB cable ferrit cores near the connectors? Could you try a different USB cable and/or a different USB port on the Raspberry Pi?

[fridolin11]

No the cable doesn't have any ferrit cores on the ends and the same problem occured with different cables on different ports. What completely solved my issue was unplugging the power to the step-down brick from my second masterbrick stack (the one that caused trouble).

So the components are powered like this:

• 24V 60W PSU
• -> Step-Down PSU and Stack 1
• -> 5V Output from Step-Down powers my Raspberry Pi over USB-C
• -> Second Stack is powered by the Raspberry Pi over the USB Cable and no longer from its own dedicated PSU

Maybe a slight difference in the voltage ouput from the different PSUs caused the problem instead of interference in the cable? Either way, my Problem is solved and all the components work fine :)

Thank you so much for your inputs!