DSD connection with TCP

[Saqib]

I've tried FMP24.exe and DSD.exe. FMP24 connects with RTL-SDR v4 and get real time data and send over TCP, and DSD starts decoding. I want to change strategy little bit, i've made a Python script where i connect with RTL-SDR and get real time data from RTL over a tunned frequency i want to connect with DSD via TCP, but i'm unable to do that, is there any possibility to do that? because when i try to connect via TCP from Python on the other hand i run 1R.bat, and it tries to connect with FMP24, not with my code, because maybe it has designed for specific exe.
i just want to shift the FMP24, working on Python.


Second Question is, is it possible to get data from Vita49, and DSD can decode it? Vita49 sends data over IP. so how can i manage that data and give it to DSD so DSD decodes it in real time?

 

[Saqib]

here is the screen shot of my Python side, from where i'm getting real time signal and sending over vb-card, but DSD is showing error,

 

[mtindor]

here is the screen shot of my Python side, from where i'm getting real time signal and sending over vb-card, but DSD is showing error,

View attachment 194413

I am sure DSDplus was never intended to be connected to by anything other than FMP*.exe. So right from the start you are probably going to have issues.

However, it looks like you are using "Direct Linking" and not TCP Linking.

In the DSDPlus Input menu, you should select "Use FMPx TCP Linking" and then set an FMPx TCP Address and FMPx TCP Port. And that FMPx TCP Address and FMPx TCP Port should be the same IP address / port that your Python script is listening on.

Then, maybe, DSDPlus will see your Python listening on ###.###.###.###:####

 

[Saqib]

I am sure DSDplus was never intended to be connected to by anything other than FMP*.exe. So right from the start you are probably going to have issues.

However, it looks like you are using "Direct Linking" and not TCP Linking.

In the DSDPlus Input menu, you should select "Use FMPx TCP Linking" and then set an FMPx TCP Address and FMPx TCP Port. And that FMPx TCP Address and FMPx TCP Port should be the same IP address / port that your Python script is listening on.

Then, maybe, DSDPlus will see your Python listening on ###.###.###.###:####

i tried but, its not working, from python side when i try to connect with 127.0.0.1:20001. the DSD console window shows this,

 

[mtindor]

i tried but, its not working, from python side when i try to connect with 127.0.0.1:20001. the DSD console window shows this,

View attachment 194414

LIke I said, it was probably never the intent of the author to allow other third party applications to connect to DSDPlus over TCP.

You probably should get out Wireshark and start sniffing the traffic on 127.0.0.1:20001 to see what FMP24 expects to see from DSDplus (and what DSDPlus expects to see from FMP*) upon connection.

 

[Saqib]

LIke I said, it was probably never the intent of the author to allow other third party applications to connect to DSDPlus over TCP.

You probably should get out Wireshark and start sniffing the traffic on 127.0.0.1:20001 to see what FMP24 expects to see from DSDplus (and what DSDPlus expects to see from FMP*) upon connection.

let me try this but i think, its impossible to connect with third party applications.

 

[mtindor]

let me try this but i think, its impossible to connect with third party applications.

It may/may not be "impossible". But it may be difficult. Use Wireshark or something to sniff TCP 20001 and see what traffic is being sent between FMP*.exe and DSDPlus.exe during the connection phase. I'm sure there is going to be some information that indicates what version of FMP*.exe is connecting to what version of DSDPlus.exe to make sure they are compatible. It may be as simple as making sure that your python script announces itself as some specific version of FMP*.exe.

 

[Saqib]

It may/may not be "impossible". But it may be difficult. Use Wireshark or something to sniff TCP 20001 and see what traffic is being sent between FMP*.exe and DSDPlus.exe during the connection phase. I'm sure there is going to be some information that indicates what version of FMP*.exe is connecting to what version of DSDPlus.exe to make sure they are compatible. It may be as simple as making sure that your python script announces itself as some specific version of FMP*.exe.

yeah Sounds good, let me check.

 

[mtindor]

yeah Sounds good, let me check.

Keep this in mind:

1. FMP24 -oT20001 (to force FMP24 to connect over the TCP link
2. I am NOT a programmer
3. I ran Wireshark and saw no easily decodable data (to my eyes) to indicate what FMP24/DSDPlus are passing to each other
4. I believe FMP24 is sending audio to DSDPlus over the link, and that data (frequency and such) is being passed back and forth
5. I see references to TLS (hmm -- would likely indicate encrypted SSL connection perhaps)

So you may not be able to accomplish anything. Even if the transmissions aren't encrypted over SSL, the data being sent back/forth may be encrypted in some other way or obfucscated so that it doesn't make sense when viewing in wireshark.

I had to fire up Wireshark on my local loopback interface to capture anything. I could definitely see when DSDPlus made the connection to FMP24. But I couldn't tell what was being sent back and forth. It's a pain in the butt doing it remotely, and I have no need to go through any more pain/trouble myself.

Good luck. Maybe you could engage in a conversation with the author at dsdplusfastlane@gmail.com and actually ask them questions... or not.

mike

 

[Saqib]

Keep this in mind:

1. FMP24 -oT20001 (to force FMP24 to connect over the TCP link
2. I am NOT a programmer
3. I ran Wireshark and saw no easily decodable data (to my eyes) to indicate what FMP24/DSDPlus are passing to each other
4. I believe FMP24 is sending audio to DSDPlus over the link, and that data (frequency and such) is being passed back and forth
5. I see references to TLS (hmm -- would likely indicate encrypted SSL connection perhaps)

So you may not be able to accomplish anything. Even if the transmissions aren't encrypted over SSL, the data being sent back/forth may be encrypted in some other way or obfucscated so that it doesn't make sense when viewing in wireshark.

I had to fire up Wireshark on my local loopback interface to capture anything. I could definitely see when DSDPlus made the connection to FMP24. But I couldn't tell what was being sent back and forth. It's a pain in the butt doing it remotely, and I have no need to go through any more pain/trouble myself.

Good luck. Maybe you could engage in a conversation with the author at dsdplusfastlane@gmail.com and actually ask them questions... or not.

mike

I tried wireshark and tcpudp to check the data between FMP24 and DSD, via 127.0.0.1:20001, but unable to check or get the data, server is just able to send data over DSD not on any other software maybe, then i create a python script for tcp connection and console the data but also there didn't get any data. So, now what should i need to do? how can i solve this problem?

 

[mtindor]

I tried wireshark and tcpudp to check the data between FMP24 and DSD, via 127.0.0.1:20001, but unable to check or get the data, server is just able to send data over DSD not on any other software maybe, then i create a python script for tcp connection and console the data but also there didn't get any data. So, now what should i need to do? how can i solve this problem?

First off, if you are monitoring the loopback interface in Wireshark and have FMP* / DSDPlus configured for TCP linking over 127.0.0.1:20001, then you will see data. If you do not, you're doing something wrong.

BUT, doing all of that is useless. You aren't going to get your Python to connect over TCP because things have been done to specifically prevent people from connecting other applications to DSDplus over TCP. If you're great with snooping network traffic and can figure out what is being sent/received between the two, I guess there is always a possibility that you could do it. But the TCP linking was designed with keeping external applications from connecting over TCP.

Bottom line, DSDPlus never claimed to be compatible with your Python TCP app, and unless you are able to perform some miracles you will likely never get your Python TCP app to connect to DSDPlus.

You certainly can continue to try -- but it's used to ask questions about doing so on this forum since clearly nobody has ever done it successfully.

Mike

 

[Saqib]

First off, if you are monitoring the loopback interface in Wireshark and have FMP* / DSDPlus configured for TCP linking over 127.0.0.1:20001, then you will see data. If you do not, you're doing something wrong.

BUT, doing all of that is useless. You aren't going to get your Python to connect over TCP because things have been done to specifically prevent people from connecting other applications to DSDplus over TCP. If you're great with snooping network traffic and can figure out what is being sent/received between the two, I guess there is always a possibility that you could do it. But the TCP linking was designed with keeping external applications from connecting over TCP.

Bottom line, DSDPlus never claimed to be compatible with your Python TCP app, and unless you are able to perform some miracles you will likely never get your Python TCP app to connect to DSDPlus.

You certainly can continue to try -- but it's used to ask questions about doing so on this forum since clearly nobody has ever done it successfully.

Mike

i'm still trying and also i left a detailed email to dsdplusfastlane@gmail.com lets see what they reply.

 

[Saqib]

First off, if you are monitoring the loopback interface in Wireshark and have FMP* / DSDPlus configured for TCP linking over 127.0.0.1:20001, then you will see data. If you do not, you're doing something wrong.

BUT, doing all of that is useless. You aren't going to get your Python to connect over TCP because things have been done to specifically prevent people from connecting other applications to DSDplus over TCP. If you're great with snooping network traffic and can figure out what is being sent/received between the two, I guess there is always a possibility that you could do it. But the TCP linking was designed with keeping external applications from connecting over TCP.

Bottom line, DSDPlus never claimed to be compatible with your Python TCP app, and unless you are able to perform some miracles you will likely never get your Python TCP app to connect to DSDPlus.

You certainly can continue to try -- but it's used to ask questions about doing so on this forum since clearly nobody has ever done it successfully.

Mike

 

[mtindor]

View attachment 194599

Ok, you got FMP24 to talk over TCP to TcpUdpTool. Did you get anything to successfully connect to DSDplus? That's what you were originally trying to do -- you were wanting to get your Python app to connect over TCP to DSDPlus.

 

[Saqib]

Ok, you got FMP24 to talk over TCP to TcpUdpTool. Did you get anything to successfully connect to DSDplus? That's what you were originally trying to do -- you were wanting to get your Python app to connect over TCP to DSDPlus.

it doesn't worked still, so i tried to change the strategy and i got little success, i record a .wav file from FMP24 and played directly in vlc, the DSD got data from it and decode the audio. so i created a python script i load that file and check its pattern and data. then in my original python script i got real time data and tried to save in the format like FMP24 does, and i got success, when i played my file in vlc the DSD get data from it, but the voice is too blury and noisy. now i just need to do some setting, then i will convert the pattern for real time.

 

[Saqib]

it doesn't worked still, so i tried to change the strategy and i got little success, i record a .wav file from FMP24 and played directly in vlc, the DSD got data from it and decode the audio. so i created a python script i load that file and check its pattern and data. then in my original python script i got real time data and tried to save in the format like FMP24 does, and i got success, when i played my file in vlc the DSD get data from it, but the voice is too blury and noisy. now i just need to do some setting, then i will convert the pattern for real time.

Here the screen shot of what i'm trying to do.

 

[mtindor]

Here the screen shot of what i'm trying to do.
View attachment 194600

Looks like you are making some progress. I'm not a coder so I'm fairly blind to what you are really doing there. Is that RTL-SDR Receiver GUI part of your python? Or is that something else altogether?

 

[Saqib]

Looks like you are making some progress. I'm not a coder so I'm fairly blind to what you are really doing there. Is that RTL-SDR Receiver GUI part of your python? Or is that something else altogether?

This is a Part of RTL-SDR Receiver (In Python) but in the background i am using my logics and algorithms (Python+Ai).