Reply To: Cant connect to Cellular
Hi, We had the same problem with cellular connection. Turned out to be a problem with the right APN adress. Make sure you have the right APN for your tele provider.
View ArticleReply To: Cant connect to Cellular
APN is correct as the sim card is tested working on mobile phone on the APN. Do i leave the Connect String and Init String all empty? What is Dial Prefix?
View ArticleNew node not showing up in Node-Red sidebar
I have a v1.3.3 AEP conduit. I installed a new node via npm: npm install node-bacnet This BacNet node isn’t showing up on the NodeRed sidebar. But I do see a <node-bacnet> installed on the...
View ArticleReply To: New node not showing up in Node-Red sidebar
Eric, The node red log is in /var/log/app. See if there is anything pertaining to the bacnet node when node-red starts. What kind of dependencies does the bacnet node have? Jeff
View ArticleReply To: mdot & mdotbox AS923
Need AS923 for DotBox, for site survey before planting the Conduit Gateway. Flashed using the following custom firmware for DotBox (AS923) but getting following errors when trying to do serial...
View ArticleReply To: I am using the mDot Box product.
Hi Tae, If you open the DotBox, you should see a USB connector just below the on/off slide switch. Assuming it is there, that can be used to power the DotBox. You could cut a hole in the plastic case...
View ArticleReply To: New node not showing up in Node-Red sidebar
Hi Jeff, For the node-red node-bacnet installation, the dependencies are gextend and bacstack. Both dependencies seem to be packaged inside the node-bacnet folder. I don’t see any errors relating to...
View ArticleReply To: New node not showing up in Node-Red sidebar
Eric, A couple of things that I noticed is that node-bacnet wants node 0.12.0 or newer, whereas the node on Conduit is stuck at 0.10.48 due to the fact that node stopped supporting the armV5...
View ArticleReply To: xDot with Universal Windows Apps (UWP)
I was able to solve this problem in the end. It might be a problem with the .Net Core, or maybe I am missing something, but it seems that .Net Core does not realize when the device has sent all the...
View Articlev1.0.35 – EU band changes
Hi can you provide some additional info about this change “Force 869.4 as additional frequency base if configured above 868.8 Configure only 4 channels when addition channels is set above 868.8″ 1....
View ArticleReply To: Packet and Ack Counter
Dear Mike, I’m uploading the following application: I’m not sure about how to get the mbed-os version? and I have set the speed on the COM port to 115200 but since I’m not using the AT firmware, how...
View ArticleReply To: Packet and Ack Counter
Sorry the application is below: mDot_Workshop https://developer.mbed.org/teams/The-Things-Network/code/mDot_Workshop/docs/6ce90b84a3fe/main_8cpp_source.html
View ArticleReply To: Conduit mLinux OTAA
I was experiencing the same problem when I set up nodes manually to the Network Server. When I did it with OTAA process with adding device and then NS created node parameters on its own. the other...
View ArticleConduit Remote Access Suggestion
Hi all, I would like to remotely access to the Conduit AP where I would like to set remotely NS address if needed. Do you have some suggestion how I could do it? Thank you.
View ArticleReply To: v1.0.35 – EU band changes
Lawrence, I updated the change log to clarify. Default channels are always created. Additional Channel setting of 869.1-869.5 will create additional channels: 868.8, 869.0, 869.525, 869.8
View ArticleReply To: Conduit Remote Access Suggestion
Miha, You will need to configure a WAN interface on one of the interfaces (Ethernet, WiFi, Cellular). Then enable access via WAN for HTTPS. Make sure you are not using the default password or you will...
View ArticleSend Message to Azure IoT
Hi, I am trying to send a message to Azure IoT using the Resource. From other resources I understand the structure of an Azure payload for the function node should be:- { “protocol”: “amqp”,...
View ArticleReply To: mdot & mdotbox AS923
min, Looks like issues with I2C which is the peripheral all those sensors are on. What mbed-os and Dot Library versions are you using? Cheers, Mike
View ArticleReply To: Transmit Failure Codes
Scott, This code is LORA_BUFFER_FULL. There was a bug where this wasn’t coupled with a good mDot error code in some cases. You’d get this when you’re attempting to send data but there’s not enough...
View ArticleReply To: Transmit Failure Codes
Scott, I was mistaken on one point. When the LORA_BUFFER_FULL error code is returned to send, the packet has been sent, but just the MAC command responses (without the payload because there wasn’t...
View Article