Dm500 not working.

[armaghanshahzad]

I have following setup:

1- Dreambox 500 2- Flashed image dm500-satip-2.0.img 3- Got IP + Signal 4- untick the "Full Mux Rx mode supported" checkbox if it's ticked, in the SAT>IP server entry. (DONE) 5- set "Maximum PIDs" to 29, in the SAT>IP server entry (DONE) 6- No channel after scanning Signal & SNR is ok.

Can you please help?

Regards Armaghan

[mildsunrise]

Do you have a clone, or is it original? Can you verify if any of this radios work? Just to make sure it's not a problem with Tvheadend.

if tuning to Hotbird 13E: http://DM500/?msys=dvbs&freq=11623&pol=v&sr=27500&pids=0,10750,254 if tuning to Astra 19.2E: http://DM500/?msys=dvbs&freq=12266&pol=h&sr=27500&pids=0,851

[armaghanshahzad]

I tried first on DM500S original but the image is not working on DM500S (Front power light blinks and no IP) and I have clone DM500 too. I am testing on this clone now. I have inverto working with Tvheadend and minisatip working vuplus ultimo in tvheadend. So there is no problem with Tvheadend.

[mildsunrise]

I tried first on DM500S original but the image is not working on DM500S (Front power light blinks and no IP)

Whoa, that's really unexpected. Could you open a separate issue for that original? It would be best if I could see a log of the RS-232 output.

I am testing on this clone now. I have inverto working with Tvheadend and minisatip working vuplus ultimo in tvheadend. So there is no problem with Tvheadend.

Hmm... Please telnet to that clone and login (root / dreambox). Then, run dvbsnoop -s signal and while that's running, open one of the URLs above in a media player. What do you see on the console? On my DM500S I see this:

cycle: 1844  d_time: 0.005 s  Sig: 63606  SNR: 62889  BER: 0  Stat: 0x1f [SIG CARR VIT SYNC LOCK ]

[runcspelex]

i got the similar issue hardware: dm500s clone - netbox100s and flexbox fl-5000 all 3 with bsbe1-702b tuner (alps) tuner shows the signal , no signal lock

[mildsunrise]

If there is no lock, then this is a well-known issue with some boards. I'm currently working on it, see jmendeth/stbx25xx-linux#1. When the issue is resolved, I'll release a new version.

[mildsunrise]

It's fixed it in the latest kernel. I've released version 2.1, can you guys test it? It should lock now.

[armaghanshahzad]

I have tested the new version. It locks the channels but only half of the channels are scanned . Muxes are identical but scanned channels are less (Compared with same LNB input )-

Good News: Scanned channels are working in VLC Player.

I got following errors (many many times):

2016-03-29 16:11:20.555 subscription: 0EBC: "scan" subscribing to mux "11856V", weight: 5, adapter: "SAT>IP DVB-S Tuner #1 (192.168.1.52)", network: "dm52", service: "Raw PID Subscription" 2016-03-29 16:11:20.578 satip: SAT>IP DVB-S Tuner #1 (192.168.1.52) - RTSP cmd error 7 (Unknown error -7) [8-404] 2016-03-29 16:11:30.549 mpegts: 11856V in dm52 - scan no data, failed

Hope this helps

Regards Armaghan

[mildsunrise]

@armaghanshahzad What happens if you force another network scan? Do new channels get discovered?

It's normal that you see lots of RTSP cmd error 7 on the logs, that means Tvheadend is trying to scan an HD mux, but the DM500 does not support HD so it fails with this error. Again, you should only see this error for DVB-S2 muxes.

Also, do the scanned channels work correctly in VLC? Are there glitches?

@runcspelex Does 2.1 work on your setup?

[runcspelex]

honestly, still without final conclusion: scanning seems worked better, when tried with ios satip-scanner .. signal levels jumpy.. scanning with tvh 4.0.8 and Satip DVB viewer without results .. no muxes found at all. had no time to check signal levels or cables.. or maybe i need to reflash ..maybe that's the reason. tried still with just one dm500..

couple days i am not at home now..

2016-03-30 12:35 GMT+03:00 Xavier Mendez notifications@github.com:

@armaghanshahzad https://github.com/armaghanshahzad What happens if you force another network scan? Do new channels get discovered?

It's normal that you see lots of RTSP cmd error 7 on the logs, that means Tvheadend is trying to scan an HD mux, but the DM500 does not support HD so it fails with this error. Again, you should only see this error for DVB-S2 muxes.

Also, do the scanned channels work correctly in VLC? Are there glitches?

@runcspelex https://github.com/runcspelex Does 2.1 work on your setup?

— You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub https://github.com/jmendeth/dm500-satip/issues/1#issuecomment-203346009

[armaghanshahzad]

Channels were scanned again. There was a crash once with the box. Now it is running for few days. I used OSCAM to decrypt that works too. Picture quality is fine in VLC. I have also tried with android satip client no channels. This version works fine with clone boxes.

I have not answered you before because I wanted to confirm the quality and stability,

[runcspelex]

@armaghanshahzad what version of tvh you are you use? what distro?

[armaghanshahzad]

Tvh Build: 4.1.1721 (2016-03-24T05:05:46+0100), and it is running on synology 1151+

[runcspelex]

my config - zentyal 4.2.2 DE on ubu LTS 14.04.1, tvh 4.0.8 asrock m350 usb3 will try compile newer tvh too..

[runcspelex]

so - on tvh 4.1-1724~g41707e1~trusty now works. i can confirm - vlc , kodi works. oscam ws cwc in tvh works. just there is some strange thing - scanning work all times on disecq BB.. (src4) is that minisatip or tvh fault?

[mildsunrise]

I have made an image with the latest minisatip, you can download it here.

You can try it, maybe it solves [some of] the issues you mentioned. However keep in mind it's an unstable version, I've done basic testing but there could be crashes or bugs.

just there is some strange thing - scanning work all times on disecq BB.. (src4) is that minisatip or tvh fault?

It could be a problem with minisatip or with my drivers (probably minisatip).

[armaghanshahzad]

Hi jmendeth,

Do I have to re-flash the image or it is possible to update the required files. Secondly, it will be very handy to have ssh-server and sftp-server for quick updates. Is it possible for you include them in the default image?

Thanks

[mildsunrise]

Do I have to re-flash the image or it is possible to update the required files.

No, you don't need to reflash. You can just login through telnet and issue the following:

killall minisatip; wget -O /bin/minisatip http://cdn.rawgit.com/jmendeth/dm500-satip/228ba3fc72f49568565795d38a4fc40dea123b77/data/minisatip && /etc/init.d/S70satip

This will download and start the new minisatip. To verify, browse to http://DM500/desc.xml and make sure you see minisatip 0.5.

Secondly, it will be very handy to have ssh-server and sftp-server for quick updates. Is it possible for you include them in the default image?

I originally wanted to install dropbear for SSH, but I didn't because it regenerates the keys each time it started, so SSH gets mad every restart. The telnet server doesn't have such a problem, it's also lighter and uses less space.

The big advantage of SSH is, as you said, quick updates. But for now, I don't think it's worth the trouble so I'll keep it off the default image. If you want them, you can either build the image yourself (and enable dropbear when asked) or mount an NFS share.

[runcspelex]

tried 0.5 still can not undersand, what is wrong with disecq setup.. works different, now got channels on AA can not get on bb..

[mildsunrise]

works different, now got channels on AA can not get on bb..

That's weird, but could be attributed to the drivers. I don't have a DiSEqC setup to test, so there's little I can do I'm afraid...

[armaghanshahzad]

I have look through other solutions for satip server. I came across https://github.com/catalinii/minisatip and there are command line switches for diseqc may be we need similar to following which I read from the earlier link:

-d --diseqc ADAPTER1:COMMITTED1-UNCOMMITTED1[,ADAPTER2:COMMITTED2-UNCOMMITTED2[,...]

The first argument is the adapter number, second is the number of committed packets to send to a Diseqc 1.0 switch, third the number of uncommitted commands to sent to a Diseqc 1.1 switch The higher number between the committed and uncommitted will be sent first. eg: -d 0:1-0 (which is the default for each adapter). note: * as adapter means apply to all adapters note: * before committed number enables fast-switch (only voltage/tone)

[runcspelex]

here is how to implement this in vlc link; http://DM500/?msys=dvbs&src=3&freq=12266&pol=h&sr=27500&pids=0,851 do you have some ideas, how we can add here cwc info for dvbcas ?

[mildsunrise]

minisatip is always compiled without dvbcsa support, so any descrambling must be done externally (i.e. by tvheadend). As for DiSEqC, I have never used it so there's little guidance I can give on the matter.

[runcspelex]

sadly spent some hours to check satip 0.5 again.. seems to be - disecq not works with tvh nor vlc used - http://www.inverto.tv/downloads/support.php?id=1789 tried with 5e, 13e, 19,2e, 36e functional just with src=1 (AA) and src=2 (AB) in satip infopage src was changing as requested, signal comes just from AA or AB http:///192.168.1.41/?src=1&freq=11996&sr=27500&pol=h&msys=dvbs&pids=0,4080,4081,4082 http:///192.168.1.41/?src=3&freq=11996&sr=27500&pol=h&msys=dvbs&pids=0,4080,4081,4082 output AA http:///192.168.1.41/?src=2&freq=11611&sr=22000&pol=h&msys=dvbs&pids=0,32,33,36 http:///192.168.1.41/?src=4&freq=11611&sr=22000&pol=h&msys=dvbs&pids=0,32,33,36 output AB my disecq config: AA=4.9e AB=19.2e (BA=13e,BB=36e not connects)

[Korjo]

Hi,

I too am trying to setup my DM500 to feed into Tvheadend. So far the adapters are displaying and the Signal Strength / SNR are both showing when I try to scan but there are no channels returned. The satellite I am trying to use is Optus D1. Details here: http://www.lyngsat.com/Optus-D1.html

I have Tvheadend 4.0.8 running on a Raspberry Pi 3 with OpenELEC. The DM500 has version 2.1 of the image. I have tried with minsatip 0.4 and 0.5 with no difference in results.

Running dvbsnoop as suggested above doesn't show any signal locks and I haven't been able to get anything to Play in VLC so far - but then again I am not sure I am using the correct links for that as there's no spike in signal when I try...

I'll attach a few logs and screenshots, let me know what else would help!

Also, is there any chance this could be attributed to bad LNB settings as that is something I always had to fiddle with on the previous DM500 firmware (Using OpenPLI). I believe mine operates at 10750 MHz.

[mildsunrise]

If there's no change in SNR as you describe, then it's probably because of LNB settings, yes. I'm busy at the moment, but you may find it useful to point VLC to your DM500 directly, passing the frequency and symbol rate manually (look at the example links).

[Korjo]

Cheers for that. I had a go with VLC and had similar results. It seems no matter what I tune to the SNR stays at ~60% but strength will change depending on what frequency is being scanned.

[runcspelex]

according signal strength - there is some issues .. if signal strength is over 75 - 80 % on usual stb (in my case shd-8900 Alien) then dm500satip shows full 100% signal, if signal is 0 or not tuned to correct position - dm500satip sits on ~60% signal level. i got some troubles with scanning too, till i understood, that i can scan only on disecq AA or AB. on those i can reach correct LNBs. and more - with tvh - if tvh do not have correct transponder list - better is to scan muxes 1by1, adding them manually.

[mildsunrise]

if signal strength is over 75 - 80 % on usual stb (in my case shd-8900 Alien) then dm500satip shows full 100% signal, if signal is 0 or not tuned to correct position - dm500satip sits on ~60% signal level.

The "stregth" field on the status page (first bar) corresponds to AGC, which as you say stays at ~60% even when there is no signal. This is because of the hardware, it has nothing to do with my firmware AFAIK.

i got some troubles with scanning too, till i understood, that i can scan only on disecq AA or AB. on those i can reach correct LNBs

So AA and AB work correctly? Hmm, good to know.

[runcspelex]

yes, thats mean 1 of 2 bits works correctly ;) as i wrote before: in satip infopage src was changing as requested, signal comes just from AA or AB http:///192.168.1.41/?**src=1**&freq=11996&sr=27500&pol=h&msys=dvbs&pids=0,4080,4081,4082 http:///192.168.1.41/?**src=3**&freq=11996&sr=27500&pol=h&msys=dvbs&pids=0,4080,4081,4082 both give output AA http:///192.168.1.41/?**src=2**&freq=11611&sr=22000&pol=h&msys=dvbs&pids=0,32,33,36 http:///192.168.1.41/?**src=4**&freq=11611&sr=22000&pol=h&msys=dvbs&pids=0,32,33,36 both give output AB

to jmendeth: no full mux support is the reason, why just 1 connection from mux in tvh available?

[Korjo]

Regarding the LNB LO setting (if that is indeed my issue), is there a way to change that within minisatip or is it be be passed in by tvheadend? Hours Googling has not turned up many results and there's no option for this that I can find within the tvheadend settings.

[mildsunrise]

No, unfortunately f_LO is hardcoded and only the SAT>IP server (minisatip) has to take it into account. It's hardcoded here, so if you want to change it you should rebuild minisatip and the firmware image.

[razajd]

Hello, I have been testing the latest image with a Clone DM500-s and its working great with universal lnbs via basic diseqc, im a noob, so still getting my way around oscam and things, my post here is related to setting up a C-Band LNB in TVheadend. any pointers how to do that?

[mildsunrise]

@Korjo @razajd What frequency ranges do your LNBs operate in? If there's enough demand, an option could be added to minisatip to allow for other kinds of LNB...

@Korjo The problem could be with my drivers not correctly setting the continuous tone

[razajd]

LOF/L: 5150 LOF/H: 5750

This is what i use in stbs for Paksat @38E and Asiasat 105.5..

I tried working with the instructions here to try n build something.. but as i am total noob with Linux, it flew over my head..

[Korjo]

Mine is not so much of a range, I have to set 10750 for all of LO High, Low and Threshold but then it works with no trouble.

[mildsunrise]

@razajd @Korjo I've made a special version of minisatip for your LNBs. To run it, please telnet to the DM500 and issue the following command:

killall minisatip; wget -O /bin/minisatip http://cdn.rawgit.com/jmendeth/dm500-satip/76df8de6ae856803ecac56c2252b2aa01131a1b6/data/minisatip && /etc/init.d/S70satip

Note that although the change is very simple, I'm completely in the blind with this...

[razajd]

Tried the above with telnet: got the below output. no luck with scanning in Tvheadend

mknod: demux0: File exists
mknod: dvr0: File exists
mknod: frontend0: File exists
mknod: net0: File exists

TVheadend says:

2016-05-23 21:28:42.000 satip: DVB-S/S2 frequency 4004000 out of range universal LNB

[mildsunrise]

@razajd Ah, it appears that tvheadend assumes you have a universal LNB. There is no option to disable this check, you should ideally recompile tvheadend without it, or use an alternative frontend.

As a quick hack to test that the firmware is doing its job, I've built another version of minisatip that should fool tvheadend into allowing those frequencies:

killall minisatip; wget -O /bin/minisatip http://cdn.rawgit.com/jmendeth/dm500-satip/07d22bb890b49e8bd2d2382d635101036a1aaec1/data/minisatip && /etc/init.d/S70satip

After doing this, make sure the Disable device-/firmware-specific workarounds checkbox is not ticked, and try scanning again.

[razajd]

yeah.. seems sat>ip is somewhat for Universal LNBs. Tried the above.. got the below error:

/bin/minisatip: line 2: syntax error: unexpected "("

[mildsunrise]

That's weird... could you reboot the DM500 and use this command instead?

killall minisatip; wget -O /bin/minisatip http://cdn.rawgit.com/jmendeth/dm500-satip/bf05d58d3177dd25adc02cc7cc47e9b3999872b0/data/minisatip && /etc/init.d/S70satip

[razajd]

Still getting similar result..

Escape character is '^]'.
dreambox login: root
Password:
# killall minisatip; wget -O /bin/minisatip http://cdn.rawgit.com/jmendeth/dm500-satip/bf05d58d3177dd25adc02cc7cc47e9b3999872b0/data/minisatip && /etc/init.d/S70satip
Connecting to cdn.rawgit.com (198.232.124.74:80)
minisatip            100% |***********************************|   389k  0:00:00 ETA
mknod: demux0: File exists
mknod: dvr0: File exists
mknod: frontend0: File exists
mknod: net0: File exists
/bin/minisatip: line 2: syntax error: unexpected "("

Later will try refalshing and running the last command by scratch.. thanks for the effort J.

[mildsunrise]

Ahhhhh mea culpa! Sorry, this time for real:

killall minisatip; wget -O /bin/minisatip http://cdn.rawgit.com/jmendeth/dm500-satip/ab32c4ee905eabe018a1aa9c1005a35ca71d4184/data/minisatip && /etc/init.d/S70satip

[Korjo]

@jmendeth thank you so much for making those extra builds. Unfortunately I have tried both of them and am still seing the 60% SNR. The LNB I have is the 'Quad' one on this page.

From what you said about setting of the continuous tone, maybe the problem's there as I had to turn the tone off fully to get the DM500 working with this LNB.

[mildsunrise]

@mxl9236 On very general terms: To compile minisatip you need to first build an initial image. Then, use the generated toolchain to compile minisatip. Replace the generated executable and build the image again.

However, minisatip 0.4 (the stable version, used in the releases) will not compile without some changes. The easiest way is to clone my fork and use the build.sh script:

# Add your generated toolchain to PATH
PATH=$PATH:/path/to/dm500-satip/buildroot/output/host/usr/bin
# Clone & build the modified source code
git clone https://github.com/jmendeth/minisatip.git -b dm500-satip-2.1 && cd minisatip
./build.sh
# Copy the minisatip executable back
cp minisatip /path/to/dm500-satip/data
# Now rebuild the firmware

The development version of minisatip (0.7) has all the required fixes so it can be compiled directly without changing anything:

# Add your generated toolchain to PATH
PATH=$PATH:/path/to/dm500-satip/buildroot/output/host/usr/bin
# Clone & build minisatip
git clone https://github.com/catalini/minisatip.git -b 0.7 && cd minisatip
./configure --host=powerpc-buildroot-linux-uclibc \
      --disable-dvbca --disable-dvbaes --disable-dvbcsa --disable-satipc
make

[mildsunrise]

@mxl9236 Did you get it working with your LNB?

[robbieb43]

Hi

Using an old Clone DM500S which runs OK will latest commando build etc and is seeing a signal. I am on a SMATV (quartro LNB with tiered multiswitch) system but not sure it is an issue as I use minisatip on my VU+ without any issues. The system did not require any box settings either - I just tell it there is a universal LNB. (I use the gigablue binary from here https://minisatip.org/forum/viewtopic.php?t=371).

Two initial satip-dm500 problems: V2.2 does not seem to be booting at all (not found by fing etc). V2.1 boots OK and announces itself to TVheadend OK but will not find any channels. Ditto with DVBAPP from the SAT>IP site. On some frequencies, the SNR bar goes orange but that's all.

[mildsunrise]

V2.2 does not seem to be booting at all (not found by fing etc).

This has happened on two of my boxes, they seem to have a corrupted flash memory and won't boot 2.2. I should add a warning or something.

V2.1 boots OK and announces itself to TVheadend OK but will not find any channels. Ditto with DVBAPP from the SAT>IP site. On some frequencies, the SNR bar goes orange but that's all.

Hmm some initial tests... Was it working (when used as a regular STB) on that setup? If it was, I'd help to see the minisatip log; ssh into the DM500 and run

killall minisatip; minisatip -R /usr/share/minisatip/html -x 80 -flll

Then start scanning with TVHeadend for instance (just a minute or so), and save the log. Then reboot the DM500.

[robbieb43]

Yes this was an ancient old clone that was only saved from the skip when I saw this project 👍 I suspect the internal architecture varies.

That said the log output from 2.1 gives promise: here is a snippet but the full log is here:

https://www.dropbox.com/s/29am6kmhlaf73fz/dm500.log?dl=0 First part of log:

[01/01 00:04:57.000]: Starting minisatip version 0.4.1, compiled with s2api version: 0500 [01/01 00:04:57.001]: New UDP socket 3 bound to 0.0.0.0:1900 [01/01 00:04:57.002]: setting multicast for 239.255.255.250 [01/01 00:04:57.003]: New UDP socket 4 bound to 239.255.255.250:1900 [01/01 00:04:57.004]: sockets_add: handle 3 (type 0) returning socket index 0 [0.0.0.0:0] read: 0x10003318 [01/01 00:04:57.004]: sockets_add: handle 4 (type 0) returning socket index 1 [0.0.0.0:0] read: 0x10003318 [01/01 00:04:57.005]: sockets_add: handle 5 (type 2) returning socket index 2 [0.0.0.0:0] read: 0x1000485c [01/01 00:04:57.005]: sockets_add: handle 6 (type 2) returning socket index 3 [0.0.0.0:0] read: 0x1000485c [01/01 00:04:57.006]: starting init_hw 0 [01/01 00:04:57.027]: trying to open [0] adapter 0 and frontend 0 [01/01 00:04:57.030]: opened DVB adapter 0 fe:7 dvr:8 [01/01 00:04:57.036]: Done setting DVR buffer to 5775360 bytes [01/01 00:04:57.037]: adapter.c:138 allocation_wrapper malloc allocated 25014 bytes at 0x10044040 [01/01 00:04:57.038]: deleting pids on adapter 0, sid -1, pids=NULL [01/01 00:04:57.067]: unable to query frontend, perhaps DVB-API < 5.5 ? [01/01 00:04:57.067]: Detected adapter 0 handle 7 DVB Card Name: ST STV0299 DVB-S [01/01 00:04:57.067]: Detected delivery system for adapter 0: dvbs [5] [01/01 00:04:57.068]: sockets_add: handle 8 (type 5) returning socket index 4 [0.0.0.0:0] read: 0x100032e8 [01/01 00:04:57.069]: done opening adapter 0 fe_sys 5 0 0 0 [01/01 00:04:57.069]: done init_hw 1 [01/01 00:04:57.069]: Initializing with 1 devices [01/01 00:04:57.125]: sockets_add: handle 9 (type 1) returning socket index 5 [192.168.1.165:58416] read: 0x100032e8 [01/01 00:04:57.125]: minisatip.c:466 get_sid returns NULL for s_id = -1 [01/01 00:04:57.126]: read RTSP (from handle 9 sock_id 5, len: 0, sid -1): SETUP rtsp://192.168.1.170/?src=1&fe=1&freq=11081&sr=22000&msys=dvbs&mtype=qpsk&pol=h&fec=56&ro=0.35 RTSP/1.0 Transport: RTP/AVP;unicast;client_port=40484-40485 CSeq: 1

[01/01 00:04:57.126]: detect_dvb_parameters (S)-> src=1&fe=1&freq=11081&sr=22000&msys=dvbs&mtype=qpsk&pol=h&fec=56&ro=0.35 [01/01 00:04:57.127]: detect_dvb_parameters (E) -> src=1, fe=1, freq=11081000, fec=5, sr=22000000, pol=2, ro=0, msys=5, mtype=0, plts=2, bw=8000000, inv=2, pids=NULL - apids=NULL - dpids=NULL x_pmt=NULL [01/01 00:04:57.127]: Setup stream -1 parameters, sock_id 5, handle 9 [01/01 00:04:57.128]: stream.c:212 get_sid returns NULL for s_id = -1 [01/01 00:04:57.128]: stream.c:484 allocation_wrapper malloc allocated 321 bytes at 0x1004a200 [01/01 00:04:57.129]: stream.c:486 allocation_wrapper malloc allocated 321 bytes at 0x1004a348 [01/01 00:04:57.129]: stream.c:488 allocation_wrapper malloc allocated 321 bytes at 0x1004a490 [01/01 00:04:57.129]: stream.c:490 allocation_wrapper malloc allocated 321 bytes at 0x1004a5d8 [01/01 00:04:57.130]: stream.c:492 allocation_wrapper malloc allocated 1326 bytes at 0x1004a720 [01/01 00:04:57.130]: Setup stream done: sid: 0 (e:1) for sock 5 handle 9 [01/01 00:04:57.130]: copy_dvb_param start -> src=0, fe=0, freq=0, fec=9, sr=0, pol=0, ro=3, msys=0, mtype=0, plts=2, bw=8000000, inv=2, pids=NULL, apids=NULL, dpids=NULL x_pmt=NULL [01/01 00:04:57.131]: copy_dvb_parameters -> src=1, fe=1, freq=11081000, fec=5 sr=22000000, pol=2, ro=0, msys=5, mtype=0, plts=2, bw=8000000, inv=2, pids=NULL, apids=NULL, dpids=NULL x_pmt=NULL [01/01 00:04:57.131]: decode_transport ->type 2, ttl 0 new socket to: 192.168.1.165:40484 [01/01 00:04:57.132]: New UDP socket 10 bound to 0.0.0.0:5500 [01/01 00:04:57.133]: New UDP socket 10 connected to 192.168.1.165:40484 [01/01 00:04:57.133]: output UDP buffer size for socket 10 is 217088 bytes [01/01 00:04:57.133]: New UDP socket 11 bound to 0.0.0.0:5501 [01/01 00:04:57.134]: New UDP socket 11 connected to 192.168.1.165:40485 [01/01 00:04:57.134]: sockets_add: handle 11 (type 6) returning socket index 6 [0.0.0.0:0] read: 0x10003318 [01/01 00:04:57.136]: reply -> 9 (192.168.1.165:58416) CL:0 : RTSP/1.0 200 OK Date: Thu, Jan 1 00:04:57 1970 GMT Cseq: 1 Transport: RTP/AVP;unicast;destination=192.168.1.165;source=192.168.1.170;client_port=40484-40485;server_port=5500-5501 Session: 1804289383;timeout=30 com.ses.streamID: 1 Server: minisatip/0.4.1

[01/01 00:04:57.137]: read RTSP (from handle 9 sock_id 5, len: 0, sid 0): PLAY rtsp://192.168.1.170/stream=1?addpids=18,57,299,3002,3003,8187 RTSP/1.0 Session: 1804289383 CSeq: 2

[01/01 00:04:57.138]: detect_dvb_parameters (S)-> addpids=18,57,299,3002,3003,8187 [01/01 00:04:57.138]: detect_dvb_parameters (E) -> src=-1, fe=-1, freq=-1, fec=-1, sr=-1, pol=-1, ro=-1, msys=-1, mtype=-1, plts=-1, bw=-1, inv=-1, pids=NULL - apids=18,57,299,3002,3003,8187 - dpids=NULL x_pmt=NULL [01/01 00:04:57.138]: Setup stream 0 parameters, sock_id 5, handle 9 [01/01 00:04:57.139]: copy_dvb_param start -> src=1, fe=1, freq=11081000, fec=5, sr=22000000, pol=2, ro=0, msys=5, mtype=0, plts=2, bw=8000000, inv=2, pids=NULL, apids=NULL, dpids=NULL x_pmt=NULL [01/01 00:04:57.139]: copy_dvb_parameters -> src=1, fe=1, freq=11081000, fec=5 sr=22000000, pol=2, ro=0, msys=5, mtype=0, plts=2, bw=8000000, inv=2, pids=NULL, apids=18,57,299,3002,3003,8187, dpids=NULL x_pmt=NULL [01/01 00:04:57.140]: Play for stream 0, type 2, rsock 10, adapter -1, sock_id 5 handle 9 [01/01 00:04:57.140]: starting init_hw 1 [01/01 00:04:57.141]: get free adapter 0 - a[0] => e:1 m:-1 sid_cnt:0 f:0 pol=0 [01/01 00:04:57.141]: Got adapter 0 on socket 5 [01/01 00:04:57.141]: set adapter 0 for stream 0 m:0 s:1 [01/01 00:04:57.142]: setting DVB parameters for adapter 0 - master_sid 0 sid 0 old f:0 [01/01 00:04:57.142]: deleting pids on adapter 0, sid -1, pids=NULL [01/01 00:04:57.142]: copy_dvb_param start -> src=0, fe=0, freq=0, fec=9, sr=0, pol=0, ro=3, msys=0, mtype=0, plts=2, bw=8000000, inv=2, pids=NULL, apids=NULL, dpids=NULL x_pmt=NULL [01/01 00:04:57.143]: copy_dvb_parameters -> src=1, fe=1, freq=11081000, fec=5 sr=22000000, pol=2, ro=0, msys=5, mtype=0, plts=2, bw=8000000, inv=2, pids=NULL, apids=18,57,299,3002,3003,8187, dpids=NULL x_pmt=NULL [01/01 00:04:57.143]: adding pids to adapter 0, sid 0, pids=18,57,299,3002,3003,8187 [01/01 00:04:57.144]: Dumping pids table for adapter 0, pid errors 0 [01/01 00:04:57.144]: pid 18, fd 0, type 0 packets 0, d/c errs 0/0, flags 2, key 255, sids: 0 -1 -1 -1 -1 -1 -1 -1 [01/01 00:04:57.144]: pid 57, fd 0, type 0 packets 0, d/c errs 0/0, flags 2, key 255, sids: 0 -1 -1 -1 -1 -1 -1 -1 [01/01 00:04:57.145]: pid 299, fd 0, type 0 packets 0, d/c errs 0/0, flags 2, key 255, sids: 0 -1 -1 -1 -1 -1 -1 -1 [01/01 00:04:57.145]: pid 3002, fd 0, type 0 packets 0, d/c errs 0/0, flags 2, key 255, sids: 0 -1 -1 -1 -1 -1 -1 -1 [01/01 00:04:57.146]: pid 3003, fd 0, type 0 packets 0, d/c errs 0/0, flags 2, key 255, sids: 0 -1 -1 -1 -1 -1 -1 -1 [01/01 00:04:57.146]: pid 8187, fd 0, type 0 packets 0, d/c errs 0/0, flags 2, key 255, sids: 0 -1 -1 -1 -1 -1 -1 -1 [01/01 00:04:57.147]: send_diseqc fd 7, pos = 0, pol = 1, hiband = 0, diseqc => e0 10 38 f2 00 [01/01 00:04:57.301]: tuning to 11081000(1331000) pol: h (2) sr:22000000 fec:56 delsys:dvbs mod:qpsk rolloff:0.35 pilot: , ts clear=147, ts pol=147 [01/01 00:04:57.302]: Dumping pids table for adapter 0, pid errors 0 [01/01 00:04:57.302]: pid 18, fd 0, type 0 packets 0, d/c errs 0/0, flags 2, key 255, sids: 0 -1 -1 -1 -1 -1 -1 -1 [01/01 00:04:57.303]: pid 57, fd 0, type 0 packets 0, d/c errs 0/0, flags 2, key 255, sids: 0 -1 -1 -1 -1 -1 -1 -1 [01/01 00:04:57.303]: pid 299, fd 0, type 0 packets 0, d/c errs 0/0, flags 2, key 255, sids: 0 -1 -1 -1 -1 -1 -1 -1 [01/01 00:04:57.304]: pid 3002, fd 0, type 0 packets 0, d/c errs 0/0, flags 2, key 255, sids: 0 -1 -1 -1 -1 -1 -1 -1 [01/01 00:04:57.305]: pid 3003, fd 0, type 0 packets 0, d/c errs 0/0, flags 2, key 255, sids: 0 -1 -1 -1 -1 -1 -1 -1 [01/01 00:04:57.305]: pid 8187, fd 0, type 0 packets 0, d/c errs 0/0, flags 2, key 255, sids: 0 -1 -1 -1 -1 -1 -1 -1 [01/01 00:04:57.306]: setting filter on PID 18 for fd 12 [01/01 00:04:57.307]: setting filter on PID 57 for fd 13 [01/01 00:04:57.308]: setting filter on PID 299 for fd 14 [01/01 00:04:57.309]: setting filter on PID 3002 for fd 15 [01/01 00:04:57.309]: setting filter on PID 3003 for fd 16 [01/01 00:04:57.310]: setting filter on PID 8187 for fd 17 [01/01 00:04:57.311]: reply -> 9 (192.168.1.165:58416) CL:0 : RTSP/1.0 200 OK Date: Thu, Jan 1 00:04:57 1970 GMT Session: 1804289383 Cseq: 2 RTP-Info: url=rtsp://192.168.1.170/stream=1;seq=310;rtptime=297 Range: npt=0.000- Server: minisatip/0.4.1

Many thanks for the help. I am trying to get an Ubuntu 14 image up for a stab at building a minisatip 0.7 as a next step but this will take a few days as I get the hardware in place.

I am also swaying towards a tuning/usb problem as I recall when I have been aligning dishes in the past, a SNR reading like this is quite common when the LNB is lying on the floor with no signal.

Rob

[robbieb43]

Hi Xavier

Some log output uploaded (tvheadend acting as client). As an aside, I have some doubts emerging about the sat>IP windows client from their web site as I am trying it on my working minisatip on my VU clone, and it also seems to be not finding channels. From now on I will use tvheadend in the diagnostics.

Many thanks for the help.

Rob

Sent from my iPad

On 26 May 2017, at 22:20, Xavier Mendez notifications@github.com wrote:

V2.2 does not seem to be booting at all (not found by fing etc).

This has happened on two of my boxes, they seem to have a corrupted flash memory and won't boot 2.2. I should add a warning or something.

V2.1 boots OK and announces itself to TVheadend OK but will not find any channels. Ditto with DVBAPP from the SAT>IP site. On some frequencies, the SNR bar goes orange but that's all.

Hmm some initial tests... Was it working (when used as a regular STB) on that setup? If it was, I'd help to see the minisatip log; ssh into the DM500 and run

killall minisatip; minisatip -R /usr/share/minisatip/html -x 80 -flll Then start scanning with TVHeadend for instance (just a minute or so), and save the log. Then reboot the DM500.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

[mildsunrise]

Hmm everything seems normal on the minisatip side. Run dvbsnoop -s signal and while that's running, scan with Tvheadend. Note if the values of SNR, sig or FLAGS change.