Anybody know anything about this?
Generally a nice concept, but the knobs & faders don’t have a scale or LED markers.
I would rather aim for something from them:
…they also provide a wider variety of control elements (diffrent fader sizes, knob types, joysticks).
What i always miss in those controllers are motorized faders or maybe a pitch/modwheel combination… but i guess we’ll never see the perfect solution that fits everyone’s needs.
I had a play with them at SB22, feelt good, I liked the “eco-system”.
Any updates, experiences here?
I just stumbled upon a kickstarter campaign for that (although it looks a bit difrent now):
https://www.kickstarter.com/projects/intechstudio/vsn1-the-visionary-controlling-tool
After all i think it’s too pricy for what it does.
Funny, this came up this morning as well on my side 
Regarding the pricing: this is no mass product, yet. The existing modules are listed on Thomann around 130 - 170 EUR which sounds fair.
Of course you can get a nanoKontrol etc. for less.
More interesting is how good and flexibe the MIDI or OSC implementation would behave in a GP setup.
I just came across this video for the next gen GRID MIDI controller. Way more flexible and powerful than I expected.
Have a look here 
If you want to do (more or less) deep customization you need to take some time - but the possibilities are really great!
BTW: I also did a remote control for my Behringer Wing Rack (SD Recording, Recording Light control) and a dedicated remote for my personal Global Rackspace. I used the page buttons on the Grid for this to switch (and sync!) context on one VSN1L.
I’m currently waiting for one more VSN1 ordered last week
Thanks for the link. I’ll need to spend some time with it. 
@themaartian
I just unpacked my 2nd VSN1 and had to downgrade the firmware to match my existing code (at least for the moment)
The examples provided are running in Grid 1.6.2 / Firmware 1.5.0!
The new module came with 1.5.1 which uses Grid 1.6.5 …
This is a little bit of PiTa - had the same situation last year when updating Grid from a 1.5.x version and had to rework my code 
Oh, Lord. That unexpectedly took me back to the '80s when I was doing hardware and software design for solar-powered Master and Remote Telemetry Units (MTUs and RTUs) for Amoco Oil Company. I was using the NSC-800 (basically a CMOS Z-80). PCs didn’t really exist yet, so I was doing development with a cross assembler on one VAX 780 and two 750s. The comm. protocol was an old (from the late '50s) hardware-based one that used a byte of FF with a legal (!) parity error to flag the final byte as the checksum. Worked great, except that I was forced to use VMS device drivers instead of terminal drivers for development and testing (terminal drivers would abort to the OS on a parity error). The problem was that device drivers were OS-version specific, so I’d come in on Monday morning and find out the DEC software support in Colorado Springs had updated the OS on my 3 VAXs and cratered my device drivers. I spent a lot of Mondays recoding and testing device drivers instead of doing actual product development. As soon as native 8080/Z-80 development systems became available, I wrote my own APIs and stopped using the VAXs.
I sympathize with your PITA completely. 
And while checking the grid forum and discord channel, there came out just another new version of Grid Editor/FW combination (1.6.7 / 1.5.3)
Sometimes it feels like updates come out faster than I can switch my underwear 
Personal hygiene is overrated.
