[Jeff Hatch]

I see the “post-up route add”, but am not sure how that works, especially with the unspecified addresses for the net and netmask.

Jeff

[Jeff Hatch]

Thierry,

Is ppp running and is there a ppp interface instantiated? Second, can you ping 8.8.8.8 or 194.230.55.99? I don’t see a gateway specified in your configuration, so I can’t tell whether the device has any routes to get to the nameservers.

Jeff

[Jeff Hatch]

Are you trying to do this on an MTR?

Jeff

[Jeff Hatch]

Asier,

Could you open a support case at https://support.multitech.com and give a detailed description of what you’re trying to do. Please include what data you are sending, what frequency your are sending the data, how many nodes you have, and any other pertinent information about your application.

Thank You,

Jeff

[Jeff Hatch]

Asier,

Could you provide more precise steps to recreate this behavior?

Jeff

[Jeff Hatch]

I believe that TrustZone requires ARMv6 or greater. The OCG is an ARMv5 processor.

Jeff

[Jeff Hatch]

Paul,

At this time I do not believe that we have anything else with an API with the same SMS capabilities.

Sorry,

Jeff

[Jeff Hatch]

Paul,

There is an undocumented API call to send an SMS on the rCell Model MTR. There is some discussion of it in this thread:

http://www.multitech.net/developer/forums/search/?bbp_search=SMS+API

We will be trying to update the API documentation in the future. In summary, to send a text through the API you can make a CURL request to:

https://conduit_ip/api/command/sms_send

with Json data in the following format:

{“recipients”: “phone_number”, “message”:”message text”}

Jeff

[Jeff Hatch]

Samuel,

Are you using the same images to write to flash each time? Is this one out of every four times failure happening on the same device each time? This is a kernel panic and it appears to be happening on the reboot when it is trying to run the ROM boot code.

If I can get some time to look into this I might be able to give you more information. If this is causing serious issues for you, file a support portal case at:

https://support.multitech.com

Jeff

[Jeff Hatch]

Asier,

You should be able to do pretty much the same thing as what’s described in the following link:

https://debian-administration.org/article/28/Making_scripts_run_at_boot_time_with_Debian

You should be able to execute your nodejs app by executing “node ” in the init.d script you add. As for port 8080, by default the Conduit does not have anything I am aware of that listens on that port.

Jeff

[Jeff Hatch]

Radu,

Configuration nodes are special “non-visible” nodes that are used to share configuration information to multiple nodes: “Some nodes need to share configuration. For example, the MQTT In and MQTT Out nodes share the configuration of the MQTT broker, allowing them to pool the connection.”

See http://nodered.org/docs/creating-nodes/config-nodes for more information.

When you delete the “visible node” in the workspace, the corresponding configuration nodes do not get deleted. To delete any extra configuration nodes you need to go to the menus in the upper right and go to Sidebar->Configuration Nodes. Once you click on that and it displays the “config” tab, you should be able to see the configuration nodes in the flow. From there you can select and delete the configuration node (double click on the node in the config list, and a pop-up screen will give you the option to delete the node).

Jeff

[Jeff Hatch]

Thierry,

For DNS you should be able to add the dns nameservers:

# Wired interface
auto eth0
iface eth0 inet static
address 192.168.2.100
gateway 192.168.2.1
dns-nameservers 12.34.56.78 12.34.56.79
netmask 255.255.255.0

Jeff

[Jeff Hatch]

Thierry,

Sorry, I thought you were running an AEP model Conduit. To set up the DNS on the mLinux model, if you have a cellular radio and SIM card, you can set up ppp with the instructions at:

Start Cell Connection on Boot

If you don’t have a cellular radio and/or SIM card, you can update the /etc/network/interfaces file to configure the eth0 with an entry like:

# Wired interface
auto eth0
iface eth0 inet static
address 192.168.2.100
gateway 192.168.2.1
netmask 255.255.255.0

Jeff

[Jeff Hatch]

Thierry,

If you have a cellular radio and a SIM card installed, once cellular is enabled and ppp is up and running you should have DNS working. If you don’t have a cellular radio and/or SIM card, in the UI you can go to Setup->Network Interfaces, select the eth0 interface and set DNS and gateway settings.

Jeff

[Jeff Hatch]

Rick,

I am able to log in to the UI with a browser, so the API should be working through the HTTP port 80. Are you using Curl to make your requests? If so, you may have to use some options to keep track of the authentication token for you after the login request.

Jeff

[Jeff Hatch]

Felix,

I am not sure that nodejs 4.4.1 is “runnable” on the Conduit. The processor is pretty old. The last I was able to confirm, the latest nodejs the Conduit could run was 0.10.x due to the fact that it is missing some of the newer instructions from the ARM instruction set that the newer nodejs takes advantage of.

Jeff

[Jeff Hatch]

Felix,

The resolv.conf is probably getting rewritten on boot. You will need to restore the DNS settings with a script during initialization.

Jeff

[Jeff Hatch]

Asier,

You will need to follow steps very similar to what’s at:

Flashing mLinux Firmware

These instructions are for the mlinux Conduit, but with the kernel ‘.bin’ and the filesystem ‘.jffs2’ for AEP you can do the same thing. To get the correct files for the version of AEP firmware you want to run please open a portal case at https://support.multitech.com

Jeff

[Jeff Hatch]

Asier,

I am not sure that the noise will have anything to do with this problem. Does the console output just stop at the point you have shown in the debug interface output? The jffs2 notice is usually correctable in on it’s own, however, it appears to be the last thing that happened before the system “hung”. It might mean that there is actually some problem with the flash file system. The kernel is up and running so the system isn’t entirely messed up.

Open a portal case at:

https://support.multitech.com

You may have to re-flash this unit through u-boot (the boot loader). If that is the case, and that doesn’t work, then the people that handle the portal cases there will be able to help with both the re-flashing attempt and anything else.

Jeff

[Jeff Hatch]

Rick,

In the previous message, the URL got messed up and should be:

https://[conduit_ip]/api/command/sms_send

and the Json data:

{“recipients”: “phone_number”, “message”:”message text”}

Jeff

[Jeff Hatch]

Rick,

The part of the API that supports sending an SMS message is in the command controller object. The URL for that will be

https:///api/command/sms_send

The Json data (post fields) will be of the following format:

{“recipients”:”“, “message”:”“}

Hope that helps,

Jeff

[Jeff Hatch]

Terrence,

Open a portal case at https://support.multitech.com. There is much better assistance with this type of problem there.

Jeff

[Jeff Hatch]

Felix,

If you don’t have a SIM card installed, have you configured the default route on the Conduit? If not, you will need to configure it in the /etc/network/interfaces file. If you have a SIM card installed, have you gotten PPP up and running and connecting?

Jeff

[Jeff Hatch]

Please open a portal case at https://support.multitech.com/ and you will get the support you need to restore your mlinux on your Conduit.

Jeff

[Jeff Hatch]

Adrian,

You will probably have to specify a DNS server if you are going to use the Ethernet LAN interface for your traffic. Otherwise, the hostname in the URL, iot.eclipse.org, will not get resolved and it will fail.

Jeff

[Jeff Hatch]

Eduardo,

To start an app automatically on boot you can write an init.d script. There are several examples of these types of scripts that start various programs on boot in the /etc/init.d directory. Once you have created your script to start/stop/restart your Node.js App, you can create a soft link in the /etc/rc*.d directory/directories to your start script. Usually the typical run level is run level 5, so you would want to add your soft link to the /etc/rc5.d directory.

Jeff

[Jeff Hatch]

Michael,

Once you successfully logged in and got the “admin@mtcdt:~#” you are at the debug console prompt. The debug console logs everything coming out from the boot, and it also logs the output of the “call home” functionality that you are seeing doing the DHCP requests. In future versions we may prevent it from logging to the console.

When you are logged in can you do a “ifconfig -a” and a “route -n” to show what address is on your Ethernet interface and to display what routing is available on the device? From that we can tell whether or not the device needs to be directly connected to or not.

Jeff

[Jeff Hatch]

Michael,

If you hit enter when in the debug console does it give you a login or password prompt. You should be able to login at the debug console and get command line access. Your device has been defaulted back to factory settings. The “Sending discover…” output is the DHCP client trying to get an address. When it fails it reverts the address on the Ethernet interface back to 192.168.2.1. You should be able to connect to your Conduit by directly connecting it to a PC on 192.168.2.1 via SSH or the Web UI.

If you cannot connect over either the Web UI or SSH, but can login to the debug console, we can help you debug what is going on.

Jeff

[Jeff Hatch]

Michael,

On the quick press, the status LED will keep blinking normally for a little bit while the unit resets. Once it resets and starts rebooting the status light will stay solid while the device boots. At a certain point as the device boots up the status LED will start blinking again.

When you attempt to reset the device with a quick press, if you have connected to the debug console with a USB cable, you should be able to tell if the device is rebooting in the console.

The same for the 5 second press.

When you held the button for at least 10 seconds, and it rebooted, was the configuration reset to defaults. It is expected that pressing for longer than 5 seconds will cause the device to reboot and reset it’s configuration to factory defaults.

That is basically it.

Jeff

[Jeff Hatch]

Rafael,

The battery will not power the device, it will preserve the clock setting so that you do not have to reset the date and time every time you power the device on.

Jeff

[Author]

Posts