Reply To: Cellular connection / modem detection.
Problem solved.. sim-adapter was poor… thanks.
View ArticleReply To: Multitech Conduit AEP and time
When the packet forwarder source was updated to include basic, gps and beacon functionalities into one binary, time was changed to only be included when a gps signal is available. This new packet...
View ArticleReply To: Multitech Conduit AEP and time
So if I’m understanding this well. The basic does not exist anymore? If there is no GPS the time isn’t added? Thanks for the answer
View ArticleReply To: Multitech Conduit AEP and time
That is correct, with the packet forwarder used for SPI cards, time is only included when a gps signal is available.
View ArticleReply To: Multitech Conduit AEP and time
But the Multitech conduit AP does not have GPS, how do I get time from them?
View ArticleReply To: Multitech Conduit AEP and time
The packet forwarder could be patched to add the time field. Or a process could be in-lined to modify the UDP packets to add a time stamp. Or the network server could fill in the missing time field....
View ArticleReply To: Multitech Conduit AEP and time
We are using open source LoRa-Server by Brocaar – https://www.loraserver.io/ I have to speak with him and see if he can add that in his server. Could a gpsfake do the trick? I have to try the...
View ArticleReply To: Multitech Conduit AEP and time
Does not look like fakegps would work. The packet forwarder looks for an updated time from the gps device. ref_ok can only be true if gps_enabled is true line 1518 /* get a copy of GPS time reference...
View ArticleReply To: Multitech Conduit AEP and time
I have been checking the code and that line seems to be there for a long time It has been always there, only with gps the variable “time” appears. But then how are my older conduits doing it? Or even...
View ArticleReply To: Multitech Conduit AEP and time
If the “older” conduits have USB lora cards then basic_pkt_fwd is used. Release v1.4.1 of packet_forwarder on lora-net
View ArticleReply To: Multitech Conduit AEP and time
And that packet forwarder is based on this? https://github.com/Lora-net/packet_forwarder
View ArticleReply To: Multitech Conduit AEP and time
Here is a link to the v1.4.1 release source https://github.com/Lora-net/packet_forwarder/tree/0011a60759a7d81656a5393e97089daab1ff1a81
View ArticleReply To: Multitech Conduit AEP and time
Ok. Many thanks for everything. Will try to convince Brocaar to add time in his server.
View ArticleReply To: Multitech Conduit AEP and time
So we made the modification in the pkt_fwd. We have it running in an Outdoor conduit (SPI version) and seems to be running correctly and doing what is expected. Now the problem, with the indoor...
View ArticleReply To: Multitech Conduit AEP and time
Here is a link to our recipes and patches for the packet forwarder and gateway. http://git.multitech.net/cgi-bin/cgit.cgi/meta-mlinux.git/tree/recipes-connectivity/lora
View ArticleReply To: Multitech Conduit AEP and time
Just tried, does not work. I found a way to reset the LoRa SX1301 and did nothing. It seems to be somewhere else the problem. The connection to the SPI are equal in both conduits? (outdoors and...
View ArticleReply To: Multitech Conduit AEP and time
The one with the card works fine with my modified forwarder, detects SPI and pass the tests. The problem is with the one that has no card: https://www.multitech.com/brands/multiconnect-conduit-ap This...
View ArticleReply To: Multitech Conduit AEP and time
Actually here are the latest. http://git.multitech.net/cgi-bin/cgit.cgi/meta-mlinux.git/tree/recipes-connectivity/lora?h=3 There is patch to add FPGA version 28, 31, and 33 that is different. #...
View ArticleReply To: Multitech Conduit AEP and time
This is my return : #mts-fpga-loader -c Checking hardware compatibility This software is licensed only for supported MultiTech products. Version Check failed. Error Code: 3 The other commands return 1...
View Article
