That is very interesting & does indeed suggest that your experimentation does deliver the required outcome. i.e. increasing SNRM & lowering sync speed accordingly.
My query is have you ever been able to lower SNRM below 6dB in order to further increase sync speed?
My connection never drops below 5.5dB SNRM these days & even when it was in need of repair it would still be useable with SNRM occasionally into negative values.
Using my HG612 modem, I have been unable to lower SNRM or increase sync speed at all from whatever the connection negotiates at resync time.
Using the SNRM tweak command, the connection does resync, but SNRM & DS sync speeds don't really alter at all.
I would like to be able to at least test my connection at 3dB SNRM if at all possible.
I notice that US bitswap changes to OFF at the higher DS sync speed/lower SNRM.
I wonder if that actually has any relevance or not?
Yes, I have tested (accidentally) at 3dB a long while ago, as I was trying an offset above 100 and it just made it the lowest possible instead. The connection was a little unstable though (loss of sync at one point and more CRC errors). I haven't got a screenshot to prove this sadly, so you'll just have to take my word on that.
My connection usually stays within -0.5 to +0.2 of the original sync'd SNRM, depending on crosstalk (unless an engineer is in the cabinet fiddling around with wires for reasons such as setting someone up on Infinity, in that event I either get a nice increase in SNRM or a horrid drop in SNRM).
I haven't found a working way to do what can be done on the FB7390 on the HG612. On the FB7390 it seems fairly painless and easy. I am going to leave it connected so long as it remains stable (e.g. no crashes, no sudden reboots, no loss of sync) and will eagerly await to see if DLM adjusts my INP from 4 to a lower value, eventually. I expect DLM to intervene and reduce max/min rate on the downstream however, due to my reduced speed as a result of an increased SNRM.
I've found the FB7390 handles bitswap in a way that it's off when you first sync, but it switches on if it encounters a certain level of errors (at least from my observations, perhaps there's another cause I'm not aware of).