restart the cam or try with no cam at all but I when I was logging I fount restarting does the trick with a DM7020.
Leroy
Am trying to log some nova 13E and it doesn't matter what I do this program wont connect to my receiver(7020) in order to start logging. The settings i have are as follows:
port 31338 is open
any idea what is wrong? I can othewise connect to my receive but not with this program
Last edited by jimmys12; 22-06-09 at 12:58 AM.
Look Here -> |
restart the cam or try with no cam at all but I when I was logging I fount restarting does the trick with a DM7020.
Leroy
XCRUISER HDSR600HD twin sat and terrestrial receiver $OOS *
XCRUISER HDSR385 Avant - sold out$OOS UltraPlus DVB-T and DVB-S2 tuners $49 Remotes $OOS
It wont work on my 7020 but the 500 it worked like a dream
never got around to figure out why ohhh it might have been that the 500 had Gemini and the 7020 has PLI not sure
When you do things right, people won't be sure that you have done anything at all
a DM500 worked better from memory.
Leroy
XCRUISER HDSR600HD twin sat and terrestrial receiver $OOS *
XCRUISER HDSR385 Avant - sold out$OOS UltraPlus DVB-T and DVB-S2 tuners $49 Remotes $OOS
I haven't done much logging in a while but I have a feeling there may be log formatting differences that cause certain image versions to be with IRD_LogExtract. So if rebooting box and restarting the softcam doesn't help, try another image.
My DM7020 has Gemini 4.3
Leroy
XCRUISER HDSR600HD twin sat and terrestrial receiver $OOS *
XCRUISER HDSR385 Avant - sold out$OOS UltraPlus DVB-T and DVB-S2 tuners $49 Remotes $OOS
Are the PID and the Seperator right for your nova 13E ???
The ones you have are for Austar or something if i remember right
When you do things right, people won't be sure that you have done anything at all
Good thinking, that's a more likely explanation.
DVBsnoop will give you the PID
There is a thread here somewhere about using it and finding the seperator.
Don't worry, it only seems kinky the first time.
dvbsnoop 1 -n -1 will give you the pid
I find dvblogger to be far more reliable than irdlogextract with my setup - as already stated, killing (or restarting) the cam can help.
You can always use dvbsnoop (telnet) and output the log to a file which can then be parsed by logging software.
Again, i find dvblogger better for this, as irdlogextract seems to have issues with the packet size/structure.
dvbsnoop -b pid > /media/hdd/log.txt
> is used to denote the ouput location
Cheers, RHCP.
Last edited by RHCP; 23-06-09 at 03:29 PM.
Democracy: Three wolves and a sheep voting on what's for lunch.
Bookmarks