you can also do the command lsusb and should see something as follows:
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 009: ID 0403:6015 Future Technology Devices International, Ltd Bridge(I2C/SPI/UART/FIFO)
Bus 001 Device 008: ID 0403:6015 Future Technology Devices International, Ltd Bridge(I2C/SPI/UART/FIFO)
Bus 001 Device 007: ID 0403:6015 Future Technology Devices International, Ltd Bridge(I2C/SPI/UART/FIFO)
Bus 001 Device 006: ID 0403:6015 Future Technology Devices International, Ltd Bridge(I2C/SPI/UART/FIFO)
Bus 001 Device 005: ID 1a40:0201 Terminus Technology Inc. FE 2.1 7-port Hub
Bus 001 Device 004: ID 0403:6015 Future Technology Devices International, Ltd Bridge(I2C/SPI/UART/FIFO)
Bus 001 Device 003: ID 0403:6015 Future Technology Devices International, Ltd Bridge(I2C/SPI/UART/FIFO)
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Then in your bash / script if you want to split them out, as in my case above, I would do:
./cgminer -o stratum+tcp://usa-east.dgb256.online:8080 -u WALLET_ADDRESS.WORKER_NAME -p x --usb 1:4,1:8,1:9 --gekko-newpac-freq 450 --gekko-r606-freq 725 --widescreen
In this example out of the 4 newpacs and 2 R606's I have running, only 2 newpacs and 1 R606 is pointed at a Digibyte coin. In the --usb portion of the script, 1:4 in my example is reference Bus 001 Device 004 which is one of my R606's. In your case if I wanted my newpacs to point at a specific pool or sha256 coin then specify the usb addresses for the newpacs and plug that into your script. Then play around with the R606 on different pools. Then you won't have to worry about resetting the newpacs each time as now you are only referencing the R606's.
You may see different results when doing the lsusb though since on a desktop. I have mine running off a Raspberry Pi 4 and they are all on one Bus lane. On a desktop you may have all the newpacs on Bus 1 and may see the R606's on Bus 2 or Bus 4 etc. It'll be easy to figure out and code accordingly.
[...]
Not sure of the difference between the Pi 3b and b+ models. I have detailed instructions though on setting up the newpacs on a Raspberry Pi 3b+ on page 28 of this thread. I have not spent much time with these devices on Windows as I ran into stability issues once I tried, went the Raspberry Pi route and never looked back. One thing to note though, if you are only going to run 1 - 4 newpacs, then a Raspberry Pi 3b+ will be fine. If you plan on getting more than that or any R606 then you will need to get minimum Raspberry Pi 4. As the 3 series ran everything off one bus lane (processes, devices, internet etc) which created bottlenecks.
My suggestions since the Pi's are easy enough, reinstall Raspbian on that device, and follow the steps on page 28 for setting up the newpac on a raspberry device and see if this resolves the issue for you.