[Mark Linneman]

That’s what I figured, but I thought I’d better ask since the “info” pages for these nodes surprisingly don’t mention any of this. Thanks, Jason.

[Mark Linneman]

Thanks. That’s good news. And now that you explained that, I retried the base64 encoding options on the UDP nodes and found that they work correctly. I could have sworn that I tried that before, and it stopped encoding at the first zero.

Just one thing is unclear, though. The examples in the Node-RED “info” for the LoRa In and Out nodes clearly show regular text strings as the msg.payload, not base-64 encoded strings. Like this one for the LoRa Output node:

“msg”: {
“payload”: “Greetings from Conduit!”,
“eui”: “00:11:22:33:44:55:66:88”,
“ack”: false,
“port”: 1
}

What causes the LoRa Input node to express the msg.payload in base-64 encoding in? Does it only do that when you choose the “bytes” payload option?

Likewise, for the LoRa Output node, how do you indicate to the node that you are giving it “binary” data versus “text”? Thanks for the clarification.

[Mark Linneman]

Jeff,

That’s great. There are discussions in the forum about making this upgrade to AEP 1.6.2 but was never clear on whether that eliminated the possibility of using Node Red.

I see that AEP 1.6.2 is pretty new. I’ll take a look at the discussions about any issues with the new firmware. Thanks.

– Mark

[Mark Linneman]

Jeff,

I’m not looking for any specific version of mLinux, but I’ve read that it’s suggested to use Ubuntu 14.04 with mLinux 3, but and Ubuntu 16.04 may be used with mLinux 4. So it seems like a good idea to try to use the most recent version of mLinux that is known to work well with the Conduit and with Node Red in order to not have to use too old a version of Ubuntu for developing C/C++ applications with.

Is there an upgrade of Node Red that is required to go to AEP-1.6.2 and mLinux 4? Thanks.

– Mark

[Mark Linneman]

Jeff,

Thanks for clarifying that. I’m now cross-compiling C programs under Ubuntu 14.04 and executing them on the Conduit Application Execution Platform. These mLinux applications are in turn being called by Node Red “exec” nodes. Since at this point I’m planning to stick with Node Red on the AEP, I need to know what my options are in terms of upgrading to a newer version of mLinux. My Conduit came with firmware v. 1.4.16 and mLinux version 3.3.22 and Node Red version 0.15.3. Does the use of Node Red limit my upgrading of mLinux? Thanks.

– Mark

[Mark Linneman]

Jeff,

I just posted a related question on another topic, but having now read this thread I gather that the same mLinux operating system is running on my Node-Red AEP product as runs in the other product, sometimes referred to as the “mLinux” product. If that’s correct, then I should be able to go to the “mLinux” application development documentation to learn more about how to develop applications for my AEP unit, keeping in mind that I am using Node-Red. (My Linux version is 3.12.27r15.)

Am I on the right track now? Thanks.

– Mark

[Mark Linneman]

Jeff,

I’m very interested in what you said about the capability of generating C/C++ applications that can be run on the AEP version of the Conduit. You said “Support on AEP for C/C++, Python, bash, node-js is correct. C/C++ applications have to be cross-compiled for the Conduit architecture.”

I am using Node-Red on our Conduit gateway, and I need to execute custom applications through the “EXEC” node. And I would like to write these applications in C/C++. These applications would have to, at the very least, have access to the CTMDT Linux file system for its input and output. (That will probably be quite sufficient. Normally I’d want to write sockets client/server TCP/IP or UDP/IP communications, but I’ll probably settle for letting Node-Red handle that.) I have MultiConnect Conduit firmware version 1.4.16 for my AEP unit, so the version 1.3 and above requirement is met.

So my question is what exactly do you mean when you say cross-compiled “for the Conduit architecture”? I assume I can use a GCC or G++ compiler. But don’t I need a “Conduit-specific” run-time library to link my code with? You’ll have to pardon me – I’ve been writing C/C++ code for decades, but not in the Linux environment. I suppose if all I really need for my I/O is access to the file system, this may be very simple. But at this point I need some things spelled out for me which ought to seem pretty rudimentary, do to my inexperience with Linux and the Multitech product. Thanks very much for your help.

– Mark

[Author]

Posts