Category Archives: SMS Modem

MOBITEK Q24, MOBITEK S80

How to Connect to MS Access Database using JDBC:ODBC Connection

  1. Depending on whether your Java application is 32-bit or 64-bit, choose the correct ODBC Data Source Administrator (64bit or 32 bit) to create the Data Source Name. Otherwise, the connection cannot be established.
      • If your Java application is 64-bit then use ODBC Data Source Administrator 64-bit
      • If your Java application is 32-bit then use ODBC Data Source Administrator 32-bit
  2. Open ODBC Data Source Administrator (make sure the correct version is used).
  3. Select “System DSN” tab. Click “Add”.
    JDBC-01
  4. In this example, we are connecting to MS Access database, in “Create New Data Source”, select “Microsoft Access Driver (*.mdb, *.accdb)” in the list. Click “Finish”.
    JDBC-02
  5. In “ODBC Microsoft Access Setup”, enter any “Data Source Name”. This name will be used in DBeaver later. So remember it. After that click “Select…” button.
    JDBC-03
  6. Now you have to locate your MS Access file. In this example we use “SMSEngine5.mdb”. Click “OK”.
    JDBC-04
  7. Example of the Data Source Name created.
    JDBC-05
  8. Open DBeaver (or any other database management tool). Click on “Database -> New Database Connection”
    JDBC-06
  9. In “Connect to database”, select “ODBC” in the list. Click “Next”
    JDBC-07
  10. Insert “Database/Schema” name the same like you created earlier in ODBC Data Source Administrator. Click “Test Connection” to test the ODBC connection.
    JDBC-08
  11. If everything is setup right, you will get the below message. Click “Finish”
    JDBC-09

Renaming “Sierra Wireless” in COM Ports

Objective: to use AT command to rename “Sierra Wireless” to “MOBITEK” so that all the 4 COM ports will display “MOBITEK”

 

Result: after using the “AT+WUSB” to change name to “MOBITEK”, the 4 COM ports in device manager still show  as “Sierra Wireless” .

 

In addition, there is no AT command to remove the other 3 COM ports, “CNS”, ‘DM” & “NMEA”

USB Drivers of FX30 and MOBITEK S80 Have Conflict — Bad_pool_caller

Problem: the USB Drivers for both FX30 and MOBITEK S80 cannot be installed in the same machine. Otherwise the below blue screen error will appear when trying to connect MOBITEK S80 3G Modem to the PC/machine.

 

Solutions: there are 3 solutions to choose:

  1. reboot Windows into “last known good configuration” (source: https://support.microsoft.com/en-my/help/4026863/windows-fix-error-0xc2-badpoolcaller);
  2. run system restore to restore Windows to the a date before FX30 USB driver was installed; or
  3. uninstall FX30 USB driver.

How to Set-Up MOBITEK S80 SMS Modem with WinPower UPS software

Applies to:

MOBITEK® S80 for SMS Over 3G Network

STEPS

  1. Connect your laptop/desktop to UPS and MOBITEK S80 Modem to laptop/desktop. Open Winpower UPS software. Go to System menu -> Act as Administrator and enter the password. The default password is “Administrator“. This step is important in order to configure Winpower software setting.

    To change the administrator password (optional), go to System menu -> Modify Administrator Password and enter the new password for administrator.
  2. Go to System menu -> Auto Search Device to search for UPS device automatically.

    Wait for the UPS to be searched.

    When found, the UPS device will be shown in the list. Double-click on it to see the UPS device status.
  3. Go to Tools menu -> SMS Setting to configure the SMS notification for UPS events.
  4. In SMS Setting, set the Com Port for MOBITEK S80 Modem, the Baud Rate to “115200“, and the Format of phone number to “Without National Code“. Enter the phone number for the notification to be sent, click Add button and select the phone number in the list. After that select the abnormal event in the event list that you want to be notified for. Click Test button to test the SMS sent successfully or not. If successful, click OK button.

How to Solve SMS Engine Fails to Initialize Despite Hyper Terminal Can Communicate with MobiGATE

Applies to:

  • All SDK (SMS API, STK API, etc.)
  • all versions of SMS Engine — Enterprise Edition

Cause: “MSComm32.ocx” did not install properly or the date of the file is incorrect. This occur when MOBITEK SMS Engine — Enterprise Edition has been reinstalled a few times on the same Windows machine.

Solution:

  1. Uninstall MOBITEK SMS Engine — Enterprise Edition.
  2. Unregister “MSComm32.ocx”:
    1. for Windows 64-bit, run “cmd” or “Command Prompt” as “administrator”, then type
      1. “cd %systemroot%\SysWoW64\“
      2. “regsvr32.exe /u mscomm32.ocx“
    2. for Windows 32-bit, goto Start → Run → type “regsvr32 /u mscomm32.ocx”
  3. Delete “MSComm32.ocx”.
  4. Re-install SMS Engine — Enterprise Edition.

or

  1. Unregister the “MSComm32.ocx” and delete it
    1. for Windows 64-bit, run “cmd” or “Command Prompt” as “administrator”, then type:
      1. “cd %systemroot%\SysWoW64\“
      2. “regsvr32 /u mscomm32.ocx“
    2. for Windows 32-bit, goto Start → Run → type “regsvr32 /u mscomm32.ocx“
  2. Copy the new “MSComm32.ocx” and manually register it:
    1. for Windows 64-bit, run “cmd” or “Command Prompt” as “administrator”, then type:
      1. “cd %systemroot%\SysWoW64\“
      2. “regsvr32 mscomm32.ocx“
    2. for Windows 32-bit, goto Start → Run → type “regsvr32 mscomm32.ocx“

 

source: https://support.microsoft.com/en-my/help/249873/how-to-use-the-regsvr32-tool-and-troubleshoot-regsvr32-error-messages