Can I run the software on a Raspberry Pi?
Is there a simple way to log parameters?
I'm using FHEM and want to process the data from my heating system. How can I do this?
I have a relay shield added to the Arduino Mega, how can I set/query the individual relays?
My heating system has parameters that are not supported in the software yet, can I help adding these parameters?
Yes, by using different pin headers (female instead of male). But please take note that you cannot use the BSB-LPB-LAN software which only runs on Arduino. You would have to use the completely different bsb_gateway software for BSB, which can be found here or the PPS-monitor software for PPS devices, which can be found here. Please contact the author of the corresponding software directly for any support related to it. All information on this website applies to the Arduino version only! No support for bsb_gateway or PPS-monitor can be given here.
No. While you can use the interface board also on a Raspberry Pi 2, you would have to use a completely different software (bsb_gateway) which can be found here. Please contact the author of bsb_gateway directly for any support related to it. All information on this website applies to the Arduino version only! No support for bsb_gateway can be given here.
Yes, there is, both standalone and remote:
For standalone usage of the device use the following procedure:
Insert a FAT32-formatted micro SD card in the slot on the Ethernet shield before powering up the device. Some devices might not recognize cards larger than 2GB, in that case use a smaller card and format it with FAT16.
Then edit BSB_lan_config.h and activate the #define LOGGER directive. Then you can add the fields you want to be logged to the variable log_parameters and set the logging period with variable log_interval. You can later change both the interval as well as the parameters during runtime using the URL command "/L=[interval],[parameter1],...,[parameter20]".
Once the setup is done, power-up the device and wait for data coming in. All data is stored in the file datalog.txt file on the card in CSV file format and can be imported easily in Excel and OpenOffice.
You can watch the content of the file with URL command "/D". To reset the file, use command "/D0". This should also be done after first powering up the device because it initializes the file with a proper CSV file-header.
Please note that the Arduino is not an exact timepiece, so even though you might set the interval to 60 seconds, the time displayed in the file (taken from the heating system) may differ - this might be up to a second per minute. If exact logging time is essential, find out the average time difference between Arduino time and real time and adjust the logging interval accordingly, e.g. use 59 seconds instead of 60.
For remote logging follow this procedure:
Run this command periodically (e.g. via a cron job):
DATE=`date +%Y%m%d%H%M%S`; wget -qO- http://192.168.1.50/1234/8310/720/710 | egrep "(8310|720|710)" | sed "s/^/$DATE /" >> log.txt
The resulting log.txt file of this example contains the logged values for parameters 8310, 720 and 710. Just change these parameter numbers in the http-request as well as the egrep command (and of course the IP address and the passcode) and you are set. Later on, you can sort the log file based on parameter numbers with the sort command:
sort -k2 log.txt
Please note that FHEM is a complex software and this is not the place to provide basic introductions or instructions. But if you have already configured other devices for FHEM, this will hopefully help you:
To access the web interface of the device, you can use FHEM's HTTPMOD module. Here's an example configuration which you can easily adapt to your own needs and parameters. Of course you need to change the IP address as well as the passcode, too. This code polls parameters 8700, 8743 and 8314 every 300 seconds and assigns these to the device "THISION" (the name of my heating system) to the readings "Aussentemperatur", "Vorlauftemperatur" and "Ruecklauftemperatur". It furthermore provides a reading "Istwert" that can be set via FHEM to provide the current room temperature to the heating system (parameter 10000). Finally, it calculates the difference between "Vorlauftemperatur" and "Ruecklauftemperatur" and assigns this difference to the reading "Spreizung".
define THISION HTTPMOD http://192.168.1.50/1234/8700/8743/8314 300
attr THISION userattr reading0Name reading0Regex reading1Name reading1Regex reading2Name reading2Regex readingOExpr set0Name set0URL
attr THISION event-on-change-reading .*
attr THISION reading0Name Aussentemperatur
attr THISION reading0Regex 8700 .*:[ \t]+([-]?[\d\.]+)
attr THISION reading1Name Vorlauftemperatur
attr THISION reading1Regex 8743 .*:[ \t]+([-]?[\d\.]+)
attr THISION reading2Name Ruecklauftemperatur
attr THISION reading2Regex 8314 .*:[ \t]+([-]?[\d\.]+)
attr THISION readingOExpr $val=~s/[\r\n]//g;;$val
attr THISION set0Name Istwert
attr THISION set0URL http://192.168.1.50/1234/I10000=$val
attr THISION timeout 5
attr THISION userReadings Spreizung { sprintf("%.1f",ReadingsVal("THISION","Vorlauftemperatur",0)-ReadingsVal("THISION","Ruecklauftemperatur",0));; }
Please note that the Regex must match from the beginning of the string, i.e. from the parameter number (such as 8700) and not from somewhere later in that string.
The following is an example for a FHEM configuration that queries and sets the three relay ports named "Heater", "Fan" and "Bell" attached to GPIO pins 7, 6 and 5 respectively (again, adjust IP and passcode accordingly):
define EthRelais HTTPMOD http://192.168.1.50/1234/G05/G06/G07 30 attr EthRelais userattr reading0Name reading0Regex reading1Name reading1Regex reading2Name reading2Regex readingOExpr readingOMap set0Name set0URL set1Name set1URL set2Name set2URL setIMap setParseResponse:0,1 setRegex attr EthRelais event-on-change-reading .* attr EthRelais reading0Name Heater attr EthRelais reading0Regex GPIO7:[ \t](\d) attr EthRelais reading1Name Fan attr EthRelais reading1Regex GPIO6:[ \t](\d) attr EthRelais reading2Name Bell attr EthRelais reading2Regex GPIO5:[ \t](\d) attr EthRelais room Heizung attr EthRelais set0Name Heater attr EthRelais set0URL http://192.168.1.50/1234/G07=$val attr EthRelais set1Name Fan attr EthRelais set1URL http://192.168.1.50/1234/G06=$val attr EthRelais set2Name Bell attr EthRelais set2URL http://192.168.1.50/1234/G05=$val attr EthRelais setParseResponse 1 attr EthRelais setRegex GPIO[0-9]+:[ \t](\d) attr EthRelais timeout 5
My heating system has parameters that are not supported in the software yet, can I help adding these parameters?
Yes, you can :)! All you need is to connect your Arduino to a Laptop/PC via USB while it is connected to your heating system and follow these steps (BSB only, LPB is similar, but telegram structure is a bit different):
- Start the Arduino IDE and turn on the serial monitor
- Enable logging to the serial console and turn on verbose output with URL-Parameter /V1 on the Arduino, e.g. http://192.168.1.50/1234/V1. Alternatively, you can log bus telegrams to SD card by using (only) logging parameter 30000 (see logging section above) and set variable log_unknown_only to 1 (URL command /LU=1) and follow logging entries with URL command /D.
- On the heating system, switch to the parameter you want to analyze (using the command wheel, arrows or whatever input mode your heating system has).
- Wait for "silence" on the bus and then switch forward one parameter and then back again to the parameter you want. You should now have something like this on the log:
DISP->HEIZ QUR 113D305F DC 8A 00 0B 06 3D 11 30 5F AB EC HEIZ->DISP ANS 113D305F 00 00 DC 80 0A 0D 07 11 3D 30 5F 00 00 03 A1 DISP->HEIZ QUR 113D3063 DC 8A 00 0B 06 3D 11 30 63 5C 33 HEIZ->DISP ANS 113D3063 00 00 16 DC 80 0A 0E 07 11 3D 30 63 00 00 16 AD 0B
The first four lines are from the parameter you switched forward to, the last four lines are from the parameter you want to analyze (doing the switching back and forth only makes sure that the last message on the bus is really the parameter you are looking for). Instead of DISP you might see RGT1, depending on what device you are using to select the parameter.
Each data telegram has the following structure:
Byte 1: always 0xDC (start of telegram)
Byte 2: source device (0x00 = heating system, 0x06 = room device 1, 0x07 = room device 2, 0x0A = display, 0x7F = all) plus 0x80
Byte 3: destination device (same values as source)
Byte 4: telegram length (start-of-telegram byte (0xDC) is not counted)
Byte 5: message type (0x02 = info, 0x03 = set, 0x04 = ack, 0x05 = nack, 0x06 = query, 0x07 = answer, 0x08 = error)
Byte 6-9: Command ID (that's what we're interested in!)
Byte 10...: Payload data (optional)
Last two bytes: CRC checksum
- The lower data telegram above has the command ID 0x113D3063. Please note that the first two bytes of the command ID are switched in message type "query" (0x06), so make sure you look at the right telegram (type "answer" (0x07), last line in this example).
- Look up the "global command table" section in file BSB_lan_defs.h and check whether an entry for this command already exists (search for STRxxxx where xxxx is the parameter number). If it does exist, go on to step 8.
- If your parameter is not yet listed in the "global command table", you have to add an entry in the "menu strings" section like this:
const char STRxxxx[] PROGMEM = "Parameter_Name_or_Function";
Now copy a line from the "global command table" section where your new parameter would fit numerically. Proceed with step 8 but rather than replacing CMD_UNKNOW you have to replace the command ID and value type of the copied line of course.
- Replace the CMD_UNKNOWN with the command ID you just found. If the return value type (column 3) is VT_UNKNOWN try and find out which parameter type from the list at the beginning of the file works. For example, if the parameter should return a temperature value, you can try VT_TEMP, VT_TEMP_SHORT, VT_TEMP_SHORT5 or VT_TEMP_WORD. For parameters which offer multiple options, you have to add a corresponding line in the "ENUM tables" section.
- If the web interface gives you the same value as is displayed on the heating system, you have found the right value type and the parameter is now fully functional (i.e. querying and setting the value will work). Congratulations!
- When you are done, double check that the new command ID is not used somewehere else in the definition file (i.e. search for the command id - only one location should come up). It's possible that command IDs exist for different parameters with different heating systems because the protocol is not standardized and manufacuters don't seem to bother how other manufacturers use the command IDs, at least with less general parameters. If it occurs that a command ID is now existing twice in the BSB_lan_defs.h file, please mark it clearly when sending us the update and state which heating system you are using. We will then add a conditional compile flag so that heatingy system X will compile differently than system Y so that in the end both will use the ambiguous command ID for the right parameter.
- Please send only the new/updated lines to bsb (ät) code-it.de - if you use a diff-file, please make sure that you download the most recent BSB_lan_defs.h from the repository before making the diff because sometimes the file gets updated without an actual new version being released immediately.