Dm500 not working. #1
Comments
|
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 |
|
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. |
Whoa, that's really unexpected. Could you open a separate issue for that original?
Hmm... Please telnet to that clone and login ( |
|
i got the similar issue |
|
If there is no lock, then this is a well-known issue with some boards. |
|
It's fixed it in the latest kernel. |
|
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" Hope this helps Regards |
|
@armaghanshahzad What happens if you force another network scan? Do new channels get discovered? It's normal that you see lots of Also, do the scanned channels work correctly in VLC? Are there glitches? @runcspelex Does 2.1 work on your setup? |
|
honestly, still without final conclusion: couple days i am not at home now.. 2016-03-30 12:35 GMT+03:00 Xavier Mendez [email protected]:
|
|
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, |
|
@armaghanshahzad |
|
Tvh Build: 4.1.1721 (2016-03-24T05:05:46+0100), and it is running on synology 1151+ |
|
my config - zentyal 4.2.2 DE on ubu LTS 14.04.1, tvh 4.0.8 |
|
so - on tvh 4.1-1724 |
|
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.
It could be a problem with minisatip or with my drivers (probably minisatip). |
|
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 |
No, you don't need to reflash. You can just login through telnet and issue the following: This will download and start the new minisatip. To verify, browse to
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. |
|
tried 0.5 |
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... |
|
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. |
|
here is how to implement this in vlc link; |
|
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. |
|
sadly |
|
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.
|
|
If there's no change in SNR as you describe, then it's probably because of LNB settings, yes. |
|
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. |
|
according signal strength - there is some issues .. |
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.
So AA and AB work correctly? Hmm, good to know. |
|
yes, thats mean 1 of 2 bits works correctly ;) to jmendeth: |
|
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. |
|
No, unfortunately fLO 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. |
|
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? |
|
LOF/L: 5150 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.. |
|
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. |
|
@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: Note that although the change is very simple, I'm completely in the blind with this... |
|
Tried the above with telnet: got the below output. no luck with scanning in Tvheadend TVheadend says:
|
|
@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: After doing this, make sure the Disable device-/firmware-specific workarounds checkbox is not ticked, and try scanning again. |
|
yeah.. seems sat>ip is somewhat for Universal LNBs. Tried the above.. got the below error:
|
|
That's weird... could you reboot the DM500 and use this command instead? |
|
Still getting similar result.. Later will try refalshing and running the last command by scratch.. thanks for the effort J. |
|
Ahhhhh mea culpa! Sorry, this time for real: |
|
@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. |
|
@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 # 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 firmwareThe 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 |
|
@mxl9236 Did you get it working with your LNB? |
|
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. |
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.
Hmm some initial tests... Was it working (when used as a regular STB) on that setup? Then start scanning with TVHeadend for instance (just a minute or so), and save the log. Then reboot the DM500. |
|
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 [01/01 00:04:57.000]: Starting minisatip version 0.4.1, compiled with s2api version: 0500 [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.137]: read RTSP (from handle 9 sock_id 5, len: 0, sid 0): [01/01 00:04:57.138]: detect_dvb_parameters (S)-> addpids=18,57,299,3002,3003,8187 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 |
|
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 ***@***.***> 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.
|
|
Hmm everything seems normal on the minisatip side. Run |
|
This seems to be pretty much how it carried on throughout the scan:
cycle: 167383 d_time: 0.004 s Sig: 65535 SNR: 65535 BER: 0 Stat: 0x01 [SIG ]
cycle: 167384 d_time: 0.005 s Sig: 65535 SNR: 65535 BER: 0 Stat: 0x01 [SIG ]
cycle: 167385 d_time: 0.004 s Sig: 65535 SNR: 65535 BER: 0 Stat: 0x01 [SIG ]
cycle: 167386 d_time: 0.004 s Sig: 65535 SNR: 65535 BER: 0 Stat: 0x01 [SIG ]
cycle: 167387 d_time: 0.005 s Sig: 65535 SNR: 65535 BER: 0 Stat: 0x01 [SIG ]
cycle: 167388 d_time: 0.004 s Sig: 65535 SNR: 65535 BER: 0 Stat: 0x01 [SIG ]
cycle: 167389 d_time: 0.004 s Sig: 65535 SNR: 65535 BER: 0 Stat: 0x01 [SIG ]
cycle: 167390 d_time: 0.004 s Sig: 65535 SNR: 65535 BER: 0 Stat: 0x01 [SIG ]
cycle: 167391 d_time: 0.004 s Sig: 65535 SNR: 65535 BER: 0 Stat: 0x01 [SIG ]
cycle: 167392 d_time: 0.005 s Sig: 65535 SNR: 65535 BER: 0 Stat: 0x01 [SIG ]
cycle: 167393 d_time: 0.004 s Sig: 65535 SNR: 65535 BER: 0 Stat: 0x01 [SIG ]
cycle: 167394 d_time: 0.013 s Sig: 65535 SNR: 65535 BER: 0 Stat: 0x01 [SIG ]
cycle: 167395 d_time: 0.004 s Sig: 65535 SNR: 65535 BER: 0 Stat: 0x01 [SIG ]
cycle: 167396 d_time: 0.003 s Sig: 65535 SNR: 65535 BER: 0 Stat: 0x02 [CARR ]
cycle: 167397 d_time: 0.091 s Sig: 0 SNR: 34722 BER: 8224 Stat: 0x00 []
cycle: 167398 d_time: 0.005 s Sig: 0 SNR: 34719 BER: 8216 Stat: 0x02 [CARR ]
cycle: 167399 d_time: 0.005 s Sig: 0 SNR: 34599 BER: 8216 Stat: 0x02 [CARR ]
cycle: 167400 d_time: 0.004 s Sig: 0 SNR: 34566 BER: 8216 Stat: 0x02 [CARR ]
cycle: 167401 d_time: 0.005 s Sig: 0 SNR: 34515 BER: 8216 Stat: 0x00 []
cycle: 167402 d_time: 0.004 s Sig: 0 SNR: 34521 BER: 8216 Stat: 0x02 [CARR ]
cycle: 167403 d_time: 0.004 s Sig: 0 SNR: 33798 BER: 8224 Stat: 0x02 [CARR ]
cycle: 167404 d_time: 0.005 s Sig: 0 SNR: 34524 BER: 8224 Stat: 0x02 [CARR ]
cycle: 167405 d_time: 0.004 s Sig: 0 SNR: 34431 BER: 8224 Stat: 0x02 [CARR ]
cycle: 167406 d_time: 0.004 s Sig: 0 SNR: 35295 BER: 8224 Stat: 0x02 [CARR ]
cycle: 167407 d_time: 0.004 s Sig: 0 SNR: 35307 BER: 8224 Stat: 0x02 [CARR ]
cycle: 167408 d_time: 0.004 s Sig: 0 SNR: 34554 BER: 8224 Stat: 0x02 [CARR ]
..
Looks like lack of signal/LNB (i.e. noise) in wrong mode perhaps?
Rob
From: Xavier Mendez [mailto:[email protected]]
Sent: Sunday, May 28, 2017 11:03 AM
To: jmendeth/dm500-satip <[email protected]>
Cc: robbieb43 <[email protected]>; Comment <[email protected]>
Subject: Re: [jmendeth/dm500-satip] Dm500 not working. (#1)
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.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub <#1 (comment)> , or mute the thread <https://github.com/notifications/unsubscribe-auth/AIA2KysaOdkbzruIqNsecZ5RlyS8G1W7ks5r-UZZgaJpZM4H1K6C> . <https://github.com/notifications/beacon/AIA2KzQ-2vMkB-8Eexs9jxWrtB8MJ-1qks5r-UZZgaJpZM4H1K6C.gif>
|
|
Just tried a direct approach using tested urls from working minisatip on dm800. It looks like the box tried to tune but does not get a lock so gives up(?): rtsp://192.168.1.170:554/?src=2&freq=11464&pol=h&ro=0.35&msys=dvbs&mtype=qpsk&plts=off&sr=22000&fec=56&pids=0,17,18,262,2310,2320 FrontEnd Info...Device: /dev/dvb/adapter0/frontend0 Basic capabilities: Current parameters: cycle: 1516 d_time: 0.004 s Sig: 0 SNR: 37488 BER: 8224 Stat: 0x00 [] Fails, then sets back to idle: FrontEnd Info...Device: /dev/dvb/adapter0/frontend0 Basic capabilities: Current parameters: cycle: 387 d_time: 0.005 s Sig: 0 SNR: 39735 BER: 8224 Stat: 0x00 [] Rob |
|
To quote your above post "Ahhhhh mea culpa!" While pluging in my serial lead I must have knackered the LNB input: my tests with my Satlink meter on the wall socket did not pick this up :-( - new plug and all sorted. Very very sorry. But happy to say all working now. As for 2.2, I guess it must be a hardware incompatibility but 2.1 working fine out of the box. Learned a lot in the process - perhaps I will have a play with my DM500C next! Thanks Rob |
|
Glad to know it's working. Yes, it definitely appeared like there was no carrier at all... (PS: you can try As for 2.2, I've just released version 2.3 which now includes a 'static' image you can flash in your case.
Great ^^ Note that DM500C and DM500T are not supported [yet?]. |
|
Thanks Xavier - great help. Interestingly 2.3 (non static) works fine out of the box. (off topic but: Thanks also for the tip on http as this should help my stack options for my Raspberry PI transcoding layer. The rtsp seemed to rule out a modified "rtranscode" and so I have been trying to to refine a gstreamer lash-up with tvheadend.) Will let you know how I get on with DVB-C. |
|
@mildsunrise Fist of all thankyou for your wonderful contribution. I have been using the image with my dm500 for ku band lnbs but it is not working with cband lnbs please suggest me what to do. |
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
The text was updated successfully, but these errors were encountered: