all

In diesem Bereich werden alle Informationen für eine Softwareentwicklung für den T-Balancer bereitgestellt:

Hier finden Entwickler eine Dokumentation der Programmierschnittstellen vor. Diese sind offengelegt, um auch anderen Anwendungen den Zugriff auf die T-Balancer-Steuerung zu erlauben sowie Software für andere Plattformen, wie Linux zu erlauben.

Mit den angeführten Daten kann jeder interessierte Entwickler sein eigenes Konfigurationsprogramm schreiben. Dazu ist nur etwas Erfahrung bei der Programmierung der Schnittstelle nötig (mitgelieferte Treiber). Da der Datenaustausch bisher über eine virtuelle serielle Schnittstelle erfolgt, ist der Programmieraufwand gering.

Erfolgreiche Entwicklungen werden an dieser veröffentlicht.

>> Was bedeuten die Alarmcodes?

0: OK - Short flash. Sytem works without failures
1: Start - Fully illuminated. System start - all fans are accelerated to
100% to check their speed. In some sec. they will slow down to your settings.
5: Sensor Error - Long flash. Error assigning the sensors! There is a
sensor which is not assigned to any fan channel.
10: Fan Error - Long flash and short beep. Unexpected blockage of a fan.
Your system is getting too hot, please check your configuration and system!
12: Flowmeter Error - long flashes and beep. The flowmeter delivers value
out of the range. Please check them, otherwise this may lead to an automatic emergency switch.
18: Critical Temperature - Long flash and long beep. Temperature limit
exceeded at one channel. Your system gets too hot, please check your configuration and system!
19-20: Switch Off - long and continius beep. Switch off is activated. A
critical temperature was reached or the flowmeter delivered values out of the allowed range.

>> Treiber für Linux

Der T-Balancer hat einen USB-Chip von FTDI. FTDI bietet sowohl für Windows als auch für Linux Treiber an.

FTDI supports 2 kinds of drivers for Linux: 
- VCP (virtual com port driver) is included in the kernel 2.4.20 or greater 
- D2XX drivers allow direct access to the USB device through DLL access. 
http://www.ftdichip.com/Drivers/FT232-FT245Drivers.htm#D2XX

>> Programmierbeispiel in C++ für Linux

This page contains examples of communicating with FTDI devices through the D2XX drivers and FTD2XX.DLL using C++ Builder: 
http://www.ftdichip.com/Projects/CodeExamples/C++Builder.htm

>> Linux-Entwicklungsforum

http://sourceforge.net/forum/forum.php?thread_id=1271826&forum_id=462785

>> How can I interprete the values from the T-Balancer?

- FanMaxSpeed: add the low- and high byte to a 16bit value (256*HB+LB), multiply it with 10.5 to receive the value for turns per minute.

- Fan RPM and Volt are only interpolated values. RPM is linear interpolated from maximum, and voltage is quadratic interpolated (results from root mean square from ideal rectangular signals)

- The flowmeters are a little more complicated. You receive a simple impulse count value. But this value is dependent from the measuring windows (1 to 4 seconds) – 235 TWI_SHWerte[10]. The 232 and 233 then means the measured pulses per second, 2 seconds, 3 seconds or 4 seconds. Divided through the window width you get the pulses per second, multiplied to 60 seconds you get the pulses per minute. To get the liter per minute or hour you have to respect the adjusted flowmeter dependent pulses/liter value. Our standard flowmeter have 509pulses/liter. This value can be found in the TBAN database on the table “Einstellungen” with the keys “Durchfluss1” and “Durchfluss2”.

-Getting the pulses is similar to pumps and fans, but not exactly. It is only usable without damaging something, if the impulse function works with an open drain circuit. Standard fans uses the 12V for reference, the flowmeters are not powered their self and receive only 5V from the sensor hub. The signal input on the sensor hub is only build for 5V input. You only have to connect ground and pulse with a pushbutton to get an impulse.