Q1: Is there API for Linovision gateway to get historical data?

Answer: There is no API to get historical data. If you have any requirements about it please contact Linovision about it.  

Q2: What kind of the material does the IOT-G67’s outer shell made of

Answer: Polycarbonate+ die-casting aluminum.

Q3: Is it possible to connect multiple IOT-G65 to the network server of one IOT-G65?  How many can I connect?

Answer: Yes, you can connect up to 4 units of devices.

Q4: I want to ask if the gateway could perform end device localization based on TDoA (Time Difference of Arrival)? 

Answer: Currently cannot. Linovision gateways support the gateway GNSS positioning now.

Q5: What are the main factors that will affect the number of the IOT-CX controller that gateway manage?

Answer: The number of IOT-CX controller that connect to gateway would be affected by factors like reporting interval, distance in between, payload length, Lora frequency band and spread factor.

Q6: What is the maximum length of the PoE cable supported for the IOT-G67 gateway ? 

Answer: The length is up to 80-100 meters.

Q7: What is the difference between LoRaWAN 1.0.2 and 1.0.3? If I am using class B, which version shall I use? And can version 1.1 compatible with 1.0.3?

Answer: LoRaWAN1.0.3 supports unicast & multicast class B devices. Class A and class C sections are unchanged compared to LoRaWAN1.0.2 with the exception of a new MAC command "DeviceTimeRequest" used to synchronize the real time clock of a device. For devices operating in class A or class C, there is no need to upgrade to LoRaWAN 1.0.3. Click here for more information about LoRaWAN 1.0.3.

Q8: What are the new features for the  LoRaWAN V1.1 compared with  LoRaWAN  v1.0.2?

Answer: LoRaWAN V1.1 protocol is optimized for battery-powered end-devices and adds support for handover roaming, Class B and security enhancements. Click here for more information about LoRaWAN 1.1.

Q9: How many super capacitors in your IOT-G67? How many Farad for each one?

Answer: IOT-G67 has 5 capacitors inside, and each one is 25 Farad.

Q10: Can the IOT-G65 and IOT-G67 support external 4G antenna?

Answer: IOT-G65 can be customized to connect external antenna, while the IOT-G67 cannot. Please contact Linovision sales if you need external antenna customization.

Q11: Why the time stamp of message that received on Network Server is different from the set time of Linovision LoRaWAN Gateway?

Answer: In standard LoRaWAN protocol, the upload time is defined on UTC time zone. So the time displayed on Chirpstack server is different due to different time zone.

Q12: Can the LoRaWAN sensor data collected by the Linovision LoRaWAN gateway be sent to cloud/websites other than the Linovision IoT Cloud?

Answer: Yes. Linovision gateway supports data transmission via MQTT/HTTP/HTTPS. You can refer to articles below:

How to Connect LoRaWAN Gateway to MQTT Broker

How to Connect Linovision LoRaWAN Gateway to HTTP(s) Server

Q13: Does the Node-RED of Linovision LoRaWAN gateway start up on boot or it needs to be started manually?

Answer: It starts up when it's enabled on Web GUI.

Q14: Is it possible to send a payload to the Linovision LoRaWAN gateway to send an instruction to a LoRaWAN Controller using HTTP like we do posting a message to a specific topic in MQTT?

Answer: No. When the gateway is connected to HTTP/HTTPS server, it only supports uplink. If you want to send downlink, one way is to use the Node-Red feature on the gateway. In that case, the gateway works as HTTP server and it requires a public IP (Cellular or WAN) to allow connection from HTTP client.

Q15: Are the IOT-G67 gateway able to use nanosecond timestamp for geolocation? 

Answer: Not supported now. Linovision have plans to upgrade chip which is suitable for geolocation. Please contact Linovision if you have any applications requiring for it.

Q16: Do you have any recommendations regarding lightning protection?

1. If we mount the gateway on relatively low height (4-5 m, on top of fiber optic PoP), and we connect the gateway body (by original metal mount) with the lightning protection of the PoP, do we need the surge protection on the antennas and LAN cable?

2. Do you have to offer some directional antennas, in cases where we want to cover only a part of space, for example 90 degrees? This would improve our reception in cases where the gateway is mounted outside of a city.

Answer:

1. The height is not the most important. The critical thing is whether there is other devices/buildings higher than your gateway. Antenna needs lightning surge protectors separately. If your network cable has passed any surge protection system, there is not need to add extra protection.

2. Not by default. If necessary, please share your directional antenna requirements to Linovision in details.

Q17: The gateway disappears from TTN quite often, how to check the issue? 

Answer: Regarding the disconnection between the gateway and TTN, you can check the following points:

1. Whether the network of the gateway is normal: Fail to Access the Network of Linovision Gateway.

2. If you use Semtech type packet forwarder, you can change to TTN type which is more stable: Linovision Gateway -The Things Stack(TTN) Integration via Basic Station

Q18: Can you inform about the difference in range between IOT-G65-L04EU-868M without external antennas and IOT-G65-L04EU-868M -EA with external antenna in an Indoor application?

Answer: The gain of external antenna is 2dB, while the gain of internal is about 1dB.

 If the gateway just need to cover the end devices in the building (2 floors nearby), the internal antenna version is enough, the signal quality (Average SNR) is 2dB less than the external antenna). The distance (max) can reach 1 km in building/park/city.

If the gateway needs to cover wider area, the external antenna version is recommended, the signal quality (Average SNR) is 6dB more than the internal antenna version.

The distance (max) can reach 2 km in buildings/parks/cities.

Q19: What is the maximum number of channels we can configure in LoRaWAN gateway to receive or send data from Nodes(Channels)?

Answer: The max number of channels that can send and receive is 8. One channel of the gateway can deal with a data packet one second, so if the interval is 1 min, it can deal 480 data packet (nodes); if your sensor interval is 1 hour, it's sure that the gateway can work with 100 devices.

Q20: What's the meaning of the packet with different colors under "Network Server->Packet" tab?

Answer: Blue and white means normal transmission and grey means the message is in queue and waiting for sending. This always happens in sending downlinks to Class A type device.

Q21: Can we connect & configure 2 sensors to the same Application in Linovision gateway? If yes, how to separate every sensor data?

Answer: If the sensor modules are the same, you can use the same application including the same decoder and the MQTT destination. You can configure decoder to add device EUI of every sensor to distinguish every sensor. For more details please refer to How to Use Payload Codec on Linovision Gateway.

Q22: Is it possible to select all international frequencies (for all LoRaWAN frequencies) in one chip with IOT-G67?

Answer: It's unable to select all LoRaWAN frequencies in only one hardware.

Q23: Does Linovision IOT-G6x gateway support Node Red? If so, do I need to expand the eMMC for it?

Answer: Linovision IOT-G6x gateway has supported Node Red with firmware version 60.0.0.35 or above. There is not need to expand the eMMC.

Q24: How to use the Node-Red of Gateway? 

Answer: Please refer to LoRaWAN Gateway User Guide about Node-RED introduction and application examples.

Q25: Can the gateway connect to the Ginjer platform?

Answer: Yes, this platform has integrated with TTN, gateway can connect Ginjer platform via TTN.

Q26: Will all the traffic go over the VPN tunnel if connect the gateway to Loriot and enable the VPN?

Answer: No, because VPN tunnels and Loriot traffic destination are different.

Q27: Why can't I see the cellular settings on the gateway Web GUI?

Answer: You can go to "Status->Overview->System information" webpage to check whether the product model contains "L0XX". If not included, it means this model doesn't support cellular. Otherwise please submit a ticket to support@linovision.com about it.

Q28: Is there a way to send data over http(s) to the gateway that will be forwarded to the lorawan-sensor? 

Answer: For the HTTP API to send the downlink message to the sensor, it's not supported in our gateway. It's suggested to use MQTT integration which supports both uplinks and downlinks.

Q29: Why can't I connect the gateway to the Internet through WLAN?

Answer: Please check the settings of WAN Failover, which supports Cellular and WAN interface there by default. You need to select WLAN as the primary interface to make the gateway access the network.

Q30: What is the DC power input connector type of IOT-G67?

Answer: The connector type for power input is M12 Connector. For detailed definitions, please refer to the chapter2.5 of IOT-G67 Quick Guide.

Q31: Can IOT-G6x gateway connect to SCADA system? 

Answer: Yes, if your SCADA supports MQTT protocol and can work as MQTT broker, you can connect Linovision gateway to SCADA system and transfer data to it. SCADA system can also poll Modbus data from IOT-C50x according to How to Achieve Modbus RTU to/over TCP between Linovision Gateways and Controllers. By the way, Linovision IOT-G6x gateway has integrated the Node-Red for flexible integration.

Q32: Can I connect gateway to Linovision IOT-G6x gateway build-in NS? How many gateways can I connect it at most? Can I use third-party gateway to connect?

Answer: One Linovision LoRaWAN gateway can connect to 4 Linovision IOT-G6x gateways at most, which is a feature of Linovision IOT-G6x gateways only.

Q33: Does the Linovision IOT-G65 support dual interfaces to connect network?

Answer: Yes, Linovision IOT-G65 supports main interface and back up interface to connect to network.

Q34: Can IOT-G6x gateway connect to multiple MQTT/HTTP servers?

Answer: Yes, Linovision IOT-G6x gateway supports to connect to 1 MQTT server and 1 HTTP/HTTPs server.