Sven Giermann Giermann

_address	name	description	unit	type	len	factor	offset	formula	role	room	cw	isScale
4999	Device type code	Geräte Typ-Code		int8be	1	1	0		value		false	false
5000	Nominal Output Power	Installierte Leistung	Kw	uint16be	1	0.1	0		value		false	false
5002	Daily Output Energy	Eigene Energienutzung heute (PV & Akku)	Kwh	uint16be	1	0.1	0		value		false	false
5003	Total Output Energy	Eigene Energienutzung gesamt (PV & Akku)	Kwh	uint32sw	2	0.1	0		value		false	false
5007	Inside Temperature	Temperatur im Wechselrichter	°C	int16be	1	0.1	0		value		false	false
5010	MPPT 1 Voltage	MPPT1 Spannung	V	uint16be	1	0.1	0		value		false	false
5011	MPPT 1 Current	MPPT1 Strom	A	uint16be	1	0.1	0		value		false	false
5012	MPPT 2 Voltage	MPPT2 Spannung	V	uint16be	1	0.1	0		value		false	false
5013	MPPT 2 Current	MPPT2 Strom	A	uint16be	1	0.1	0		value		false	false

Inspired by this

More of my guides: Debloating LDPlayer - Debloating Nox (Updated)

Edit 22/8/2021: I have updated MEmu and it seems like it reinstalls the apps and re-enables the services. Repeat steps 5, 7, 8, and 9 if you update MEmu.

Debloating MEmu

In my experience, Nox can be quite slow and choppy, and looks like I'm not the only person with this problem. A lot of people say that MEmu performs better than Nox, and I could agree with that. I have no chopping issues with it so far. But like Nox, there are kinda shady stuff going on.

Build your own Audacity for Windows with ASIO driver support

!!Breaking news - Steinberg recently open sourced the ASIO SDK (GPLv3) so Audacity will be able to release ASIO binaries. As they are focussed on Audacity 4 it might not happen anytime soon though!!

You might want Audacity to work with the ASIO drivers supplied with your sound devices. Commmon reasons for this are:

Only ASIO drivers are available for your hardware (eg Behringer mixers)
Performance - ASIO has low latency (delays)
You don't want to use the ASIO4All bridging driver with non ASIO drivers
Multi channel support - though Audacity is not so good at handling other than Stereo or Mono

How to make a Release Android App debuggable

Let's say you want to access the application shared preferences in /data/data/com.mypackage.
You could try to run adb shell and then run-as com.mypackage ( or adb shell run-as com.mypackge ls /data/data/com.mypackage/shared_prefs), but on a production release app downloaded from an app store you're most likely to see:

run-as: Package 'com.mypackage' is not debuggable

	/*
	* Demonstrate using an http server and an HTML form to control an LED.
	* The http server runs on the ESP8266.
	*
	* Connect to "http://esp8266WebForm.local" or "http://<IP address>"
	* to bring up an HTML form to control the LED connected GPIO#0. This works
	* for the Adafruit ESP8266 HUZZAH but the LED may be on a different pin on
	* other breakout boards.
	*
	* Imperatives to turn the LED on/off using a non-browser http client.

	#!/bin/bash
	#The MIT License
	#
	#Copyright (c) 2007 Cappy

	#Permission is hereby granted, free of charge, to any person obtaining a copy
	#of this software and associated documentation files (the "Software"), to deal
	#in the Software without restriction, including without limitation the rights
	#to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
	#copies of the Software, and to permit persons to whom the Software is