| Unable to initialize modem: Error 80000018 from lineGetID |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through April 13, 2018 ⬆ |
◄ ► |
| Author | Message | ||||
| Vijay Kalagara New member Username: Vkalagara Post Number: 15 Registered: 08-2014 |
Hello - We are having issues connecting to GSM modem (Multi-Tech Systems MTC-LAT1) using NowSMS software. We have to recycle the modem power in order to make the connection to work again. I am attaching a zip file with 2 log files. Can you please check on the logs and let us know what we need to do to resolve the issue? Appreciate all your Help! Thanks Vijay
| ||||
| Vijay Kalagara New member Username: Vkalagara Post Number: 16 Registered: 08-2014 |
Any suggestions on how to resolve this issue? Thanks Vijay | ||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 5841 Registered: 08-2008 |
Hi Vijay, Looking at the specs, this is a serial device, correct? Trying a different COM port and cable is generally advisable. Are you using a USB adapter cable? If so, there are issues that Windows uses very old drivers for cables that use the Prolific PL2303H chipset. For details, see this thread: https://support.nowsms.com/discus/messages/1/72456.html ... scroll down to the device manager screen capture. Note that the info and link to manufacturer web site still apply to Windows 10 and 2012/2016 Server. I would be interested in seeing a log that shows the activity right before the modem becomes unresponsive. Maybe that will offer a clue. Scanning the technical manuals for that device, I notice some timing instructions, which suggests that NowSMS might be talking to the modem too quickly, which might cause the modem to crash. At least that seems a possibility... Try manually editing the SMSGW.INI file, and under the [Section Header] for the modem, add MinimumReadDelay=100 Let's see if that makes a difference and prevents the modem from crashing. -- Des NowSMS Support | ||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 5879 Registered: 08-2008 |
Hi Vijay, I understand that you've been in contact with our sales staff, and are still experiencing this problem every 15 to 20 days. When the problem occurs, does restarting the computer resolve the problem, or does the modem need to be power cycled? If restarting the computer resolves the problem, there is a config option to take this action if a modem is unresponsive. I don't think this will work for you, as this tends to work only for some USB modems. If restarting the modem is required...then did you try the MinimumReadDelay=100 setting that I mentioned previously ... note this needs to be under the [Modem - name here] section of SMSGW.INI. I'd also recommend trying a value of 200 for this setting. Another suggestion...if not using NowSMS Lite and not sending MMS...try configuring NowSMS to use the COM port directly instead of the named modem driver. If you cannot use the COM port configuration, go into phone and modem settings in the Windows control panel...remove the multitech modem, then manually add Standard 33600 Modem, and associate this driver with the appropriate COM port...and configure NowSMS to use that. (This driver may seem an odd choice, but it is the most universal.) Any chance of capturing a log that shows the activity right before the modem becomes unresponsive? -- Des NowSMS Support | ||||
| Vijay Kalagara New member Username: Vkalagara Post Number: 17 Registered: 08-2014 |
Thank You, Des! We are directly connecting to the COM port and here is the configuration we have under Modem section in SMSGW.ini file: [Modem - COM3:] RouteName=ATGTexting ReceiveSMS=Yes ReceiveMMS=No ReceiveTo=ME The Process is working fine from 11/21/2017. We will add MinimumReadDelay=200 next time when it fails. Thanks Vijay | ||||
