View Full Version : [VU+ Uno] MgCAMD Problem
I have CCCam working perfectly.
but MGCAMD does not seams to work in Vix Image.
Unfortunate we cant really help with such a general statement, provide us with some more information such as how is it not working for you exactly ?. Then maybe we can be of assistance.
I enter in newcamd.list:
CWS_KEEPALIVE = 300
CWS_INCOMING_PORT = 21000
CWS = IP port login password 01 02 03 04 05 06 07 08 09 10 11 12 13 14 lan server1
and it doesnt work. checked it on Dream Box reciever and seems to work fine there.
Try this in newcamd.list only
CWS = 127.0.0.1 PORT USER PASS 01 02 03 04 05 06 07 08 09 10 11 12 13 14 lan cardserver
Change ip to your pc or box ip if its not an internal card/server
Also what version of Mgcamd are you using and where did you get it.Mgcamd working fine in my duo here.
I am using:
enigma2-plugin-cams-Mgcamd_1.38-ViX.ipk
Thnaks, but still dont work.
have you changed the box type in MG_CFG?
if 00 set to 06 :-)
I,m using Mgcamd 1.35a and is fine.. i would probably just use that mate unless you require that version for a specific key/provider etc.
where can I get a complete version of 1.35a
From here mate loads there to choose from
http://www.filecrop.com/enigma2-plugin-cams-mgcamd-1.35-mipsel.ipk.html
CoolerMaster
17-03-12, 13:28
Try this in newcamd.list only
CWS = 127.0.0.1 PORT USER PASS 01 02 03 04 05 06 07 08 09 10 11 12 13 14 lan cardserver
Change ip to your pc or box ip if its not an internal card/server
Also what version of Mgcamd are you using and where did you get it.Mgcamd working fine in my duo here.
I have mgcamd working on my vu duo however it needs restarting every so often as it stops working. Have you also come across this issue? Currently have mgcamd 1.38 Vix installed, have also tried with 1.35a and changed 'B Line' to 06 but problem still remains. Running Vix 2.3 (Linux 3.1.1) is this Image or mgcamd configuration related? Have learnt from another forum that a guy has blackhole image installed on his duo with the latest linux 3.1.1 kernel and mgcamd and has never had to restart the cam to get it working again which leads me to believe it could be image related.
Mr. Mister
17-03-12, 15:03
There was never a 1.38 made by the Vix team..
It was made by another 3rd party..
im running mgcamd 1.38 with vix 2.3 and have no problems
I have mgcamd working on my vu duo however it needs restarting every so often as it stops working. Have you also come across this issue? Currently have mgcamd 1.38 Vix installed, have also tried with 1.35a and changed 'B Line' to 06 but problem still remains. Running Vix 2.3 (Linux 3.1.1) is this Image or mgcamd configuration related? Have learnt from another forum that a guy has blackhole image installed on his duo with the latest linux 3.1.1 kernel and mgcamd and has never had to restart the cam to get it working again which leads me to believe it could be image related.
Have a look at line L in mg_cfg and make sure log is off i.e. L:{00}
phil
CoolerMaster
19-03-12, 19:00
Have a look at line L in mg_cfg and make sure log is off i.e. L:{00}
phil
Saw this mentioned in another forum on Friday and checked my configuration. The default for L line is not set to off, I changed it to {00} & since Friday it has been working flawlessly. Looks like this was definetly what was causing the problem.
My Duo has developed the same problem as CoolerMaster's; I'm VERY often having to prompt a restart of MGcamd (1.35a).
It appears that CoolerMaster's problem was corrected by editing to L: {00}
My question is: Is the character spacing crucial?
For instance, my own config file shows the L line as: L: { 00 }
Are the character spaces before and after the two zeros correct? ...or should they be deleted as in CoolerMaster's solution?
Thanks.
Mr. Mister
03-07-13, 19:40
what version of MGcamd you using.. ?
Hi Mr Mister,
I'm running 1.35a
abu baniaz
03-07-13, 21:13
All the other settings have the spaces.
Powered by vBulletin® Version 4.2.5 Copyright © 2024 vBulletin Solutions Inc. All rights reserved.