[FunkstoerungParticipant 2015-01-01 at 21:14 Post count: 28]

#1556 In reply to: USB in Vmware |

Tja, bekomme immer die folgende Error Message: TypeError: af_inet address must be tuple not nonetype

Im Knx Userforum hatte es wohl jemand gelöst, aber leider nicht geschrieben wie.

http://knx-user-forum.de/knx-eib-forum/19162-licht-geht-nicht.html

Ist schon merkwürdig, mit der ETS kann ich über die IP und Port des EIBD konfigurieren, aber der HS will mit den gleiche Einstellungen nicht.

Kann mir jetzt nur noch vorstellen das es am multicast liegt. Vielleicht geht das bei meinem Switch nicht

[RoellerKeymaster 2014-01-15 at 13:01 Post count: 53]

#1227

Topic: Newbie: How to program/config Homeserver in forum Gira HomeServer |

1) Understanding
A Dutch (Belgium) manual explaining the Homeserver, Experte Software, how to program/configure, etc.
Mirror download: http://www.roelbroersma.nl/media/pdf/Handleiding_Gira_Homeserver_3.pdf

2) Address your devices (program the devices, give it a 3 number ‘address’ like “2.3.1”) using ETS software: http://pirateproxy.net/torrent/8186732/ETS_4.1.6_Professional

3) Build a Homeserver and import the devices/address. Now it’s time to create the logic (bind switches to actors, create time schemes, etc.)

Here is a YouTube video about how to setup the homeserver (using the free Gira Experte software and IMPORT the addresses in it which you gave to the devices using the ETS4 software).

[EIB_DIYParticipant 2013-10-16 at 02:07 Post count: 1]

#1022

Topic: Hardware HS3 Tutorial – English in forum Gira HomeServer |

Hi.
Here is my summary on how I built a working hardware box.

Hardware :
– a used Wyse J400 WT941GXL WinTerm thin client (must be one with a VIA CPU, some are with AMD !!!).
– a 2GB female IDE 40-pin Disk-on-module flash drive (mine is from Transcend).
– an old ISDN-PCI card with HFC-S PCI chip (not really needed but since I had it anyway …)
– some PC133 RAM (2 x 512MB is the max)

The Wyse WT941GXL is a nice start for this project as it is a real mini-PC with an original VIA EPIA motherboard (1 GHz C3 CPU) with 100% passive cooling and an on-board VIA Rhine VT6103 LAN chip.
Used, it is also quite cheap to buy today.
My Wyse box was the “luxe” version, so it came with 512 MB ram and a small hard drive of 40GB.
The normal version comes with less ram and a small DOM (no HDD) : just add some ram if needed. Until today, I still have 512MB ram in mine.

I removed the HDD from my Wyse box, so no moving parts anymore, like the original box.
The power supply unit inside the Wyse box has two cables ready to give power to DOM’s but, I had to modify one of the cables as it wasn’t with the right connector for my 2GB DOM. The soldering iron was needed to modify it the right way but it was a quick and very easy work. Some heat-shrink tube was also handy to make it looking good.

Now the config :
In the BIOS settings, I load “Optimized settings”, then I modify this :
– serial port : 3F8 irq 4
– parallel port : Normal
– no boot logo
– pushing the power button shuts down immediately (no 4 sec wait)
– all passwords disabled (by default, the BIOS from Wyse uses “Fireport” as admin password).
I’m not sure what are the best settings for the “power management” section.
N.B. Wyse uses a modified BIOS, I think it is possible to flash the latest “normal” BIOS from VIA but I didn’t tried this and have no idea what it could change (in good or bad…).

The 2GB DOM is plugged into the first IDE slot, but set as “slave”.
I used FreeDOS and “fdisk” to make 4 Primary DOS partitions :
16MB (Active), 110MB, 870MB, 870MB. All 4 formatted in FAT.
Install FreeDOS on drive C: (16MB) and make this partition bootable.
Copy the firmware files (“DOLINUX.BAT, …) on drive D: ; I used firmware version 2.5.
It is also the right time to copy the 2 nice utilities (read below) on drive C:.
For what I tried, the easiest way for doing this is to use another IDE HDD/DOM, already formated and configured with FreeDOS and having all useful file copied on it.
Plug this other HDD/DOM as secondary master and boot on it by changing the BIOS boot order. The advantage of doing it this way is that you are sure that the partition table on the 2GB DOM are correctly created regarding the disk geometry reported by the BIOS ; I’ve see strange things happening when the DOM was partitionned/formatted on one PC and then moved on another PC.
Remeber that DOS has a weired way of giving drive letters when you have 2 HDDs on a computer :
C: is the first primary DOS partition on the first HDD
D: is the first primary DOS partition on the second HDD
then all other DOS partitions form the first HDD
and then all other DOS partitions form the second HDD
Once you have created the 4 partions on the 2GB DOM, you must reboot before formating and copying, so it is MUCH easier if you only have one DOS partition on your temporary HDD (the one in secondary master IDE) :
C: is your temporary
D: will be your future C: (16MB)
E: will be your future D: (110MB)
etc.

Now the “magical tour” :
On the internet, you will find 2 very nice utilities (to be copied on a subdirectory of your C: drive …)
The first one is “eeprom.exe” (and eeprom.txt), made by VIA to edit some settings on the LAN chipsets like the VT6103. I used version 3.14 of this utility, but some others do exist also.
Search on the web with “VT6103” and “eeprom” as keywords …
The usage is very simple : in DOS, type “eeprom.exe -km1 XXXXXXXXXXXX” where the X’s are your desired MAC address without “:” nor “-“.
The other nice utility is “SMBCFG.EXE”.
This is a menu driven utility made to read and MODIFY some information stored into your motherboard, like serial numbers for exemple. Those information are also used by DMIDECODE in Linux.
I found 2 “serial number” strings empty in my Wyse box, so I filled both with my MAC address.
Search on the web with “smbcfg.rar” and “biosrepair.com” as keywords …

Remove the temporary HDD, close the Wyse box and restart … you should have a dos prompt soon.
Use the 2 utilities.
Reboot the box.
Go to drive D: and type DOLINUX + enter, firmware 2.5 should start with NET NET NET …
Push the power button twice to reboot.
Now, all it take to start the firmware automatically is to edit the autoexec.bat file and, at the end, go to the D: drive and execute “DOLINUX.BAT”.

When it is OK, make a very light config with the expert 2.5 (IP and KNX base settings, one “admin” user with password and rights set, …) and push the config into the box via serial port (you will need a null modm cable between your PC and the COM port of the Wyse box).
After a reboot and a download, your box should restart with an IP address and be rechable via network.

From that point, you can stop expert 2.5 and start expert 2.10.
A firmware upgrade of the box to 2.10, via network, is working with one exception : “DOLINUX.BAT” has been replaced by “DOLINUX2.BAT”, so the AUTOEXEC.BAT file must be adapted.
If your box keeps rebooting with firmware 2.10, then you should look for another MAC address and reuse the two nice utilities ; it is possible to stop DOS from playing the AUTOEXEC.BAT file if you push F5 (or another “F” key ???) at the right time, in order to get out of the infinite reboot loop.

I didn’t try firmwares above 2.10 yet.

[EfeeParticipant 2013-10-04 at 00:33 Post count: 13]

#1015 In reply to: HS3 Tutorial – German |

okay, komme nun zumindest über den Browser an den Server ran. Neues Projekt übertragen.
Im EIB bekomme ich ein “?” bei der Phys. Adresse. Hab ich die im ETS nicht gescheit konfiguriert? oder es liegt halt wirklich and der MDT Schnittstelle.

Naja, einen kleinen SChritt weiter zumindest.

Danke euch.

Gruß
Efee

[hs815Participant 2013-04-16 at 11:11 Post count: 1]

#756 In reply to: Firmware Experte 4 |

Hy Gedia,

i figured out, that with new kernel you dont nee dhc or hdb anymore..

it just works with sda…

thats what i did:

i updated my old HS3 (on kvm) to the new 4.0
the major change was the harddisk is now sda and no longer hdc
i use a suse11.3 64bit (know its not the newest).
created 4 partitions:
/dev/sda1               1         132     1060258+  82  Linux swap / Solaris
/dev/sda2             133        1177     8393962+  83  Linux
/dev/sda3            1178        1309     1060290    6  FAT16
/dev/sda4            1310        1441     1060290    6  FAT16

then i extracted the firmware file from experte 4 (zip) for HS3
(because i works with my old mac-address)
therefor i unpacked the inird with
gzip -dc ../INITRD | cpio -id
to a dir..

then i copied the hs dir to the rootpath of my linux
and when i started i needed to install some python-packages..
but first i copied all the python-dirs to my linux /usr/lib/python
there is a PIL dir which is needed..

then i can start it. With a script.

*****************************************
PYTHONPATH=/usr/lib/python/PIL
export PYTHONPATH
TZ=CET-1CEST,M3.5.0/2:00,M10.5.0/3:00
export TZ
hwclock –hctosys –utc
setserial /dev/ttyS0 autoconfig
setserial /dev/ttyS1 autoconfig

#only needed for serial transfer 1 time:
#/hs/bin/hs_main trans
#killall -9 python

/hs/bin/hs_main main
reboot
*********************
The communication for the first time I did with a nullmodem cable to windows8
The serialport on the new hs was ttys0…. It also changed…
Now it works fine…

on original HS4-hardware there are
15MB
110MB
870MB
870MB

all dos formatted, but the do something strange with turbodisk..
and then start it with loadlin to a ram -image. with busybox

[borkenParticipant 2013-04-11 at 11:42 Post count: 2]

#730 In reply to: HS and USB interface |

The problem, at least when running the HS as a VM, is that the HS connects to the wrong USB-device.  I also read the posts that this should be possible to alter.

However, since I was starting the HS by ISO-file mount to the virtual CD-rom, I was not able to edit the file needed (no access to the linux system before the HS main starts.

A workaround is to make your own KNX IP-GW, by using a Raspbarry PI and the EIBD software. I got that to work, at least I managed to use the ETS to program the KNX-bus through that IP-gw. The HS can then talk to this IP-GW over multicast.