TRIGGERcmd
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login

    Tentando Executar um Script python no terminal LX com o TriggerCMD mas não estou conseguindo

    Raspberry Pi
    2
    80
    4.9k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • Antonio Francisco S.SantosA
      Antonio Francisco S.Santos @Antonio Francisco S.Santos
      last edited by

      @Antonio-Francisco-S-Santos UID PID PPID C STIME TTY TIME CMD
      root 1 0 0 16:44 ? 00:00:04 /sbin/init splash
      root 2 0 0 16:44 ? 00:00:00 [kthreadd]
      root 3 2 0 16:44 ? 00:00:00 [rcu_gp]
      root 4 2 0 16:44 ? 00:00:00 [rcu_par_gp]
      root 8 2 0 16:44 ? 00:00:00 [mm_percpu_wq]
      root 9 2 0 16:44 ? 00:00:00 [rcu_tasks_rude_]
      root 10 2 0 16:44 ? 00:00:00 [rcu_tasks_trace]
      root 11 2 0 16:44 ? 00:00:00 [ksoftirqd/0]
      root 12 2 0 16:44 ? 00:00:07 [rcu_sched]
      root 13 2 0 16:44 ? 00:00:00 [migration/0]
      root 14 2 0 16:44 ? 00:00:00 [cpuhp/0]
      root 15 2 0 16:44 ? 00:00:00 [cpuhp/1]
      root 16 2 0 16:44 ? 00:00:00 [migration/1]
      root 17 2 0 16:44 ? 00:00:00 [ksoftirqd/1]
      root 20 2 0 16:44 ? 00:00:00 [cpuhp/2]
      root 21 2 0 16:44 ? 00:00:00 [migration/2]
      root 22 2 0 16:44 ? 00:00:00 [ksoftirqd/2]
      root 25 2 0 16:44 ? 00:00:00 [cpuhp/3]
      root 26 2 0 16:44 ? 00:00:00 [migration/3]
      root 27 2 0 16:44 ? 00:00:00 [ksoftirqd/3]
      root 29 2 0 16:44 ? 00:00:00 [kworker/3:0H-kblockd]
      root 30 2 0 16:44 ? 00:00:00 [kdevtmpfs]
      root 31 2 0 16:44 ? 00:00:00 [netns]
      root 33 2 0 16:44 ? 00:00:00 [kworker/1:1-events]
      root 34 2 0 16:44 ? 00:00:00 [kauditd]
      root 36 2 0 16:44 ? 00:00:00 [khungtaskd]
      root 37 2 0 16:44 ? 00:00:00 [oom_reaper]
      root 38 2 0 16:44 ? 00:00:00 [writeback]
      root 39 2 0 16:44 ? 00:00:00 [kcompactd0]
      root 59 2 0 16:44 ? 00:00:00 [kblockd]
      root 60 2 0 16:44 ? 00:00:00 [blkcg_punt_bio]
      root 61 2 0 16:44 ? 00:00:00 [watchdogd]
      root 62 2 0 16:44 ? 00:00:00 [kworker/0:1H-mmc_complete]
      root 63 2 0 16:44 ? 00:00:00 [rpciod]
      root 65 2 0 16:44 ? 00:00:00 [xprtiod]
      root 66 2 0 16:44 ? 00:00:00 [kswapd0]
      root 67 2 0 16:44 ? 00:00:00 [nfsiod]
      root 68 2 0 16:44 ? 00:00:00 [kthrotld]
      root 71 2 0 16:44 ? 00:00:00 [iscsi_eh]
      root 72 2 0 16:44 ? 00:00:00 [iscsi_destroy]
      root 73 2 0 16:44 ? 00:00:00 [nvme-wq]
      root 74 2 0 16:44 ? 00:00:00 [nvme-reset-wq]
      root 75 2 0 16:44 ? 00:00:00 [nvme-delete-wq]
      root 78 2 0 16:44 ? 00:00:00 [DWC Notificatio]
      root 79 2 0 16:44 ? 00:00:00 [uas]
      root 80 2 0 16:44 ? 00:00:07 [vchiq-slot/0]
      root 81 2 0 16:44 ? 00:00:00 [vchiq-recy/0]
      root 82 2 0 16:44 ? 00:00:00 [vchiq-sync/0]
      root 83 2 0 16:44 ? 00:00:00 [zswap-shrink]
      root 86 2 0 16:44 ? 00:00:01 [kworker/0:5-mm_percpu_wq]
      root 87 2 0 16:44 ? 00:00:00 [sdhci]
      root 88 2 0 16:44 ? 00:00:00 [irq/49-mmc0]
      root 90 2 0 16:44 ? 00:00:00 [mmc_complete]
      root 91 2 0 16:44 ? 00:00:00 [kworker/1:1H-kblockd]
      root 92 2 0 16:44 ? 00:00:00 [kworker/1:2H-kblockd]
      root 93 2 0 16:44 ? 00:00:00 [jbd2/mmcblk0p2-]
      root 94 2 0 16:44 ? 00:00:00 [ext4-rsv-conver]
      root 97 2 0 16:44 ? 00:00:00 [ipv6_addrconf]
      root 98 2 0 16:44 ? 00:00:00 [kworker/3:2-mm_percpu_wq]
      root 113 2 0 16:44 ? 00:00:00 [kworker/3:2H-kblockd]
      root 115 2 0 16:44 ? 00:00:00 [kworker/2:2H-kblockd]
      root 121 1 0 16:44 ? 00:00:01 /lib/systemd/systemd-journald
      root 160 1 0 16:44 ? 00:00:00 /lib/systemd/systemd-udevd
      root 204 2 0 16:44 ? 00:00:00 [vchiq-keep/0]
      root 207 2 0 16:44 ? 00:00:00 [SMIO]
      root 221 2 0 16:44 ? 00:00:00 [mmal-vchiq]
      root 223 2 0 16:44 ? 00:00:00 [mmal-vchiq]
      root 226 2 0 16:44 ? 00:00:00 [mmal-vchiq]
      root 270 2 0 16:44 ? 00:00:00 [cfg80211]
      root 273 2 0 16:44 ? 00:00:00 [brcmf_wq/mmc1:0]
      root 275 2 0 16:44 ? 00:00:00 [brcmf_wdog/mmc1]
      root 283 2 0 16:44 ? 00:00:00 [mmal-vchiq]
      root 284 2 0 16:44 ? 00:00:00 [mmal-vchiq]
      root 285 2 0 16:44 ? 00:00:00 [mmal-vchiq]
      root 286 2 0 16:44 ? 00:00:00 [mmal-vchiq]
      systemd+ 335 1 0 16:44 ? 00:00:00 /lib/systemd/systemd-timesyncd
      root 338 1 0 16:44 ? 00:00:01 /usr/sbin/haveged --Foreground --verbose=1 -w 1024
      root 376 1 0 16:44 ? 00:00:00 /usr/sbin/rsyslogd -n -iNONE
      root 377 1 0 16:44 ? 00:00:04 node /usr/share/triggercmdagent/app/src/daemon.js --run /root/.TRIGGERcmdData
      root 378 1 0 16:44 ? 00:00:00 /usr/sbin/cupsd -l
      root 379 1 0 16:44 ? 00:00:00 /usr/sbin/alsactl -E HOME=/run/alsa -s -n 19 -c rdaemon
      avahi 381 1 0 16:44 ? 00:00:00 avahi-daemon: running [TonyPiPro.local]
      root 382 1 0 16:44 ? 00:00:00 /usr/sbin/ModemManager --filter-policy=strict
      root 383 1 0 16:44 ? 00:00:04 /usr/bin/python3 /home/pi/hiwonder-toolbox/hw_button_scan.py
      root 386 1 0 16:44 ? 00:00:17 /usr/bin/python3 /home/pi/hiwonder-toolbox/hw_wifi.py
      avahi 390 381 0 16:44 ? 00:00:00 avahi-daemon: chroot helper
      message+ 391 1 0 16:44 ? 00:00:00 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only
      root 396 1 0 16:44 ? 00:00:00 /usr/sbin/rngd -r /dev/hwrng
      root 401 1 0 16:44 ? 00:00:00 /usr/lib/udisks2/udisksd
      root 402 1 0 16:44 ? 00:00:00 /usr/sbin/cron -f
      root 407 1 0 16:44 ? 00:00:00 /usr/bin/python3 /home/pi/hiwonder-toolbox/hw_remote.py
      root 408 1 3 16:44 ? 00:02:20 /usr/bin/python3 /home/pi/TonyPi/TonyPi.py
      root 410 1 6 16:44 ? 00:04:06 /usr/bin/pigpiod
      nobody 416 1 0 16:44 ? 00:00:00 /usr/sbin/thd --triggers /etc/triggerhappy/triggers.d/ --socket /run/thd.socket --user nobody --deviceglob /dev/input/e
      root 417 1 0 16:44 ? 00:00:00 /lib/systemd/systemd-logind
      root 430 1 0 16:44 ? 00:00:00 /usr/bin/python3 /home/pi/hiwonder-toolbox/hw_find.py -t TONYPIPRO
      root 495 1 0 16:44 ? 00:00:00 /usr/sbin/cups-browsed
      root 505 1 0 16:44 ? 00:00:00 /usr/bin/vncserver-x11-serviced -fg
      root 516 505 0 16:44 ? 00:00:14 /usr/bin/vncserver-x11-core -service
      root 526 1 0 16:44 ? 00:00:00 /usr/sbin/sshd -D
      root 527 1 0 16:44 ? 00:00:00 /usr/lib/policykit-1/polkitd --no-debug
      root 540 1 0 16:44 ? 00:00:00 /usr/sbin/lightdm
      dnsmasq 549 1 0 16:44 ? 00:00:00 /usr/sbin/dnsmasq -x /run/dnsmasq/dnsmasq.pid -u dnsmasq -r /run/dnsmasq/resolv.conf -7 /etc/dnsmasq.d,.dpkg-dist,.dpkg
      root 629 540 2 16:44 tty7 00:01:17 /usr/lib/xorg/Xorg :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
      root 634 1 0 16:44 tty1 00:00:00 /bin/login -f
      root 643 1 0 16:44 ? 00:00:00 haveged
      root 659 1 0 16:44 ? 00:00:06 /usr/bin/vncagent service 15
      root 672 1 0 16:44 ? 00:00:00 /sbin/dhcpcd -q -b
      root 691 1 0 16:44 ? 00:00:00 wpa_supplicant -B -c/etc/wpa_supplicant/wpa_supplicant.conf -iwlan0 -Dnl80211,wext
      root 711 540 0 16:44 ? 00:00:00 lightdm --session-child 14 17
      pi 716 1 0 16:44 ? 00:00:00 /lib/systemd/systemd --user
      pi 717 716 0 16:44 ? 00:00:00 (sd-pam)
      pi 766 711 0 16:44 ? 00:00:00 /usr/bin/lxsession -s LXDE-pi -e LXDE
      pi 774 716 0 16:44 ? 00:00:00 /usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only
      pi 833 766 0 16:44 ? 00:00:00 /usr/bin/ssh-agent /usr/bin/im-launch x-session-manager
      pi 864 1 0 16:44 ? 00:00:00 /usr/bin/fcitx -d
      pi 874 1 0 16:44 ? 00:00:00 /usr/bin/dbus-daemon --syslog --fork --print-pid 5 --print-address 7 --config-file /usr/share/fcitx/dbus/daemon.conf
      pi 878 1 0 16:44 ? 00:00:00 /usr/bin/fcitx-dbus-watcher unix:path=/tmp/dbus-Wd5SygDeF8,guid=3bff97bd434c9201ce685dc464710c18 874
      pi 881 716 0 16:44 ? 00:00:00 /usr/lib/gvfs/gvfsd
      pi 886 716 0 16:44 ? 00:00:00 /usr/lib/gvfs/gvfsd-fuse /run/user/1000/gvfs -f -o big_writes
      pi 895 766 0 16:44 ? 00:00:00 openbox --config-file /home/pi/.config/openbox/lxde-pi-rc.xml
      pi 898 766 0 16:44 ? 00:00:00 lxpolkit
      pi 904 766 0 16:44 ? 00:00:27 lxpanel --profile LXDE-pi
      pi 905 766 0 16:44 ? 00:00:01 pcmanfm --desktop --profile LXDE-pi
      pi 911 1 0 16:44 ? 00:00:00 /usr/bin/ssh-agent -s
      pi 918 1 0 16:44 ? 00:00:00 /usr/bin/python3 /usr/share/system-config-printer/applet.py
      pi 929 1 0 16:44 ? 00:00:00 /usr/lib/geoclue-2.0/demos/agent
      pi 947 716 0 16:44 ? 00:00:00 /usr/bin/pulseaudio --daemonize=no
      pi 952 1 0 16:44 ? 00:00:00 /usr/bin/vncserverui service 16
      rtkit 969 1 0 16:44 ? 00:00:00 /usr/lib/rtkit/rtkit-daemon
      pi 973 952 0 16:44 ? 00:00:00 /usr/bin/vncserverui -statusicon 5
      pi 974 716 0 16:44 ? 00:00:00 /usr/lib/gvfs/gvfs-udisks2-volume-monitor
      pi 986 634 0 16:44 tty1 00:00:00 -bash
      pi 990 716 0 16:44 ? 00:00:00 /usr/lib/gvfs/gvfs-gphoto2-volume-monitor
      pi 1006 716 0 16:44 ? 00:00:00 /usr/lib/gvfs/gvfs-goa-volume-monitor
      root 1009 1 0 16:44 ? 00:00:00 /usr/bin/hciattach /dev/serial1 bcm43xx 460800 noflow -
      root 1010 2 0 16:44 ? 00:00:00 [kworker/u9:1-hci0]
      root 1012 2 0 16:44 ? 00:00:00 [kworker/u9:2-hci0]
      root 1013 1 0 16:44 ? 00:00:00 /usr/bin/python3 /home/pi/TonyPi/Extend/multi_control_server.py
      root 1015 1 0 16:44 ? 00:00:15 /usr/bin/python3 /home/pi/TonyPi/Extend/multi_control_client.py
      root 1017 1 1 16:44 ? 00:00:47 /usr/bin/python3 /home/pi/TonyPi/Joystick.py
      pi 1028 716 0 16:44 ? 00:00:00 /usr/lib/gvfs/gvfs-afc-volume-monitor
      root 1034 1 0 16:44 ? 00:00:00 /usr/lib/bluetooth/bluetoothd
      pi 1040 1 0 16:44 ? 00:00:00 /usr/lib/menu-cache/menu-cached /run/user/1000/menu-cached-:0
      pi 1044 716 0 16:44 ? 00:00:00 /usr/lib/gvfs/gvfs-mtp-volume-monitor
      root 1049 1 0 16:44 ? 00:00:00 /usr/bin/bluealsa
      root 1056 2 0 16:44 ? 00:00:00 [krfcommd]
      pi 1065 881 0 16:44 ? 00:00:00 /usr/lib/gvfs/gvfsd-trash --spawner :1.5 /org/gtk/gvfs/exec_spaw/0
      lp 1258 378 0 16:44 ? 00:00:00 /usr/lib/cups/notifier/dbus dbus://
      colord 1259 1 0 16:44 ? 00:00:00 /usr/lib/colord/colord
      root 4879 2 0 17:14 ? 00:00:04 [kworker/u8:0-events_unbound]
      root 5969 2 0 17:23 ? 00:00:00 [kworker/3:1]
      root 6382 2 0 17:27 ? 00:00:04 [kworker/u8:1-events_unbound]
      root 6900 2 0 17:31 ? 00:00:00 [kworker/2:1-events]
      pi 6995 904 0 17:32 ? 00:00:00 lxterminal
      pi 7004 6995 0 17:32 pts/0 00:00:00 bash
      root 7082 2 0 17:32 ? 00:00:02 [kworker/u8:2-events_unbound]
      root 7140 526 0 17:33 ? 00:00:00 sshd: pi [priv]
      pi 7158 7140 0 17:33 ? 00:00:00 sshd: pi@pts/1
      pi 7159 7158 0 17:33 pts/1 00:00:00 -bash
      root 7380 2 0 17:35 ? 00:00:00 [kworker/0:2H]
      root 7423 2 0 17:35 ? 00:00:00 [kworker/1:0]
      root 7430 377 0 17:35 ? 00:00:00 /bin/sh -c /home/pi/TonyPi/Extend/Pegar_Objeto.sh
      root 7431 7430 0 17:35 ? 00:00:00 /bin/bash /home/pi/TonyPi/Extend/Pegar_Objeto.sh
      root 7434 7431 99 17:35 ? 00:18:18 /usr/bin/python3 /home/pi/TonyPi/Extend/ApriltagTrack.py
      root 7456 1 0 17:35 ? 00:00:00 dbus-launch --autolaunch cb12512d764b467aa157bee72a6681fe --binary-syntax --close-stderr
      root 7457 1 0 17:35 ? 00:00:00 /usr/bin/dbus-daemon --syslog-only --fork --print-pid 5 --print-address 7 --session
      root 7470 2 0 17:35 ? 00:00:00 [kworker/2:1H]
      root 7474 2 0 17:35 ? 00:00:01 [kworker/0:2-events]
      root 7583 2 0 17:36 ? 00:00:00 [kworker/2:0-mm_percpu_wq]
      root 7767 377 0 17:37 ? 00:00:00 /bin/sh -c /home/pi/TonyPi/Extend/Pegar_Objeto.sh
      root 7768 7767 0 17:37 ? 00:00:00 /bin/bash /home/pi/TonyPi/Extend/Pegar_Objeto.sh
      root 7771 7768 1 17:37 ? 00:00:05 /usr/bin/python3 /home/pi/TonyPi/Extend/ApriltagTrack.py
      root 7937 2 0 17:39 ? 00:00:00 [kworker/1:0H]
      root 8114 2 0 17:40 ? 00:00:00 [kworker/0:0-events]
      root 8115 377 0 17:40 ? 00:00:00 /bin/sh -c /home/pi/TonyPi/Extend/Pegar_Objeto.sh
      root 8116 8115 0 17:40 ? 00:00:00 /bin/bash /home/pi/TonyPi/Extend/Pegar_Objeto.sh
      root 8119 8116 1 17:40 ? 00:00:03 /usr/bin/python3 /home/pi/TonyPi/Extend/ApriltagTrack.py
      root 8257 2 0 17:41 ? 00:00:00 [kworker/2:2-mm_percpu_wq]
      root 8306 2 0 17:42 ? 00:00:00 [kworker/u8:3-events_unbound]
      root 8343 377 0 17:42 ? 00:00:00 /bin/sh -c /home/pi/TonyPi/Extend/ApriltagTrack.py
      root 8344 8343 2 17:42 ? 00:00:02 /usr/bin/python3 /home/pi/TonyPi/Extend/ApriltagTrack.py
      pi 8539 7159 0 17:43 pts/1 00:00:00 ps -ef
      pi@TonyPiPro:~ $

      1 Reply Last reply Reply Quote 0
      • Antonio Francisco S.SantosA
        Antonio Francisco S.Santos
        last edited by

        {"trigger":"Pegar_Objeto.sh","command":"/home/pi/TonyPi/Extend/Pegar_Objeto.sh","ground":"background","voice":"Pegar Objeto","allowParams": "false"},

        1 Reply Last reply Reply Quote 0
        • Antonio Francisco S.SantosA
          Antonio Francisco S.Santos
          last edited by

          {"trigger":"ApriltagTrack.py","command":"/home/pi/TonyPi/Extend/Pegar_Objeto.sh","offCommand":"killall python3","ground":"background","voice":"Pegar Objeto","allo$

          RussR 1 Reply Last reply Reply Quote 0
          • RussR
            Russ @Antonio Francisco S.Santos
            last edited by

            @Antonio-Francisco-S-Santos, please try this as your offCommand after you confirm it works manually.

            kill -9 $(pgrep -f "/usr/bin/python3 /home/pi/TonyPi/Extend/ApriltagTrack.py")
            

            Russell VanderMey

            1 Reply Last reply Reply Quote 0
            • Antonio Francisco S.SantosA
              Antonio Francisco S.Santos
              last edited by

              Executando direto do terminal aparece:
              pi@TonyPiPro:~ $ kill -9 $(pgrep -f "/usr/bin/python3 /home/pi/TonyPi/Extend/ApriltagTrack.py")
              -bash: kill: (1683) - Opera▒▒o n▒o permitida
              pi@TonyPiPro:~ $

              RussR 1 Reply Last reply Reply Quote 0
              • RussR
                Russ @Antonio Francisco S.Santos
                last edited by Russ

                @Antonio-Francisco-S-Santos, it's saying you don't have access, so you'll need to prefix the command with sudo, like this:

                sudo kill -9 $(pgrep -f "/usr/bin/python3 /home/pi/TonyPi/Extend/ApriltagTrack.py")
                

                I see you're running the TRIGGERcmd background agent, which runs as root, so you don't need the sudo prefix when you add it to your commands.json.

                You'll need to escape the command's quotes too, like this:

                "offCommand": "kill -9 $(pgrep -f \"/usr/bin/python3 /home/pi/TonyPi/Extend/ApriltagTrack.py\")"
                

                Russell VanderMey

                1 Reply Last reply Reply Quote 0
                • Antonio Francisco S.SantosA
                  Antonio Francisco S.Santos
                  last edited by

                  @Russ said in Tentando Executar um Script python no terminal LX com o TriggerCMD mas não estou conseguindo:

                  Quando tento montar o comando ele só salvar dessa maneira:
                  {"trigger":"Sonar_barrier.py","command":"/home/pi/TonyPi/Extend/Caminhar.sh","offCommand":"kill -9 $(pgrep -f","ground":"background","voice":"Caminhar","allowParams": "false"}

                  RussR 1 Reply Last reply Reply Quote 0
                  • RussR
                    Russ @Antonio Francisco S.Santos
                    last edited by Russ

                    @Antonio-Francisco-S-Santos, you need "allowParam": "true". Otherwise the agent will ignore the offCommand field.

                    Please try this entry.

                     {
                      "trigger": "Sonar Barrier",
                      "command": "/home/pi/TonyPi/Extend/Caminhar.sh",
                      "offCommand": "kill -9 $(pgrep -f \"/usr/bin/python3 /home/pi/TonyPi/Extend/ApriltagTrack.py\")",
                      "ground": "foreground",
                      "voice": "Caminhar",
                      "voiceReply": "",
                      "allowParams": "true"
                     }
                    

                    Russell VanderMey

                    Antonio Francisco S.SantosA 1 Reply Last reply Reply Quote 0
                    • Antonio Francisco S.SantosA
                      Antonio Francisco S.Santos
                      last edited by

                      Olá, Com esse ultimo comando que você me mandou não faz nenhuma ação
                      {"trigger":"ApriltagTrack.py","command":"/home/pi/TonyPi/Extend/Pegar_Objeto.sh","offCommand":"kill -9 $(pgrep -f "/usr/bin/python3 /home/pi/TonyPi/Extend/ApriltagTrack.py")","ground":"foreground","voice":"Fechar Objeto","voiceReplay": "","allowParams": "true"}

                      1 Reply Last reply Reply Quote 0
                      • Antonio Francisco S.SantosA
                        Antonio Francisco S.Santos @Russ
                        last edited by

                        @Russ Esse comando executa a função perfeitamente mas quando executo o comando de fechar nada acontece:
                        {"trigger":"Pegar_Objeto.sh","command":"/home/pi/TonyPi/Extend/Pegar_Objeto.sh","ground":"background","voice":"Pegar Objeto","allowParams": "false"},

                        RussR 1 Reply Last reply Reply Quote 0
                        • RussR
                          Russ @Antonio Francisco S.Santos
                          last edited by Russ

                          @Antonio-Francisco-S-Santos, I don't know why it's not killing your python script. Maybe try killing your Pegar_Objeto.sh bash script instead.

                          "offCommand": "kill -9 $(pgrep -f \"/bin/bash /home/pi/TonyPi/Extend/Pegar_Objeto.sh\")",
                          

                          How do you know it's not killing your script. Are you listing your processes with ps -ef after you run the command with "off" as the parameter?

                          Russell VanderMey

                          Antonio Francisco S.SantosA 1 Reply Last reply Reply Quote 0
                          • Antonio Francisco S.SantosA
                            Antonio Francisco S.Santos @Russ
                            last edited by

                            @Russ Olá Professor não consegue fechar os Script quando executado pelo TriggerCMD, se executar dentro do Debian no Terminal e abrir outro terminal com o comando Kill consegue fechar. o que pode ser professor?

                            RussR 1 Reply Last reply Reply Quote 0
                            • RussR
                              Russ @Antonio Francisco S.Santos
                              last edited by Russ

                              @Antonio-Francisco-S-Santos, Google translated that as, "... cannot close the Script when executed by TriggerCMD, if you run it inside Debian in Terminal and open another terminal with the Kill command you can close it."

                              So I think you're saying this kill command only kills the Pegar_Objeto.sh script when you run the Pegar_Objeto.sh script manually, but not if you run it via TRIGGERcmd?

                              kill -9 $(pgrep -f "/bin/bash /home/pi/TonyPi/Extend/Pegar_Objeto.sh")
                              

                              If you look at the pgrep command's help, you'll see that the -f parameter specifies the full process name, but I found that you can specify a partial process name.

                              $ pgrep --help
                              Usage:
                               pgrep [options] <pattern>
                              
                              Options:
                               -d, --delimiter <string>  specify output delimiter
                               -l, --list-name           list PID and process name
                               -a, --list-full           list PID and full command line
                               -v, --inverse             negates the matching
                               -w, --lightweight         list all TID
                               -c, --count               count of matching processes
                               -f, --full                use full process name to match
                              

                              So please try this instead:

                              kill -9 $(pgrep -f Pegar_Objeto.sh)
                              

                              In your commands.json it would look like this:

                              "offCommand": "kill -9 $(pgrep -f Pegar_Objeto.sh)",
                              

                              Russell VanderMey

                              Antonio Francisco S.SantosA 1 Reply Last reply Reply Quote 0
                              • Antonio Francisco S.SantosA
                                Antonio Francisco S.Santos
                                last edited by

                                Executei esse comando manualmente mas não reve efeito:
                                kill -9 $(pgrep -f "/bin/bash /home/pi/TonyPi/Extend/Pegar_Objeto.sh")

                                Coloquei tambem o endereço do código principal:
                                kill -9 $(pgrep -f "/bin/bash /home/pi/TonyPi/Extend/ApriltagTrack.py")
                                Mesmo assim não fechou o Script

                                Antonio Francisco S.SantosA 1 Reply Last reply Reply Quote 0
                                • Antonio Francisco S.SantosA
                                  Antonio Francisco S.Santos @Russ
                                  last edited by

                                  @Russ said in Tentando Executar um Script python no terminal LX com o TriggerCMD mas não estou conseguindo:

                                  kill -9 $(pgrep -f Pegar_Objeto.sh)

                                  Agora colando dessa forma no terminal ele consegue fechar:
                                  kill -9 $(pgrep -f ApriltagTrack.py)

                                  Ainda não testei esse comando la no TriggerCMD

                                  1 Reply Last reply Reply Quote 0
                                  • Antonio Francisco S.SantosA
                                    Antonio Francisco S.Santos @Antonio Francisco S.Santos
                                    last edited by

                                    @Antonio-Francisco-S-Santos Testei esse comando no TriggerCMD, funcionou perfeitamente só um Script que ficou dando esse erro:
                                    64e7dafc-1627-45ad-acba-6d3c72549238-2023-06-03-211559_1920x1080_scrot.png

                                    RussR Antonio Francisco S.SantosA 2 Replies Last reply Reply Quote 0
                                    • RussR
                                      Russ @Antonio Francisco S.Santos
                                      last edited by

                                      @Antonio-Francisco-S-Santos, that kill command requires root access, so if you prefix that command with sudo it should work. You could also run the script with sudo like this:

                                      sudo /home/pi/TonyPi/Extend/Stop_Caminhar.sh
                                      

                                      Russell VanderMey

                                      1 Reply Last reply Reply Quote 0
                                      • Antonio Francisco S.SantosA
                                        Antonio Francisco S.Santos @Antonio Francisco S.Santos
                                        last edited by

                                        @Antonio-Francisco-S-Santos Professor Você é um gênio os Comandos agora funcionaram perfeitamente, com o sudo no inicio como você mencionou. Obrigado meu irmão.
                                        Agora uma outra dúvida:
                                        Como saber o nível da bateria que alimenta o Raspberry pi pelo Trigger CMD? Seria isso mais ou menos:
                                        battery_monitor

                                        RussR 1 Reply Last reply Reply Quote 0
                                        • RussR
                                          Russ @Antonio Francisco S.Santos
                                          last edited by

                                          @Antonio-Francisco-S-Santos, awesome! I'm glad it's all working now.

                                          About monitoring your battery - I don't think the Raspberry Pi can monitor its input power voltage without an external circuit, maybe like this HAT:
                                          https://www.elecrow.com/wiki/index.php?title=Current/Voltage/Power_Monitor_HAT_for_Raspberry_Pi

                                          Russell VanderMey

                                          1 Reply Last reply Reply Quote 0
                                          • Antonio Francisco S.SantosA
                                            Antonio Francisco S.Santos
                                            last edited by

                                            Professor, Tenho outra dúvida, esse código .py abrindo ele na IDE Thoony Python ele funciona normal mas se criar um Script .sh ele reconhece o Giroscópio e o Acelerómetro mas não faz nenhuma ação. aparece esse erro:
                                            latin-1' codec can't encode character '\uff01' in position 12: ordinal not in range(256)

                                            Aqui estar o Código:
                                            import time
                                            import hiwonder.Board as Board

                                            print('''


                                            功能:幻尔科技TonyPi扩展板,PWM舵机控制例程



                                            Official website:http://www.hiwonder.com
                                            Online mall:https://huaner.tmall.com/

                                            以下指令均需在LX终端使用,LX终端可通过ctrl+alt+t打开,或点
                                            击上栏的黑色LX终端图标。

                                            Usage:
                                            python3 BusServoMove.py

                                            Version: --V1.2 2021/07/03

                                            Tips:

                                            • 按下Ctrl+C可关闭此次程序运行,若失败请多次尝试!

                                            ''')

                                            while True:
                                            # 参数:参数1:舵机接口编号; 参数2:位置; 参数3:运行时间
                                            Board.setPWMServoPulse(2, 1500, 500) # 2号舵机转到1500位置,用时500ms
                                            time.sleep(0.5) # 延时时间和运行时间相同

                                            Board.setPWMServoPulse(2, 1800, 800) #舵机的转动范围0-180度,对应的脉宽为500-2500,即参数2的范围为500-2500
                                            time.sleep(0.5)
                                            
                                            Board.setPWMServoPulse(2, 1500, 300)
                                            time.sleep(0.2)
                                            
                                            Board.setPWMServoPulse(2, 1800, 800)  
                                            Board.setPWMServoPulse(1, 1800, 800)
                                            time.sleep(0.5)
                                            
                                            Board.setPWMServoPulse(2, 1500, 800)  
                                            Board.setPWMServoPulse(1, 1500, 800)
                                            time.sleep(0.5)
                                            
                                            Antonio Francisco S.SantosA 1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post