Use of the NVIDIA Jetson Nano for DATV

[g0mjw]

When did you download the Nano software? It has changed recently. You need to change a few things in config files on the PI too.

Mike

[G4WIM]

EDIT - some success

re-installed the F5OEO scripts and accepted the newer ffmpeg stuff and it now works with the Picam - hurray.

Tried it with Portsdown and while it controls the settings there's no sign of any video program or provider info - very odd, almost like there's a network or switch issue ?


Regards Tim

##################################

Tried the Nano Lime stand alone with Picam and usb mike plugged - same as before so it's pointing toward the Nano.

Here's what the screen shows when I enter the tx script with a 333kS request.

Looks like on line 39 it's not finding ffmpeg which maybe related to me not accepting the updated ffmpeg when building the Nano code ?
======================

Regards Tim

tim@192.168.1.26:~/dvbsdr/scripts$ ./jetson_nano.sh
DVB LongFrame
Frame Size=64800
Net TS bitrate input should be 329289

VideoBitrate = 188037
VideoPeakBitrate = 206840
./include/nanoencode.sh: line 39: ffmpeg: command not found
DVB LongFrame
Frame Size=64800
Net TS bitrate input should be 329289
Using live mode
Reference clock 40.00 MHz
LimeSDR-Mini Library 19.04.0-g54614dae Firmware 5 Gateware 1.24 Temperature 45.00
TXLPF set to 5.000 MHz (requested 0.899 MHz [out of range])
ERROR: Pipeline doesn't want to pause.
ERROR: from element /GstPipeline:pipeline0/GstAlsaSrc:alsasrc0: Could not open audio device for recording. Device is being used by another application.
Additional debug info:
gstalsasrc.c(743): gst_alsasrc_open (): /GstPipeline:pipeline0/GstAlsaSrc:alsasrc0:
Device 'hw:2' is busy
Filter calibrated. Filter order-4th, filter bandwidth set to 5 MHz.Real pole 1st order filter set to 2.5 MHz. Preemphasis filter not active
TX LPF configured
Use limemini.cal Calibration
sample_rate: 665999.991553


CoefBufferSize=1
Fifo =0/129540 dropped 0 underrun 0 overrun 0 Link=0.000000
Fifo =64260/129540 dropped 0 underrun 0 overrun 0 Link=0.000000
Fifo =67320/129540 dropped 0 underrun 0 overrun 0 Link=0.000000
Fifo =71400/129540 dropped 0 underrun 0 overrun 0 Link=0.000000
Fifo =71400/129540 dropped 0 underrun 0 overrun 0 Link=0.000000
Fifo =74460/129540 dropped 0 underrun 0 overrun 0 Link=0.000000
Fifo =74460/129540 dropped 0 underrun 0 overrun 0 Link=0.000000
Fifo =58140/129540 dropped 0 underrun 0 overrun 0 Link=0.000000
Fifo =41820/129540 dropped 0 underrun 0 overrun 0 Link=0.000000
Fifo =40800/129540 dropped 0 underrun 0 overrun 0 Link=0.000000
Fifo =32640/129540 dropped 0 underrun 0 overrun 0 Link=2659952.000000

[G4WIM]

Still can't seem to get the RPI to play with the Nano so going to check network switch etc.

I do have the nano working with the PI cam - but not as well as it used to be as it seems to suffer from freezes and other artifacts whereas before it was very smooth.

On the terminal connected to the nano I get a lot of these every few seconds:

[mpegts @ 0x556c97e430] dts < pcr, TS is invalid00:40:32.89 bitrate= 329.3kbits/s speed=0.999x
[mpegts @ 0x556c97e430] dts < pcr, TS is invalid00:40:36.60 bitrate= 329.3kbits/s speed=0.999x

Any idea as to what's going on or if this is 'normal' ?

Regards Tim

[G4WIM]

Further to this saga despite the RPI being able to control the Lime via the Nano - ie set freq tx / rx and shut down thus showing connectivity thru' the network when I enter M3 on the RPI and request info about the Lime FW info it reports no available device.

I've tried replacing the switch which handles the Nano, LKV, RPI and PC running OBS but same results.

I've rebuilt the rpi using release 201906060

Very odd - running out of ideas.....

Regards Tim

[G4WIM]

Hi Mike,

I've followed the instructions provided by Dave at the top of this thread which downloads the F5OEO code from github so I guess I have the latest version.

On the rpi I've entered all the usual passwords and IP addresses via the rpi touch screen.

As I mentioned above the rpi is controlling the nano / lime nicely but no video - this despite the RPI being unable to report the Lime FW status.


Regards Tim

[M0SKM]

Hello Tim,

Sorry you are still having problems with the software.

Since my first install of Evariste's DVBSDR there has been at least one update. Because the update took place after Dave's Portsdown interface I have avoided the new DVBSDR; I wonder if there is an incompatibility which is causing your problem?

If you don't manage to sort it I can put a copy of my file image on the web for you.

73 Steve

[G4WIM]

Hi Steve,yep - sadly still having problems and have run out of ideas.

Completely rebuilt the rpi from scratch (tried both the production and dev versions) and it appears to communicate with the nano / lime but won't pass any video.

Still not sure where the problem lies nano or rpi or possibly both !

Suspect something must have changed as my first attempt just worked right out of the box - then as far as I can tell it just stopped for some reason !

I think the clue is that the rpi can't report the FW in the Lime so maybe its a gateway problem.

I took the lime and plugged it directly into the rpi and flashed the gateway to 1.29 which the rpi said was the correct version, but still no joy when plugged into the nano

If you've got any images you could share somehow that'd be great.

Regards Tim

[G4WIM]

ok so F5OEO mentioned on Jun 27 about his new version of dvbsdr but has not been integrated into Portsdown - so it could be I'm running his latest code but its not compatible with Portsdown yet ?

[G8GKQ]

Tim

I'm just back from Finningley and have been trying to go through this thread. Some initial thoughts:

• If you have the Lime plugged into the Jetson, you can't check its software from the Portsdown. It needs to be directly connected.
• There have been no relevant changes to the Portsdown software, but I haven't done a new Jetson build since I wrote the original notes, so there may have been external changes that have broken things.
• The Jetson build is not a "supported" Portsdown config, so I don't monitor for external changes (which I do for the core capability)
• There should not be any issues with 2 Portsdowns on the network. I have 3 running most of the time!
• Evariste's code has changed, but I can't see anything that might have broken things. However, I will study it later in the week.

Dave

[G4WIM]

Hi Dave,

thanks for taking a look over this rather convoluted thread which shows my attempts to resolve what I've likely broken.

Noted about the 'red herring' of not being able to show Lime FW via the rpi from the nano - which is why I did indeed connect the Lime directly to the RPI.

Reading F5OEO github it does seem as though he has updated his code but that may not be the problem - most likely something I've done or not done to screw something up.

Bottom line is that external video stream isn't making it to the Nano and I did read in his network_modulate.sh script that the external TS modulation port was 12000.

#Transport Stream from network
IP_PORT=12000

going from memory I thought it was 10000 at the rpi end - but again could be a red herring as I'm going from memory and don't have the rpi script in front of me.

Regards Tim