I have been doing development with the PX4 Matlab Toolbox. I use a custom startup script to launch the apps I need to use. Yesterday, I lost the ability to send commands in the NSH terminal but I can still see the output during startup. If I reboot the pixhawk without the SD card and custom startup script I can access the shell correctly. Can someone please identify where my startup script is conflicting with the shell?
usleep 1000 uorb start usleep 1000 #nshterm /dev/ttyACM0 & #usleep 1000 px4io start usleep 1000 #commander start #usleep 1000 #mavlink start -d /dev/ttyS2 -b 57600 #usleep 5000 #dataman start #usleep 1000 #navigator start #usleep 1000 sh /etc/init.d/rc.sensors usleep 1000 #sh /etc/init.d/rc.logging #usleep 1000 #gps start #attitude_estimator_q start ekf2 start #position_estimator_inav start usleep 1000 mtd start usleep 1000 param load /fs/mtd_params usleep 1000 rgbled start usleep 1000 nshterm /dev/ttyS6 & #this will make ttyS6 the serial console usleep 1000 px4_simulink_app start exit
EDIT: So I performed some debug tests. I had access to the shell when “position_estimator_inav start” was enabled because it caused the script to error out? After commenting that out, I start commenting out different commands but still have the same issue where I am unable to send NSH commands.