Category Archives: IoT

Internet of Things

“Device driver software was not successfully installed” Warning Message

Applies to: MOBITEK S80 Modem

The warning “Device driver software was not successfully installed” can be ignored as long as there are 4 COM ports appeared when you plug in MOBITEK S80 Modem with PC.

 

The 4 COM ports are:-

  • Sierra Wireless AT Command Port (UMTS)
  • Sierra Wireless CNS Port (UMTS)
  • Sierra Wireless DM Port (UMTS)
  • Sierra Wireless NMEA Port (UMTS)

Comparison Between MOBITEK S80 SMS Modem in VMWare and VirtualBox

  VMware VirtualBox
Installing USB Driver (USBDriverInstaller_SL80XX_V11.5.0.0.exe) Easy to install without the needs of other pre-installation software.
  • Require installation of “Extension Pack in VirtualBox”
  • Require configuration in “USB Settings”

(source: https://www.wintips.org/how-to-setup-usb-on-virtualbox-guest-oracle/)
MOBITEK S80 appearance in Device Manager Can detect the MOBITEK S80 after USB Driver installed without COM port disappearing It cannot detect MOBITEK S80 Modem vis USB port, refer to

The work around is to use serial port in VirtualBox by linking/mapping USB port (host) to serial port (VM), refer to https://mobitek-system.com/blog/2017/11/how-to-set-up-mobitek-s80-modem-in-virtualbox/
Hyper Terminal test Able to run Hyper Terminal test on connected MOBITEK S80 MOBITEK S80 Modem will not response in hyper terminal if connected via USB port in virtual machine, refer to https://mobitek-system.com/blog/2020/06/fail-to-get-mobitek-s80-to-work-in-usb-port-in-virtualbox/

How to Solve USR-TCP Cannot Detect MOBITEK S80 Modem on LAN

  1. Use “Advance IP Scanner”

    to scan for a free IP address on LAN. The free IP address will be assigned to MOBITEK S80 Modem later.
  2. Disconnect MOBITEK S80 Modem from LAN.
  3. Directly connect MOBITEK S80 Modem with laptop/PC through LAN port/cable.
  4. Run “USR-TCP”,

    Assign a new IP address that does not belong to any device in “Advanced IP Scanner” (step 1) to the MOBITEK S80 Modem . As well as configure the “Default Gateway”, “Subnet Mask”, etc.
  5. Disconnect MOBITEK S80 Modem from laptop/PC.
  6. Re-connect MOBITEK S80 Modem to LAN through router/switch.
  7. Run “USR-TCP” to detect MOBITEK S80 Modem.
  8. If  “USR-TCP” still cannot detect MOBITEK S80 Modem  then use web browser, enter the IP address of MOBITEK S80 Modem into the address bar. If a web administration page is displayed then the connection is successfully established.

    Web Administration Page of MOBITEK S80 Modem

  9. Use “USR-VCOM”

    to add a COM port that links the COM port with the IP address of S80.
  10. Use “Hyper Terminal”, connect via COM port, run “hyper terminal test”. If test is passed then S80 is working on the LAN.

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

Summary Table — MOBITEK Modem in Linux Mint in VM and Linux Mint as Host OS

MODEM Linux Mint in VM Linux Mint in Dell-D630
MOBITEK S80 MOBITEK S80 does not work (no response in CuteCom) in VM-Linux Mint MOBITEK S80 can work in Linux Mint using USB. There are 4 COM ports created in Linux (ttyUSB0, ttyUSB1, ttyUSB2, ttyUSB3), only “ttyUSB3” is used for the AT command.
MOBITEK Q24 MOBITEK Q24 is working (can send and read SMS) in VM-Linux Mint MOBITEK Q24 also can work in Linux using “ttyUSB0”

 

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”

How To Solve Modem Cannot be Connected or Unresponsive in CuteCom Linux

Applies To: MOBITEK S80 Modem, MOBITEK Q24 Modem, Linux OS

 

Caused By: permission or privilege to use serial port or USB port is NOT assigned to current user.

 

Solution: grant permission to current user by adding  “tty”, “dialout” into “Groups” of the current user.

  1. Optional — install “Cutecom” from Software Manager.

    Linux_USB-01Click on “install”
    Linux_USB-02
  2.  Go to “User and Groups”.
    Linux_USB-03
  3.  Click on the current user and then click on “Groups”.
    Linux_USB-04
  4.  Assign the following “Groups” or permissions to the user:-
    • dialout
    • root
    • sudo
    • tty
  5. Alternatively, command line can be used to add permission to the user:-
  6.  Restart Linux.

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.