Andrew Lindsay
Forum Replies Created
-
AuthorPosts
-
Andrew Lindsay
ParticipantIf you need to use an off-line toolchain then have a look at https://developer.mbed.org/cookbook/Homepage#software-development for available options.
thanks
Andrew
Andrew Lindsay
ParticipantThanks Jason.
Andrew Lindsay
ParticipantHave you tried increasing the number of join requests?
Andrew
Andrew Lindsay
ParticipantHi Brandon,
Thanks for the info. I’ll try this again without ACKs and wait for TTN to get their back-end updated as part of their development process.
Cheers
Andrew
Andrew Lindsay
ParticipantFor some reason it is getting timeouts while waiting for the ACK response. So looks like either the Conduit is not handling the packets properly or its detecting errors and not forwarding the packet.
Andrew
Andrew Lindsay
ParticipantJason,
“synch_word” is 52. I have seen a single message get through ok, but that appears to be the only one after running this for a few days. Compared to using a local private address where all packets were being received.
thanks
Andrew
Andrew Lindsay
ParticipantOne thing you need to bear in mind is that the mDot to Conduit communications via LoRaWAN will require the smallest possible data payload if you are looking to use maximum range. In some cases this could be as small as 12 bytes. This is also dependant on the SF and BW used. The Conduit to Cloud is a different area and you’re not restricted in the payload size as you are going over the internet.
Andrew
Andrew Lindsay
ParticipantHi Brandon,
I’d be interested in being a Beta tester for the AEP version of the Lora packet forwarder for TTN.
Also, my replacement LORA-MAC card has arrived so I can continue to develop sensor nodes.
Thanks
Andrew
Andrew Lindsay
ParticipantAs I understand it, when using public mode and TTN the LoRaWAN packets are passed straight on to TTN server. This then does all the authentication and network/session key generation etc for the end nodes joining the network. This is all done on the Conduit in the AEP version and therefore would not work as-is. Whether it is possible to add in the packet forwarder as an option and subscribe to TTN data I’m not sure but there are other ways to access the data coming from the LoRa end nodes via TTN.
This is therefore making the TTN gateway product look like an attractive option as it will have just a single function of a packet forwarder.
Andrew
Andrew Lindsay
ParticipantCould there be an option to dump the packets to the local mqtt broker as it does already and forward them on also?
Andrew
Andrew Lindsay
ParticipantSomehow I guessed that might be the answer.
ok, I’ll give that a try.
thanks
Andrew
Andrew Lindsay
ParticipantThanks guys.
Much appreciated
Andrew
Andrew Lindsay
ParticipantIf you want to program the mDot and are not currently familiar with the mbed environment then you’ll need to start at https://developer.mbed.org/ follow the Getting Started link then move on to the mDot Platform.
Without knowing your current skills and experiences its hard to pitch this at the right level. What I’ve provided should help you get started with the mbed environment and the mDot modules.
Andrew
Andrew Lindsay
ParticipantIf you are trying to use the AT commands on the mDot, you need to use the PA_2/PA_3 pins instead and not PA_9/PA_10.
Regards
Andrew
Andrew Lindsay
ParticipantHi Lawrence,
I got an RMA number and form from the support site and a UK address to return the MTAC-LORA card. I forgot how small it is!!
I’m guessing if we had a support contract then we’d have replacement parts without having to send the faulty part back first. I’m hoping they can turn it around in less than a week but its all downtime and for a fully operational network this wouldn’t be acceptable.
If there is anything that can be done to speed this up then that would be great.
thanks
Andrew
October 5, 2015 at 10:17 am in reply to: mDot Does Not Join Conduit Network From Distance Of Approximately 0.5 Mile #9483Andrew Lindsay
ParticipantWhat Spreading Factor and Tx power are you using? I used SP12 and a Tx power of 14. which are about the max for EU use in the 868MHz band.
Andrew
Andrew Lindsay
ParticipantLooks like I’ll be without a LoRa card in my Conduit for as long as it takes Multitech to send a replacement after sending mine back to them.
Guess thats going to slow down the implementation of The Things Network.
Andrew
Andrew Lindsay
Participantjust looking at the MTAC-LoRa photos….metal shield so guess not an easy fix.
Andrew
Andrew Lindsay
ParticipantBrandon,
Thanks. Is this a simple solder fix or defective components? If solder joint as you’ve previously pointed out, I have enough years soldering experience to attempt a fix.
I’ll also raise a support call too.
Out of interest, what should the ping and RSSI values be for the ranges I used?
thanks for your help
Andrew
Andrew Lindsay
ParticipantHi Brandon,
Results, No Antennas approx 6 inches between SMA connectors:
at+ping -111,4.5 OK at+rssi -119, -119, -65, -87 OK
No Antennas, approx 3 inches between SMA connectors:
at+ping -108,4.0 OK at+rssi -104, -119, -65, -90 OK
Thanks
Andrew
Andrew Lindsay
ParticipantHi Brandon,
I’ll give this a try and report back.
thanks
Andrew
Andrew Lindsay
ParticipantI’m trying SF_12 now as I’m in the EU there isn’t the restriction of 11 bytes payload size, payload is currently about 16 bytes but hoping to get this down by re-coding it as a binary payload instead of minimal json.
btw, almost every time I look at this site, there is new information!
Thanks
Andrew
Andrew Lindsay
ParticipantThanks, got it now.
Andrew Lindsay
ParticipantWith my current setup I have been able to achieve 1200m range between the Conduit AEP mounted in the highest point in my roof space, antenna pointing vertically down (as the mounting holes indicate this way) and a mDot.
Both are using the supplied Multitech 3dBi antenna. Spreading factor was 9, bw 125KHz.This range was achieved through a large housing estate, trees etc so not line of sight. Other parts of the town I am only able to get about 500m but this may have been down to the mDot and antenna being inside a car. More testing is still being done.
Regards
Andrew
Andrew Lindsay
ParticipantHow, functionally, does the Public mode differ from the Non-Public mode? The page referred to doesnt make this clear. Even a quick google isnt helpful.
thanks
Andrew
Andrew Lindsay
ParticipantThanks Brandon, much appreciated.
Andrew
Andrew Lindsay
ParticipantWhen mDot firmware is referred to, is this just the AT command interpreter and not some low level code that the mDot needs in order to function?
Reason I’m asking is that i use the mbed environment to reprogram the mDot so this appears to effectively overwrite the mDot firmware here.Thanks
Andrew
Andrew Lindsay
ParticipantJust a quick note, Conduit now updated to 1.0.31.
Thanks
Andrew
Andrew Lindsay
ParticipantHi Mike,
thanks for the link to the doc. I cant really see whats changed from the existing version.
I’ve tried the ping function in the library, what exactly does it ‘ping’ as it is not seeing the MDOT_OK response but MDOT_TIMEOUT? I’m guessing its trying to ping the Conduit gateway? Is there anything to setup on the Conduit to respond to pings? I have the AEP version, if that makes a difference?
Thanks
Andrew
Andrew Lindsay
ParticipantBrandon,
Thanks, I’ll request an updated firmware. Not sure why I’m not able to set the spreading factor. Could be a code issue as it works on the very basic library example.
Regards
Andrew
-
AuthorPosts