MDMA 1.0.0.31 Beta Testing

Status
Not open for further replies.
ginggs

ginggs

༼ つ ◕_◕ ༽つ
Super Moderator
Joined
Jun 26, 2006
Messages
12,171
Reaction score
737
Location
Kapkaupunki
MDMA 1.1.0.0 is released.

Screenshot here.

WARNING:
There have been reports that (some?) ZTE modems are rejecting the AT+ZBANDI=0 command to return the modem to automatic band selection. This could be a big problem for users of UMTS 900 networks. Please do not change the band selection on ZTE modems until further notice.
Possible fix for ZTE modems that can no longer access UMTS 900 here.

What's new in 1.0.0.31 since 1.0.0.30c:
  • MDMA's GUI is now in a new "landscape" orientation optimized for netbook displays, thanks to Terencek's polite reminders. The old "portrait" orientation has been deprecated.
  • Replaced the unused Cell Description field with an SNR (signal to noise ratio) display for the Huawei modems that support this feature. You don't have to do anything, if you modem supports it, you see numbers here, if not, you won't. At this stage I'm not entirely sure of what these values represent, but if you're interested have a read here.
    Ununocitum's theory on the reported SNR values is here.
  • In order to work around the problem of the E1820 ignoring the AT to command from the 3gpp specification to deactivate all PDP contexts (i.e. disconnect from the internet), MDMA now uses Windows RAS to hang up the connection.

    The downside of this is you must have a RAS entry named 'MDMA'. The easiest way to do this is to create a copy of the one created by your other dashboard.
    Failure to do this will result in the following error when using the 'Connect' button in MDMA:
    Cannot load dialog.

    Error 623: The system could not find the phone book entry for this connection.
    Click to expand...
    On the upside though, if you edit the properties of your 'MDMA' RAS entry and uncheck 'Prompt for name and password, certificate, etc,', 'Include Windows logon domain' and 'Prompt for phone number' in the Options tab, MDMA will now connect mit only vun click.
What's new in 1.0.0.31 beta 10:
  • Fix LAC received as 0x2B0012 instead of 0x2B12 on LongCheer modems
  • Frequency band configuration dialogs for Huawei, Sierra Wireless and ZTE modems - thanks 1geoff99
  • Removed /HWBAND and /ZBAND command line options
  • Added /SWREGION command line option to change Sierra Wireless region code
  • Display which COM port is in use if unable to open port
  • Update status bar and disable Connect button when searching for network - thanks sajunky
What's new in 1.0.0.31 beta 9:
  • Support 'Automatic' connection type for Icera chipset (ZTE K3805-Z) - thanks Jacques le Roux
  • Added detection and support for Long Cheer modems (Mecer notebook) - thanks TheMark
  • Added Telkom/8.ta to USSD Help and now only list commands for home network (based on IMSI)
  • Added command line options to specify USSD decoding mode (Plain, PDU, Hybrid, Packed7 and Unicode)
  • Added /DIAGLOG diagnostics logging command line option (currently only for USSD debugging)
  • Stricter decoding of E220 firmware 11.313.02.00.01 USSD responses
  • The above fixed USSD responses from other modems containing high ASCII characters e.g. mobilità - thanks Adriano
  • Merged /OPSELAUTO and /OPSEL command line options for network operator selection
  • Fixed display of ICCID where digits were swapped (how did nobody notice this?)
  • Added logging of SNR and QoS values and add /SPEEDLOG logging - thanks [noparse]www.samara-mobile.ru[/noparse]
  • Enable DS flow reporting on Huawei modems (after being disabled by Mobile Partner v21)
  • Retrieve Cell ID and LAC from devices that do not support it on +CGREG but do on +CREG (ZTE K3520-Z and possibly others?)
  • Renamed /U2DIAG to /HWCDROM and added /ZCDROM for controlling emulated CD-ROM and SD card
  • Added /HWBAND and /ZBAND for network band selection
What's new in 1.0.0.31 beta 8:
  • Added 50ms delay after sending ESC,CR,LF - now initializes Sierra Wireless AirCard USB 307 and 309 modems - thanks 1geoff99
  • I think the above fix may have improved compatibility with the Vodafone K4605 (Huawei E372) as well
  • Display 'Telkom' for MCC/MNC 65502 if modem has no response
  • Huawei counters are reset if received data speed exceeds 21.6Mbps (not 2.16Mbps, doh!)
What's new in 1.0.0.31 beta 7:
  • Detects Cell-C branded ZTE MF190 modems
  • Fixed a bug where ZTE modems were being sent Icera commands
What's new in 1.0.0.31 beta 6:
  • Vodafone K3805-Z (ZTE) with Icera chipset is now supported
    Icera was subsequently bought out by Nvidia, Icera's original Vodafone K3805-Z press release can now be found here.
  • Added command line switch to bypass enabling reception of Cellular Broadcast Messages (current ZTE K3805-Z firmware crashes hard!)
  • The /commandset command line switch can now be used even when the modem is automatically detected, overriding the detected command set
  • Added Icera command set option (for ZTE K3805-Z)
  • HSD+UPA is now displayed as HSPA
  • 'Firmware Version' is now a multiline edit box with a vertical scrollbar
  • Added 'Registered' and 'Roaming' status checkboxes
  • Added command line switch for manual network selection
 
Last edited:
How to create a copy of a dial-up networking connection in Windows 7 (and Vista?):
Click the network icon on the task bar / Open Network and Sharing Centre / Change Adapter Settings / Right-Click on on your other dashboard's dial-up connection / Create Copy / Right-Click on the newly created copy / Rename

How to create a copy of a dial-up networking connection in Windows XP:
Start / Control Panel / Network Connections / Right-click on your other dashboard's dial-up connection / Create Copy / Right-Click on the newly created copy / Rename

Help! The Rename option is disabled:
  1. Are you sure you are clicking on a dial-up networking connection and not a broadband network adapter?
  2. Speak to your network administrator about policies

Tested /HWBAND settings for Huawei modems:
ValueDescriptionTested Models
400380GSM900/GSM1800/UMTS2100E220/E272/E1820
2000000400380GSM900/GSM1800/UMTS900/UMTS2100E1820
2000000000380GSM900/GSM1800/UMTS900E1820
3FFFFFFFAll BandsE220
4F80380AutomaticE272

Error 756 - The connection is already being dialled:
Make sure the number to be dialled is *99# and "use dialling rules" is unchecked. Thanks sajunky!
See this post.
 
Last edited:
Hi ginggs

I got my ZTE MF190 Modem only yesterday so I'm still new to this. I tried MDMA 1.0.0.31 Beta 7. It runs and shows the signal strength, but when I click on connect it says "Cannot load dialog. Error 623: The system could not find the phone book entry for this connection."

I'm probably doing something wrong or not understanding how this is supposed to work. Can you assist?
 
Viva said:
Hi ginggs

I got my ZTE MF190 Modem only yesterday so I'm still new to this. I tried MDMA 1.0.0.31 Beta 7. It runs and shows the signal strength, but when I click on connect it says "Cannot load dialog. Error 623: The system could not find the phone book entry for this connection."

I'm probably doing something wrong or not understanding how this is supposed to work. Can you assist?
Click to expand...

I get the same, and I have read all about creating a copy of another connection, and then creating a "MDMA RAS" entry ... but I can,t figure out where, or how, to do this, even after reading Ginggs' instructions ... as he wrote below:
The down side of this is you must have a RAS entry named 'MDMA'. The easiest way to do this is to create a copy of the one created by your other dashboard.
Failure to do this will result in the following error when using the 'Connect' button in MDMA:
Cannot load dialog.

Error 623: The system could not find the phone book entry for this connection.
On the up side though, if you edit the properties of your 'MDMA' RAS entry and uncheck 'Prompt for name and password, certificate, etc,', 'Include Windows logon domain' and 'Prompt for phone number' in the Options tab, MDMA will now connect mit only vun click.
Click to expand...
 
Hi Ginggs

Currently using 1.0.0.31 Beta 7 on an E272 on a notebook with Win 7, connected to VC. Strangely enough it connects fine works as well as ever, but the dashboard doesnt give up/download speeds or data transferred, and it doesn't indicate that it is connected.
 
MDMA 1.0.0.31 Beta 7 (or any version) does not work with the Sierra Aircard 307. Get 'Mobile data device not responding' message. Actually, it does sometimes work, but mostly doesn't.
 
Last edited:
MDMA 1.0.0.31 Beta 7 seems to be only detecting the CellC branded ZTE MF190 after the CellC dashboard program has been opened at least once after a startup. Is this by design or some kind of limitation? The other thing is that MDMA gives me a signal strength reading and it can be used to initiate the connection, but I don't see any readings or statistics about the speed or data being used. It all stays at 0. Am I doing something wrong or is something wrong on my side? I really like MDMA - it's lightweight and much easier to use than the dashboard program which feels slow in comparison.
 
1geoff99 said:
MDMA 1.0.0.31 Beta 7 (or any version) does not work with the Sierra Aircard 307. Get 'Mobile data device not responding' message. Actually, it does sometimes work, but mostly doesn't.
Click to expand...
Any chance I could play with this modem for a few days?
 
Antonf said:
Currently using 1.0.0.31 Beta 7 on an E272 on a notebook with Win 7, connected to VC. Strangely enough it connects fine works as well as ever, but the dashboard doesnt give up/download speeds or data transferred, and it doesn't indicate that it is connected.
Click to expand...
I've just tested 1.0.0.31 Beta 7 on Windows XP with an E272 connected to Vodacom and the data transfer speeds, data counters and Connect/Disconnect button all seem to be working.
E272 firmware version 11.415.05.00.00.

What happens on another PC? What happens with MDMA 1.0.0.30c?
 
Viva said:
MDMA 1.0.0.31 Beta 7 seems to be only detecting the CellC branded ZTE MF190 after the CellC dashboard program has been opened at least once after a startup. Is this by design or some kind of limitation?
Click to expand...
It is not intentional and I did not notice this behaviour when I tested.
What exactly are you seeing? Does MDMA just sit there waiting for the device to appear, or do you see any error messages?
If you look in the Windows Device Manager, does the modem only appear after its own dashboard is run?
Viva said:
The other thing is that MDMA gives me a signal strength reading and it can be used to initiate the connection, but I don't see any readings or statistics about the speed or data being used. It all stays at 0. Am I doing something wrong or is something wrong on my side?
Click to expand...
Unfortunately only Huawei modems report their usage stats over the AT interface, so using this method, MDMA is not able to show speeds and data usage for modems from any other manufacturer.
Viva said:
I really like MDMA - it's lightweight and much easier to use than the dashboard program which feels slow in comparison.
Click to expand...
Thanks! I'm looking at extracting the speed and usage information from Windows RAS in a future version of MDMA, hopefully this will make MDMA more useful to you.
 
Getting a lot less 628 errors if any with the new version. Normally I have to play around with restarting the pc/resetting the modem and phyically inserting/disconnecting the modem. Which of course was a lot of hassle.
 
HideInLight said:
Getting a lot less 628 errors if any with the new version. Normally I have to play around with restarting the pc/resetting the modem and phyically inserting/disconnecting the modem. Which of course was a lot of hassle.
Click to expand...
Interesting, thanks for the feedback. I'm trying to think what could cause this, perhaps this is a side-effect of MDMA now having its own dial-up networking connection that can't be dicked around with by another dashboard.
 
I guess this could be slightly OT, as I am not using the latest MDMA beta (because I can't figure out the creation of the RAS setting).

This a.m. I had a MDMA 'pop-up' stating that I had received a SMS message on the card I use in the USB modem, using the older MDMA interface. How would I access / read this SMS?
I assume it is just a conformation of a 2.1GB data bundle I loaded this a.m., but would still like to know how to access the SMS
 
HideInLight said:
Getting a lot less 628 errors if any with the new version. Normally I have to play around with restarting the pc/resetting the modem and phyically inserting/disconnecting the modem. Which of course was a lot of hassle.
Click to expand...

Me too with E1820 on Cell C. That was last night. The network was very unstable though. My router struggled for 20 minutes to connect.
 
Hi, I had a ZTE MF190 too, ditched it after two weeks fighting with CellC since my modem lost internet connectivity without disconnecting time after time if you're not actively surfing for anything between 2 and 10 minutes. The reason why you only see the modem after opening the dashboard is that the modem only gets activated after the virtual cd is ejected. You can test this by right clicking CellC cd in my computer and clicking Eject. It's a real crpy modem, had the same problems with Vodacom sym, three different computers, and they still want to take it in for two weeks to test? I feel like starting a topic to outline what happend through the last two weeks! I eventually bought a new modem from Vodacom just to be able to use my data from CellC.
 
Last edited:
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X