does it read the card details in the main program windows?
... I thought that my JayCar MK II phoenix was working 100% - but now I am loosing confidence as to whether it really is
... first of all - from an electrical (construction point of view) the device checks out 100% - all the voltages are correct
... the problem is trying to read data with the device from a card ...
I have been busy in setting up a new DM500 image and think ... sorry ... am sure that I got it 10% now ... however am unable to successfully get anything from my phoenix and the gamma ..
OK .. the gamma is working 100% - tested on a strong - all is OK and its auto updating ...
I got the DM500s configured - serial port all set-up and JayCar MK II configured and connected ... (data is being transmitted as the red LED does flicker)
In my case set to 6MHz, front push button PUSHED-IN and the JP1 set to connect pin 1 and 2 - the phoenix mode ..
... but I cannot get any sensible data from the JayCar MK II ...
Before ripping my hair out ... It would be nice to just do a simple data test with the JayCar MK II ... just to see if the serial comms is really working?
I thought I would use the GWM071b to do this ...
this is the CARD log I receive ..
05 Apr 2008 10:46:20 newcamd Running
05 Apr 2008 10:45:54 Phoenix Client_Phoenix
05 Apr 2008 10:46:20 IDS Running
05 Apr 2008 10:46:20 Phoenix Card ATR : xxxxxxxxxxxxxx...x (data received here)
05 Apr 2008 10:46:20 Phoenix Setup Comm Port \\.\com1
05 Apr 2008 10:46:20 Phoenix Connecting
05 Apr 2008 10:46:20 Phoenix COMM Error Unable to open serial device
... this indicates that there is a problem .. OR am I missing something ??
unfortunately - I don’t have a handy wafer card or pic to program / read .. so cannot test the JayCar MK II ... I don't want to experiment with the gamma for obvious reasons ... so need to find some simple program which can verify the serial connection is working with the JayCar MK II in its phoenix mode ...
.. any help would be really appreciated - before I go crazy
Look Here -> |
does it read the card details in the main program windows?
if you connect the jaycar to your computer and use either Fmcard or mrt-irdetocardexplorer to read the gamma.
they will both read the card and if they have issues then it could be the reader.
i have uploaded fmcard and the necessary ocx files as well as irdetocardexplorer
... guys - thanks for your quick responses ...
.. yes .. but it does not make sense ...
GWM comes back in main prog with ATR 2rLll
... this is obviousy wrong and indicates a comms problem Parity or stop bits ?
(the gamma does work - I am running it in a strong right now)
... will do some testing right now ... thanks for the upload
EDIT: Looks like the phoenix IS working ... here is the response from Card Explorer for Irdeto ...
Reset Successful
ATR: xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx
TS: 3B = DIRECT
T0: 9F = TA1 TD1 Specified, 15 historical characters
TA1: 21 = Clock factor = 558, bit rate = 1
TD1: 0E = T14 Protocol
TCK = 9D Calculated TCK = 9D
Historical Bytes: 49 52 44 45 54 4F 20 41 43 53 20 56 34 2E 31
I R D E T O A C S V 4 . 1
Programming Voltage = 0.0 volts
Programming Current = 25.0 ma
Maximum Clock Frequency = 6.0MHZ
Assuming a 3.5790MHz clock:
Work ETU = 0.0001559095 seconds
Guard Time = 0.0018709137 seconds
Baud Rate After Reset = 6414
work waiting time = 1496.73093042749 ms
... well at least this settles one thing ... the JAyCar MK II does work and the PC comm port is working
... however WHY is the DM500s having problems is reading the gamma ??
... have covered all aspects of the config(s) ... even used dreamup with the serial port - so that works -yes - I know sometimes dreamup works but phoenix will not ... if this IS the case - is there a way to check this or confirm that this is what's happening?
... perhaps there is a simple DM prog to check data to-from phoenix on serial port?
... I guess final test would be to use a 'working' image for DM configured for JayCar MK II and the serial and see what happens ??
... hmmm ... I think the image I configured should work ... but you never know ... I could have mised something trivial which is killing it
EDIT2: ... anoher thought ... does Card Explorer for Irdeto ... do something clever - like configure itself automatically for the serial port? ... I could not see this ... other than the options section .... it does have a delay of 20ms and a RX timeout of 5ms - perhaps these parameters need to be used in the DM's configs also? ... not seen this in others' config files though ... ??
Last edited by eyesee; 05-04-08 at 11:05 PM. Reason: result of test
With GW change your read freq from 3.57 to 6mhz.
Leroy
older gemini version
newer pli version in flash wizard format
just remember that they both use different base images so you can not use flash wizard to load the pli over a gamini image .
I have uploaded the two different versions so you can use the one that is what you have installed at the moment
eg":
gemini = load the gemini with dreamup
pli = load pli version with flash wizard
also the cred for these images go to Z80
... I think you just flash it twice ...
... the first flash will be corrupted ... BUT it will change the Gemini imaged DM to a PLi ... so the second flash will work 100% ...
... hope this is correct ??
EDIT: Probably safer to use dreamup with ANY Pli image FIRST - then use FW
... I've got the PLi image - so used the FW ... Got a 100% OK flash confirmation from FW ...
When I rebooted the DM ... I went through the configs and then when finished and rebooted once again ... I get PLi - please stand by - message ... then screen goes blank for 2-3 sec and then once again the PLi - please stand by - message appears ... but this time its there for a very L O N G time and does not clear from the screen
... I can however navigate and go to various set-up menus ... when clearing the menu(s) ... the DM still goes back to the - please stand by - screen
... is this a bug? or something ... or is there something wrong with my flash / setup?
I have a universal LNB - so probably will need to reset to 10700 and rescan ...
... when I did the setup - I did not have LNB cable plugged into DM (though I try it first before LNB connection) ... could this be why the second - please stand by - message is 'hanging' ??
no its because you will need to set the lnb at the correct value then reboot no need to rescan
OK ...
Pli image is up and runing - don't know what happened - but it works now
... receiving the FTA channel ...
Phoenix is set to 6mhz - is this the default on this image?
Is there anything else I need to change / add to the newcs.xml OR the CCcam.cfg?
Gamma in the phoenix as it is now yeilds nothing
EDIT: chacked the configs - they seem to be OK - at 6Mhz and correct port ... I noticed Firewall settings - are these active in the Pli image and do I need to change? - I don't think so because I am not CS - newcs is the server and CCcam is being used as the client? - these are set-up correctly ans should work .. I am missing something here .. I'm sure ... but what
EDIT2:
added <parity>none</parity> to newcs.xml
looking at newcs servr ..
.--------------------------------------------------------------------------------------------------------.
| Status | CAID | Enabled | Exported | Mhz | PTS | Resets | Ecms | Node | Reader |
|----------|------|---------|----------|-----|-----|---------|----------|-----------------|--------------'
| Empty | 0000 | Yes | Yes | 600 | No | 0 | 0 | /dev/tts/0 | 0 (external jaycar mk2)
| Empty | 0000 | Yes | Yes | 357 | No | 0 | 0 | /dev/sci0 | 1 (Upper Cardreader)
'-----------------------------------------------------------------------------------------
status is EMPTY - even though there is a gamma in the card reader - hmmm?
make sure the "Don't open serial port" is ticked. in the menu setup
and a do a soft restart to enable changes.
... OK ... for those of you that one day may be reading this post ...
First of all you just got to say a big thanks to all the members here for their support in trying to 'fix' problems
... however ... sometimes you can just go crazy in looking for non existant problems in software configs ... especially when there ?could? be a H/W problem.
I've learned a great deal in trying to 'fix' config settings ... but finally can conclude that there was nothing to fix ... I think I must be one of those with a our of spec DM ...
... my phoenix checked out ok ... but the DM50s just wont 'talk' to it
... will be trying same image with same phoenix on another DM500s and hope that this will conclude this 'learning experiance'
Bookmarks