KNX/EIB ETS4, N148/22 and bus monitor

[Warichet]

Hi,

I've a N148/22.
Tunnel 1 is configured 1.1.249 10.0.1.244, for eibd, works fine
Tunnel 2 is configured 1.1.248 10.0.1.244, for ETS4 Lite, test OK
Tunnel 3 is configured 1.1.247 10.0.1.244, test OK

I'm trying to use the Bus Monitor, doesn't work
Message says: the tunnel server is available but no more connections are accepted.

I guess I made a mistake in the config ?
I understand that the monitor needs another tunnel than ETS but how can I specify it ?

[Sipple]

Hi Raymond

Sometimes I have the same Problem. Surprisingly, only the ETS complains. Just reset the N148 and try again. Worked for me.

If you find a better solution, please let me know

Bye, Martin

[Warichet]

Just reset the N148 and try again.

OK, I'll try
I was unsure about the remaining tunnels; so there was 1 tunnel free with a PA assigned, and other tunnels left unassigned.

As a test, I just configured the communication as "IP routing" (yeah!) and both ETS and bus monitor seem to work

[Sipple]

As a test, I just configured the communication as "IP routing" (yeah!) and both ETS and bus monitor seem to work

But not via the N148. I guess you use the eibd as the KNX Routing interface now.

[Warichet]

I guess you use the eibd as the KNX Routing.

No. I checked again.
Other bizarre thing, I'm unable to configure the HS for ETS, although it has been discovered and is displayed as available. Bizarre !

Ouups, you are right (the eibd connection has been renamed)

[Sipple]

Ah, ok.
Well, at least it's working now.

[Warichet]

at least it's working now.

Mmmyes, but not the way I want.
I want the N148 to be the interface (not eibd)
Also, I cannot figure out why the interface via the HS is not working (but discovered), although it is working from ETS3 since years and the config looks right.

[Sipple]

Have you tried the Reset yet?

[Warichet]

Have you tried the Reset yet?

No, not yet.
I'm a bit scared

Which Reset do you mean ? a BCU reset ?
remove bus cable
push&hold the programming button
re-connect the bus cable
still hold the programming button for 5 sec

[Sipple]

Just remove the power from the N148.
I use Power over Ethernet, so it's easy for me (unplug LAN cable for some seconds is enough).
If you use the yellow/white connector for a power supply, just remove that. You can leave the KNX Bus attached.

A question from my side: How do you check which and how many tunnels are active? I only used the ETS to look for all existing physical adresses and I'm not sure about what I actually get

[Sipple]

Another solution for the ETS Bus Monitor problem is to use the Group Monitor instead. This one always works.

To be honest, after using the ETS4 for about a year now, I still don't know why we have a Bus and a Group Monitor. What's the difference, or better to say, what can the Bus Monitor do what the Group Monitor can not?

Greetings, Martin

[Klaus Gütter]

Another solution for the ETS Bus Monitor problem is to use the Group Monitor instead. This one always works.

To be honest, after using the ETS4 for about a year now, I still don't know why we have a Bus and a Group Monitor. What's the difference, or better to say, what can the Bus Monitor do what the Group Monitor can not?

Greetings, Martin

Supported by the bus monitor but not the group monitor:

• Display telegrams with target = individual address (physical address)
• Display link layer ack/nak/busy
• Show telegram repetitions

Supported by the group monitor but not the bus monitor:

• Send telegrams

[Warichet]

Just remove the power from the N148

OK, did it. Didn't help, same error message

I use Power over Ethernet

Me too

How do you check which and how many tunnels are active?

I'm unsure about my setup, and I'm unsure about the right way to do it.
I've installed the N148/22 months ago, I assigned PA 1.1.249, IP 10.0.1.244 and I used it for eibd.
Recently, I wanted to test ETS4 and wanted to use one of the free tunnels of the N148
Within ETS4, parameters of the communication, I first tried 1.1.249
Obviously, it didn't work (expected)
So I selected the next one, 1.1.248 and assigned it for use of ETS. The test is OK and ETS seems to work (not done very much)
I configured the next available tunnel, for use with the bus monitor or whatever application might need it. The test is OK, but the monitor doesn't work. Still the same error message

Again, I'm unsure about my setup.

Is this thing supposed to work ?
Anyone managed to make it work ?

I'm not sure about what I actually get

You get problems, that's for sure (pardon )

[Sipple]

Well, what I found out so far.
First of all, you have to use another EIB/KNX interface to programm the FIRST physical address and the application for the N148 with the ETS (on the parameter page enter a name and select DHCP or enter IP stuff manually).
In my case this is e.g. 1.1.63. This is the only thing I had to do manually.
With this physical address you can program/change the application and e.g. let the Program-LED blink via the ETS.
If this is done, press the Program-LED for more than 5s (but not more than 10s) and the Interface will automatically assign additional physical addresses.
In my case, it was 1.1.85 to 1.1.89, so FIVE more addresses. 4 for tunneling, 1 for object server. BUT!!!!! I'm not 100% sure about that. There is no detailed documentation about that (at least I haven't found one which EXACTLY says what's going on). I found out about these 5 addresses by using the ETS and searched for existing physical addresses an the bus.
In the short documantation one can read that the additional physical addresses can be set by ETS. How??? Where??? I guess that's simply wrong!
Anyway - When this procedure is done, the ETS will find the N148 automatically and uses one of the additional physical addresses.
Surprisingly, the ETS does not show USED additional physical tunneling addresses, except the own one. That means (in my case):

1.1.63 = physical address initially used to program the N148 via another EIB/KNX-Interface, program Application (set up name and e.g. DHCP), test Program-LED. Not used for anything else.
1.1.85 = right now used by my ALIX1D board under Debian Squeeze with EIBD. (NOT FOUND BY ETS when searching for existing physical addresses on the bus).
1.1.86 = right now used by my Atom board under Debian Lenny with EIBD. (NOT FOUND BY ETS when searching for existing physical addresses on the bus).
1.1.87 = right now used locally by the ETS4, found by ETS when searching for existing physical addresses on the bus and marked as local.
1.1.88 = found by ETS when searching for existing physical addresses on the bus, not used by anything yet, so considered free.
1.1.89 = found by ETS when searching for existing physical addresses on the bus, not used by anything yet, so considered free.

All I had to do to set up e.g. the two EIBD's is telling them the IP address of the Interface assigned by DHCP (or manually) and that it is tunneling. ETS4 found the Interface automatically if I remeber it right, but I never entered one of these additional physical addresses in the ETS4. But the ETS4 will SHOW the used one by clicking on the interface in the communication setup of the ETS4. It seems to be possible to change it, but I never touched it and it works. Only issue is the sporadic Bus-Monitor Error Message you got as well. In my case, I was able to run the Bus Monitor by switching power of the N148 off and on. I'm quite sure it's more an ETS4 bug rather than the N148. Group Monitor works fine while Bus Monitor complains.

@ Klaus: Thank's for this info. Where have you found it? ETS4 help is still empty

[vento66]

@ Klaus: Thank's for this info. Where have you found it? ETS4 help is still empty

Wenn man bedenkt das Klaus bei der IT-GmbH beschäftigt ist, und diese die ETS schreibt...