DM800 Evocam config

[smith]

I've read the other threads about getting Evocam to work with E2 but I don't seem to be able to fix it! This is my camd_cfg in user/keys:-

I think the box copies the files in user/keys to var/keys when running. They all look there in both directories, what am I missing?

# debug messages level

# EMM messages
# 00 don't show any EMM's
# 01 show only valid EMM's, default setting
# 02 show valid and bad EMM's with complete data display
M: { 01 }

# ECM messages
# 00 don't show any ECM's
# 01 show only valid ECM's, default setting
# 02 show valid and bad ECM's with complete data display
C: { 01 }

# AU
# 00 is ignored (default)
# 01 enable AU
# 02 AU Auto
A: { 02 }

# Key update
# 01 update only new keys, default setting
# 02 update all keys (used for valid PMK checking)
U: { 01 }

# Key files folder
# 00 keyfiles in /var/keys
# 01 keyfiles in /var/tmp
T: { 00 }

# # Hash pids
# 00 hash all pids
# 01 hash only pids with implemented algos (default)
H: { 00 }

# share Mode
# 00 Pure emu
# 01 Pure emu
# 02 Pure emu
# 03 alle network clients
# 04 newcamd share
# 05 radegast share
# 06 camd35 share(not in use)
G: { 00 }

# On Screen Display for Multicam
# 00 No OSD (default)
# 01 display Smartcard messages, box IP required
# 02 display Smartcard messages new nhttpd format, box IP required
O: { 01 }
USER = root
PWD = password

# To use UDP log
# 00 disabled
# 01 enabled
L: { 01 }192.168.0.115 10000

[smith]

Tried a "working" set of files from another user with no joy. Perhaps it is an issue with the image which is Blackhole v0.11.

Has anybody got Evocam v2.17 working with BH v0.11?

[mercenary]

i cant get it working with PLI either

[AllyB]

having the same problem as of about 2-3 weeks, on mgcamd it crashes too much but cant get it to load on evocamd

[zaf786]

Tried a "working" set of files from another user with no joy. Perhaps it is an issue with the image which is Blackhole v0.11.

Has anybody got Evocam v2.17 working with BH v0.11?

I had it working on 7025 i don,t see a reason why it won,t work on 800 have you had a look what attributes your k*ys and roms are set.they should be 644 if they are 644 and not working try chmodd 755 and restart enigma see what happens long shot this is worth a try

[smith]

A 7025 is E2 isn't it? Which image and cam versions have you used. All the files in the directory are set to 755. This is strange, obviously the pure emu setting stops the cam going to look for network keys, there must be another reason why it will not look at the key files.

[AllyB]

mine are all set to 755 too i think, which ones need to be 644? everything in the "keys" folder?

[zaf786]

A 7025 is E2 isn't it? Which image and cam versions have you used. All the files in the directory are set to 755. This is strange, obviously the pure emu setting stops the cam going to look for network keys, there must be another reason why it will not look at the key files.

Hi try this go to usr/bin and look for evocamd_2.17 and replace with this file and chmodd 755 and reboot and start your cam again to be safe save the existing evocamd_2.17 to desktop have all your files in correct folder usr/k and usr/scce chmod 644
extract the file with winrar before putting in usr/bin

[smith]

Thanks, tried the file and still no luck. Evocam seems to be working and it knows the stream is encrypted, the "N" is blue. The fact that it isn't going green seems to idicates that it cannot find the files.

[AllyB]

yep didn't work for me either, black screen as soon as i try to switch to evocamd, works fine again on mgcamd, but freezing lots
thanks for tryin, any other suggestions welcome

[smith]

I'm baffled, never seen this with Evocam using E1 on DM500, 600, DBox2's. Must be an E2 quirk as it seems to afflict a few images, not just Nabilosat BH. Although these images are generally for sat systems, so perhaps its something to do with the cable services side.

[AllyB]

so need to change the image? is there a dk image for the dm800?

[smith]

No I don't think it is an image problem, I think it is the way that the Enigma 2 OS is handling the the CAM messages. The fact that some people seem to still have it working with E2 (Enigma) means that there should be a way to configure it to work. I just can't see where it is going wrong at the moment. Perhaps sleep on it.

[mercenary]

please post your details here if you have a DM800 and evocam working!

[mercenary]

i think this is the cause, can someone, any dreambox model.

run evocamd from the prompt and see what its output should be.

mine is

root@dm800 ~ # evocamd
DEMUX DEVICE: No such file or directory