# CANUTILS in node-red

**URL:** <https://discourse.nodered.org/t/canutils-in-node-red/94209>\
**Category:** General\
**Created:** [27 December 2024 18:11 UTC](https://discourse.nodered.org/t/canutils-in-node-red/94209 "2024-12-27T18:11:34Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ino](https://avatars.discourse-cdn.com/v4/letter/i/bbe5ce/32.png) [@Ino](https://discourse.nodered.org/u/Ino)\
**Post date:** [27 December 2024 18:11 UTC](https://discourse.nodered.org/t/canutils-in-node-red/94209/1 "2024-12-27T18:11:34Z")

</div>

I want to send a file with CAN messages with node-red. In the terminal it works fine with canplayer -I /home/candump.log (canutils). Now I want to send the same command from node-red with an exec node. Unfortunately the result is an error (infile: No such file or directory). The "infile" is the option which is used to set the file with the can messages as given in the help

-I (default stdin)

anyone can help me?

Thanks in advantage

Ino

---

<div class="post-metadata">

**Author:** ![jbudd](https://avatars.discourse-cdn.com/v4/letter/j/5f8ce5/32.png) [@jbudd](https://discourse.nodered.org/u/jbudd)\
**Post date:** [27 December 2024 21:15 UTC](https://discourse.nodered.org/t/canutils-in-node-red/94209/2 "2024-12-27T21:15:02Z")

</div>

Can you show us the settings for your exec node and the exact stdout and stderr output from the node?

---

<div class="post-metadata">

**Author:** ![Ino](https://avatars.discourse-cdn.com/v4/letter/i/bbe5ce/32.png) [@Ino](https://discourse.nodered.org/u/Ino)\
**Post date:** [28 December 2024 12:41 UTC](https://discourse.nodered.org/t/canutils-in-node-red/94209/3 "2024-12-28T12:41:07Z")

</div>

input: timestamp

Command: canplayer -I  
Append msg.payload (not checked)  
/home/Argos/candump-test.log

stdout : no output  
stderr : {"\_msgid":"b1371f0b27fa7bd6",  
"topic":"","  
payload":"infile: No such file or directory\n","rc":{"code":1,  
"message":"Command failed: canplayer -I /home/Argos/candump-test.log\ninfile: No such file or directory\n"}}  
return code : {"\_msgid":"8235dd77db8baed4","  
topic":"","payload":{"code":1,  
"message":"Command failed: canplayer -I /home/Argos/candump-test.log\ninfile: No such file or directory\n"}}

---

<div class="post-metadata">

**Author:** ![jbudd](https://avatars.discourse-cdn.com/v4/letter/j/5f8ce5/32.png) [@jbudd](https://discourse.nodered.org/u/jbudd)\
**Post date:** [28 December 2024 13:00 UTC](https://discourse.nodered.org/t/canutils-in-node-red/94209/4 "2024-12-28T13:00:44Z")

</div>

> [@Ino](#):
>
> Command: canplayer -I  
> Append msg.payload (not checked)  
> /home/Argos/candump-test.log

1. If Append msg.payload is not checked, how does it know to process `/home/Argos/candump-test.log`? A screen capture of the setup might have clarified this.

2. Does the file `/home/Argos/candump-test.log` actually exist? (Your original post says that from the command line it's `/home/candump.log` that works.

3. Does it make a difference if your exec node uses the full pathname of canplayer? (Use `which canplayer` to find this)

---

<div class="post-metadata">

**Author:** ![Ino](https://avatars.discourse-cdn.com/v4/letter/i/bbe5ce/32.png) [@Ino](https://discourse.nodered.org/u/Ino)\
**Post date:** [28 December 2024 13:13 UTC](https://discourse.nodered.org/t/canutils-in-node-red/94209/5 "2024-12-28T13:13:49Z")

</div>

sorry jbudd, found the problem and that was me. 2 raspberry's, 2 running node-red versions, too late and too much use of ctrl C and control V. The reason of malfunction was the use of the wrong file. It is working fine now and the next challenge is to stop the canplayer.  
many thanks for your reply!

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [28 March 2025 13:14 UTC](https://discourse.nodered.org/t/canutils-in-node-red/94209/6 "2025-03-28T13:14:18Z")

</div>

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.