Peter Ferland
Forum Replies Created
-
AuthorPosts
-
Peter FerlandBlocked
We generally recommend that you use the MQTT broker. When you say “high load” what is the number of transmissions at the same time?
Do you see any errors in the lora server or node red logs? Sometimes the light in the browser goes red even though messages are still coming through, however it sounds like it is disconnecting in your case.
Peter FerlandBlockedThe LoRa starter kit bluemix flow does this, you can download it from the device hq app store.
In short, use an http request node to send a GET request to http://localhost/api/system/macAddress. You can then use a function node to store that in a global variable (context.global) so other function nodes can use that variable in the future without performing another API request.
Peter FerlandBlockedYes, its 0.25 Pa not kPa.
Peter FerlandBlockedIt is in hex, and you do need to decide it to get the final results. For example, 0b indicates that a temperature reading is in the following 2 bytes. The table on the “Data packet format” page says “0.0625 Degrees C (Signed MSB)”. 0x0163 is 355 decimal, times 0x0625 is 22.1875 degrees C.
Peter FerlandBlockedWhat IP are you trying to set?
Peter FerlandBlockedSpreading factor is not explicitly set on the dot in that example. You can take a look at the function update_peer_to_peer_config in dot_util.cpp to see an example of the setTxDataRate method being used.
Peter FerlandBlockedCurrently the Conduit’s lora-network-server can only handle one Network Id and AppId. You could approximate this by using the first byte of the payload to identify the type of application it is. This could be as simple as a small program that subscribes to lora/+/+, then publishes to topics for app1/app2/etc. that your other programs are subscribed to.
April 13, 2017 at 9:41 am in reply to: Troubleshooting potential Conduit Transmit packet loss. #18272Peter FerlandBlockedYou could subscribe to the lora/+/down topic to see the payload of the packets when queued. You’d have to correlate them with the other log using the SeqNo.
(the mosqutto command line tools aren’t installed by default on an AEP conduit, but can be installed using opkg install mosquitto-clients)
April 13, 2017 at 9:36 am in reply to: Can't uninstall Loriot binary, unable to run lora-network-server #18271Peter FerlandBlockedYou can restore a factory default configuration by holding in the reset button for 30s. If that does not work, it would probably be easiest to perform a firmware upgrade using the latest firmware (even if that one is already installed) to be certain that you have wiped out all traces of the loriot install.
April 13, 2017 at 9:09 am in reply to: Configuring Conduit AEP to use computers internet connection. #18270Peter FerlandBlockedYou can disable the cellular connection by deselecting the “Enabled” check.
On your windows 10 machine you’d have to bridge your WAN connection to your ethernet port, then set a static ip address, gateway and dns as appropriately on the Conduit under setup then network interfaces.
For bridging connections on a Windows 10 computer, take a look at this guide: http://www.windowscentral.com/how-set-and-manage-network-bridge-connection-windows-10
April 12, 2017 at 11:00 am in reply to: Troubleshooting potential Conduit Transmit packet loss. #18260Peter FerlandBlockedYour interpretation of the logs is correct.
Is it always the same mDots? There may be something related to the location they’re at that is degrading reception.
It is not unexpected to lose some packets at random in any wireless system. You might consider transmitting several times to reduce the probability of all of your dots missing the message or some method for the mDots to know that they missed a message when they next check in.
Peter FerlandBlockedThe node will not select a gateway, if both hear it both will forward it. You would have to detect duplicates on your network server.
Peter FerlandBlockedAre you outdoors and have a clear view of the sky? You will not get a GPS lock indoors.
Peter FerlandBlockedThe data packet format is described on this page: http://www.multitech.net/developer/software/dot-box-and-evb-software/data-packet-format/
Make sure to select “Bytes” in the settings for the LoRa input node before parsing msg.data.
April 10, 2017 at 2:07 pm in reply to: Trouble adding new node to Node Red to connect to Azure IoT Hub #18227Peter FerlandBlockedYes you need an internet connection.
Peter FerlandBlockedIt will work. The REST API you’re using is always running on an AEP conduit, its what provides the administration webpage. You can in fact configure the LoRa server mode using the api/loraNetwork/lora endpoint.
Peter FerlandBlockedPer the LoRaWAN standard for US915 the 8 downlink channels are always 923.3-927.5 MHz. Uplink channels are divided into 64 channels ranging from 902.3 to 914.2MHz. The Conduit can listen on only 8 uplink channels at a time and the frequency band setting is selecting which 8 of those 64 to listen on. More details on the frequencies/channels for each region can be found in the “LoRaWAN Regional Parameters” document which can be freely downloaded from the lora alliance https://www.lora-alliance.org/For-Developers/LoRaWANDevelopers (free registration required)
April 7, 2017 at 11:09 am in reply to: mtxdot XDOT-NA1-A00 MODULE SERIAL MODE(peer to peer ) DATA MISSING #18200Peter FerlandBlockedPlease email sales@multitech.com for any price quotes.
Peter FerlandBlockedmbed-os is required by the libmdot-mbed5 library’s LoRaWAN stack on the mDot. The version of mbed-os must match the version libmdot was compiled against. You can check this by looking at the “revisions” view on the online compiler. If you need a more recent version of mbed-os to support a sensor library, then you can use libmdot-dev-mbed5 which is compiled against more recent versions of mbed-os.
Peter FerlandBlockedI’d recommend using the REST api on the conduit. You can find more details on the API here: http://www.multitech.net/developer/software/mtr-api-reference/
Peter FerlandBlockedIt looks like an mbed HAL issue for the stm32l1x series so the mdot should not be effected.
- This reply was modified 7 years, 7 months ago by Peter Ferland.
Peter FerlandBlockedWhich version of mbed is this bug on?
Peter FerlandBlockedThis is not supported at the moment but is a feature that is planned in the near future.
Peter FerlandBlockedIts configurable. The ICMP/TCP Check interval field defaults to 10 minutes.
April 5, 2017 at 8:42 am in reply to: Accessing USB Device via the USB Device Connector on the conduit back panel. #18162Peter FerlandBlockedThats the node red node.
April 4, 2017 at 4:28 pm in reply to: Accessing USB Device via the USB Device Connector on the conduit back panel. #18158Peter FerlandBlockedYou can connect a USB serial port to the “USB Host” connector and it should be recognized by the kernel and the appropriate /dev entry should appear. You must then manually configure a “Serial” node for the serial port.
Peter FerlandBlockedThe keep alive feature periodically sends the a small amount of data to keep the cell connection up. If the connection fails, the ppp link is restarted. If you take different actions based on the ppp status (e.g. storing more data) then you should keep checking. If the only action you’re taking is to reset the ppp link, then you can rely on the built in keep alive feature to do that.
Peter FerlandBlockedIts a simple ping, so just entering google.com would work.
- This reply was modified 7 years, 7 months ago by Peter Ferland.
Peter FerlandBlockedOn the cellular page of the admin dashboard do you have keep alives enabled?
Peter FerlandBlockedAre you able to send an SMS message using AT commands?
at+cnmi=2,2,0,1,0 at+cmgf=1 at+cmgs=”+1 YOUR PHONE NUMBER”
You’ll get an extra prompt. Type your message then press control-z to send.
If the SIM has data service, does a ping work? Try
at#sgact=1,1 at#ping=”www.google.com” at#sgact=1,0
-
AuthorPosts