BGS2T - Windows 10 driver | Thales IoT Developer Community
January 30, 2018 - 3:44pm, 6222 views
I got this modem, I want to use it to call some energy meters and read the profiles.
The problem is that I need to use it under windows 10 and I am not able to do it.
I've tried installing a standard modem at 56k but no chance to get it working.
I've even tried installing a driver that it is working on windows XP (BGS2 5.1.1234.4 22/06/2011 by Cinterion Wireless Modules GmbH) but nothing.
I've also contacted Cinterion and got a reply from Mr. Staffa who, after a quick check, asked me to write on this forum sure that I could get a fast support.
Could someone please help?
I've checked that there is no update for this driver. Could you describe in details what the problem is and how this works on WinXP?
the problem is that on windows 10 the modem does not reply to any query. It simply does not work with the driver I've mentioned neither with the standard modem that Gemalto suggests for windows 7.
On windows XP I am using a software by a company called DPEE to call some energy meters and get their values. I setup the software with a phpne number and the meter serial no and perform the call.
Could you be more specific on the type of informations that you'd need to understand the issue? I am not so skilled with serial communications and so on, and I am not able to write a driver by myself.
Is it the same device not working that you have used successfully with WinXP? Maybe it is a matter of hardware connections or configuration of your software.
Do you create any dial-up connection in Windows or just configure the module in your software? Maybe some configuration ***** to be changed like baudrate or other parameters of serial port - please compare with the settings on WinXP.
You have probably installed the modem driver via Windows Device manager. What happens if you open the modem properties and query the modem? Does it not reply?
I think that you can also use some terminal program for serial communication to connect to the modem port and check if you can execute any AT commands.
It is exactly the same hardware. I can use it under windos XP, but I have to take with me an obsolete notebook which is very heavy... I can't use it on my notebook with windows 10 instead.
If I check the parameters one by one between the two windows versions, they are all the same. COnsider that Gemalto suggests to install, under windows 7 and vista, a built in driver which is not available under Windows 10. That is why I've installet the BGS2 driver supplied by gemalto.
Following the configuration:
Maximum speed of the port: 9600 bauds
Protocol: RLP Analog
Flow control: None
Data bits: 8, Parity: none, Stop bits: 1
If I try to query the modem through the diagnosis tab, I receive no reply.
I've not tried to query via putty, I am tring to understand how to do it.
I think that you should start from verifying that the module is replying on the COM port that you are using with some terminal like TeraTerm, Termite, Zoc or similar. Usually the default serial port settings for the Gemalto modules is: 115200 bauds, 8 data bits, no flow control, 1 stop bit. You may also test other baudrates.
As for the modem driver please make sure that the correct COM port is used and please try to change the maximum port speed to 115200.
If you have a new notebook with Win10 it probably does not have a serial interface and you are using some RS232-USB converter. It could also be a source of the problem - you may test it with your old laptop to check if it works correctly. Sometimes these converters are causing problems.
Hi and thanks for replying that fast.
Yes, I am using a usb/232 converter, but is exactly the same that I am using on windows XP laptop (whic does not have a serial port) and it is working. Also, I am sure that this converter works on windows 10 since I am using it with other applications to query some modbus devices, and everything is ok.
After a bit of fight with putty and settings, it came out that for some odd reason the modem had been configured with parity even 7 bit 1 stop bit, guess who and why did it since I bought the modem brand new and I've been the only one to use it, and I am pretty sure that I was not able to handle the modem via serial interface up to now.
Now I've installed the BGS2 driver, and if I wuery ghe modem from the "hardware properties window" I receive the following output (taken from the log)
ATQ0V1E0 - OK
AT+GMM - BGS2-W
AT+FCLASS=? - (0,1,2)
AT#CLS=? - Command not supported
AT+GCI? - Command not supported
AT+GCI=? - Command not supported
ATI1 - Cinterion
ATI2 - OK
ATI3 - OK
ATI4 - OK
ATI5 - OK
ATI6 - OK
ATI7 - OK
So I understand that the modem is communicating.
Now, if I try to use it via my software (WinEMT by DPEE) the software returns a message saying that it was impossibile to reach the remote device because it was not able to reach its modem. If I look at the modem log, I see the following lines (sorry if I do not translate to english properly):
02-05-2018 16:32:37.963 - File: C:\WINDOWS\system32\tapisrv.dll, Version 10.0.16299
02-05-2018 16:32:37.963 - File: C:\WINDOWS\system32\unimdm.tsp, Version 10.0.16299
02-05-2018 16:32:37.963 - File: C:\WINDOWS\system32\unimdmat.dll, Version 10.0.16299
02-05-2018 16:32:37.963 - File: C:\WINDOWS\system32\uniplat.dll, Version 10.0.16299
02-05-2018 16:32:37.965 - File: C:\WINDOWS\system32\drivers\modem.sys, Version 10.0.16299
02-05-2018 16:32:37.965 - File: C:\WINDOWS\system32\modemui.dll, Version 10.0.16299
02-05-2018 16:32:37.966 - File: C:\WINDOWS\system32\mdminst.dll, Version 10.0.16299
02-05-2018 16:32:37.966 - Modem type: BGS2
02-05-2018 16:32:37.966 - Info path: mdm_bgs2.inf
02-05-2018 16:32:37.966 - Modem informations section: Modem1
02-05-2018 16:32:37.966 - Hardware ID: bgs2
02-05-2018 16:32:37.966 - Failed opening modem device. Error 00000057
What I understand is that the software failed to open the modem device because of an error 0000057, but this is where I am stuck, I cannot go further. I suppose it could be a matter of permissions, but I do not know how to fix this.
I did another test using the windows "56000 modem" driver.
Querying the modem through the device properties tab works properly. If I try to use my software instead the call does not work, and in the log I see the following:
02-05-2018 17:19:57.513 - File: C:\WINDOWS\system32\tapisrv.dll, Version 10.0.16299
02-05-2018 17:19:57.513 - File: C:\WINDOWS\system32\unimdm.tsp, Version 10.0.16299
02-05-2018 17:19:57.513 - File: C:\WINDOWS\system32\unimdmat.dll, Version 10.0.16299
02-05-2018 17:19:57.514 - File: C:\WINDOWS\system32\uniplat.dll, Version 10.0.16299
02-05-2018 17:19:57.514 - File: C:\WINDOWS\system32\drivers\modem.sys, Version 10.0.16299
02-05-2018 17:19:57.515 - File: C:\WINDOWS\system32\modemui.dll, Version 10.0.16299
02-05-2018 17:19:57.515 - File: C:\WINDOWS\system32\mdminst.dll, Version 10.0.16299
02-05-2018 17:19:57.516 - Modem type: Standard modem 56000 bps
02-05-2018 17:19:57.516 - Modem informations path: mdmgen.inf
02-05-2018 17:19:57.516 - Modem informations section: Gen556F
02-05-2018 17:19:57.516 - Hardware ID: moto1_gen
02-05-2018 17:19:57.519 - 115200,8,N,1, ctsfl=1, rtsctl=2
02-05-2018 17:19:57.520 - Modem initialization.
02-05-2018 17:19:57.530 - Send: AT<cr>
02-05-2018 17:19:57.582 - Receive: <cr><lf>OK<cr><lf>
02-05-2018 17:19:57.582 - Interpreted response: OK
02-05-2018 17:19:57.592 - Send: AT&FE0V1&C1&D2S95=47S0=0<cr>
02-05-2018 17:19:57.630 - Receive: <cr><lf>ERROR<cr><lf>
02-05-2018 17:19:57.630 - Interpreted response: Error
02-05-2018 17:19:57.630 - Session's data:
02-05-2018 17:19:57.630 - Read : 15 byte
02-05-2018 17:19:57.630 - Write: 0 byte
P.S. sorry, I translated the above log from italian, so some expressions might not reflect exactly what an english log could report.
I have tested the dial-up connection with my Win10 and BGS2.
Unfortunately while using the Gemalto driver I've met the similar problems (Failed opening modem device. Error 00000057). So indeed there must be some problem with this driver in Win10 OS.
However I've also tested the Standard 28800 bps Modem driver and I was able to successfully establish the dial-up connection. I've changed the maximum port speed to 115200 in modem properties under Windows Device Manager. And also I did the same in modem configuration started from "Connect Dial-up Connection" window that pops up when you want to establish the connection. I clicked "Properties" and then "Dial-up Connection Properties" opened. Then I clicked "Configure" for the desired modem.
I hope that will help you too.
thumbs up for you man! It works.
Wonder why it did not worked with the standard 56000 modem, and why in windows 7/vista it is supposed to work with the standard 115200 modem.
Note that I set up the maximum port speed at 115200, but in the predefined settings the speed of the port is set up at 57600 and cannot be higher than that.
Now that I've seen that it works, I've tried the standart 56000 modem with the same settings as the stantard 28800, but no it does not work.
Ok, in the end we have come out with a solution, hope this helps other folks!
Thanks a lot Bartolomiej
These Windows drivers are quite old and they were originally created for CSD calls. It's hard to say why 56k driver is not working properly while 28.8k is working fine. For this solution the driver name doesn't matter and the most important thing is that there is a proper driver that does the job.