[Info] [Erfahrungsbericht] Powerline an VDSL 35b: FRITZ!Powerline 1220 vs. devolo Magic 2 – massive Unterschiede bei DSL-Störungen und eine Lösung

[wg2003]

Hi

If the VDSL Performer status is 'yes', then I presume your Devolo are communicating with the Fritzbox via TR-064. However, at some point in FritzOS, I remember I had to activate TR-064 (it was as a separate tab), but because I'm on FTTP, I can't see it, or they have deactivated it.

You used to be able to download the support information using the Devolo app for Windows, but I don't know if it's still the case. I remember they tried to retire the Windows app in favour of Android and iOS apps because these days, most use their phones to set up everything.

I'm on the same version of tgc Devolo app for Android, and I use MS Outlook app as my email client. Try setting up a Microsoft email address and use the app to see if you're more successful in getting the Zip file.

 

[wg2003]

TR-064 in FritzOS is configurable in Permit Access for Apps in Home Network > Network > Advanced Network Settings

Produktentwicklungen rund um FRITZ!

Hier gibt es Informationen rund um die FRITZ!Box zu Schnittstellen und Protokollen. Wir freuen uns über Ihr Interesse! ✔

fritz.com

 

[Ganzir]

Thanks for pointing me in the right direction!

I managed to generate a ZIP file using devolo Cockpit 5.2.0.185 under Windows. The DSLCOEXISTENCE entries were indeed present in the .cld files, but Base64-encoded, which explains why my initial text search found nothing.

After decoding the files, I found the following entries on both my Magic 2 adapters (MT2999 and MT3157):

DSLCOEXISTENCE.GENERAL.ENABLE=YES
DSLCOEXISTENCE.GENERAL.RUNNING=YES
DSLCOEXISTENCE.GENERAL.GATEWAY_SUPPORTS_TR064=YES
DSLCOEXISTENCE.GENERAL.GATEWAY_COMPATIBLE=YES
DSLCOEXISTENCE.GENERAL.STATUS_CODE=-231
The diagnostics also report:

• DSL profile: 35b
• DSL link status: Up
• Gateway: Fritzbox
• DSL information queries: 53 / 43
• Measurements: 11 / 13
• DSL disconnections: 0 / 0
• Target power mask applied: YES / YES

Interestingly, both adapters report mimo_vdsl17a as their configured power mask profile, although the DSL connection uses profile 35b. The available profiles also include mimo_vdsl35b.

This is strong evidence that the adapters are actually obtaining DSL connection information from my FRITZ!Box 7690, rather than merely identifying it as compatible.

Two questions remain:

1. Do you happen to know what status/error code -231 means?
2. Is the use of mimo_vdsl17a on a VDSL 35b connection expected behavior?

In any case, thanks again for your help. Without your suggestion to inspect the diagnostic dumps, I would probably never have found this information!

 

[wg2003]

Did you change the profile on the Devolo adapters? There's an option to have either Profile 17 or 35. This is done in the Powerline settings of Devolo (I have an English version.) Please note that you would need to do it on *each* Devolo adapter, not just one of them.

Yes, the adapters query the Fritzbox for the SNR margin and, from what I remember, also errors. This influences the operational mode of Devolo adapters.

With Devolo Performer, I found the impact of powerline on my DSL line at the time minimal, if not at all.

 

[Ganzir]

Thanks for the clarification!

I checked the Powerline settings on my devolo adapters. They are currently configured as follows:

- Automatic compatibility mode: Enabled
- Transmission mode: MIMO
- VDSL profile: 17a (default)

My actual DSL connection uses profile 35b.

According to the description in the devolo web interface, automatic compatibility mode attempts to detect interference and dynamically adjust the transmission power to achieve the best possible performance without disturbing the DSL connection.

This raises an interesting question: Does the manually selected VDSL profile (17a/35b) have any effect while automatic compatibility mode is enabled, or is it only used as a fallback when automatic interference mitigation is disabled or fails?

The diagnostic dumps report "DSLCOEXISTENCE.GENERAL.RUNNING=YES" and "GATEWAY_COMPATIBLE=YES", while the configured power mask remains "mimo_vdsl17a".

So far, my VDSL connection has remained stable, with no CRC errors or errored seconds observed during testing. Cockpit currently reports approximately 341 Mbit/s between the two Magic 2 adapters.

For now, I intend to leave automatic compatibility mode enabled, since it appears to be working well. However, I'm curious whether changing the selected profile to 35b would make any difference while automatic mode is active.