This was suprisingly non-obvious. Key clues:
- https://www.devopsrun.com/t-ubuntu-18-04-xrdp-authentication-is-required-to-create-a-color-managed-device
- http://c-nergy.be/blog/?p=13390
# initial setup
sudo apt update
This was suprisingly non-obvious. Key clues:
# initial setup
sudo apt update
IPFire supports net-to-net connections.
Part of setting up the connection with non-IPFire peers often involves generating a .ovpn file from the client package.
There are some client docs about how to do this, but not net-to-net.
For net-to-net clients, IPFire generates a zip file containing two files. Both files are named based on the name you choose for the VPN.
I recently installed PSpice for TI (version 17.4-2020 S002 Windows SPB 64-bit edition
).
After installing, Git for Windows bash no longer worked as expected. Instead of starting up in my home directory, it started up in the (emulated) root directory; and it didn't load my profile. (In other words, installing PSpice for TI broke my Git for Windows installation.)
Investigation revealed that the installation had created an environment variable HOME
in my profile, with the value c:\mcci\projects\SBP_Data
. It was easy enough to fix this.
System
{ | |
"version": "3.14.0", | |
"description": "Open-source, cross-platform family of tools designed to build, test and package software", | |
"homepage": "https://cmake.org/", | |
"license": "BSD-3-Clause", | |
"architecture": { | |
"64bit": { | |
"url": "https://github.com/Kitware/CMake/releases/download/v3.14.0/cmake-3.14.0-win64-x64.zip", | |
"hash": "40e8140d68120378262322bbc8c261db8d184d7838423b2e5bf688a6209d3807", | |
"extract_dir": "cmake-3.14.0-win64-x64" |
{ | |
"version": "3.14.7", | |
"description": "Open-source, cross-platform family of tools designed to build, test and package software", | |
"homepage": "https://cmake.org/", | |
"license": "BSD-3-Clause", | |
"architecture": { | |
"64bit": { | |
"url": "https://github.com/Kitware/CMake/releases/download/v3.14.7/cmake-3.14.7-win64-x64.zip", | |
"hash": "e3ce0bdd966dc9a8e9c57ea949bc195c36c6f843bd3e431990d59c381be7ba8e", | |
"extract_dir": "cmake-3.14.7-win64-x64" |
I needed the list of supported languages for highlightjs, used by Markdown code fences (```).
There is a list at https://highlightjs.org/usage/, but was not readable. But it looked like markdown, so I grabbed it and made a markdown table.
Language | Classes | Package |
---|---|---|
1C | 1c | |
ABNF | abnf | |
Access logs | accesslog | |
Ada | ada |
// Updated 2017-04-20 23:08 EDT tmm@mcci.com -- fix typos in comments | |
// Add this in your application's "payload formats" section of | |
// https://console.thethingsnetwork.org | |
function Decoder(bytes, port) { | |
// Decode an uplink message from a buffer | |
// (array) of bytes to an object of fields. | |
var decoded = {}; | |
if (port === 1) { | |
cmd = bytes[0]; |
// this Node-RED decoding function decodes the record sent by the Catena 4450 M101 power monitor | |
// written in a big hurry, so no points for style | |
var b = msg.payload; // pick up data for convenience; just saves typing. | |
// an empty table to which we'll add result fields: | |
// | |
// result.vBat: the battery voltage (if present) | |
// result.vBus: the USB charger voltage (if provided) | |
// result.boot: the system boot counter, modulo 256 |
There is no example for using a UART in conjunction with RTXv5 as of this writing. This gist presents an adapted example that was tested in conjunction with Keil V5, RTX APIv2 and the Blinky example.
Create the RTX_Blinky project in a spare directory using the "Pack Installer" button.
MCCI needs OpenSSL for a Windows project (that will be cross-platform). A casual search didn't turn up either a good source for cross-platform libraries, which meant we have to build them ourselves. A deeper search found a detailed guide here, and yet the details don't match what I found when I checked out the code; and the post doesn't talk about doing it directly from GitHub (which I wanted to do).
Here's the procedure for building OpenSSL on 64-bit Windows 10, with Visual Studio 2015. Others (July 2019) report that this procedure works with Visual Studio 2017 as well. I've not had a chance to try with Visual Studio 2019.
As this procedure dates from late 2016, you may find that there's a CMake or other, newer, procedure that's more suitable.