Posts by musogeek

Quote from smart0742

I´m in Friday-Sunday :) Now .. ¿how do I get to Liverpool from Manchester airport on a Friday afternoon????

We don't even know who you are or where you are from - maybe an intro post is more appropriate?

Quote from triscross

while you had it running did you notice any improvement

To be honest I didn't notice - The OS GUI was very slow on the machine, but running as a server I don't really see any difference - I suppose it depends on how closely you are analysing it, but if you have to look hard to notice a difference, then I don't think your peers will bother doing the same!

either me or Sandman is at crossed wires here - I thought you meant on your PC server, and Sandman seems to think you mean on a receiver...:misdoubt:

I was using CCcam - in fact a whole ubuntu OS on a 4gb micro SD card plugged in to a USB converter. - It did the job but it did get quite hot so not sure how long it would have lasted, but it was running like this for about 5-6 weeks with no issues. Not sure how much of it will be stored in ram during use, but my Lappy HD that is running my server is spinning all the time so I would imagine that it does access it alot. I wouldn't see an issue with using an SSD and would think it would be a safer option than what I was using!

because the unit has plug and play tuners, you would usually find that the warranty is still intact - I know that if it was bought from sat-shop for example, they would accept a return from the original purchaser within the warranty period. These boxes are usually quite good, wondering if you have tried reflashing it?

can't comment on what I think is the best - never had the receiver - take a look here;

enigma1-support
dm500&clone-images

Open up the receiver to see if the tuners are connected correctly inside - tuners in the Qbox are rem***ble, and are easy to check - each tuner should fit firmly on several rows of pins, and one should overlap the other, and then is kept in place with a screw. Inside there are also 2 patch leads running from the tuners to the input and outputs on the back of the receiver. Make sure these are tight and installed correctly.

Quote from deerhunter290378

ok so why on my system if im watching 28.2 and a recording starts on 28.2 it moves my dish and records on tuner b then greying out the multisats - exactly the opposite of above problem? , i have tuner a as 28.2 fixed and tuner b as usals??

Because that is the other side of the coin. Enigma2 is not ideal at setting priorities that would be useful for those of us (and that is a lot) who have one fixed sly and one motorised. What would be ideal is if you could tell it to always record on the fixed dish as a priority regardless of whether you are watching a channel on the fixed dish or motorised, that way, you would always have the motorised free. How it works at the moment is that it will prioritise tuner A first, and if it is being used, then will go to tuner B. The idea of having your fixed on tuner A and motorised on Tuner B is so that once the recording has started, you can then use tuner B - the problem being is if you were already watching something on your fixed, and then a recording starts on another transponder in the same position, then it will not use tuner A, as it is taken. Best solution I have found is to have 2 receivers, that way I am in control!

Quote from dekelster

Could someone tell me the correct tuner config for my desired setup.

I have a fixed dish pointed at 28.2 and a motorised dish with twin lnb. (2nd output is not used)

I have tuner one setup as advanced which is fed via the motorised dish & tuner 2 set as simple and fixed at 28.2 this is fed from the fixed dish.

This works fine as long as i'm not recording anything on 28.2. If i am recording on 28.2 then I can't view any feeds from the motorised dish. (all grayed out)

ta

Display More

Sounds to me like a classic priority issue - when you are recording it uses tuner A, and if your tuner A is motorised, then you can only use fixed on tuner B - unless you are watching something before the recording starts. If this is the case then it will use tuner B to record - not a perfect solution, but If you swapped so your fixed is on tuner A and motorised on Tuner B, then if you decide to watch something that isn't on 28.2e during a recording, then you can, because it will be recording on tuner A.

One reason I bought it was for the supposed DVB-T support that isn't but I still think it is a great little receiver, and compliments my Vu+ Duo! Not tried Oscam on the TeamRed but know it works on AAF image.

The Gigablue doesn't yet seem to support the USB DVB-T tuner properly as of yet. You can get some sort of success with v2 teamred firmware (we are now on v4), but there was no sound on the receiver when I tried it with an af9015 chipset tuner, but I managed a picture. The odd thing is that the TeamRed developers seem to suggest that they support a number of DVB-T tuners, but there seems to be no account of anything working from v3. It does seem to recognise the tuner is there, but it shows in the tuner config as a vtuner dvb-s - and there is no way to scan it. I have tried with 2 af9015 chipset dual tuner sticks and also a wintv n***-t.

The openAAF seems to be further behind still in getting this to work. I can't see it being a priority while they are trying to sell the 800SE model, which has the option of a terrestrial tuner for an extra cost, infact it seems to have gone backwards since version v3 on the TeamRed firmware, which leaves me wondering if this is related?

I think either wait, or sell the solo and get an 800SE with a DTT if you can't wait.

Quote from cardreader

The whole weekend for me too please!!!!

all good works on forum

where you travelling from and how you getting here?

Well you said your cards are not updating, do you mean that the entitlements are running or will be running out? -what card is it? have you managed to get the card to update before?

There are some guides on the forum about updating your card, but if you can be a bit more specific about your problem we can point you in the right place...

Quote from sparkey

the dhcp on the router does it need to be on

would leave this on - can be turned off but will be more difficult setting up your other devices

Does your router support dyndns? My router, infact the last 3 routers I have had enable you to put in dyndns details so on router reboot it should as far as I am aware update your IP address with your dyndns. If you have too many reboots then you can get locked out from dyndns. If you have issues with logging on then go to their website to reset your password.

Still you say you have problems with your entitlements updating? Still would need more info on this part of your problem to help there.

Had to move this post as the section you posted in was for if all else fails and you require teamviewer help. You will get best help if you post in the right sections because more people will be able to help.
If all else fails and no one can help in the open forums, then that is still an option as a final resort...

If you are using dhcp on your router, there could be an IP conflict going on somewhere. Depending on your router, there is normally a way to fix a device (using the device's mac address) to a fixed IP address on your router, so then dhcp will not try to set an IP address that may conflict with one that you have fixed on another device. I am assuming you have chosen a static IP address on your box rather than dhcp? This is vital.

Is this two separate issues you have as well, as you say that the card isn't updating?

No issues with Oscam to Oscam, maybe there is a problem with either the accout you set for your peer in oscam.user, or the way your peer has you set up in their reader account in oscam.server - assuming that all is ok with his other peers and your other peers, then that is probably where the issue lies - and without seeing this, then I can't see what is or might be wrong.

if you are just using CCcam read your card and to share internally, then you don' need

N: 127.0.0.1 10000 linuxsat support 01 02 03 04 05 06 07 08 09 10 11 12 13 14 256

in either of the 2 receivers. This would be used if you are using Oscam as a cardreader. I assume this isn't the case or you might have posted your oscam configs as well.

so delete this line in both CCcam.cfg files

put the first CCcam.cfg you have posted on the receiver which has your local card

put the second in the receiver that you are sharing this to, but take a look at how you have the line in the secong CCcam.cfg;

F: 192.168.0.9 12000 SHARE JORDAN1

this is wrong.

where you put F: - this should be C:
192.168.0.9 should be the IP address of the receiver with the card in - so assuming it is, then this line should be

C: 192.168.0.9 12000 SHARE JORDAN1

boxkey needs to be in the CCcam.cfg where your card is, not the one you are sharing it to

BOXKEY: /dev/sci0 xxxxxxxx

been doing some googling and there are a few things that come up not sure if it is all related to your issue - stick with it, I am sure someone will be able so help! - Do you need to use Oscam? you could read your cards in CCcam direct - that is how I have mine set up.
another long shot but worth a try

try adding the following to the reader entry for your card in oscam.server

smargopatch = 1

for question 1 - you need to change it to static

have a read of this for answer to question 2 - you might get away without a smartreader

http://linuxsat-support.com/os…-connect-oscam-cccam.html
with above tutorial, remember where it has 127.0.0.1 - change to the ip of your receiver where the card is. Use your DM500s
above method only to be used with receivers on the same internal network as your server.

for question 3, you will need CCcam 2.1.3 or you will need a smartcard reader as above won't work.

all the information is in the forum, just takes a while to sink in, but it will all click into place!