NUCs not available on attenuator matrix

[Ezemaduka Chibuikem]

Hello Team,

I am new to the platform and I'm attempting to test run a TX/RX experiment on the controlled RF environment (attenuator matrix) using the mobisys21-gnuradio:0 profile. While trying to instantiate the profile, the system reports that NUC5300s are unavailable, though the resource availability page indicates that NUCs (nuc1–nuc4) are free. The same issue occurs even when I attempt reservations for later dates.

Could you please confirm whether the availability page reflects the actual, current status of the hardware?

Thank you,

Chibu 

[Kirk Webb]

Hi Chibu,

I'll dig into this and get back to you once I have something.

-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 visit https://groups.google.com/d/msgid/powder-users/CAL6-zxHOkJQkgybF%2Bft2SQvTzTWMWBq9q82ciQKKChJfbZuKVg%40mail.gmail.com.

[Ezemaduka Chibuikem]

Okay, thank you

To view this discussion visit https://groups.google.com/d/msgid/powder-users/CAFKO4CFGzFmHnUCULYfduABmKb2j4qQ8AVa3jBj18ymZCm%2BNrA%40mail.gmail.com.

[Kirk Webb]

Hi Chibu,

There is an issue where the precheck thinks that no `nuc5300` nodes are available when you get to the "Schedule" step when using this profile, but they actually are.  I assume you are seeing something like this:

Try clicking "Finish"; the experiment should instantiate successfully. We are looking into the confusion in the precheck.  When making a reservation, you will need to add lines for each individual nuc5300 node you want to reserve; i.e., a reservation for `nuc1`, `nuc2`, etc. These nodes are what we call "individually reservable". They belong to a common `nuc5300` type, but are treated as distinct for the purposes of reservations, so that people can target them specifically. This is also where the precheck is getting confused, since this profile is requesting `nuc5300` nodes, not specific, individual nodes.

You will likely want to reference this page to see what is connected to what in the attenuator matrix:

  https://www.powderwireless.net/atten.php

BR,

-Kirk

To view this discussion visit https://groups.google.com/d/msgid/powder-users/CAL6-zxF1qC93azpxV39wz2yvzPPOMASwmToSeNJzENic5fgDFQ%40mail.gmail.com.

[Ezemaduka Chibuikem]

Hi Kirk,

Thank you — I’ll try again and let you know how it goes. Just to confirm, are you suggesting that I can modify the gen-lib profile source code by setting the hardware to the particular node name, for example,

rx.hardware_type = “nuc1”  instead of 

rx.hardware_type = “nuc5300”?

To view this discussion visit https://groups.google.com/d/msgid/powder-users/CAFKO4CE6U5HvL1ME0-bUe49ti2E6L%3DcvVV_%3DREa__8PMdeOqjw%40mail.gmail.com.

[Kirk Webb]

Yes, you can do this, though you would comment out:

rx.hardware_type = "nuc5300"

and add:

rx.component_id = "nucX"

BR,

-Kirk

To view this discussion visit https://groups.google.com/d/msgid/powder-users/CAL6-zxHHZhY-%3Dx1%3DoK28tGKQ4H0Be%2Btghf9K_LfVXk1nPKO%2BRA%40mail.gmail.com.