N148/22 setup

[Warichet]

Hi,

I've used the SuFu but didn't help this time.

I'm installing a N48/22 according to the doc
I've assigned a fixed IP and a PA.

The LED on the front blink
The procedure about pushing the Prog button until the LED goes out seems to work.
The procedure about pushing the Prog button more the 5 sec but less then 10 seems to work, the LED blinks rapidly.

With ETS, the N148 replies at "Device Info".
The N148 replies at Ping

Everything seems to work normally, but in ETS 3.0e, I see only 1 channel, instead of 4.

I'm sure I forgot something, but what ?

PS: I didn't go through the intermediary step via DHCP, but assigned directly a fixed IP. I hope this is not the cause.

[Warichet]

Hi,

Forgot to mention ...
The purpose of the N148/22 is to make the interface between eibd (on the NAS) and KNX.
Not to be used as an ETS interface for programming, I'm using the HomeServer to do that.

The question is: in this configuration, do I need to do the setup in ETS "supplement / Options etc" ?

[Sipple]

Hi Warichet

how do you check the number of channels in the ETS? I doubt that you can see that directly. In my case, the N148 occupies 6 physical adresses on the EIB side. The first one is the one you assign when you program the PA with the ETS. 4 more are automatically assigned for tunneling when you press the button for >5s, plus 1 objectserver connection address. So actually 6 addresses altogether. Which addresses it will reserve seems to be random. The only way I know to find out the tunneling/objectserver addresses is by using the busmonitor of the ETS and search for all PA's.
Here's a link to the things I found out (last post). If you need a translation, just tell me :-)

https://knx-user-forum.de/knx-eib-fo...ssvergabe.html

Greetings, Martin

[saft6luck]

You'll see only one device but this single device can be opened 4 times. Each of these virtual devices will use one of 6 different PAs, the one you assigned manually and the others that were assigned automatically.

Edit: Need to precise my answer: the manual address I mean is configured in ETS3/.../communication at settings (sorry, I don't use the English version).
The way the other 5 addresses are automatically configured depends on the PA address which you use for programming the device and are selected by 'searching' the bus for free 'space' around this PA. In case you want to use one of these addresses later on for other devices you just need to start the search process again.

[Warichet]

Hi Martin,

how do you check the number of channels in the ETS?

First of all, I must say I've no experience about the N148/22. All I can do is RTFM and search the forum.
The doc says, in summary: you can have 1 channel + 4 others; you must assign a PA for each channel.
So I was trying to do that, but in ETS I see only one, hence the question

4 more are automatically assigned for tunneling when you press the button for >5s

I've been doing that many times, hoping for additional addresses to pop-up, in order to be configured.

Which addresses it will reserve seems to be random.

Pfff, what a crummy design !


Hi saft6luck,

You'll see only one device but this single device can be opened 4 times. Each of these virtual devices will use one of 6 different PAs, the one you assigned manually and the others that were assigned automatically.

OK, thank you. The doc could have been more explicit about that

the manual address I mean is configured in ETS3/.../communication at settings

That was one of my questions.
In my particular configuration, the N148/22 is not used with ETS nor programming. It is used for eibd running on a NAS and give it access to the bus.
In that case, do I still need to configure in ETS3/.../communication at settings ?

Anyone having a NAS with eibd, please ? Maybe a word about your config ?

Thank you for your kind help.

[Sipple]

Well, I don't use a NAS, but the EIBD is always the same.
Since you have programmed the standard PA of the N148 including the parameters for IP (DHCP or not) and assigned the automatic PA's with the >5s procedure, you're ready to go. No more configuration necessary.
Just start the EIBD on your NAS with e.g.

eibd -D -T -S -d -i --pid-file=/var/run/eibd.pid ipt:192.168.178.39

Should work.

[Warichet]

Since you have programmed the standard PA of the N148 including the parameters for IP (DHCP or not) and assigned the automatic PA's with the >5s procedure, you're ready to go.

Just start the EIBD on your NAS with e.g.
eibd -D -T -S -d -i --pid-file=/var/run/eibd.pid ipt:192.168.178.39

Yet another last minute problem, I can't start eibd anymore, it has worked before
eibd --info brings me
-sh: eibd: command not found
but I'm in the right directory !
[/share/MD0_DATA/optware/opt/bin] # ls -al e*
-rwxr-xr-x 1 admin administ 299752 Feb 27 08:46 eibd*

I've rebooted the NAS since the last test.
Did I break something ? or forgot to save something ?

Thank you for your help

[Tru]

eibd --info brings me
-sh: eibd: command not found
but I'm in the right directory !

To start in the local directory you need to call it as ./eibd. Possibly you have changed your PATH variable somehow.

[makki]

Maybe too simple but ./eibd ... (or use absolute path)?
And for what the N148/22-channel-thing if you have eibd running, with -S -T it has a Tunneling server for somewhat >60.000 concurrent connections

Makki

P.S.: be sure to use a recent eibd with this, as there was an issue on high telegram-load (with the previous /11, I guess it might apply for this also) the interface being somewhat "overdriven" by eibd..

[Warichet]

To start in the local directory you need to call it as ./eibd.

OK

Possibly you have changed your PATH variable somehow.

I'm unable to do that

And for what the N148/22-channel-thing if you have eibd running, with -S -T it has a Tunneling server for somewhat >60.000 concurrent connections

Fine
My error is more explicit now
[/share/MD0_DATA/optware/opt/bin] # ./eibd --info
./eibd: error while loading shared libraries: libpthsem.so.20: cannot open shared object file: No such file or directory
But this has worked before. Do I need to load those libraries after each reboot ?

Sorry to be a pain

[makki]

Hmm, somehow pthsem got lost obviously between reboots
I've no idea about the Qnap in general but wonder somehow about your eibd-path and wether pthsem was really installed into the system or just dropped in somewhere..

A dirty solution might be:

LD_PRELOAD=/path/to/my/libpthsem.so.20 /path/to/my/eibd

Makki