Node-RED flow for controlling a Blink(1) USB indicator light
Node-RED is a truly awesome framework for visually building data flows. There is a lot of focus on wiring together hardware devices and Internet of Things, but there are also plenty of modules for connecting to email, social media, various online services etc.
After using it during some months I can confirm that stability is absolutely fine, don’t think I have had a single issue with the setup due to Node-RED itself.
Version 0.10.1 came out a week or so ago (early Feb 2015) and brought things like better partitioning of flows in the form of subflows, improved Raspberry Pi support, binary MQTT payloads to name just a few of the improvements.
I am running Node-RED on an always-on Mac, running latest OS X. This machine is very stable but for various reasons I do need to restart it every now and then. It would then be very nice to have Node-RED start automatically at boot. That’s somewhat complex to do, but having an app starting at login is trivial – let’s do that instead. I am always logged into this computer anyway, so it won’t be a problem.
Let’s try an experiment.
I have set up a questionnaire that anyone can fill in and submit.
There you can add working and non-working memory configurations for your Synology NAS. Ideally this will enable people to increase the memory in their NAS:es without lots of trial and error on what memory works in what NAS models – or spammers will fill the document with crap data… Time will tell.
Background is that I started a similar effort here on the blog, but Google Forms are way better for this, so let’s use that instead.
Let’s go – don’t be shy!
Update: Let’s work together and capture data on what memory modules work, and which don’t, on the DS1515+ and other Synology NAS models!
As noted in a previous post, a new Synology DS1515+ NAS landed here the other week. It’s a very nice products in most respects, but a couple of rather annoying details bring the overall impression down – more on that in a later post.
The DS1515+ ships with 2 GB of RAM, with an extra, empty memory slot available for memory upgrades. 2 GB is really on the low side if you intend to run additional applications on the NAS. CrashPlan for example is built on Java, which is pretty resource hungry to begin with, then the memory consumption goes up with the number of files backed up.
Synology specs tells us that a 4 GB SO-DIMM can be added, for a total of 6 GB. Stories from the Synology forum however indicate that it is quite possible to replace both the internal (some disassembly required, probably voiding warranty..) and user accessible RAM modules, for a total of 16 GB RAM.
With a bunch of different SO-DIMM modules in the drawers here, let’s test them to see which ones can be used with the DS1515+ and which ones cannot.
A great feature of Qlik Sense is that your ETL/load script scripts can be moved over from existing QlikView apps with very few modifications. Basically, you need to change the data sources to Sense’s way of doing things* (which I would say is a lot more robust and flexible), then things are likely to work straight off the bat.
Qlik Sense is very nice in most ways, the development environment however still falls short when compared to the one found in QlikView. Having a proper Windows client (which QlikView has) just gives more flexibility than using a web based editor and development environment.
Don’t get me wrong – Sense gets the job done – just that for people whose muscle memory is tuned to the QlikView development environment, Sense feels somewhat limiting and slow. That said, after spending a fair bit of time both porting existing QlikView apps to Sense, as well as developing new Sense apps from scratch, the development environment becomes less and less of an issue. I’d say that Qlik still has way to go though. But hey – we are looking at version 1 – I am sure there are plenty of good things to come in future versions.
Anyway – if you spend significant parts of your days in an application, you want to be as effective as possible in your work. QlikView has quite a few powerful keyboard shortcuts, Qlik Sense has somewhat fewer, but still useful. These are listed in this online Qlik Sense help page.
Seems that the help page is not complete though – some shortcuts are not listed there.
Let’s compile a list of them here, please feel free to add additional ones in the comments!
|Ctrl-K||Comment (using //) the lines currently selected in the code editor.
Update: Turns out it is the “Update for Windows Server 2012 (KB3013767)” that when installed on the server in question prevents the QlikView Directory Service to start. Installing the other two updates mentioned below (KB3004365 and KB3029449) does not affect QV operation.
While doing regular maintenance of a QlikView server (running 11.20 SR8) recently (as part of my daytime job), the latest Windows service packs were installed, as usual. This is normally just routine procedure, but not this time.
QlikView Directory Service fails to start
After installation was done and the server restarted, it was impossible to log into the QlikView Access Point (i.e. the system’s web UI). The reason was that QlikView’s Directory Service, QDS, failed to start. Even manual attempts at starting it gave the error shown to the right. The error dialog mentions dependencies that fail to start, but this particular service does not have any dependencies listed in its properties dialog. Strange…