View Full Version : PLMNsel is same for all positions (THAT'S BAD)
I found that PLMNsel (6F30 - prefered network list) is same for all positions in SimEmu6.00
That's bad. If I go roaming, I want to use different roaming-provider on different home-networks.
Do you (Dainel) maybe planing to change that in future versions?
regards
Not too many of us go roaming often :)
I think Daniel will put his next efforts in programming Sim-emu for the funcard... maybe on that version he'll implement it :)
@pisac
Did you have problems with roaming ?
I used SIM-EMU in France and I only had to do, by suggestion of local provider, change the network from the "network menu" and the SIM-EMU worked perfectly.
But if it is necessary, in the next version I'll make this file distinct for each number.
Regards
I have not problems with roaming, because i'm using manual network selection.
But, when automatic network selection is active, and I have more phone lines with roaming capability, then I cannot set prefered network for one of phone lines to be different from prefered network for another phone line.
Example (just example):
If I have two phones, home networks: 220 01, and 220 03
and if I go in Romania, then I prefer to:
When using 220 01, to roaming through 226 10
When using 220 03, to roaming through 226 03
that can be done by manual selection, but if I want automatic selection (using prefered networks list), then it cannot be done because PLMNsel is same for all phone numbers.
Also, FPLMN is same for all phones (and are erased whenever I change phone line) and that prolong connecting time while roaming (because when I change active phone line, then mobile phone again search through networks which are forbiden for that phone line)
Because I did some programming over Dejan's source code for silver card, I have version which have folowing files separated for any of provider positions:
6F38 ;SERVICE TABLE
6FAD ;ADMINISTRATIVE DATA
6FB5 ;Enhanced Multi Level Pre-Emption and Priority
6F46 ;PROVIDER NAME
6F78 ;ACC Access Control Class
6F30 ;PLMN SEL
6F37 ;ACM_MAX_VALUE
6F41 ;PRICE PER UNIT AND CURRENCY TABLE
6F7B ;FPLMN
6F40 ;MSISDN
6F42 ;SMS PARAMETERS
also my version have PIN1 and PUK1 (PUK1 is same for all positions, PIN1 is same but with different first number), with selfdestruction, and 250 ADN in FLASH by storing 7 characters (7x8=56bits) in 4 (flash)words (4x14=56bits)
But, I have no time to continue developing other functions for compatibility with other mobile phones than Nokia (REHABILITATE, SEEK...) and also I bought mobile phone with plenty of memory so 250 ADN on silver card is not anymore important to me. I'm using SimEmu because it have proactive menus, with easy changing of IMSI, KI, PROVIDER NAME, PUK... (which on my version I can change only with dejan's sim_scan, and provider name or PUK only by reprogramming whole card).
That's right. I remember that I must to clear the FPLMN after the change of position, because some phones did not work without this procedure.
Regards
So, when you have time, undoubtedly consieder to separate following files...
6F30 ;PLMN SEL
6F7B ;FPLMN
6F7E ;LOCI (Location Information, forgot to mention this file)
...(and not to erase when changing positions) because phone will faster search networks, especially (!!) while roaming, and also phone will be able to use prefered network list while roaming.
----
If you have plenty of time (which I believe is not the case), consieder also to do following changes:
6FAD ;ADMINISTRATIVE DATA
6FB5 ;Enhanced Multi Level Pre-Emption and Priority
6F78 ;ACC Access Control Class
Separate those files, because then you will be able to use some of positions for special purpose (for example with greater priority, or to be motorola test card, or similar...)
6F42 ;SMS PARAMETERS
Double or triple, because some people (like me) use more than one SMS configuration with same provider (different SMS center, or different validity, or different message type...)
6F40 ;MSISDN
Separate (and reduce, 1 or 2 is enough), because I like (and maybe some other geek :-) to store actual phone number (of actual position) in it. Also, some phones (ericsson 888...) show this number when booting.
----
regards
By the way, I'm willing to help you, if you are willing to share (part of) source code...
regards
The shared SMSCs part would be nice :)
@pisac
6F30 ;PLMN SEL - Ok to separate in the next version.
6F7B ;FPLMN - No. It must be clear for compatibilty reason. It is more important that a few seconds that depend of the phone.
6F7E ;LOCI - Already is separated.
6F42 ;SMS PARAMETERS - Could be increased in the next version
Regards
I think there's no need to increase the number of SMS parameters...
Just make them all (10) visible on any selected position.
Rarely people use all the 10 positions, and if they do they use some of them for the same operator (there are no 10 operators per country)...
Making it so that the SMS parameters go circular depending on the currently selected position also gives the following advantages:
- If you need 1 parameter per number and have a special operator for which you use 4 parameters you won't be wasting space (instead of having 4 parameters for the 10 positions you use, let's say 5 positions, and use the parameters from the other 3)
- You can edit the SMS parameters from any position making it possible to configure the phone without booting to each position..
---to simemu:
I understand how can FPLMN make problems to some phones, but only when FPLMN is common to all positions:
1) When you chose some of your 10 SIM positions (home network providers) then mobile phone may check available networks (particulary when roaming), and store forbiden networks in FPLMN (networks which do not have roaming agreement with particular home network).
2) If you change position (chose another home network provider) then mobile phone again check available networks, and some phones may have problem to connecting to home network if they found same network in FPLMN (which is stored during previous checking of networks, while home network was different). That's why you erasing FPLMN (when it's common to all positions)
3) But, if FPLMN is separated to all positions (like I did in my version of Dejan's software for silver), then when you change position (home network), FPLMN will be changed too, and will be blank (if it's first time that you started that position) or will be filled with values that are stored when you previously started that particualr position - if in previous checking of networks some of them was forbidden, they still will be forbidden (so there is no problem).
Try, I'm assured that you won't have any problems.
---to alf:
Some phones can handle only one SMS parameter, so first SMS parameter must be different for all positions. I think it will be hard to organise file SMS PARAMETERS in a way that when you change position, phone "see" different first SMS parameter record although all records are in same file.
Also, there are no 10 operaters in country, but there are small countries with 4 operators (Serbia and Montenegro, ex Yugoslavia), and neighboor countries with also 2-3-4 operators... (Romania, Bosnia and Herzegovina, Croatia, Bulgaria, Albania, Macedonia, Hungary), and if I have all 4 home operators (for example), and one of operators in all neighboor countries (for example), that is already 11!. And you cannot use SMS centers for one of them with another. So, I think your proposition is not so beneficial (at least in my case).
@pisac
I implemented the SMS parameters in Dejan's version very easily.
All the 8 SMS parameters would be available... depending on the selected position the first would change and the others accordingly. It worked perfect even on phones with support for one parameter only...
If it didn't change automatically there would be no point in having 8 parameters if I'd always had to send by set...
This was for 8 positions...
ok_rcc: cmp sel_f2,042h ; if it's sms parameters move rec. num to selected card
jne no_42
movf rec_no,w
addwf prov_num,w
; sublw 1
andlw 007h
; addlw 1
jmp is_42
no_42: movf rec_no,w
is_42: movwf r6
movlw 0bh
addwf r0,w
call get_data7
jmp nex_rd_r1
@pisac
The problem is the Refresh command and not when powering off the phone.
I have tried what you said and did not work. Some phones "remember" the previous network after the Refresh command and forbid the new network in spite of the information of FPLMN.
I can put a FPLMN for each position, but it must be cleared after use the Refresh.
Powering off and on in the other network, will be faster.
--- to simemu:
Ok. If it's your expirience, then I cannot disagree. But, solution always exist, for example you can:
-Separate FPLMN and add in proactive configuration menu new option: "FPLMN", with values: "erase" and "not erase" (Like "Loader" with "disable" and "enable")
On phones which do not have problems with FPLMN after refresh, erase function can be turn off (not erase).
I think it will be interesting to add menu "advanced", with several advanced options, like:
-FPLMN erase/not erase
-Administrative Data (6FAD) value input (maybe someone wants 81 instead 00 ...)
-SimEmu menu disable (forever, or enable with SMS)
-registered PLMN show/don't show (only name of phone#X)
and similar functions, that we at the moment can enable/disable only before eeprom or flash programming
--- to alf:
You'r right. It's much easyer than I thought at the beginning.
I take note of all your suggestions for a future release.
The configuration via SMS's is each time useless, because tha last phones don't write SMS in the SIM and cannot be configurated through this way.
Thanks and regards
Thank you, for great software!
:-)