Merten 6288xx (4gang PB + RTCU)

[Warichet]

Hello,

I've just received following Merten devices:
Thermostat 628846
BCU for Thermostat 623299

I've loaded the latest version of the application, 3.1
I try to parameter the device and I get a warning:
"This application is only for devices above ver 3A"

I guess 3A is a hardware version (not the classical vdx application) ?

How can I read / know for sure the hardware version of the device ?
Is it already obsolete ?
Is it possible to upgrade that device ? if yes, how can I do it ?

Device info tells me this:

Général version masque 2.1
Adresse Individuelle 1.1.69
Fabricant du Participant Merten
N° de commande $00000062329902440000
Numéro de Série $000C00060039
Tension de bus 27,7V (±0.5V)
Mode de programmation Arrêt
Erreur d'utilisation OK ($FF)
Type PEI de Hardware Seriel: FT1.2 / Protocole chargeable
Programme d'application
Program Multifunction with RTCU and fan coil 1814/3.1
Type de participant $1814
Version 3.1
Etat de Chargement Chargé
Etat d'Utilisation En cours
Communication de Groupe
Etat de chargement de la table d'adresse Chargé
Etat de chargement de la table d'association Chargé

I see nowhere a version number like 3A, or similar
Also, just after power-on, de device runs a kind of self-test and it displays shortly: " A 3.0 "
Any clue ?

Warm greetings from a hot Midi-Pyrénées
Raymond

[HartmutB]

Hi Raymond,

Merten has upgraded their RTCU versions with fancoil support over the past months. Hardware version raised from 1.x oder 2.x to 3.x. Maybe your RTCU got some upgrade, too.

Hardware and application version has to match, no new application with old hardware and viceversa.
I don't know of any hardware upgrade expect of "new buy" .
As far as i know, device info doesn't tell you the hardware version (I checked with two of my devices in different versions).

Try to use the older application 3.0 (still part of the entire Merten product database). Just import that one device.

I'd be interessted in your experiences.

Regards,
Hartmut

[Warichet]

Hi Hartmut,

It's always a pleasure to see that someone on the forum cares of my problem

Merten has upgraded their RTCU versions with fancoil support over the past months. Hardware version raised from 1.x oder 2.x to 3.x. Maybe your RTCU got some upgrade, too.

Aah ?!? I though it is a relatively new device. Not so long ago, it was still in the Merten's news headlines ! In my case, it is 3 days old.

Hardware and application version has to match

As a system engineer, I fully agree, but to fullfill the requirements, one should be able to know the current/expected versions and act accordingly (without bothering TechSup for a trivial case).

As far as i know, device info doesn't tell you the hardware version

No, indeed. Someone told me "it's written at the back of the application plate". I've to check. But, from a famous company such as Merten, I expect a bit more then the average; i.e. a tool to read / upgrade the hardware/firmware, just as you do for any PC's motherboard. (I hope those guys didn't burn everything in silicium )

Try to use the older application 3.0 (still part of the entire Merten product database).

... OK.... or ... the other way around.
That is, I've loaded 3.1 and it seems to work, at least, I don't see error messages, nor in ETS, nor on the device itself, but I'm still in doubt as I've no reference to what is normal and what is not.

As an aside: I'm a long time and loyal Merten customer. I've been extremely happy with Merten's TechSup for a year or two, but these last times, I've been disappointed twice.
Once for the 4 gang PB that doesn't deliver status when associated with a dimmer and now, about my question:
"Is it possible to upgrade that device ? if yes, how can I do it".
I didn't get a to-the-point answer, except that I should load 3.0 because it is compatible with my device. Imho, a bit short and not very technical. Is this the Schneider effect ?

Warm regards from a hot Midi-Pyrénées
Raymond

[HartmutB]

Hi Hartmut,

It's always a pleasure to see that someone on the forum cares of my problem

You are welcome. We all here depend on others to share experiences - own problems or others.

Hi Hartmut,
That is, I've loaded 3.1 and it seems to work, at least, I don't see error messages, nor in ETS, nor on the device itself, but I'm still in doubt as I've no reference to what is normal and what is not.

I didn't get this at first time: Appyling the application to the device worked and the device (seems to) work OK ?
If it is only a hint in the ETS similar to this one,

then you don't have to worry. If the application didn't match the hardware of the device, the device would fail at startup time and show an "ERR xxx" in the display. Because of this happening not before the moment you transfer the application, it just might be a hint to check before spending the time configuring the settings and losing all work when changing the application later.

I agree with you, that is is user unfriedly to be unable to check the hardware version before selecting the application.


Regards,
Hartmut

[Warichet]

You are welcome.

Hi Hartmut,

I've a minor annoyance with this 628846.
I've programmed the display in mode d12, (page 43).
Hence the display is alternating between:
temp int,
temp ext,
time.


I like it very much, but....at each re-programming of the device, it looses the d12 setting of the display and I've to re-programm it manually, from the front panel .
Is this normal / abnormal ? do you have the same experience ?
imho it should be possible to program these settings via EIB, but I don't see where.
Of course, if I didn't enable the ad-hoc mode, I don't see the correspondings KOs.

Also, I'm unable to display the external temp , although I've linked with a GA that contains this ext temp (which I can read with the ETS monitor and which is displayed correctly in the HS Visu.

Could it be that I'm already bumping in the limitations of an "old" hardware version ?

Greetings from Midi-Pyrénées

[HartmutB]

Hi Hartmut,
I like it very much, but....at each re-programming of the device, it looses the d12 setting of the display and I've to re-programm it manually, from the front panel .
Is this normal / abnormal ? do you have the same experience ?
imho it should be possible to program these settings via EIB, but I don't see where.
Of course, if I didn't enable the ad-hoc mode, I don't see the correspondings KOs.

You should be able to set this in ETS, there is a parameter "display mode". Are you just setting the display mode via keys of the device ? Then of cause it will be overwritten with the default settings of the ETS parameters after programming.

Also, I'm unable to display the external temp , although I've linked with a GA that contains this ext temp (which I can read with the ETS monitor and which is displayed correctly in the HS Visu.

No idea, I'm just toggling between temp wanted, temp actual and time. Works for me. FYI: Time isn't polled by the device and has to be "pushed" on the bus to be used. Maybe you have to push ext temp on a 5min basis or something similar on the knx bus, too.

Could it be that I'm already bumping in the limitations of an "old" hardware version ?

Don't think so.


Just to clear up: I don't use a 6288xx, but I think, the software is the same in all newer RTCUs independent of design (I'm using System-M 6232xx and 6236xx, both have application 1814/3.0, too - I think).


Regards
Hartmut

[Warichet]

You should be able to set this in ETS, there is a parameter "display mode".

INDEED I overlooked it. Thaaanks

Are you just setting the display mode via keys of the device ? Then of cause it will be overwritten with the default settings of the ETS parameters after programming.

Yes, sure you are right.
You know what ? I RTFM and thought it was OK

Maybe you have to push ext temp on a 5min basis or something similar on the knx bus, too.

Aah ?!? maybe, good idea
But as I can read it via the ETS monitor and the HS2 is getting it right, I thought it was OK, unless the HS2 is able to poll on demand ?

Thanks a lot Hartmut

[Warichet]

Maybe you have to push ext temp on a 5min basis or something similar on the knx bus, too.

Hé, hé
The Viessmann Vitocom 200 has a parameter on Datenpunkt 1 "zykluszeit"
set it to 5 min
bingo

Thanks again