Intellicom Innovation AB

The NetBiter WS100/WS200 firmware version 3.30 has 500 KB memory reserved for log files.

It could be a smaller amount, depending on the configuration (such as number of pictures, picture size, number of alarms, presentation pages etc.)

How many log parameters that can be stored depends on the data type of the parameters etc. When configuring the log an estimation is done that will show the time before the log is full.

			A SMS text message can be 70 characters long. the standard length of a SMS is 160 character, but depending on the language support( as Cyrillic) in NetBiter WS100/WS200 it will be limited to 70 characters. [ hide ] [ direct link to this faq item ]

			The GPS should support the NMEA protocol, up to version 3, and sends $GGA and $RMC messages type. It should communicate with a RS232 interface on a baudrate between 1200 and 115200. NetBiter WS200 has been tested with EverMore SA-920 and GPS simulation software. [ hide ] [ direct link to this faq item ]

			In NetBiter Config my NetBiter doesn't show in the listing, why? Your NetBiter could have been configured to use a DHCP server, which assign a IP address to the module. If the module is connected to a network without a DHCP, there is no IP address assigned and the module will not appear in the NetBiter Config list. To be able to set a static IP address, the NetBiter could be connected directly to a computer using a crossover ethernet cable (ordinary ethernet cable can be used for NetBiter webSCADA WS200). In NetBiter Config, click the Advanced Option button at the bottom left corner of the program window. Now a DHCP server can be started from NetBiter Config. Check the Enable internal DHCP server checkbox. Make sure that the computer is directly connected to the NetBiter. Now the NetBiter will be given a temporary IP address, and the module will show in the NetBiter Config list. Double click on the module, and set a static IPaddress, gateway and DNS server. Disabled the DHCP server, found under the Advanced Option button. Now the module will show in the NetBiter Config's listing again. [ hide ] [ direct link to this faq item ]

			If the presentation pages do not show any values it is probably some incorrect with the Modbus settings. Go to Setup/Modbus and make sure that the settings are correct. [ hide ] [ direct link to this faq item ]

			There can be 64 log parameters assigned, and 64 alarms configured in the NetBiter webSCADA. [ hide ] [ direct link to this faq item ]

			There can be 32 Modbus devices connected to a NetBiter webSCADA. [ hide ] [ direct link to this faq item ]

			Some modbus slaves have a small timing issue resulting in that they don't listen for a small amount of time when other slaves have been accessed, most devices follow the modbus specification for these timings, but some require a slightly higher value. We have added a setting to compensate for this, and you will find it under Setup - Modbus, the parameter in questions is "Extra delay between messages", try some different settings here, starting with 20, increasing the value in steps of 20 to see if this resolves the issue. If you don't get a positive result at 200ms then there is probably something else that causes the problem. [ hide ] [ direct link to this faq item ]

			There are built in registers that could be setup as alarm points, so you could get an alarm when the traffic exceeds a specified limit, for example, if total bytes sent and received during the last 24 hours is more than 10,000,000 bytes you could get an alarm. [ hide ] [ direct link to this faq item ]

			This is of course dependant on how many pages you browse and if you have pages with images, but a small estimate: Login, open page with image, refreshing values 5 times, open log page, download logfile (600x3 values, 23kB in size) this generated 450kB of traffic, so with a subscription that has 1GB included data traffic you could do this operation 2000 times in a month. [ hide ] [ direct link to this faq item ]

			No. The GPRS connection is an internet connection so, dependent on your subscription, you get a local connection to your service provider. After the connection is made, it doesn’t matter to what country the data is transferred. [ hide ] [ direct link to this faq item ]

			Depends on the requirements, for normal usage (loggings and alarms) and viewing data on NetBiter.net there is no need for any fixed IP. If there is a need to connect directly to the WS100/WS200 webSCADA to control and change values or settings, then a fixed IP sim-card must be used. NetBiter.net will get additional functions so the need for fixed IP should be minimized, and hopefully be eliminated in due time. [ hide ] [ direct link to this faq item ]

			Following ports is used for NetBiter WS100/WS200: 80 Webserver 502 Default port if Modbus TCP is used for internal registers (if gateway is enabled) 502 For communicating with Modbus TCP slave devices. Port 502 is the default port for Modbus TCP 2525 Mailserver 5222 NetBiter.net 8080 Extra Webserver [ hide ] [ direct link to this faq item ]

			This will also generate data, the amount is dependent on what kind of attack this is. [ hide ] [ direct link to this faq item ]

			The cost is dependent on the amount of data being sent and received, when connected to the NetBiter.net the WS100/WS200 will generate traffic to indicate that it is “alive”, this is limited to a few bytes a couple of times/hour. When using “always connected” there is a setting “Host to ping” and “Ping timer”, if active this will also generate a small amount of traffic to keep the connection alive. [ hide ] [ direct link to this faq item ]

			To connect to NetBiter.net following following settings should set: If you are using a cable connection to Internet, make sure that gateway and Primary DNS is configured at Setup/Ethernet. If you are using GPRS make sure that you have entered the APN at Setup/Modem. The APN (Access Point Name) should be supplied by the SIM card provider. Enable NetBiter.net at Setup/NetBiter.net. The correct activation code has to be entered (should be set as default). The code is found on a paper in the delivered box . Port 5222 has to be open for outgoing traffic in the firewall. The NetBiter Status, at the bottom of the page, should be read Connected to server. How to add the device on NetBiter.net, please consult the help at www.netbiter.net To ensure that you can connect to the server the attached file can be used. This is a Microsoft Windows XP/Vista application that should be run on the same network as the NetBiter WS100/WS200 and will report if there are problems to connect to the NetBiter.net server (traffic blocked in firewall etc.). NetBiter Connection Test Tool [ hide ] [ direct link to this faq item ]

			The SNMP version used to send SNMP traps in NetBiter WS100/WS200 is version 1.NetBiter WS100/WS200 only sends SNMP traps. It is not possible to send SNMP messages to NetBiter Ws100/WS200. SNMP traps is sent to a SNMP manager, which is set in the Setup/SNMP -menu item in the NetBiter WS100/WS200. The SNMP message is decoded with a MIB-file that can be uploaded to the SNMP manager. This file will make the trap to be in plain text. [ hide ] [ direct link to this faq item ]