How can I monitor serial port traffic in transit?
Is there any port monitoring tool to watch the "packets"/stream/characters written on the serial-port?
I especially want to check if my program written in java works so I need some kind of tool to see if application is actually sending the data through the port.
Edits:
- I figured out, I was missing a
r, so that prevented my program from writing on to the port - Similar questions on sibling sites: 1, 2
linux serial-port
add a comment |
Is there any port monitoring tool to watch the "packets"/stream/characters written on the serial-port?
I especially want to check if my program written in java works so I need some kind of tool to see if application is actually sending the data through the port.
Edits:
- I figured out, I was missing a
r, so that prevented my program from writing on to the port - Similar questions on sibling sites: 1, 2
linux serial-port
3
Packets aren't written on the port. Characters are. It's not like Ethernet at all.
– LawrenceC
Apr 30 '11 at 18:33
1
Similar questions from sibling SE sites: stackoverflow.com/q/940374/12892 and serverfault.com/q/112957/4276
– Cristian Ciupitu
Feb 4 '15 at 8:12
add a comment |
Is there any port monitoring tool to watch the "packets"/stream/characters written on the serial-port?
I especially want to check if my program written in java works so I need some kind of tool to see if application is actually sending the data through the port.
Edits:
- I figured out, I was missing a
r, so that prevented my program from writing on to the port - Similar questions on sibling sites: 1, 2
linux serial-port
Is there any port monitoring tool to watch the "packets"/stream/characters written on the serial-port?
I especially want to check if my program written in java works so I need some kind of tool to see if application is actually sending the data through the port.
Edits:
- I figured out, I was missing a
r, so that prevented my program from writing on to the port - Similar questions on sibling sites: 1, 2
linux serial-port
linux serial-port
edited 1 hour ago
Alex Stragies
3,3851639
3,3851639
asked Apr 30 '11 at 10:05
DeepakDeepak
3392611
3392611
3
Packets aren't written on the port. Characters are. It's not like Ethernet at all.
– LawrenceC
Apr 30 '11 at 18:33
1
Similar questions from sibling SE sites: stackoverflow.com/q/940374/12892 and serverfault.com/q/112957/4276
– Cristian Ciupitu
Feb 4 '15 at 8:12
add a comment |
3
Packets aren't written on the port. Characters are. It's not like Ethernet at all.
– LawrenceC
Apr 30 '11 at 18:33
1
Similar questions from sibling SE sites: stackoverflow.com/q/940374/12892 and serverfault.com/q/112957/4276
– Cristian Ciupitu
Feb 4 '15 at 8:12
3
3
Packets aren't written on the port. Characters are. It's not like Ethernet at all.
– LawrenceC
Apr 30 '11 at 18:33
Packets aren't written on the port. Characters are. It's not like Ethernet at all.
– LawrenceC
Apr 30 '11 at 18:33
1
1
Similar questions from sibling SE sites: stackoverflow.com/q/940374/12892 and serverfault.com/q/112957/4276
– Cristian Ciupitu
Feb 4 '15 at 8:12
Similar questions from sibling SE sites: stackoverflow.com/q/940374/12892 and serverfault.com/q/112957/4276
– Cristian Ciupitu
Feb 4 '15 at 8:12
add a comment |
8 Answers
8
active
oldest
votes
I found projects called Linux Serial Sniffer, jpnevulator, and Moni. The first two look like they do exactly what you want. The last one calls itself a monitor, but it actually looks like a standard serial communication program.
1
thanks for that !! i will give it a try. by the way i solved the issue from my java side. i was missing a r, so that prevented my message from writing on to the port. thanks for that anyways!!
– Deepak
Apr 30 '11 at 18:24
3
The «LInux Serial Sniffer» is buggy, it absolutely takes out incoming data, thus another application which is actually listen to serial see nothing. But, at least, the data that goes outside seems to go without problem.
– Hi-Angel
Mar 31 '15 at 11:12
3
From the jpnevulator FAQ: "Jpnevulator was never built to sit in between the kernel and your application."
– Shelvacu
Jun 12 '17 at 2:14
1
The link referring to Moni is dead.
– Yaron
Dec 12 '18 at 15:24
add a comment |
socat is a tool to connect (nearly) everything to (nearly) everything, and tee can duplicate streams.
In your usecase you could connect your serial port /dev/ttyS0 to a PTY /tmp/ttyV0, then point your application to the PTY, and have socat tee out Input and Output somewhere for you to observe.
Googling "socat serial port pty tee debug" will point you to several examples, one being:
socat /dev/ttyS0,raw,echo=0
SYSTEM:'tee in.txt |socat - "PTY,link=/tmp/ttyV0,raw,echo=0,waitslave" |tee out.txt'
The files in.txt and out.txt will then contain the captured data.
This has been confirmed to work by commenters (@ogurets).
1
Just tried it and have both input and output recorded. Socat version "1.7.2.4+sigfix" from Debian Jessie packages.
– ogurets
May 17 '17 at 21:41
The idea is good, but not evensocatcan proxy ioctl calls.
– peterh
Jan 24 at 13:34
add a comment |
I don't think the serial driver has any tracing functionality that would allow you to watch packets. You can use strace to observe all the reads and writes from your application:
strace -s9999 -o myapp.strace -eread,write,ioctl ./myapp
1
can is send packets to the port if nothign is connected ?
– Deepak
Apr 30 '11 at 12:53
strace will tell you if it tried to send characters to the port, and what the kernel responded with when it tried. depending on your flow control settings characters may arrive at the disconnected TXD pin or may not.
– Jasen
Jun 28 '18 at 5:19
add a comment |
When I debug interaction of my application with a serial port, I use moserial.
5
What're you talking about, in the docs written it's just a terminal.
– Hi-Angel
Mar 31 '15 at 10:53
add a comment |
Try this:
screen /dev/tty.usbserial-blahblah 9600
works for me.
23
This opens the port and assumes control over it, so nothing else can use it. This does not "monitor" or "sniff" the traffic.
– Ian M
Jan 23 '15 at 7:12
add a comment |
interceptty does that job:
interceptty /dev/ttyACM0 /dev/ttyDUMMY
or, with a nice output format and with configuring the backend device, and with line buffering:
interceptty -s 'ispeed 19200 ospeed 19200' -l /dev/ttyACM0 /dev/ttyDUMMY | interceptty-nicedump
and then connect with your programme to /dev/ttyDUMMY.
@AlexStragies: I have it on my arch linux system. AUR page: aur.archlinux.org/packages/interceptty, copy of the sources: repo.j5lx.eu/archive/interceptty/interceptty-0.6.tar.gz
– Golar Ramblar
Apr 3 '17 at 10:22
I had to download it (usingwgetsince clicking on the.tar.gzfile seemed to corrupt it somehow), installgccandmake, then run./configureandmake install. Does exactly what the OP and I want though.
– Graeme Moss
May 31 '17 at 23:18
Your answer is far the best.
– peterh
Jan 29 at 15:35
add a comment |
Have a look at ttyUSBSpy.
It is on alpha stage, but it works.
2
It doesn't. It is written in python, and the code does import someimport pcopy, which is even Google gave up to find.
– Hi-Angel
Mar 31 '15 at 10:43
2
Software/Homepage looks abandoned. Is not in package managers.
– Alex Stragies
Apr 16 '17 at 16:28
add a comment |
minicom is missing from the list of tools to monitor serial ports. Use it as for example to listen to arduino device:
minicom --device /dev/ttyACM0 --baud 9600
OP wrote "monitor", but meant "sniffer" ( = is able to read traffic in transit), while minicom is a serial port "client", and as such is not an answer to this question. The answer below from mike made the same mistake, and the comment there explains the terminology problem as well.
– Alex Stragies
2 hours ago
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f12359%2fhow-can-i-monitor-serial-port-traffic-in-transit%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
8 Answers
8
active
oldest
votes
8 Answers
8
active
oldest
votes
active
oldest
votes
active
oldest
votes
I found projects called Linux Serial Sniffer, jpnevulator, and Moni. The first two look like they do exactly what you want. The last one calls itself a monitor, but it actually looks like a standard serial communication program.
1
thanks for that !! i will give it a try. by the way i solved the issue from my java side. i was missing a r, so that prevented my message from writing on to the port. thanks for that anyways!!
– Deepak
Apr 30 '11 at 18:24
3
The «LInux Serial Sniffer» is buggy, it absolutely takes out incoming data, thus another application which is actually listen to serial see nothing. But, at least, the data that goes outside seems to go without problem.
– Hi-Angel
Mar 31 '15 at 11:12
3
From the jpnevulator FAQ: "Jpnevulator was never built to sit in between the kernel and your application."
– Shelvacu
Jun 12 '17 at 2:14
1
The link referring to Moni is dead.
– Yaron
Dec 12 '18 at 15:24
add a comment |
I found projects called Linux Serial Sniffer, jpnevulator, and Moni. The first two look like they do exactly what you want. The last one calls itself a monitor, but it actually looks like a standard serial communication program.
1
thanks for that !! i will give it a try. by the way i solved the issue from my java side. i was missing a r, so that prevented my message from writing on to the port. thanks for that anyways!!
– Deepak
Apr 30 '11 at 18:24
3
The «LInux Serial Sniffer» is buggy, it absolutely takes out incoming data, thus another application which is actually listen to serial see nothing. But, at least, the data that goes outside seems to go without problem.
– Hi-Angel
Mar 31 '15 at 11:12
3
From the jpnevulator FAQ: "Jpnevulator was never built to sit in between the kernel and your application."
– Shelvacu
Jun 12 '17 at 2:14
1
The link referring to Moni is dead.
– Yaron
Dec 12 '18 at 15:24
add a comment |
I found projects called Linux Serial Sniffer, jpnevulator, and Moni. The first two look like they do exactly what you want. The last one calls itself a monitor, but it actually looks like a standard serial communication program.
I found projects called Linux Serial Sniffer, jpnevulator, and Moni. The first two look like they do exactly what you want. The last one calls itself a monitor, but it actually looks like a standard serial communication program.
answered Apr 30 '11 at 18:22
Shawn J. GoffShawn J. Goff
30.1k19112134
30.1k19112134
1
thanks for that !! i will give it a try. by the way i solved the issue from my java side. i was missing a r, so that prevented my message from writing on to the port. thanks for that anyways!!
– Deepak
Apr 30 '11 at 18:24
3
The «LInux Serial Sniffer» is buggy, it absolutely takes out incoming data, thus another application which is actually listen to serial see nothing. But, at least, the data that goes outside seems to go without problem.
– Hi-Angel
Mar 31 '15 at 11:12
3
From the jpnevulator FAQ: "Jpnevulator was never built to sit in between the kernel and your application."
– Shelvacu
Jun 12 '17 at 2:14
1
The link referring to Moni is dead.
– Yaron
Dec 12 '18 at 15:24
add a comment |
1
thanks for that !! i will give it a try. by the way i solved the issue from my java side. i was missing a r, so that prevented my message from writing on to the port. thanks for that anyways!!
– Deepak
Apr 30 '11 at 18:24
3
The «LInux Serial Sniffer» is buggy, it absolutely takes out incoming data, thus another application which is actually listen to serial see nothing. But, at least, the data that goes outside seems to go without problem.
– Hi-Angel
Mar 31 '15 at 11:12
3
From the jpnevulator FAQ: "Jpnevulator was never built to sit in between the kernel and your application."
– Shelvacu
Jun 12 '17 at 2:14
1
The link referring to Moni is dead.
– Yaron
Dec 12 '18 at 15:24
1
1
thanks for that !! i will give it a try. by the way i solved the issue from my java side. i was missing a r, so that prevented my message from writing on to the port. thanks for that anyways!!
– Deepak
Apr 30 '11 at 18:24
thanks for that !! i will give it a try. by the way i solved the issue from my java side. i was missing a r, so that prevented my message from writing on to the port. thanks for that anyways!!
– Deepak
Apr 30 '11 at 18:24
3
3
The «LInux Serial Sniffer» is buggy, it absolutely takes out incoming data, thus another application which is actually listen to serial see nothing. But, at least, the data that goes outside seems to go without problem.
– Hi-Angel
Mar 31 '15 at 11:12
The «LInux Serial Sniffer» is buggy, it absolutely takes out incoming data, thus another application which is actually listen to serial see nothing. But, at least, the data that goes outside seems to go without problem.
– Hi-Angel
Mar 31 '15 at 11:12
3
3
From the jpnevulator FAQ: "Jpnevulator was never built to sit in between the kernel and your application."
– Shelvacu
Jun 12 '17 at 2:14
From the jpnevulator FAQ: "Jpnevulator was never built to sit in between the kernel and your application."
– Shelvacu
Jun 12 '17 at 2:14
1
1
The link referring to Moni is dead.
– Yaron
Dec 12 '18 at 15:24
The link referring to Moni is dead.
– Yaron
Dec 12 '18 at 15:24
add a comment |
socat is a tool to connect (nearly) everything to (nearly) everything, and tee can duplicate streams.
In your usecase you could connect your serial port /dev/ttyS0 to a PTY /tmp/ttyV0, then point your application to the PTY, and have socat tee out Input and Output somewhere for you to observe.
Googling "socat serial port pty tee debug" will point you to several examples, one being:
socat /dev/ttyS0,raw,echo=0
SYSTEM:'tee in.txt |socat - "PTY,link=/tmp/ttyV0,raw,echo=0,waitslave" |tee out.txt'
The files in.txt and out.txt will then contain the captured data.
This has been confirmed to work by commenters (@ogurets).
1
Just tried it and have both input and output recorded. Socat version "1.7.2.4+sigfix" from Debian Jessie packages.
– ogurets
May 17 '17 at 21:41
The idea is good, but not evensocatcan proxy ioctl calls.
– peterh
Jan 24 at 13:34
add a comment |
socat is a tool to connect (nearly) everything to (nearly) everything, and tee can duplicate streams.
In your usecase you could connect your serial port /dev/ttyS0 to a PTY /tmp/ttyV0, then point your application to the PTY, and have socat tee out Input and Output somewhere for you to observe.
Googling "socat serial port pty tee debug" will point you to several examples, one being:
socat /dev/ttyS0,raw,echo=0
SYSTEM:'tee in.txt |socat - "PTY,link=/tmp/ttyV0,raw,echo=0,waitslave" |tee out.txt'
The files in.txt and out.txt will then contain the captured data.
This has been confirmed to work by commenters (@ogurets).
1
Just tried it and have both input and output recorded. Socat version "1.7.2.4+sigfix" from Debian Jessie packages.
– ogurets
May 17 '17 at 21:41
The idea is good, but not evensocatcan proxy ioctl calls.
– peterh
Jan 24 at 13:34
add a comment |
socat is a tool to connect (nearly) everything to (nearly) everything, and tee can duplicate streams.
In your usecase you could connect your serial port /dev/ttyS0 to a PTY /tmp/ttyV0, then point your application to the PTY, and have socat tee out Input and Output somewhere for you to observe.
Googling "socat serial port pty tee debug" will point you to several examples, one being:
socat /dev/ttyS0,raw,echo=0
SYSTEM:'tee in.txt |socat - "PTY,link=/tmp/ttyV0,raw,echo=0,waitslave" |tee out.txt'
The files in.txt and out.txt will then contain the captured data.
This has been confirmed to work by commenters (@ogurets).
socat is a tool to connect (nearly) everything to (nearly) everything, and tee can duplicate streams.
In your usecase you could connect your serial port /dev/ttyS0 to a PTY /tmp/ttyV0, then point your application to the PTY, and have socat tee out Input and Output somewhere for you to observe.
Googling "socat serial port pty tee debug" will point you to several examples, one being:
socat /dev/ttyS0,raw,echo=0
SYSTEM:'tee in.txt |socat - "PTY,link=/tmp/ttyV0,raw,echo=0,waitslave" |tee out.txt'
The files in.txt and out.txt will then contain the captured data.
This has been confirmed to work by commenters (@ogurets).
edited Jan 5 at 18:46
answered Aug 27 '15 at 16:23
Alex StragiesAlex Stragies
3,3851639
3,3851639
1
Just tried it and have both input and output recorded. Socat version "1.7.2.4+sigfix" from Debian Jessie packages.
– ogurets
May 17 '17 at 21:41
The idea is good, but not evensocatcan proxy ioctl calls.
– peterh
Jan 24 at 13:34
add a comment |
1
Just tried it and have both input and output recorded. Socat version "1.7.2.4+sigfix" from Debian Jessie packages.
– ogurets
May 17 '17 at 21:41
The idea is good, but not evensocatcan proxy ioctl calls.
– peterh
Jan 24 at 13:34
1
1
Just tried it and have both input and output recorded. Socat version "1.7.2.4+sigfix" from Debian Jessie packages.
– ogurets
May 17 '17 at 21:41
Just tried it and have both input and output recorded. Socat version "1.7.2.4+sigfix" from Debian Jessie packages.
– ogurets
May 17 '17 at 21:41
The idea is good, but not even
socat can proxy ioctl calls.– peterh
Jan 24 at 13:34
The idea is good, but not even
socat can proxy ioctl calls.– peterh
Jan 24 at 13:34
add a comment |
I don't think the serial driver has any tracing functionality that would allow you to watch packets. You can use strace to observe all the reads and writes from your application:
strace -s9999 -o myapp.strace -eread,write,ioctl ./myapp
1
can is send packets to the port if nothign is connected ?
– Deepak
Apr 30 '11 at 12:53
strace will tell you if it tried to send characters to the port, and what the kernel responded with when it tried. depending on your flow control settings characters may arrive at the disconnected TXD pin or may not.
– Jasen
Jun 28 '18 at 5:19
add a comment |
I don't think the serial driver has any tracing functionality that would allow you to watch packets. You can use strace to observe all the reads and writes from your application:
strace -s9999 -o myapp.strace -eread,write,ioctl ./myapp
1
can is send packets to the port if nothign is connected ?
– Deepak
Apr 30 '11 at 12:53
strace will tell you if it tried to send characters to the port, and what the kernel responded with when it tried. depending on your flow control settings characters may arrive at the disconnected TXD pin or may not.
– Jasen
Jun 28 '18 at 5:19
add a comment |
I don't think the serial driver has any tracing functionality that would allow you to watch packets. You can use strace to observe all the reads and writes from your application:
strace -s9999 -o myapp.strace -eread,write,ioctl ./myapp
I don't think the serial driver has any tracing functionality that would allow you to watch packets. You can use strace to observe all the reads and writes from your application:
strace -s9999 -o myapp.strace -eread,write,ioctl ./myapp
answered Apr 30 '11 at 11:48
GillesGilles
542k12810991616
542k12810991616
1
can is send packets to the port if nothign is connected ?
– Deepak
Apr 30 '11 at 12:53
strace will tell you if it tried to send characters to the port, and what the kernel responded with when it tried. depending on your flow control settings characters may arrive at the disconnected TXD pin or may not.
– Jasen
Jun 28 '18 at 5:19
add a comment |
1
can is send packets to the port if nothign is connected ?
– Deepak
Apr 30 '11 at 12:53
strace will tell you if it tried to send characters to the port, and what the kernel responded with when it tried. depending on your flow control settings characters may arrive at the disconnected TXD pin or may not.
– Jasen
Jun 28 '18 at 5:19
1
1
can is send packets to the port if nothign is connected ?
– Deepak
Apr 30 '11 at 12:53
can is send packets to the port if nothign is connected ?
– Deepak
Apr 30 '11 at 12:53
strace will tell you if it tried to send characters to the port, and what the kernel responded with when it tried. depending on your flow control settings characters may arrive at the disconnected TXD pin or may not.
– Jasen
Jun 28 '18 at 5:19
strace will tell you if it tried to send characters to the port, and what the kernel responded with when it tried. depending on your flow control settings characters may arrive at the disconnected TXD pin or may not.
– Jasen
Jun 28 '18 at 5:19
add a comment |
When I debug interaction of my application with a serial port, I use moserial.
5
What're you talking about, in the docs written it's just a terminal.
– Hi-Angel
Mar 31 '15 at 10:53
add a comment |
When I debug interaction of my application with a serial port, I use moserial.
5
What're you talking about, in the docs written it's just a terminal.
– Hi-Angel
Mar 31 '15 at 10:53
add a comment |
When I debug interaction of my application with a serial port, I use moserial.
When I debug interaction of my application with a serial port, I use moserial.
edited Nov 8 '11 at 18:04
Michael Mrozek♦
61.8k29192212
61.8k29192212
answered Nov 8 '11 at 17:55
Renat ZaripovRenat Zaripov
18217
18217
5
What're you talking about, in the docs written it's just a terminal.
– Hi-Angel
Mar 31 '15 at 10:53
add a comment |
5
What're you talking about, in the docs written it's just a terminal.
– Hi-Angel
Mar 31 '15 at 10:53
5
5
What're you talking about, in the docs written it's just a terminal.
– Hi-Angel
Mar 31 '15 at 10:53
What're you talking about, in the docs written it's just a terminal.
– Hi-Angel
Mar 31 '15 at 10:53
add a comment |
Try this:
screen /dev/tty.usbserial-blahblah 9600
works for me.
23
This opens the port and assumes control over it, so nothing else can use it. This does not "monitor" or "sniff" the traffic.
– Ian M
Jan 23 '15 at 7:12
add a comment |
Try this:
screen /dev/tty.usbserial-blahblah 9600
works for me.
23
This opens the port and assumes control over it, so nothing else can use it. This does not "monitor" or "sniff" the traffic.
– Ian M
Jan 23 '15 at 7:12
add a comment |
Try this:
screen /dev/tty.usbserial-blahblah 9600
works for me.
Try this:
screen /dev/tty.usbserial-blahblah 9600
works for me.
answered Jun 16 '13 at 17:01
MikeMike
631
631
23
This opens the port and assumes control over it, so nothing else can use it. This does not "monitor" or "sniff" the traffic.
– Ian M
Jan 23 '15 at 7:12
add a comment |
23
This opens the port and assumes control over it, so nothing else can use it. This does not "monitor" or "sniff" the traffic.
– Ian M
Jan 23 '15 at 7:12
23
23
This opens the port and assumes control over it, so nothing else can use it. This does not "monitor" or "sniff" the traffic.
– Ian M
Jan 23 '15 at 7:12
This opens the port and assumes control over it, so nothing else can use it. This does not "monitor" or "sniff" the traffic.
– Ian M
Jan 23 '15 at 7:12
add a comment |
interceptty does that job:
interceptty /dev/ttyACM0 /dev/ttyDUMMY
or, with a nice output format and with configuring the backend device, and with line buffering:
interceptty -s 'ispeed 19200 ospeed 19200' -l /dev/ttyACM0 /dev/ttyDUMMY | interceptty-nicedump
and then connect with your programme to /dev/ttyDUMMY.
@AlexStragies: I have it on my arch linux system. AUR page: aur.archlinux.org/packages/interceptty, copy of the sources: repo.j5lx.eu/archive/interceptty/interceptty-0.6.tar.gz
– Golar Ramblar
Apr 3 '17 at 10:22
I had to download it (usingwgetsince clicking on the.tar.gzfile seemed to corrupt it somehow), installgccandmake, then run./configureandmake install. Does exactly what the OP and I want though.
– Graeme Moss
May 31 '17 at 23:18
Your answer is far the best.
– peterh
Jan 29 at 15:35
add a comment |
interceptty does that job:
interceptty /dev/ttyACM0 /dev/ttyDUMMY
or, with a nice output format and with configuring the backend device, and with line buffering:
interceptty -s 'ispeed 19200 ospeed 19200' -l /dev/ttyACM0 /dev/ttyDUMMY | interceptty-nicedump
and then connect with your programme to /dev/ttyDUMMY.
@AlexStragies: I have it on my arch linux system. AUR page: aur.archlinux.org/packages/interceptty, copy of the sources: repo.j5lx.eu/archive/interceptty/interceptty-0.6.tar.gz
– Golar Ramblar
Apr 3 '17 at 10:22
I had to download it (usingwgetsince clicking on the.tar.gzfile seemed to corrupt it somehow), installgccandmake, then run./configureandmake install. Does exactly what the OP and I want though.
– Graeme Moss
May 31 '17 at 23:18
Your answer is far the best.
– peterh
Jan 29 at 15:35
add a comment |
interceptty does that job:
interceptty /dev/ttyACM0 /dev/ttyDUMMY
or, with a nice output format and with configuring the backend device, and with line buffering:
interceptty -s 'ispeed 19200 ospeed 19200' -l /dev/ttyACM0 /dev/ttyDUMMY | interceptty-nicedump
and then connect with your programme to /dev/ttyDUMMY.
interceptty does that job:
interceptty /dev/ttyACM0 /dev/ttyDUMMY
or, with a nice output format and with configuring the backend device, and with line buffering:
interceptty -s 'ispeed 19200 ospeed 19200' -l /dev/ttyACM0 /dev/ttyDUMMY | interceptty-nicedump
and then connect with your programme to /dev/ttyDUMMY.
edited Apr 3 '17 at 10:27
answered Apr 2 '17 at 13:19
Golar RamblarGolar Ramblar
600318
600318
@AlexStragies: I have it on my arch linux system. AUR page: aur.archlinux.org/packages/interceptty, copy of the sources: repo.j5lx.eu/archive/interceptty/interceptty-0.6.tar.gz
– Golar Ramblar
Apr 3 '17 at 10:22
I had to download it (usingwgetsince clicking on the.tar.gzfile seemed to corrupt it somehow), installgccandmake, then run./configureandmake install. Does exactly what the OP and I want though.
– Graeme Moss
May 31 '17 at 23:18
Your answer is far the best.
– peterh
Jan 29 at 15:35
add a comment |
@AlexStragies: I have it on my arch linux system. AUR page: aur.archlinux.org/packages/interceptty, copy of the sources: repo.j5lx.eu/archive/interceptty/interceptty-0.6.tar.gz
– Golar Ramblar
Apr 3 '17 at 10:22
I had to download it (usingwgetsince clicking on the.tar.gzfile seemed to corrupt it somehow), installgccandmake, then run./configureandmake install. Does exactly what the OP and I want though.
– Graeme Moss
May 31 '17 at 23:18
Your answer is far the best.
– peterh
Jan 29 at 15:35
@AlexStragies: I have it on my arch linux system. AUR page: aur.archlinux.org/packages/interceptty, copy of the sources: repo.j5lx.eu/archive/interceptty/interceptty-0.6.tar.gz
– Golar Ramblar
Apr 3 '17 at 10:22
@AlexStragies: I have it on my arch linux system. AUR page: aur.archlinux.org/packages/interceptty, copy of the sources: repo.j5lx.eu/archive/interceptty/interceptty-0.6.tar.gz
– Golar Ramblar
Apr 3 '17 at 10:22
I had to download it (using
wget since clicking on the .tar.gz file seemed to corrupt it somehow), install gcc and make, then run ./configure and make install. Does exactly what the OP and I want though.– Graeme Moss
May 31 '17 at 23:18
I had to download it (using
wget since clicking on the .tar.gz file seemed to corrupt it somehow), install gcc and make, then run ./configure and make install. Does exactly what the OP and I want though.– Graeme Moss
May 31 '17 at 23:18
Your answer is far the best.
– peterh
Jan 29 at 15:35
Your answer is far the best.
– peterh
Jan 29 at 15:35
add a comment |
Have a look at ttyUSBSpy.
It is on alpha stage, but it works.
2
It doesn't. It is written in python, and the code does import someimport pcopy, which is even Google gave up to find.
– Hi-Angel
Mar 31 '15 at 10:43
2
Software/Homepage looks abandoned. Is not in package managers.
– Alex Stragies
Apr 16 '17 at 16:28
add a comment |
Have a look at ttyUSBSpy.
It is on alpha stage, but it works.
2
It doesn't. It is written in python, and the code does import someimport pcopy, which is even Google gave up to find.
– Hi-Angel
Mar 31 '15 at 10:43
2
Software/Homepage looks abandoned. Is not in package managers.
– Alex Stragies
Apr 16 '17 at 16:28
add a comment |
Have a look at ttyUSBSpy.
It is on alpha stage, but it works.
Have a look at ttyUSBSpy.
It is on alpha stage, but it works.
edited Sep 18 '14 at 19:46
Cristian Ciupitu
2,10911622
2,10911622
answered Apr 18 '13 at 8:35
user37414user37414
271
271
2
It doesn't. It is written in python, and the code does import someimport pcopy, which is even Google gave up to find.
– Hi-Angel
Mar 31 '15 at 10:43
2
Software/Homepage looks abandoned. Is not in package managers.
– Alex Stragies
Apr 16 '17 at 16:28
add a comment |
2
It doesn't. It is written in python, and the code does import someimport pcopy, which is even Google gave up to find.
– Hi-Angel
Mar 31 '15 at 10:43
2
Software/Homepage looks abandoned. Is not in package managers.
– Alex Stragies
Apr 16 '17 at 16:28
2
2
It doesn't. It is written in python, and the code does import some
import pcopy, which is even Google gave up to find.– Hi-Angel
Mar 31 '15 at 10:43
It doesn't. It is written in python, and the code does import some
import pcopy, which is even Google gave up to find.– Hi-Angel
Mar 31 '15 at 10:43
2
2
Software/Homepage looks abandoned. Is not in package managers.
– Alex Stragies
Apr 16 '17 at 16:28
Software/Homepage looks abandoned. Is not in package managers.
– Alex Stragies
Apr 16 '17 at 16:28
add a comment |
minicom is missing from the list of tools to monitor serial ports. Use it as for example to listen to arduino device:
minicom --device /dev/ttyACM0 --baud 9600
OP wrote "monitor", but meant "sniffer" ( = is able to read traffic in transit), while minicom is a serial port "client", and as such is not an answer to this question. The answer below from mike made the same mistake, and the comment there explains the terminology problem as well.
– Alex Stragies
2 hours ago
add a comment |
minicom is missing from the list of tools to monitor serial ports. Use it as for example to listen to arduino device:
minicom --device /dev/ttyACM0 --baud 9600
OP wrote "monitor", but meant "sniffer" ( = is able to read traffic in transit), while minicom is a serial port "client", and as such is not an answer to this question. The answer below from mike made the same mistake, and the comment there explains the terminology problem as well.
– Alex Stragies
2 hours ago
add a comment |
minicom is missing from the list of tools to monitor serial ports. Use it as for example to listen to arduino device:
minicom --device /dev/ttyACM0 --baud 9600
minicom is missing from the list of tools to monitor serial ports. Use it as for example to listen to arduino device:
minicom --device /dev/ttyACM0 --baud 9600
answered Mar 4 at 11:34
user216125user216125
1244
1244
OP wrote "monitor", but meant "sniffer" ( = is able to read traffic in transit), while minicom is a serial port "client", and as such is not an answer to this question. The answer below from mike made the same mistake, and the comment there explains the terminology problem as well.
– Alex Stragies
2 hours ago
add a comment |
OP wrote "monitor", but meant "sniffer" ( = is able to read traffic in transit), while minicom is a serial port "client", and as such is not an answer to this question. The answer below from mike made the same mistake, and the comment there explains the terminology problem as well.
– Alex Stragies
2 hours ago
OP wrote "monitor", but meant "sniffer" ( = is able to read traffic in transit), while minicom is a serial port "client", and as such is not an answer to this question. The answer below from mike made the same mistake, and the comment there explains the terminology problem as well.
– Alex Stragies
2 hours ago
OP wrote "monitor", but meant "sniffer" ( = is able to read traffic in transit), while minicom is a serial port "client", and as such is not an answer to this question. The answer below from mike made the same mistake, and the comment there explains the terminology problem as well.
– Alex Stragies
2 hours ago
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f12359%2fhow-can-i-monitor-serial-port-traffic-in-transit%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
3
Packets aren't written on the port. Characters are. It's not like Ethernet at all.
– LawrenceC
Apr 30 '11 at 18:33
1
Similar questions from sibling SE sites: stackoverflow.com/q/940374/12892 and serverfault.com/q/112957/4276
– Cristian Ciupitu
Feb 4 '15 at 8:12