[USRP-users] TX from N310 External LO Error

2022-11-30 Thread Jonathan Tobin 
Hello all - I am trying to transmit a test waveform from an N310 using the 
sample program tx_waveforms. When I set "tx_lo_source=external" I get the error 
below. When I set it to internal, the program runs smoothly, but there is no 
output. I am supplying an external LO at twice the desired output frequency. I 
am using uhd 4.3.0.0.


./tx_waveforms --args 
"addr=192.168.10.2,master_clock_rate=153.6e6,tx_lo_source=external" --freq 1e9 
--gain 10 --bw 1e6 --rate 9.6e6 --subdev "A:1" --channels "0" --wave-freq 100e3

Creating the usrp device with: 
addr=192.168.10.2,master_clock_rate=153.6e6,tx_lo_source=external...
[INFO] [UHD] linux; GNU C++ version 7.5.0; Boost_106501; 
UHD_4.3.0.HEAD-0-g1f8fd345
[INFO] [MPMD] Initializing 1 device(s) in parallel with args: 
mgmt_addr=192.168.10.2,type=n3xx,product=n310,serial=3218B5F,name=ni-n3xx-3218B5F,fpga=HG,claimed=False,addr=192.168.10.2,master_clock_rate=153.6e6,tx_lo_source=external
[INFO] [MPM.PeriphManager] init() called with device args 
`fpga=HG,master_clock_rate=153.6e6,mgmt_addr=192.168.10.2,name=ni-n3xx-3218B5F,product=n310,tx_lo_source=external,clock_source=internal,time_source=internal'.
[ERROR] [RPC] RuntimeError: MYKONOS_waitInitCals() returned an ARM error

[ERROR] [MPM.RPCServer] init() failed with error: RuntimeError: 
MYKONOS_waitInitCals() returned an ARM error

Error: RuntimeError: Error during RPC call to `init'. Error message: 
RuntimeError: MYKONOS_waitInitCals() returned an ARM error



Thanks,
Jonathan
___
USRP-users mailing list -- usrp-users@lists.ettus.com
To unsubscribe send an email to usrp-users-le...@lists.ettus.com

[USRP-users] Re: TX from N310 External LO Error

2022-11-30 Thread Rob Kossler 
Hi Jonathan,
At startup, the init_cal will always be conducted at 2.5GHz requiring an
external LO at 5 GHz.  After the init cal, then you can re-tune your
external LO to twice the desired operating frequency.  It wasn't clear to
me from your comment if your external LO is initially configured to 5 GHz
or to 2 GHz.  If the latter, try with 5 GHz and if startup occurs
correctly, retune it to 2 GHz after that point.
Rob

On Wed, Nov 30, 2022 at 1:43 PM Jonathan Tobin 
wrote:

> Hello all - I am trying to transmit a test waveform from an N310 using the
> sample program tx_waveforms. When I set "tx_lo_source=external" I get the
> error below. When I set it to internal, the program runs smoothly, but
> there is no output. I am supplying an external LO at twice the desired
> output frequency. I am using uhd 4.3.0.0.
>
>
> ./tx_waveforms --args
> "addr=192.168.10.2,master_clock_rate=153.6e6,tx_lo_source=external" --freq
> 1e9 --gain 10 --bw 1e6 --rate 9.6e6 --subdev "A:1" --channels "0"
> --wave-freq 100e3
>
> Creating the usrp device with:
> addr=192.168.10.2,master_clock_rate=153.6e6,tx_lo_source=external...
> [INFO] [UHD] linux; GNU C++ version 7.5.0; Boost_106501;
> UHD_4.3.0.HEAD-0-g1f8fd345
> [INFO] [MPMD] Initializing 1 device(s) in parallel with args:
> mgmt_addr=192.168.10.2,type=n3xx,product=n310,serial=3218B5F,name=ni-n3xx-3218B5F,fpga=HG,claimed=False,addr=192.168.10.2,master_clock_rate=153.6e6,tx_lo_source=external
> [INFO] [MPM.PeriphManager] init() called with device args
> `fpga=HG,master_clock_rate=153.6e6,mgmt_addr=192.168.10.2,name=ni-n3xx-3218B5F,product=n310,tx_lo_source=external,clock_source=internal,time_source=internal'.
> [ERROR] [RPC] RuntimeError: MYKONOS_waitInitCals() returned an ARM error
>
> [ERROR] [MPM.RPCServer] init() failed with error: RuntimeError:
> MYKONOS_waitInitCals() returned an ARM error
>
> Error: RuntimeError: Error during RPC call to `init'. Error message:
> RuntimeError: MYKONOS_waitInitCals() returned an ARM error
>
>
>
> Thanks,
> Jonathan
> ___
> USRP-users mailing list -- usrp-users@lists.ettus.com
> To unsubscribe send an email to usrp-users-le...@lists.ettus.com
>
___
USRP-users mailing list -- usrp-users@lists.ettus.com
To unsubscribe send an email to usrp-users-le...@lists.ettus.com

[USRP-users] Re: TX from N310 External LO Error

2022-11-30 Thread Marcus D. Leech 

On 30/11/2022 17:46, Rob Kossler wrote:

Hi Jonathan,
At startup, the init_cal will always be conducted at 2.5GHz 
requiring an external LO at 5 GHz.  After the init cal, then you can 
re-tune your external LO to twice the desired operating frequency.  It 
wasn't clear to me from your comment if your external LO is initially 
configured to 5 GHz or to 2 GHz.  If the latter, try with 5 GHz and if 
startup occurs correctly, retune it to 2 GHz after that point.

Rob
It has also been suggested to use "init_cals=BASIC" in the device 
argument in this situation.  It's not clear to me exactly what

  that does.




On Wed, Nov 30, 2022 at 1:43 PM Jonathan Tobin 
 wrote:


Hello all - I am trying to transmit a test waveform from an N310
using the sample program tx_waveforms. When I set
"tx_lo_source=external" I get the error below. When I set it to
internal, the program runs smoothly, but there is no output. I am
supplying an external LO at twice the desired output frequency. I
am using uhd 4.3.0.0.


./tx_waveforms --args
"addr=192.168.10.2,master_clock_rate=153.6e6,tx_lo_source=external"
--freq 1e9 --gain 10 --bw 1e6 --rate 9.6e6 --subdev "A:1"
--channels "0" --wave-freq 100e3

Creating the usrp device with:
addr=192.168.10.2,master_clock_rate=153.6e6,tx_lo_source=external...
[INFO] [UHD] linux; GNU C++ version 7.5.0; Boost_106501;
UHD_4.3.0.HEAD-0-g1f8fd345
[INFO] [MPMD] Initializing 1 device(s) in parallel with args:

mgmt_addr=192.168.10.2,type=n3xx,product=n310,serial=3218B5F,name=ni-n3xx-3218B5F,fpga=HG,claimed=False,addr=192.168.10.2,master_clock_rate=153.6e6,tx_lo_source=external
[INFO] [MPM.PeriphManager] init() called with device args

`fpga=HG,master_clock_rate=153.6e6,mgmt_addr=192.168.10.2,name=ni-n3xx-3218B5F,product=n310,tx_lo_source=external,clock_source=internal,time_source=internal'.
[ERROR] [RPC] RuntimeError: MYKONOS_waitInitCals() returned an ARM
error

[ERROR] [MPM.RPCServer] init() failed with error: RuntimeError:
MYKONOS_waitInitCals() returned an ARM error

Error: RuntimeError: Error during RPC call to `init'. Error
message: RuntimeError: MYKONOS_waitInitCals() returned an ARM error



Thanks,
Jonathan
___
USRP-users mailing list -- usrp-users@lists.ettus.com
To unsubscribe send an email to usrp-users-le...@lists.ettus.com


___
USRP-users mailing list --usrp-users@lists.ettus.com
To unsubscribe send an email tousrp-users-le...@lists.ettus.com
___
USRP-users mailing list -- usrp-users@lists.ettus.com
To unsubscribe send an email to usrp-users-le...@lists.ettus.com

[USRP-users] Re: TX from N310 External LO Error

2022-11-30 Thread Kenneth Burchfield 
Hi Jonathan,

What Rob said is correct.  You need to supply a 5 GHz LO initially so that
the startup calibrations for the N310 will be correct.  However, if I
recall correctly, the device should still initialize even with an LO not
equal to 5 GHz (though your going to see imaging / possible LO leakage in
the frequency domain if this is the case).

Is your LO power within spec of the device?  The ad9371 requires an
external LO between +0 dBm and +6 dBm with higher frequencies requiring
higher power.  Providing an LO below that power spec will give you the
MYKONOS_waitInitCals() error.

If you are within that spec, then you can modify your init_cals and
incrementally test adding calibrations until you figure out which
calibration is throwing the error.  So your args would look like this
initially ( --args
"addr=192.168.10.2,master_clock_rate=153.6e6,tx_lo_source=external,init_cals=BASIC")
and then you can add more init_cals by doing
init_cals=BASIC|TX_ATTENUATION_DELAY|PATH_DELAY etc.  The | is the append
operation.  The calibrations are listed in the link below.

https://files.ettus.com/manual/page_usrp_n3xx.html#n3xx_mg_calibrations

Hope this helps
Scott

On Wed, Nov 30, 2022 at 4:48 PM Rob Kossler  wrote:

> Hi Jonathan,
> At startup, the init_cal will always be conducted at 2.5GHz requiring an
> external LO at 5 GHz.  After the init cal, then you can re-tune your
> external LO to twice the desired operating frequency.  It wasn't clear to
> me from your comment if your external LO is initially configured to 5 GHz
> or to 2 GHz.  If the latter, try with 5 GHz and if startup occurs
> correctly, retune it to 2 GHz after that point.
> Rob
>
> On Wed, Nov 30, 2022 at 1:43 PM Jonathan Tobin 
> wrote:
>
>> Hello all - I am trying to transmit a test waveform from an N310 using
>> the sample program tx_waveforms. When I set "tx_lo_source=external" I get
>> the error below. When I set it to internal, the program runs smoothly, but
>> there is no output. I am supplying an external LO at twice the desired
>> output frequency. I am using uhd 4.3.0.0.
>>
>>
>> ./tx_waveforms --args
>> "addr=192.168.10.2,master_clock_rate=153.6e6,tx_lo_source=external" --freq
>> 1e9 --gain 10 --bw 1e6 --rate 9.6e6 --subdev "A:1" --channels "0"
>> --wave-freq 100e3
>>
>> Creating the usrp device with:
>> addr=192.168.10.2,master_clock_rate=153.6e6,tx_lo_source=external...
>> [INFO] [UHD] linux; GNU C++ version 7.5.0; Boost_106501;
>> UHD_4.3.0.HEAD-0-g1f8fd345
>> [INFO] [MPMD] Initializing 1 device(s) in parallel with args:
>> mgmt_addr=192.168.10.2,type=n3xx,product=n310,serial=3218B5F,name=ni-n3xx-3218B5F,fpga=HG,claimed=False,addr=192.168.10.2,master_clock_rate=153.6e6,tx_lo_source=external
>> [INFO] [MPM.PeriphManager] init() called with device args
>> `fpga=HG,master_clock_rate=153.6e6,mgmt_addr=192.168.10.2,name=ni-n3xx-3218B5F,product=n310,tx_lo_source=external,clock_source=internal,time_source=internal'.
>> [ERROR] [RPC] RuntimeError: MYKONOS_waitInitCals() returned an ARM error
>>
>> [ERROR] [MPM.RPCServer] init() failed with error: RuntimeError:
>> MYKONOS_waitInitCals() returned an ARM error
>>
>> Error: RuntimeError: Error during RPC call to `init'. Error message:
>> RuntimeError: MYKONOS_waitInitCals() returned an ARM error
>>
>>
>>
>> Thanks,
>> Jonathan
>> ___
>> USRP-users mailing list -- usrp-users@lists.ettus.com
>> To unsubscribe send an email to usrp-users-le...@lists.ettus.com
>>
> ___
> USRP-users mailing list -- usrp-users@lists.ettus.com
> To unsubscribe send an email to usrp-users-le...@lists.ettus.com
>
___
USRP-users mailing list -- usrp-users@lists.ettus.com
To unsubscribe send an email to usrp-users-le...@lists.ettus.com

[USRP-users] Re: TX from N310 External LO Error

2022-11-30 Thread Jonathan Tobin 
Thanks for the responses everyone. Adding the "init_cals=BASIC" argument got 
rid of the error (I suppose a band-aid until I can grab a higher frequency sig 
gen). I was only supplying a 2 GHz signal, but it was at +3 dBm. I'll have to 
experiment the power.

Thanks for the help.


Thanks,
Jonathan

From: Kenneth Burchfield 
Sent: Wednesday, November 30, 2022 4:20 PM
To: Rob Kossler 
Cc: Jonathan Tobin ; usrp-users 

Subject: Re: [USRP-users] Re: TX from N310 External LO Error

Hi Jonathan,

What Rob said is correct.  You need to supply a 5 GHz LO initially so that the 
startup calibrations for the N310 will be correct.  However, if I recall 
correctly, the device should still initialize even with an LO not equal to 5 
GHz (though your going to see imaging / possible LO leakage in the frequency 
domain if this is the case).

Is your LO power within spec of the device?  The ad9371 requires an external LO 
between +0 dBm and +6 dBm with higher frequencies requiring higher power.  
Providing an LO below that power spec will give you the MYKONOS_waitInitCals() 
error.

If you are within that spec, then you can modify your init_cals and 
incrementally test adding calibrations until you figure out which calibration 
is throwing the error.  So your args would look like this initially ( --args 
"addr=192.168.10.2,master_clock_rate=153.6e6,tx_lo_source=external,init_cals=BASIC")
  and then you can add more init_cals by doing 
init_cals=BASIC|TX_ATTENUATION_DELAY|PATH_DELAY etc.  The | is the append 
operation.  The calibrations are listed in the link below.

https://files.ettus.com/manual/page_usrp_n3xx.html#n3xx_mg_calibrations

Hope this helps
Scott

On Wed, Nov 30, 2022 at 4:48 PM Rob Kossler 
mailto:rkoss...@nd.edu>> wrote:
Hi Jonathan,
At startup, the init_cal will always be conducted at 2.5GHz requiring an 
external LO at 5 GHz.  After the init cal, then you can re-tune your external 
LO to twice the desired operating frequency.  It wasn't clear to me from your 
comment if your external LO is initially configured to 5 GHz or to 2 GHz.  If 
the latter, try with 5 GHz and if startup occurs correctly, retune it to 2 GHz 
after that point.
Rob

On Wed, Nov 30, 2022 at 1:43 PM Jonathan Tobin 
mailto:to...@augustusaero.com>> wrote:
Hello all - I am trying to transmit a test waveform from an N310 using the 
sample program tx_waveforms. When I set "tx_lo_source=external" I get the error 
below. When I set it to internal, the program runs smoothly, but there is no 
output. I am supplying an external LO at twice the desired output frequency. I 
am using uhd 4.3.0.0.


./tx_waveforms --args 
"addr=192.168.10.2,master_clock_rate=153.6e6,tx_lo_source=external" --freq 1e9 
--gain 10 --bw 1e6 --rate 9.6e6 --subdev "A:1" --channels "0" --wave-freq 100e3

Creating the usrp device with: 
addr=192.168.10.2,master_clock_rate=153.6e6,tx_lo_source=external...
[INFO] [UHD] linux; GNU C++ version 7.5.0; Boost_106501; 
UHD_4.3.0.HEAD-0-g1f8fd345
[INFO] [MPMD] Initializing 1 device(s) in parallel with args: 
mgmt_addr=192.168.10.2,type=n3xx,product=n310,serial=3218B5F,name=ni-n3xx-3218B5F,fpga=HG,claimed=False,addr=192.168.10.2,master_clock_rate=153.6e6,tx_lo_source=external
[INFO] [MPM.PeriphManager] init() called with device args 
`fpga=HG,master_clock_rate=153.6e6,mgmt_addr=192.168.10.2,name=ni-n3xx-3218B5F,product=n310,tx_lo_source=external,clock_source=internal,time_source=internal'.
[ERROR] [RPC] RuntimeError: MYKONOS_waitInitCals() returned an ARM error

[ERROR] [MPM.RPCServer] init() failed with error: RuntimeError: 
MYKONOS_waitInitCals() returned an ARM error

Error: RuntimeError: Error during RPC call to `init'. Error message: 
RuntimeError: MYKONOS_waitInitCals() returned an ARM error



Thanks,
Jonathan
___
USRP-users mailing list -- 
usrp-users@lists.ettus.com
To unsubscribe send an email to 
usrp-users-le...@lists.ettus.com
___
USRP-users mailing list -- 
usrp-users@lists.ettus.com
To unsubscribe send an email to 
usrp-users-le...@lists.ettus.com
___
USRP-users mailing list -- usrp-users@lists.ettus.com
To unsubscribe send an email to usrp-users-le...@lists.ettus.com