This section is a selection of frequently asked questions that relate to common issues encountered.
Feel free to email us should you have further questions on

Checking Airtime on the GSM Commander
The GSM Commander can only reflect your local currency value of airtime. It is not able to report on the SMS or data bundle balance (if such a bundle is loaded to the cell number in question). SO What Now? We normally suggest having some airtime loaded on the cell number along with your SMS and / or data bundle. Let us assume you have loaded ZAR 20 to the cell number with a 500 SMS bundle, you will then program the GSM Commander to alert the required personal when the Airtime has dropped to ZAR 19. This alert indicates to us that either the bundle has been depleted or used up (as we are now consuming airtime and not the bundle). You can now re-load with a new bundle and top up with enough airtime to get you back above you alert threshold. If you are still not 100% sure what we are on about, please feel free to contact
Network Related Errors
Are you experiencing some “strange” behavior from your GSM Commander? Things such as the unit just ringing when you call it and it doesn’t activate statements, but yet it can make calls out to people in the list . . . or the usual “my Commander doesn’t want to boot up . . .” Well here is a couple of check points to tick off, this will give us an indication if the GSM Modem has become faulty or if it is indeed a network related issue, and it may even save yourself a phone call to the support desk 1) When running a contract SIM card in the unit there is often the following issue, the networks like to charge you extra to enable Caller ID (CLID), of coarse the GSM Commander needs to know who is calling it otherwise it will not action any statement which starts with “IF voice call received from any number in my list . . .” You can get around this by saying “If voice call received from any number” instead, but that will put your entire system at risk of some “random” person calling the number by chance and activating the Commander (so steer clear of that). 2) Does you SIM Card have a PIN enabled? Most Pre-paid SIM cards come standard with a SIM Pin enabled, you have 2 options available to you to get around this: Option 1: Remove the power from the GSMC and remove SIM card, place it in a cell phone and go to settings on the phones menu, in the settings there will be an option to disable SIM pin, disable it and reinsert it into the Commander and power up. Option 2: If you are well aware the SIM has a pin you can go into the software and click on the settings tab, on the top left of the screen you will see in big bold letters “SIM PIN”, un-check the disable option and enter the correct SIM Pin, oh yes and do not forget to save the setup to the device after making the changes. PLEASE NOTE: We will always insist you try option 1 above first, as this way we are sure that the Commander has access to the SIM Card (we sometimes may have the wrong pin or misplaced a digit when typing the SIM Pin into the software) What SIM Card are you using??? Did you try and be wise and purchase a DATA SIM Card that people typically use for M2M devices?? The GSM Commander can work with a DATA Sim card, but be warned it will not be able to send or receive any voicecalls, so if you are wanting that feature (as most of us do) then please refrain from using those DATA SIM Cards.
Issues loading Software on to GC048b with Windows v7+
Are you trying to load GC048A/B software onto Windows 7 / 8 or 10, it is most likely coming up with the following error message: driver is not digitally signed. This is how to fix it : The GC-048B is a older unit, that was designed before Windows signed drivers. It works perfectly with Windows XP, without and procedure. Please find the procedure, on how to disable driver signature enforcement for Windows 7.
  1. During boot-up, continuously press F8 to get to Advanced Boot Options. Note: On some systems, you need to first press F2 to go into Boot Menu, then press F8 to reach Advanced Boot Options.
  2. When the menu appears, use the DOWN arrow key to scroll to “Disable Driver Signature Enforcement.”
  3. Press .
  4. Continue the boot process. Drivers should detect fine now.