08-21-2020 03:27 PM
Great news!
05-26-2023 09:51 AM - edited 05-26-2023 09:51 AM
@TenJigoku77 wrote:
Hi guys !
I'm happy to announce you that the solution with tshark is working fine.
I didn't finalize my application but it is well on track.So I launch tshark from "system exec.vi" and I execute severals command line to :
1) Select the interface
2) Acquire frames during a specified amoung of time, or after n packets acquired
3) Store those data in a pcap file
4) Read the pcap file and extract data as a json or xml file
I even succeed in selecting the correct channel for my zigbee network by re-writting the correct file.
Idem for the zigbee network key.
Anyway thanks guys for your help, you changed my week ^^
I have a similar requirement of Capturing the UDP data Frame Data )and Saving the same as pcap file and load/replay back the saved pcap file in LabVIEW UI.
Please share the one you have tried to check whether that suits my requirement
05-26-2023 02:51 PM
Hi !
I used the following command line :
the description of the command lines elements can be found here :
https://www.wireshark.org/docs/man-pages/tshark.html
I chosed to save the data as a json file, in order to read the data later with a labview thread, and as a pcap to be able to read the data back with wireshark if needed.
After that I needed to extract all the desired data from the json file. It's here that I spent a lot of time ^^'
05-26-2023 04:18 PM - edited 05-26-2023 04:19 PM
Thanks for the response, I will try based on the suggestion.
What does the sub vi does, does it logs the data. If yes how?
Thanks a million.
05-27-2023 01:52 AM
Hi !
This sub vi starts tshark, and then tshark will log acquire data and log them as specified in the command line.
In this command line, for example I specified the path file and the extension (pcap and json).
So technically it's tshark that does all the work, this sub vi just call tshark.
09-07-2023 02:11 PM
Hi!
How do you stop the tshark capture? Do you send a Ctrl-C command through the system exec?
Thanks!
09-07-2023 06:49 PM
I think you have two options. The first is to configure tshark to run for a certain amount of time and then it exits by itself. The other is to kill it from the taskkill command (from a new prompt).
04-04-2025 01:47 PM
Here is what I'm doing. Indeed taskill. I didn't see any drawback as far as I can tell.