A: Almost. The SiteManagers without built-in 3G modem can use an external GPRS/3G/4G USB adapter. The SiteManager includes a large number of drivers for different adapters. Refer to the 3G/GPRS USB Adapter Compatibility list that we keep updated with latest information and experience.
A: The APN (Access Point Name), is the individual ISP providers' gateway from their 3G/GPRS networks into the Internet. The SiteManager includes a list of the commonly used APNs for global ISPs, and will automatically try APNs that matches the ISP. In case the SiteManager does not have success connecting with any of the APNs, you may have to enter it specifically. Contact your ISP or SIM card provider to get information about the APN. You can also check the SiteManager log to determine which APNs it has tried. (Type APN in the log filter field) Examples of APNs for some larger Danish 3G/GPRS providers that are automatically selected in the SiteManager:
- 3: data.tre.dk
- TDC/Telmore: internet
- Telia: www.internet.mtelia
- Telenor: internet
A: SiteManager does not natively support Profibus. You have two options to solve this:
1. If you connect a CPU via MPI (e.g. our SE MPI100), you can via this reach a Profibus device (es panel) "via siemens routing".
2. You can connect the SiteManager via Ethernet to a profibus adapter such as the netlink 50-mpi from Hilscher.
A: Koyo PLCs typically have two serial ports. You may experience problems with the Default port.
Successful tests have been made with a SiteManager connected to the Koyo COM port 2 configured to DirectNet (the Direct Soft5 program auto negotiates to 38400, 8, odd, 1).
A: The first thing to check is if the email was triggered at all. In the GateManager console, go to the appliance for which the alert is attached, and check the Alert log. Also check that the email address is correct.
If this is true, there is a propability that the email has been caught in a spam filter. The alert email has an xml file attached that will make some spam filters to block the mail.
If the alert has been accepted by the spam filter in the past, but suddenly gets blocked, it could be because the alert is triggered often, and the spam filter may subsequently block it as "repeated spam" after a while.
The best resolution is to enter the spam filter setup and white list all emails from the GateManager
A: It is possible to install the SiteManager Soft PC as a Windows Service. This is the procedure:
1. Log on as administrator and install the SiteManager Soft PC (SM PC)
2. When the SM PC is rightfully installed - install the SM PC as server by the following command:
- "%ProgramFiles%\Secomea\SiteManager PC\SiteManagerPC.exe" -install
this will install the SM PC as service in the background.
You can still log on as user level, but the TrayIcon will not be available. It does not help trying to start the TrayIcon manually. (By "TrayIcon" is referred to the Secomea "ON" icon which in reality represents the SiteManagerPC.exe program)
If you need to browse the admin WEB interface of the SM PC from the local PC you can use the url:
> http://10.128.128.129:3/ (Username = admin // PW = admin (if not changed) )
Command for uninstalling SM PC as service:
> SiteManagerPC.exe -remove
A: Most likely you have a personal firewall blocking the communication between the tray icon program and the LinkManager main process that handles the virtual adapter. The firewall build into Windows XP and Windows7 usually do not course problems, while a third party firewall may. Try check the following:
A: You may experience that the signal is weak in your area. You can check the signal strenght in the SiteManager menu Status --> Network. SQ (Signal Quality) indicates the reception. For normal operation the signal strength should be 6 or higher, but you may experience adequate speeds for SQ as low as 2, but you should also expect drop-outs.
Secomea can provide an antenna together with an adapter that will fit most USB modems (partnumber 26894). If you want to make sure that your USB modem is compatible, we recommend purchasing it from Secomea (26888). Note that some USB modems, typically from Huawei, has been found to be unstable when connected several days. Check our black-list of modems for latest info.
If you do not get any signal, you are probably in an area outside data communications coverage. If you get a signal, but cannot make a connection you may be more than 35km away from the base station in which case the network rejects your signal because of time delay - NOTE: This cannot be corrected by any antenna.
For 3G/HSDPA communications the maximum distance to the cellphone tower is approximately 8km. Usually a modem will automatically switch to GPRS. You may want to force the modem to only use GPRS in order to prevent it from flickering back and forth. This must be done by an initialisation string entered in the the UPLINK2 settings. Such initialization strings will depend on the modem manufacturer. E.g. Option uses the command AT_OPSYS=0 for forcing GPRS, while other manufacturers uses the command AT+COPS=1,0,"nn",0 (where nn denotes the ISP. The ISP will also be shown in square brackets on the Network status in the SiteManager menu).
A: It may be the 3G modem presents it self to Windows as a PPP interface. This is seen in some regions for Vodafone subscriptions. In this scenario LinkManager will have problems resolving the GateManager IP from the DNS name inside the certificate. You should solve it by issuing a LinkManager certificate that uses the GateManager IP address instead of the DNS name. You can verify the IP address by simply pinging the dns name (e.g. "ping gm04.secomea.com"), which will resolve the GateManager IP address.
Alternatively you can create a static IP entry inside the LinkManager configuration menu for the DNS name as follows: Click the Advanced menu to enter the menu. Select System -> Dev1 -> DNS -> Static . Add a Static Host Entry with the GateManager DNS name as Hostname (e.g. gm04.secomea.com) and the GateManager IP address as IP address (e.g. 18.104.22.168).
Note: this has been observed on LinkManager version v6041_11017. A solution to this scenario may become available in a future LinkManager release.
This is solved in a later SiteManager firmware. Please update to latest version
This is solved in a later SiteManager firmware. Please update to latest version
Yes, but only models with built-in UMTS modem (xx39) running firmware 5.1 (13025) or later, and only if the SIM card supports SMS messaging.
For further information see the SiteManager xx39 SMS alert system application note.
If you cannot find your device in the list of vendor agents, you should always first try the Generic / Serial agent. This agent will attempt to detect and negotiate serial settings with the device based on RFC2217. This agent should work in 98% of cases.
Microsoft Blue Screen Of Death (BSOD)
Observations on the Internet show that Intel Microsoft virtualization does not like to share the service between different systems like Virtual PC and Virtual Box at the same time - The result is a BSOD.
Eg see link at the end of this FAQ.
What is generating BSOD on Win7 with Virtual PC:
If Virtualization is enabled in the PC's BIOS a BSOD will occure if you are running Virtual PC guest systems while you start the LinkManager on the Host system (LinkManager includes a component that uses VBox)
How to awoid BSOD with Virtual PC guests:
Disabling the VT-x in the BIOS will solve the problem.
With Vt-x enabled what else can be done:
If the Virtualization is enabled in the BIOS and running Windows7(32b/64b) you can without any problem run LinkManager inside the Virtual PC guest OS just like you can run LM inside a vmware Player guest OS. Note that LinkManager can only run inside a vmware guest OS if you are running Win7 and VT-x is enabled. With Virtual PC you can always run LinkManager inside the guest OS (VT-x enabled or not).
You might be able to run a vmware guest OS and have the LinkManager running on the host PC while VT-x is enabled. We have not seen a BSOD but it might happen.
You can always run LM on the host or inside a Virtual PC. With VMWare you can only run LinkManager on the Host PC, it will not start inside a VMWare guest OS.
Windows 2008 or a HyperV server:
Windows 2008 will behave like Windows 7.
> Windows 7 (32bit/64bit), VT-x enabled in BIOS
> Virtual PC guest is running and you start LinkManager on the Host OS.
What is working with Virtual PC (no BSOD)
> Windows 7(32b/64b), VT-x DISABLED in BIOS
> Virtual PC is running any Guest PC and you can with out problems start LinkManager in the Host PC.
What is working with Virtual PC(no BSOD)
> Windows 7(32b/64b), VT-x ENABLED in BIOS
> LinkManager is running inside the Virtual PC Guest PC.
Also read this post on the Microsoft forum:
Spencer Shi-MSFT Microsoft - wrote July, 2012:
Quote: "First, please make sure that VPC is the only virtualization software on the same machine. This is because we do not support a scenario which involves running VPC and another virtualization software on the same machine including Hyper-V. The first client VM running gets the handle to VMM (e.g. the CPU registers) and when you try to run more than one VM solution on a given host, it will cause the system crash.
Then if this is not the scenario you are experiencing, please send me the dump file via SkyDrive or other 3rd party tool for analysis. "end-Quote
Usually, anything you can connect directly to a computer, will also work with our SiteManager.
For devices connected via ethernet, use the Generic > Nat All, 2-way agent. This opens up every single port towards the device, allowing full access on all TCP and UDP port.
For serial conected devices, please use the Generic > Serial agent. If you still are experiencing troubles with connection, try to set speed and Data / Parity / Stop bit in the paramter details of the agent. Also, please see our guide covering serial agent setup and trouble-shooting guide.
For USB devices, you can use the Custom > USB agent. Please referer to our guide covering the setup and use of custom USB agent.
Bridgeway Configuration Tool automatically scans the COM ports to locate the device. We have experienced that in some cases, the tool is not capable to scan the LinkManager virtual COM port.
The solution is to disable the physical COM ports on the computer. You go in to the Device Manager, and right-click on the COM ports, and disable them. Next, reboot the PC and Bridgeway Configuration Tool should be able to scan the LinkManager virtual COM ports.
There are two ways to provide access from the UPLINK network to the DEVICE network. If you want full access from one PC to the DEVICE network, you can use the Custom > SCADA agent. You type in the IP address of the PC that needs to connect to the DEVICE network in the agent parameter details, and check the "DEV source translation" checkbox. Now, you just need to tell the PC where to look for the DEVICE network. You can do this by adding a static route to the PC (see details on how to do this on a Windows PC here: http://technet.microsoft.com/en-us/library/cc757323(v=ws.10).aspx). Use the UPLINK address of the SiteManager as gateway for the network.
If you want to restrict access to a specific device on the DEVICE network, you can use the Custom > Forwarding agent. Read more on how to use the forwarding agent here: Using_the_forwarding_agent.pdf
To be able to communicate across the UPLINK and DEV interface, you can use the Custom > Forwarding agent. Read more on how to use the forwarding agent here: Using_the_forwarding_agent.pdf
To be able to access the Internet from the DEVICE network, you need to create a Custom > SCADA agent. In the Parameter Details of the agent, type in the IP address of the device, which needs access to the Internet. Check the "Enable UPLINK Source Translation" box, and make sure the IP address of the DEV port is set as default gateway on the device.