Brandon Bayer
Forum Replies Created
-
AuthorPosts
-
Brandon Bayer
BlockedBut you will need to get the rootfs and bin files for AEP through the portal.
-Brandon
Brandon Bayer
BlockedPaul,
Instructions and the script for flashing from uboot are here:
-Brandon
Brandon Bayer
BlockedHey there,
Have you tried following these instructions? http://www.multitech.net/developer/software/mlinux/using-mlinux/mlinux-cellular-connection/
If so, check
/var/log/messages
for pppd logging after you start pppd.-Brandon
Brandon Bayer
BlockedJeff,
You can put the text body in a file and use the
-f
option~# sms send usage: send [ OPTIONS ... ] < number > where OPTIONS := { --alphabet { seven-bit | eight-bit } | -f, --file < input-file > | --smsc-addr < smsc-addr > | --cmgw-first }
-
This reply was modified 8 years, 4 months ago by
Brandon Bayer.
-
This reply was modified 8 years, 4 months ago by
Brandon Bayer.
-
This reply was modified 8 years, 4 months ago by
Brandon Bayer.
-
This reply was modified 8 years, 4 months ago by
Brandon Bayer.
Brandon Bayer
BlockedHello,
A mini SIM card is not needed unless you want a cellular internet connection. You can get one through AT&T or T-Mobile, etc.
-Brandon
Brandon Bayer
BlockedAndreas,
Sorry about this! There’s a bug in 1.3.2 that disables Node-RED on upgrade.
To renable it, check the Node-RED Enabled box on the Apps page in the UI.
-Brandon
Brandon Bayer
BlockedYeah, mLinux doesn’t currently build with a 4.x kernal 🙁
-Brandon
Brandon Bayer
BlockedAjay,
I’m not aware of any way to do this. The only way to make sure your data is saved it to save your data periodically or on each update.
-Brandon
August 18, 2016 at 10:09 am in reply to: What is the difference between a mLinux Conduit HW and a NodeRED Conduit HW? #14565Brandon Bayer
BlockedHoon,
Nope, the only differences are:
1. Part number
2. Firmware loaded at factory
3. Front panel decalYes, if you load mLinux firmware on an AEP Conduit, the leds will behave as programmed in the mLinux firmware (or as customized by you)
-Brandon
Brandon Bayer
BlockedTibor,
You should be able to get the login prompt via the USB debug port by hitting the
key. -Brandon
Brandon Bayer
BlockedHey Chris,
Yes, on the AEP model, most config files are generated from the API. You can easily increase lora logging level on AEP from the UI on the bottom of the Lora configuration page.
-Brandon
Brandon Bayer
BlockedMariusz,
Thank you for that. I think you are correct that it’s a typo, but for our verification purposes, can you post specific steps and environments required to reproduce this? This is the first time anyone has discovered this as far as we know. I’m currently unable to reproduce it.
-Brandon
Brandon Bayer
BlockedFrederic,
I studied the debug output for awhile and did some digging in the tinc code. I’m not sure what the problem is besides that it’s a problem finding the openssl library. My best guess at this point is maybe that version of tinc and openssl are not compatible together..?
-Brandon
Brandon Bayer
BlockedFrederic,
Hmm, I’m not sure. Did you try switching the order of
openssl
andlzo
in the tinc DEPENDS?Can you post all of the bitbake output surrounding this failure?
-Brandon
Brandon Bayer
BlockedFrederic,
It sounds like you may need to add openssl to the DEPENDS Bitbake variable. Each Bitbake has to specify all of it’s dependencies.
-Brandon
July 22, 2016 at 11:18 am in reply to: issue require nodejs module in functionGlobalContext doesn't work #14284Brandon Bayer
BlockedAjay,
I’m not sure which feature requests you were wondering about, but you can see all the changes in the AEP Changelog.
As for NPM modules, yes, they will be lost on firmware upgrade unless you install them under
/var/config/
-Brandon
Brandon Bayer
BlockedHey Jerome,
Unfortunately this is expected behavior. The Conduit doesn’t have any compilers or build tools because it simply doesn’t have the needed performance.
The only way to install these type of packages is to cross-compile them on a standard Linux PC using the mLinux SDK and then install them on the Conduit. But be aware that any installed packages not in /var/config/ will be lost on a firmware upgrade.
-Brandon
-
This reply was modified 8 years, 8 months ago by
Brandon Bayer.
Brandon Bayer
BlockedAntonio,
You also need to have a public IP address from your PPP provider. If you can’t
ping
the Conduit’s PPP IP address from your computer command line, then it almost certainly has a private IP address which is hidden behind your cellular provider’s firewall. Generally it costs more to have a public IP address for your SIM.-Brandon
Brandon Bayer
BlockedAre you sure the network server is running? (
ps aux | grep lora
) Are there any lora log files in/var/log/
? If so, what are the contents?-Brandon
May 20, 2016 at 11:41 am in reply to: How to send SMS via MTR-H5 from a 3rd party application #12627Brandon Bayer
BlockedRick, what firmware version do you have? We fixed some things related to http & login in the latest release (3.4.2).
-Brandon
Brandon Bayer
BlockedmLinux model defaults:
root/root
AEP model defaults:
admin/admin
Brandon Bayer
BlockedBrandon Bayer
BlockedSeungkyu,
What download link are you referring to? You should be able to download mLinux images from here: http://www.multitech.net/developer/downloads/
-Brandon
Brandon Bayer
BlockedDone 🙂
Brandon Bayer
BlockedBryan,
In his post, he noted he’s using a MTR-H6-B16.
-Brandon
Brandon Bayer
BlockedBorut,
No, there’s not an option for that. And yes, you are correct, the API doc really needs updating!
-Brandon
Brandon Bayer
BlockedQuentin,
Ok, I’m glad you got that to work! mLinux doesn’t have the web GUI or Node-RED. If want AEP again, you’ll need to open a support case and ask for the AEP upgrade files. Then follow the mLinux flashing instructions (auto-flash, not U-boot) using the AEP files.
-Brandon
Brandon Bayer
BlockedQuentin,
Did you set the env variables before flashing (issuing
run krb
)?You’ll need to start over and carefully go through the U-Boot flashing instructions again. You shouldn’t need to modify the script before running it in Minicom. In any case, the quotes (
'
) around the commands are critical (you removed them).-Brandon
Brandon Bayer
BlockedQuentin,
Oh yes. So you’ll need to follow the U-Boot firmware flashing instructions on the following page:
Before you put add this to the boot init script again, test it from the command line and make sure the process is backgrounded (you get back to the command prompt without having to hit Ctrl-C)
/etc/init.d/myapp start
-Brandon
-
This reply was modified 9 years ago by
Brandon Bayer.
-
This reply was modified 9 years ago by
Brandon Bayer.
Brandon Bayer
BlockedQuentin,
That’s probably because your node process isn’t being backgrounded. You could add ‘&’ right before ‘>>’, or you can use start-stop-daemon as in the below example:
#!/bin/sh PATH=/sbin:/bin:/usr/sbin:/usr/bin DAEMON=/sbin/radio-monitor NAME=radio-monitor ANGEL=/sbin/radio-angel DESC="Radio Monitor" PIDFILE=/var/run/radio-monitor.pid start() { start-stop-daemon --start --background --make-pid -p $PIDFILE --exec $ANGEL -- $DAEMON } stop() { start-stop-daemon --stop --exec $ANGEL -p $PIDFILE rm $PIDFILE } case "$1" in start) echo -n "Starting $DESC: " start echo "$NAME." ;; stop) echo -n "Stopping $DESC: " stop echo "$NAME." ;; restart|force-reload) echo -n "Restarting $DESC: " stop sleep 1 start echo "$NAME." ;; *) N=/etc/init.d/$NAME echo "Usage: $N {start|stop|restart|force-reload}" >&2 exit 1 ;; esac exit 0
-Brandon
-
This reply was modified 9 years ago by
Brandon Bayer.
-
This reply was modified 8 years, 4 months ago by
-
AuthorPosts