Errors Starting Experiment

[Maxwell McManus]

Good morning, 

I ran into two errors starting an experiment this morning, and was hoping for some clarification. I planned to use the "shout-long-2024" profile for channel measurements on 7 rooftop CBAND nodes (BES, Behavioral, FM, Honors, Hospital, USTAR, MEB) and reserved 3360-3400 MHz. For reference, the failed experiments were titled "memcmanu-210827" and "memcmanu-210828". 

The first error I got was "Not enough bandwidth available for link", which I assume (based on previous post here) refers to the ethernet switch bandwidth since I am starting 7 nodes simultaneously. Is this just too many nodes to run at once? 

The second error (screenshot attached) is that I am requesting frequency out of range - however, the allowable range mentioned is 3358-3700 MHz. 

Additionally, I was also having some trouble collecting data from MEB last month - I noticed that only the RX2 antenna is able to sense spectrum using UHD FFT. I was not able to find a solution to this before my experiment timed out - is there any way to configure the selected antenna per node using the SHOUT automatic measurements? Or will I need to configure manual point-to-point measurements in order to collect data using MEB? 

Thank you in advance for your help! Any assistance or advice will be greatly appreciated. Let me know if there is any more information I can provide. 

My best, 

Maxwell 

[Kirk Webb]

Hello Maxwell,

Can you send a link to your profile? Under the "advanced" settings,
there may be a setting to "ignore interswitch bandwidth", or something
similar sounding. This should get you past the "not enough available
bandwidth" error. If this isn't there, then it should be easy enough
to add to the profile script.

We haven't (yet) checked on how the `cbrssdr1-meb` radio is connected
to the antenna; apologies for this as it fell off our radar. In Shout,
you will likely need to change the client startup script to exclude
the "-t" flag that tells it to use the TX/RX port for receiving (which
will have it use "RX2" instead). You can do this by editing the
"2.start_client.sh" script before running it on the compute host
paired with `cbrssdr1-meb`. As for the frequency range issue, I
believe your profile has inherited an error in the bounds checking in
the profile script. I can also advise you on what change to make here,
though it is fairly straightforward.

-Kirk

> --
> You received this message because you are subscribed to the Google Groups "Powder Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to powder-users...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/powder-users/000c1372-d59a-4a71-bfa6-426bd57facd4n%40googlegroups.com.

[Maxwell McManus]

Hi Kirk, 

Here is a link to the profile: Powder - Show Profile (powderwireless.net)

I see that there is an option to ignore the interswitch bandwidth limitations - enabling this allowed the experiment to start with all 7 nodes. 

Thank you for pointing out the "-t" flag, I will try this and see if it works. If not, at least this is a much better starting point for debugging on my own. 

I figured out that the error with frequency bounds can be avoided (most of the time) by selecting a different range (i.e. 3500-3510), moving to the "3. Finalize" step, then returning to the "2. Parameterize" step. I'm using the "shout-long-2024" profile directly, so I'm not sure if I can make public changes, but it would still be helpful to have an idea of how to fix this so I can copy the profile and avoid this in the future. 

Thank you for your help!

My best, 

Maxwell 

You received this message because you are subscribed to a topic in the Google Groups "Powder Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/powder-users/x-FV4tDfROM/unsubscribe.
To unsubscribe from this group and all its topics, send an email to powder-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/powder-users/CAFKO4CEdZr7qsujFPyXBtnojT-DkDtFPNtxMtVVrwdBWm_ZBbw%40mail.gmail.com.

[Kirk Webb]

I will check with the individual that owns the profile you are using
to see about fixing the issue with frequency bounds checking.

-Kirk

On Mon, Jul 1, 2024 at 10:30 AM Maxwell McManus

> To view this discussion on the web visit https://groups.google.com/d/msgid/powder-users/CAHL-zh2s14iioe1wixhYpkr2zf57zmCUkLwcBqRAs48SeY3yuw%40mail.gmail.com.