<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>MEVISYS on Mevisys</title>
		<link>https://mevisys.net/</link>
		<description>Recent content in MEVISYS on Mevisys</description>
		<generator>Hugo</generator>
		<language>en</language>
		
		
		
		
			<lastBuildDate>Thu, 08 Oct 2026 15:33:00 +0000</lastBuildDate>
		
			<atom:link href="https://mevisys.net/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Aplication 1</title>
				<link>https://mevisys.net/projects/application1/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>https://mevisys.net/projects/application1/</guid>
				<description>První aplikace</description>
			</item>
			<item>
				<title>MeSca</title>
				<link>https://mevisys.net/projects/mesca/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>https://mevisys.net/projects/mesca/</guid>
				<description>MEVISYS SCADA Configurator.</description>
			</item>
			<item>
				<title>Backend - Rust</title>
				<link>https://mevisys.net/posts/backend-rust/</link>
				<pubDate>Thu, 08 Oct 2026 15:33:00 +0000</pubDate>
				<guid>https://mevisys.net/posts/backend-rust/</guid>
				<description>&lt;p&gt;When building the site with a full-stack framework like Nuxt, I realized that developing with JavaScript or TypeScript just wasn&amp;rsquo;t the right fit for me. Consequently, I started looking for a solution that would give me greater confidence.&lt;/p&gt;&#xA;&lt;p&gt;Backend solutions can be divided into those built on scripting (interpreted) languages and those that leverage traditional compiled languages.&lt;/p&gt;&#xA;&lt;p&gt;Python is another interpreted language on this list. It’s part of my regular toolkit, and I actually used it within the MEVISYS platform to build the MeSca project (you can check it out under the Projects tab). While Python could certainly do the job, it inherently shares a very similar set of characteristics with JavaScript and TypeScript. Because of this, Python is out of the question for building a high-speed, reliable application.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Frontend</title>
				<link>https://mevisys.net/posts/frontend/</link>
				<pubDate>Mon, 05 Oct 2026 12:49:00 +0000</pubDate>
				<guid>https://mevisys.net/posts/frontend/</guid>
				<description>&lt;p&gt;Currently, the most widely adopted frontend solutions are:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;React&lt;/li&gt;&#xA;&lt;li&gt;Angular&lt;/li&gt;&#xA;&lt;li&gt;Vue&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;React is by far the most widely adopted solution. It debuted back in 2013, with Meta (Facebook and others) serving as its primary developer. It is a complex ecosystem, and mastering it comes with a fairly steep learning curve.&lt;/p&gt;&#xA;&lt;p&gt;Angular debuted in 2016 and is the most complex and difficult framework to learn among those listed. Developed primarily by Google, it is the most robust option available and is typically reserved for the most demanding enterprise applications.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Full-stack</title>
				<link>https://mevisys.net/posts/full-stack/</link>
				<pubDate>Sun, 04 Oct 2026 11:23:00 +0000</pubDate>
				<guid>https://mevisys.net/posts/full-stack/</guid>
				<description>&lt;p&gt;Our initial thought was to build the entire web solution — both frontend and backend — using a single full-stack framework. It’s an enticing idea, especially considering the size of the team behind the project.&lt;/p&gt;&#xA;&lt;p&gt;Our research into current technologies revealed that the most widely used solutions today are:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Next.js&lt;/li&gt;&#xA;&lt;li&gt;Astro&lt;/li&gt;&#xA;&lt;li&gt;Nuxt&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;Their common denominator is that they are all programmed using JavaScript (or TypeScript). Beyond that, however, they differ quite significantly.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Current Status</title>
				<link>https://mevisys.net/posts/actual-state/</link>
				<pubDate>Sat, 03 Oct 2026 09:15:00 +0000</pubDate>
				<guid>https://mevisys.net/posts/actual-state/</guid>
				<description>&lt;p&gt;Toward the end of 2024, we got back to working on the MEVISYS platform. Having moved on from the Embedded Linux architecture, we shifted our focus to a new technical solution that has much stronger economic potential and, more importantly, is simple enough for our small team to realistically bring to life.&lt;/p&gt;&#xA;&lt;p&gt;We also began focusing much more intensely on the security of the entire solution. These considerations led to a major shift in our architectural logic. Now, all core business logic lives on the server. At the installation site, we deployed a relatively simple — and therefore cheaper — hardware unit. There is no longer any need to program the device; instead the logic lives on the server.&lt;/p&gt;</description>
			</item>
			<item>
				<title>The Initial Idea</title>
				<link>https://mevisys.net/posts/first-idea/</link>
				<pubDate>Thu, 01 Oct 2026 20:35:00 +0000</pubDate>
				<guid>https://mevisys.net/posts/first-idea/</guid>
				<description>&lt;p&gt;Our work on the MEVISYS platform began back in 2018. While developing a complex Embedded Linux device, we realized that Embedded Linux could actually have great potential as a cost-effective solution for data acquisition and measurement applications.&lt;/p&gt;&#xA;&lt;p&gt;We aimed for a modular, brick-style system featuring a central unit and several additional I/O units, all designed to mount onto a standard DIN rail. With this in mind, we chose compact, space-efficient enclosures from Phoenix Contact, which take up minimal space on a DIN rail (just 25 mm). Our goal was to engineer an Embedded Linux module that would fit perfectly inside.&lt;/p&gt;</description>
			</item>
			<item>
				<title>About us</title>
				<link>https://mevisys.net/about/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>https://mevisys.net/about/</guid>
				<description>&lt;p&gt;MEVISYS is short for &amp;ldquo;Measurement &amp;amp; Visualisation Systems&amp;rdquo;.&lt;/p&gt;&#xA;&lt;p&gt;Within the MEVISYS platform we handle:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;measuring quantities using sensors: temperature, pressure, position, &amp;hellip;&lt;/li&gt;&#xA;&lt;li&gt;recording measured data into databases&lt;/li&gt;&#xA;&lt;li&gt;visualisation of values via a web interface&lt;/li&gt;&#xA;&lt;li&gt;remote control&lt;/li&gt;&#xA;&lt;li&gt;monitoring of the complete solution&lt;/li&gt;&#xA;&lt;li&gt;server management&lt;/li&gt;&#xA;&lt;li&gt;support and consulting&lt;/li&gt;&#xA;&lt;li&gt;&amp;hellip; and other related activities&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;Our goal is not only the development of this system, but also putting it to practical use in real-world environments.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Services</title>
				<link>https://mevisys.net/services/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>https://mevisys.net/services/</guid>
				<description>&lt;p&gt;We offer complete services, from selecting the measurement method through to displaying the measured data.&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;selection of measurement methods and sensors (temperature, humidity, &amp;hellip;)&lt;/li&gt;&#xA;&lt;li&gt;selection of suitable hardware&lt;/li&gt;&#xA;&lt;li&gt;supply, installation, configuration and commissioning of hardware&lt;/li&gt;&#xA;&lt;li&gt;installation and commissioning of the server solution&lt;/li&gt;&#xA;&lt;li&gt;ongoing administration and service of the entire system&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;We offer both an immediate deployment of our already-developed system for a quick start, and complete custom development tailored precisely to your specific requirements.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Team</title>
				<link>https://mevisys.net/team/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>https://mevisys.net/team/</guid>
				<description>&lt;h2 id=&#34;people&#34; class=&#34;relative group&#34;&gt;People &lt;span class=&#34;absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100&#34;&gt;&lt;a class=&#34;group-hover:text-primary-300 dark:group-hover:text-neutral-700&#34; style=&#34;text-decoration-line: none !important;&#34; href=&#34;#people&#34; aria-label=&#34;Anchor&#34;&gt;#&lt;/a&gt;&lt;/span&gt;&lt;/h2&gt;&lt;p&gt;&lt;strong&gt;David Wünsche&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;Software engineer specializing in industrial metrology, embedded Linux, and server systems. He developed reliable systems for data acquisition and visualization and collaborated on their deployment at critical operations around the world. He focuses on data visualization, user-friendliness of software, and modern practices.&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;FEL CTU, electronics&lt;/li&gt;&#xA;&lt;li&gt;e-mail: &lt;a href=&#34;mailto:david.wunsche@wincak.name&#34;&gt;david.wunsche@wincak.name&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;phone: +420 721 315 359&lt;/li&gt;&#xA;&lt;li&gt;portfolio: &lt;a href=&#34;https://portfolio.wincak.name&#34; target=&#34;_blank&#34; rel=&#34;noreferrer&#34;&gt;portfolio.wincak.name&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;git: &lt;a href=&#34;https://gitlab.com/wincak&#34; target=&#34;_blank&#34; rel=&#34;noreferrer&#34;&gt;gitlab.com/wincak&lt;/a&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tomáš Novák&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;Embedded engineer specializing in measurement, industrial, and special-purpose electronics. He has built and programmed many electronic devices in C, and also developed a number of applications in C++, the Qt framework, Python, and other languages.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
