Testing run_cgf_demo on target

Hi @SivaRamaKrishnaNV, I accepted the answer before as you mentioned, any custom node integration gets logged, however we still facing issues with display.

powering off/on was the only option before, when it was irresponsive I tried with remmina vnc to have a dispaly remotely, still the same issue.

roadrunner is a black screen and launcher exit status is 33.

Hi @SivaRamaKrishnaNV friendly ping for any idea you have on this yet.

Dear @ashwin.nanda ,
I see log level is still DW_LOG_ERROR in the picture you have shared. Please use sudo ./run_cgf_demo.sh --loglevel DW_LOG_VERBOSE to enabled verbose logs. Then, I would expect to see the prints from HelloWorldNodeImpl.cpp/SumNodeImpl.cpp in camera_pipeline0.log to confirm if the nodes are executed.

Please double check the modified files with the files I have shared. I would expect the application to work with the steps I have provided on freshly installed machine.

Note: Please use text messages instead of pictures for logs while posting. This helps others in the community to search.

Hello @SivaRamaKrishnaNV ,
We are running the script as you have mentioned, please find the message while running the script below

sudo ./run_cgf_demo.sh --loglevel DW_LOG_VERBOSE
20241009_140431
20241009_140431
DW_TOP_PATH=/usr/local/driveworks
RR_TOP_PATH=/usr/local/driveworks/apps/roadrunner-2.0
CGF_SYS_PATH=/usr/local/driveworks/apps/cgf_demo
RR_LOG_PATH=/usr/local/driveworks-5.14/bin/LogFolder
RR_RUN_CFG_PATH=/usr/local/driveworks-5.14/bin/RunFolder
DATA_PATH=
Current DISPLAY is :1
fs.mqueue.msg_max = 4096
|–> Tuning network stack
LD_LIBRARY_PATH: /usr/local/driveworks/apps/roadrunner-2.0:/usr/local/driveworks/src/cgf/nodes:/usr/local/driveworks/bin::/usr/local/driveworks/lib
/usr/local/driveworks-5.14/bin/LogFolder dir exists
/usr/local/driveworks-5.14/bin/RunFolder dir exists
total 12
drwxr-xr-x. 3 root root 4096 Sep 30 15:10 .
drwxr-xr-x. 5 root root 4096 Sep 30 15:10 …
drwxr-xr-x. 3 root root 4096 Sep 30 15:10 config
Running command: /usr/local/driveworks/bin/launcher --binPath=/usr/local/driveworks/bin --spec=/usr/local/driveworks/apps/cgf_demo/CGFDemo.app.json --logPath=/usr/local/driveworks-5.14/bin/LogFolder --dwdatapath=/usr/local/driveworks/data --schedule=/usr/local/driveworks/apps/cgf_demo/CGFDemo__standardSchedule.stm,/usr/local/driveworks/apps/cgf_demo/CGFDemo__slowSchedule.stm --start_timestamp=0 --loglevel=DW_LOG_VERBOSE --fullscreen=1 --winSizeW=1280 --winSizeH=800 --disableStmControlLogger=1 --gdb_debug=0 --app_parameter= --useLCM=0 --datapath=/usr/local/driveworks/data/samples/cgf/trafficlightturning-hyperion8 --mapPath=maps/sample/sanjose_loop --path=/usr/local/driveworks/apps/roadrunner-2.0 --virtual=1 > /usr/local/driveworks-5.14/bin/LogFolder/launcher.log 2>&1
Check if reset NetworkStack needed
Restore LD_LIBRARY_PATH to
=======================================================================
launcher exit status: 33

Please find the LogFolder of the same below for your reference. Issue still persists, display cant be seen after the script is run.
LogFolder.zip (3.7 MB)

follow this to run your first minimal cgf app with just HelloworldNode and SumNode and multiple transport tested including nvsci.
nv_driveworks/README_en.md at main · ZhenshengLee/nv_driveworks (github.com)

Hi @SivaRamaKrishnaNV any updates so far? we would like to have the insight.

Dear @ashwin.nanda ,
From camera_pipeline0_0.log , I notice the SumNode and HelloWorldNode are executed only once.

<13>1 2024-10-09T14:05:07.552047Z - camera_pipeline0 33418 - - [1728482624924711us][DEBUG][tid:28][HelloWorldNodeImpl.cpp:78][HelloWorldNode] [Epoch 0] Sent value0 = 0
<13>1 2024-10-09T14:05:07.552105Z - camera_pipeline0 33418 - - [1728482624924775us][DEBUG][tid:28][HelloWorldNodeImpl.cpp:82][HelloWorldNode] [Epoch 0] Sent value1 = 10000
<13>1 2024-10-09T14:05:07.552122Z - camera_pipeline0 33418 - - [1728482624924792us][DEBUG][tid:28][HelloWorldNodeImpl.cpp:85][HelloWorldNode] [Epoch 0] Greetings from HelloWorldNodeImpl: Hello Demo!
<13>1 2024-10-09T14:05:07.552173Z - camera_pipeline0 33418 - - [1728482624924843us][DEBUG][tid:28][SumNodeImpl.cpp:72][SumNode] [Epoch 0] Received 0 from input VALUE_0, received 10000 from input VALUE_1. Add together: 10000!

Do you notice the same after system poweroff/on? If so, can you please re-install CGF packages and double check if CGF Demo working properly before trying modifications. Also, check adding --offscreen=1 to confirm if display is causing the app to be failed.

Hello @SivaRamaKrishnaNV

sudo ./run_cgf_demo.sh --loglevel DW_LOG_VERBOSE
20241023_124047
20241023_124047
DW_TOP_PATH=/usr/local/driveworks
RR_TOP_PATH=/usr/local/driveworks/apps/roadrunner-2.0
CGF_SYS_PATH=/usr/local/driveworks/apps/cgf_demo
RR_LOG_PATH=/usr/local/driveworks-5.14/bin/LogFolder
RR_RUN_CFG_PATH=/usr/local/driveworks-5.14/bin/RunFolder
DATA_PATH=
Current DISPLAY is :1
fs.mqueue.msg_max = 4096
|–> Tuning network stack
LD_LIBRARY_PATH: /usr/local/driveworks/apps/roadrunner-2.0:/usr/local/driveworks/src/cgf/nodes:/usr/local/driveworks/bin::/usr/local/driveworks/lib
/usr/local/driveworks-5.14/bin/LogFolder dir exists
/usr/local/driveworks-5.14/bin/RunFolder dir exists
total 12
drwxr-xr-x. 3 root root 4096 Sep 30 16:10 .
drwxr-xr-x. 5 root root 4096 Sep 30 16:10 …
drwxr-xr-x. 3 root root 4096 Sep 30 16:10 config
Running command: /usr/local/driveworks/bin/launcher --binPath=/usr/local/driveworks/bin --spec=/usr/local/driveworks/apps/cgf_demo/CGFDemo.app.json --logPath=/usr/local/driveworks-5.14/bin/LogFolder --dwdatapath=/usr/local/driveworks/data --schedule=/usr/local/driveworks/apps/cgf_demo/CGFDemo__standardSchedule.stm,/usr/local/driveworks/apps/cgf_demo/CGFDemo__slowSchedule.stm --start_timestamp=0 --loglevel=DW_LOG_VERBOSE --fullscreen=1 --offscreen=1 --winSizeW=1280 --winSizeH=800 --disableStmControlLogger=1 --gdb_debug=0 --app_parameter= --useLCM=0 --datapath=/usr/local/driveworks/data/samples/cgf/trafficlightturning-hyperion8 --mapPath=maps/sample/sanjose_loop --path=/usr/local/driveworks/apps/roadrunner-2.0 --virtual=1 > /usr/local/driveworks-5.14/bin/LogFolder/launcher.log 2>&1
Check if reset NetworkStack needed
Restore LD_LIBRARY_PATH to
=======================================================================
launcher exit status: 0

We have added --offscreen=1 in this script.
Please find the attached LogFolder for your reference
LogFolder.tar.gz (2.3 MB)

Dear @ashwin.nanda,
Looks like sample working without any issue when display is disabled(–offscreen=1) .
Other DW samples working which need GUI output?

Hello @SivaRamaKrishnaNV

Yes, when we are running another sample it is showing us display. Even when running the sample CGF it is showing but when we are implementing custom node (helloworldnode and sumnode) there is no display at that time.

Dear @prit.shah ,
Make sure you are running the application in the same window where export DISPLAY:=0 is set when tested using VNC. I don’t see any issue with VNC viewer client from host.

Hello @SivaRamaKrishnaNV

After passing this argument we are getting another error mentioned below

> sudo ./run_cgf_demo.sh --loglevel DW_LOG_VERBOSE
> 20241029_105149
> 20241029_105149
> DW_TOP_PATH=/usr/local/driveworks
> RR_TOP_PATH=/usr/local/driveworks/apps/roadrunner-2.0
> CGF_SYS_PATH=/usr/local/driveworks/apps/cgf_demo
> RR_LOG_PATH=/usr/local/driveworks-5.14/bin/LogFolder
> RR_RUN_CFG_PATH=/usr/local/driveworks-5.14/bin/RunFolder
> DATA_PATH=
> Current DISPLAY is :0
> fs.mqueue.msg_max = 4096
> |–> Tuning network stack
> LD_LIBRARY_PATH: /usr/local/driveworks/apps/roadrunner-2.0:/usr/local/driveworks/src/cgf/nodes:/usr/local/driveworks/bin::/usr/local/driveworks/lib
> /usr/local/driveworks-5.14/bin/LogFolder dir exists
> /usr/local/driveworks-5.14/bin/RunFolder dir exists
> total 12
> drwxr-xr-x. 3 root root 4096 Sep 30 16:10 .
> drwxr-xr-x. 5 root root 4096 Sep 30 16:10 …
> drwxr-xr-x. 3 root root 4096 Sep 30 16:10 config
> Running command: /usr/local/driveworks/bin/launcher --binPath=/usr/local/driveworks/bin --spec=/usr/local/driveworks/apps/cgf_demo/CGFDemo.app.json --logPath=/usr/local/driveworks-5.14/bin/LogFolder --dwdatapath=/usr/local/driveworks/data --schedule=/usr/local/driveworks/apps/cgf_demo/CGFDemo__standardSchedule.stm,/usr/local/driveworks/apps/cgf_demo/CGFDemo__slowSchedule.stm --start_timestamp=0 --loglevel=DW_LOG_VERBOSE --fullscreen=1 --winSizeW=1280 --winSizeH=800 --disableStmControlLogger=1 --gdb_debug=0 --app_parameter= --useLCM=0 --datapath=/usr/local/driveworks/data/samples/cgf/trafficlightturning-hyperion8 --mapPath=maps/sample/sanjose_loop --path=/usr/local/driveworks/apps/roadrunner-2.0 --virtual=1 > /usr/local/driveworks-5.14/bin/LogFolder/launcher.log 2>&1
> Check if reset NetworkStack needed
**> Restore LD_LIBRARY_PATH to **
> =======================================================================
> launcher exit status: 217

Hello @SivaRamaKrishnaNV ,

can we have an update on this?

Hello @SivaRamaKrishnaNV

Is there any update on this ?