0 Members and 1 Guest are viewing this topic.
Hi SergseroThanks a lot for all the explanations.I started testing both, very interesting specially ModeSMixer !!I noticed that it keeps retraing to connect )at least at starting ... this is interesting in environments such internet ...where connections, broadband etc can drop sometimes.... It allows an "auto Restart" I used ModeSMixer with the following command :sudo ./modesmixer --inConnect 18.104.22.168:30002 --outConnect avr:maquinas.no-ip.org:31002That does a TCP conection from port 30002 in the local host (successfully) to a remote host (maquinas.no-ip.org) TCP 31002That dos not succeed because it is indeed an UDP listening port.Would it be possibly to add a funtionality to allow to specify TCP or UDP mode ??I am not shure if this make sense ... since UDP is a connctioless protocol, but this would allow to use ModeSMixer in a widerenvironments ... such as mixing to RTL1090 in windows....What do You think about this .. ?Best regards - Congratulations and thanks a lot for developing and for make it available for the folks !Juan
Hi Juan,I'm sorry for not being made ??a detailed description. There is two different programs.ModeSDeco is SDR console (without GUI) decoder with tcp-output-server in RAW (BEAST BIN or AVR ASCII) or MSG formats streaming data specifically designed for RTL DVB-T dongle. It is similar to dump1090, rtl1090 or adsb#.ModeSMixer is mixer (software data combiner) and transcoder for network-data-sources and/or for 'classical" ModeS receivers that to merge them data streams in one.It can receiving input data in any format: BEAST, AVR/AVR-MLAT, SBS-RAW or MSG (automatic recognition) from tcp-data sources and/or serial port device: COM* in windows or /dev/ttyUSB* in linux for receiver.Receiving network data can be as "listening server --inServer" on <port> or as client, "pulling --inConnect" data from a remote server on <host:port>. In the case of direct-attached receiver "--inSerial": <serial port:data rate:flow control>.The merged output-data-stream can be accessed in network via embedded server (--outServer) in specified format <type>: bin, avr, avrmlat, msg, sbsraw on tcp <port>, or "pushed" (--outConnect) to the remote server with specified address <host> and <port> in the same formats <type>.The number of combined input sources and output connections with one format type and/or concurrent access for different types are limited only computer performance. For example, is a possible for microADSB: ./modesmixer --inSerial /dev/ttyACM0:115200 --outServer bin:30040 --outServer msg:30003 --outServer sbsraw:30006 --outConnect avrmlat:30001 which will allow him to be at the same time: BEAST's receiver, source for flightradar24.com sender, Kinetic BaseStation RAW data stream and send AVR MLAT to remote server .I'm using collinear antenna http://www.radial.ru/catalog/antennas/vertical/a10_1090/eng/ with high gain (10dBi) and LNA (30dB) http://www.kuhne-electronic.de/en/products/low-noise-amplifiers/ku-lna-1090-a-tm.html for cable (~60m LMR) loss compensation with SBS-1eR, Beast and RTL2832/T820R dongles. And such receiving systems work fine for me. In my opinion, need to consider the structural features of DVB-T dongles: high sensitivity receiver chip though there is no band pass filter (pre-selector) and low ADC (8bit) dynamic range.I prefer use the narrow-band resonant antenna, which weaken effect of adjacent-station interference. And for suppression of out-of-band signals used band pass filter (~6MHz) and LNA with high IP3.There are specifically made ??available cmd-options to set different values in program and found optimal for specific conditions. In many cases, the program work fine, if you specify only <gain control> as maximal (42 - for Elonics E4000 or 49.6 - for Rafael Micro R820T), output message <format> and <server on port>: ./modesdeco --gain 42 --msg --net 30003.Sincerely,Sergey