Reply To: GNSS module fix
Yes, thats exactly my point. I think, “tmst” can be taken as some sort of reference as explained below:- Conduit #1 x = time_2nd packet – time_ist packet y = tmst_2nd packet – tmst_1st packet...
View ArticleReply To: How to retrieve AEP firmware version using SSH ?
Hello Yoshihiro Once you SSH into the Conduit, at the command prompt try the ‘version’ command. Example: admin@mtcdt:~#version
View ArticleReply To: DNS Settings (mlunix)
Hello guys! I’m new here. Someone solved this problem? I have same problem with conduit mlinux, I can’t access the internet. Help me, please! Thanks!
View ArticleReply To: How to retrieve AEP firmware version using SSH ?
Hello Steve. I’ve confirmed to be able to retrieve AEP firmware version using ‘version’ command. Thank you so much for your quick response ! Best Regards,
View ArticleReply To: How to change the rx2Frecuency
Thank you, Jason. I’m working with class A, and the idea is that the end devices are programmed with the Rx2frecuency depending on the conduit they connect to, with which I understand that this...
View ArticleReply To: How to change the rx2Frecuency
Hello Jason again. the commands work very well, but now I do not know how to restart the lora-network-server without restarting the conduit for the changes to take effect. If I modify the parameters...
View ArticleMosquitto disconnected
Many times when the parameters of the lora-network-server are saved, it does not restart, which stops the data from reaching the node-RED application. This also happens when at other times, but I do...
View ArticleUnable to get wlan0 to show in MultiConnect Conduit – AEP – v1.4.4
Hi Everyone! We have a couple of MultiConnect® Conduit (MTCDTIP-LEU1-267A) and I’m trying to debug an issue where we loose connection randomly and need to restart the devices. We are using LTE for...
View ArticleReply To: call home update configuration
Julien, Do you have access to the logs on any of the Conduits? There may be more information in the Conduit logs as to what is failing. Jeff
View ArticleReply To: Unable to get wlan0 to show in MultiConnect Conduit – AEP – v1.4.4
Patrik, On the Conduit, could you list the contents of /opt/rs9113? That is where those modules should be (initially). If they are in that directory, then something is going wrong with the rs9113...
View ArticleReply To: Unable to get wlan0 to show in MultiConnect Conduit – AEP – v1.4.4
Jeff, In /opt there are only the following folders; lora node-red serial-streamer If I do a lsmod I get; admin@mtcdt:/opt# lsmod Module Size Used by nf_nat_ftp 1468 0 nf_conntrack_ftp 5583 1...
View ArticleReply To: Unable to get wlan0 to show in MultiConnect Conduit – AEP – v1.4.4
Patrik, Was this Conduit upgraded from mLinux? What is the output of the following command: get-eeprom-device-info or get-eeprom-device-config Jeff
View ArticleReply To: Unable to get wlan0 to show in MultiConnect Conduit – AEP – v1.4.4
Jeff, Not that we are aware of, here’s the output; [INFO] eeprom_main.c:mts_id_eeprom_inspect:291: sizeof: 512 [INFO] eeprom_main.c:mts_id_eeprom_inspect:292: vendor-id: Multi-Tech Systems [INFO]...
View ArticleReply To: Unable to get wlan0 to show in MultiConnect Conduit – AEP – v1.4.4
Patrik, I have figured out the problem. It is in a script /etc/init.d/remove-rs9113. It is removing the rs9113 driver because the hardware ID is not “MTCDT-0.1″. The intent of the script is to make...
View ArticleReply To: Unable to get wlan0 to show in MultiConnect Conduit – AEP – v1.4.4
Patrik, We can provide you with a package to install to put the rs9113 driver back on your device. There will be a couple of other steps to follow we will give you through the support portal. Jeff
View ArticleReply To: Unable to get wlan0 to show in MultiConnect Conduit – AEP – v1.4.4
Thank you for the help Jeff! I’m adding a ticket thru the support portal. I also suspect that the drivers for the GPS is missing in the same way. Patrik
View ArticleReply To: DNS Settings (mlunix)
Hello guys! I solved this problem just add the line: post-up echo “nameserver 8.8.8.8″ > /etc/resolv.conf The results are: PING http://www.google.com (216.58.202.4) 56(84) bytes of data. 64 bytes...
View ArticleReply To: Unable to get wlan0 to show in MultiConnect Conduit – AEP – v1.4.4
Patrik, There were a number of bugs in the gps related code that have been fixed since AEP 1.4.4 that is on the IP67 you have. The driver level gps functionality works. It is at the application level...
View ArticleReply To: Unable to get wlan0 to show in MultiConnect Conduit – AEP – v1.4.4
Jeff, Ok, we’ll se what they can do, the reason I’m thinking that there also might be some missing drivers for GPS is the following from the boot.log; Tue Mar 13 14:12:50 2018: udevd[422]: failed to...
View ArticleReply To: Unable to get wlan0 to show in MultiConnect Conduit – AEP – v1.4.4
Patrik, That has more to do with the fact that gpsd is not running, and even if it was, I am not sure that the rule that is causing that is valid anymore. I’ve seen that on devices that are...
View Article