View Full Version : S Italia version 3 002 Card Burn
Wow how hot does one of these cards get in a db500 its only in for a few secs and the chip is roasting
So is it possible to use the serial rs232 port on the dream with a card reader running at 358mhz
I only have a multipro 2000 card reader which can run in 357 or 6mhz so if I configure newcs is it possible to read the rs232 on the dreambox
Also if I have this card running at 3.57mhz will that be quick enough to handle the ecms?
Thanks in advance
Ok I have worked out how to get cccam to read the serial port of the dm500s but I didnt really want to use cccam can anyone confirm this is not possible with newcs if only to stop me looking
My mate is looking at modding the 500s so that the internal card reader reads at around 3.3 volts this should ensure card does not get burned
I have seen diagram to mod 7020 but not 500 does anyone have schemes/diagrams
Thanks
sonic1
18-08-2009, 01:50 PM
newcs works fine and probaly better with Mgcamd and newcs
Hi Sonic
I have now connected a pheonix compatible reader on the DM500s serial port I must be missing something
Do I need to add the serial port linux drivers on the dreambox or does the nabilo image have these installed? and I need to work out what lines to put in newcs.xml to read the serial port as oposed to the internal card slot
any help appreciated
Thanks
sonic1
18-08-2009, 03:03 PM
Need to see your newcs.xml for starters and which emu have you gone for ?
Thanks for the reply
I am using mgcand to connect but Im not even at that stage yet I have tested mgcamd and newcs config and all is working well in internal card reader slot but I cant leave the card in internal slot due to the reader over heating problem with n d s version 3 cards
here is the section of my newcs xml
<name>phoenix</name>
<type>Phoenix</type>
<node>/dev/tty/s0</node>
<mhz>358</mhz>
<export>yes</export>
<enabled>yes</enabled>
<blocksa>No</blocksa>
<blockua>No</blockua>
<blockga>No</blockga>
<PTShandshake>no</PTShandshake>
<crypto-special>no</crypto-special>
<carddetect>yes</carddetect>
<newcamd_port>65555</newcamd_port>
part of the log
15:09:31 ] [ Phoenix ] Opening device /dev/tty/s0
15:09:31 ] [ Phoenix ] Could not get device /dev/tty/s0
15:09:31 ] [ Loader ] Reset failed ...
15:09:31 ] [ Loader ] Reader type 2 on node /dev/tty/s0
15:09:31 ] [ Phoenix ] Opening device /dev/tty/s0
15:09:31 ] [ Phoenix ] Could not get device /dev/tty/s0
15:09:31 ] [ Loader ] Reset failed ...
15:09:31 ] [ Loader ] Reader type 2 on node /dev/tty/s0
15:09:31 ] [ Phoenix ] Opening device /dev/tty/s0
15:09:31 ] [ Phoenix ] Could not get device /dev/tty/s0
15:09:31 ] [ Loader ] Reset failed ...
15:09:31 ] [ Loader ] Reader type 2 on node /dev/tty/s0
15:09:31 ] [ Phoenix ] Opening device /dev/tty/s0
15:09:31 ] [ Phoenix ] Could not get device /dev/tty/s0
15:09:31 ] [ Loader ] Reset failed ...
15:09:31 ] [ Loader ] Reader type 2 on node /dev/tty/s0
15:09:31 ] [ Phoenix ] Opening device /dev/tty/s0
15:09:31 ] [ Phoenix ] Could not get device /dev/tty/s0
15:09:31 ] [ Loader ] Reset failed ...
15:09:31 ] [ Loader ] Reader type 2 on node /dev/tty/s0
15:09:31 ] [ Phoenix ] Opening device /dev/tty/s0
15:09:31 ] [ Phoenix ] Could not get device /dev/tty/s0
15:09:31 ] [ Loader ] Reset failed ...
sonic1
18-08-2009, 03:38 PM
Thanks for the reply
I am using mgcand to connect but Im not even at that stage yet I have tested mgcamd and newcs config and all is working well in internal card reader slot but I cant leave the card in internal slot due to the reader over heating problem with n d s version 3 cards
here is the section of my newcs xml
<name>phoenix</name>
<type>Phoenix</type>
<node>/dev/tty/s0</node>
<mhz>358</mhz>
<export>yes</export>
<enabled>yes</enabled>
<blocksa>No</blocksa>
<blockua>No</blockua>
<blockga>No</blockga>
<PTShandshake>no</PTShandshake>
<crypto-special>no</crypto-special>
<carddetect>yes</carddetect>
<newcamd_port>65555</newcamd_port>
I have not tested this but the deafult pheonix xml reads different.
<device>
<name>Phoenix on Com1</name>
<type>phoenix</type>
<mhz>368</mhz>
<node>/dev/ttyS0</node>
<parity>odd</parity>
<reset>normal</reset>
<export>Yes</export>
<enabled>Yes</enabled>
<blocksa>No</blocksa>
<blockua>No</blockua>
<blockga>No</blockga>
<blockC0>Yes</blockC0>
<carddetect>no</carddetect>
<newcamd_port>15050</newcamd_port>
<autosid>Yes</autosid>
<pincode>0000</pincode>
<priority>round</priority>
</device>
Test and let me know how it goes.
Interesting it does not loop now here is the log I assume "could not get device" means it cant talk to the reader as opposed to not talking to the card - I have to say I am using a multipro 2000 card reader set to pheonix mode 3.58mhz what I need to do I guess is somehow test the card reader by using a linux command just to seee if the serial port is working?
[ NewCS ] Process ID is: 184
[ 15:42:13 ] [ Loader ] Starting Telnet on port 10001
[ 15:42:13 ] [ Loader ] Reader type 2 on node /dev/ttyS0
[ 15:42:13 ] [ Phoenix ] Opening device /dev/ttyS0
[ 15:42:13 ] [ Phoenix ] Could not get device /dev/ttyS0
[ 15:42:13 ] [ Loader ] Reset failed ...
[ 15:42:13 ] [ Loader ] Starting Newcamd Server on port 15050
[ 15:42:13 ] [ NewCS ] Ready to GO! :)
~ > [ 15:42:13 ] [ Newcamd ] Newcamd thread Server started on port 15050
newcamd: main loop
sonic1
18-08-2009, 04:09 PM
Not sure but I have just noticed this
<device>
<name>Phoenix on Com1</name>
<type>phoenix</type>
<mhz>368</mhz>
<node>/dev/ttyS0</node>
<parity>odd</parity>
<reset>normal</reset>
<export>Yes</export>
<enabled>Yes</enabled>
<blocksa>No</blocksa>
<blockua>No</blockua>
<blockga>No</blockga>
<blockC0>Yes</blockC0>
<carddetect>no</carddetect>
<newcamd_port>15050</newcamd_port>
<autosid>Yes</autosid>
<pincode>0000</pincode>
<priority>round</priority>
</device>
Try carddetect YES
I am not sure if that applies to internal reader only.
noticed the carddetect option sends it in a loop so it is trying to detect a card in a reader it cant find
Couple of things spring to mind
Its likely my card reader is not compatible and I cant find anyone using a multipro on the forums I think Im going to have to buy a genuine pheonix with power supply then again if my mate can mod the reader on the 500s to receive just 3.5 volts then I think it will work with internal slot
Shame really I was beggining to enjoy trying to get this to work thanks for your help and if you think of anything else please post
Many Thanks
I have now managed to get newcs to recognise the com port on the dreambox the data light is flashing on the programmer
What I had to do is create the serial device in /dev like so
mknod -m 666 /dev/ttyS0 c 4 64
now I guess what I need to do is modify the above line so to allow newcs to talk to the card reader properly but Im not a unix boffin so I would need someone to tell me what the settings are for a multipro pheonix mode card reader
All good stuff reminds me of the old days
sonic1
18-08-2009, 04:57 PM
Keep trying m8 I am sure you will get there, like you say it's all part of the fun. :respect-055:
Thanks sonic1
I now got newcs to detect no card in the reader and when card is inserted it goes through the following loop so I guess its not passing the correct command to the card like you say I will keep trying but the only way I could be certain is to use original pheonix I guess
Thanks
17:00:48 ] [ Phoenix ] Opening device /dev/ttyS0
17:00:48 ] [ Phoenix ] Setting Parity to: NONE
17:00:48 ] [ Phoenix ] Setting 2 Stop bits on node /dev/ttyS0
17:00:48 ] [ Phoenix ] Setting Baud to standard 9600
17:00:48 ] [ Phoenix ] Normal RESET on node /dev/ttyS0
17:00:50 ] [ Loader ] Reset failed ...
17:00:50 ] [ Loader ] Reader type 2 on node /dev/ttyS0
17:00:50 ] [ Phoenix ] Opening device /dev/ttyS0
17:00:50 ] [ Phoenix ] Setting Parity to: NONE
17:00:50 ] [ Phoenix ] Setting 2 Stop bits on node /dev/ttyS0
17:00:50 ] [ Phoenix ] Setting Baud to standard 9600
17:00:50 ] [ Phoenix ] Normal RESET on node /dev/ttyS0
17:00:52 ] [ Loader ] Reset failed ...
17:00:52 ] [ Loader ] Reader type 2 on node /dev/ttyS0
17:00:52 ] [ Phoenix ] Opening device /dev/ttyS0
17:00:52 ] [ Phoenix ] Setting Parity to: NONE
17:00:52 ] [ Phoenix ] Setting 2 Stop bits on node /dev/ttyS0
17:00:52 ] [ Phoenix ] Setting Baud to standard 9600
17:00:52 ] [ Phoenix ] Normal RESET on node /dev/ttyS0
17:00:54 ] [ Loader ] Reset failed ...
17:00:54 ] [ Loader ] Reader type 2 on node /dev/ttyS0
17:00:54 ] [ Phoenix ] Opening device /dev/ttyS0
17:00:54 ] [ Phoenix ] Setting Parity to: NONE
17:00:54 ] [ Phoenix ] Setting 2 Stop bits on node /dev/ttyS0
17:00:54 ] [ Phoenix ] Setting Baud to standard 9600
17:00:54 ] [ Phoenix ] Normal RESET on node /dev/ttyS0
17:00:56 ] [ Loader ] Reset failed ...
dubious
19-08-2009, 12:49 AM
Dunno what image you're using but don't forget you have to disable debug on the serial port, expert options in the menu I think.
Although the card should be ok really in the 500 sci with a newish image.
@dubious
Thats interesting from my readings I understood the burn issue was to do with the voltage being supplied to the card reader which in the 500s is 5.2 volts and I beleive its this which burns the card
Im using nabilo darman II from earlier this year newcs 1.66 and mgcamd 1.27
Obviously the sci slot would be preferable
Funnily enough I got the card reader to recognise a version 5 irdeto card but it did not read it properly as it never returned the CAId's
When I went through the debug port to have a look - newcs would only report the card is inserted or not inserted whichever was the case BUT it could not read the entitlements
I have go to thinking its the card reader its fairly old perhpas 6 or 7 years even though it emulates a pheonix but perhaps the firmware cannot pass the right command through to the card
In short I can get newcs to detect if a card is inserted or not which suggests it is talking to the reader but what I cant get is newcs to read the card
Like I said before in the main card slot all is fine so no prob with card and and newcs but obviously the chip on the card starts to overheat after 154 seconds i mean really hot compared to the new white uk card which does not get any hotter than before
Powered by vBulletin® Version 4.2.5 Copyright © 2024 vBulletin Solutions Inc. All rights reserved.