Testing different bs_param settings (TC) and so far so good. Had a massive drop in tone around the usual tones that I seem to be effected by and I did get a spike in FEC, and the tone hasn't recovered yet but it's not continually rising by thousands per second.
Early days but might've found a temporary solution, will update later but I expect it'll go wrong sooner or later .
EDIT 1:
The initial effected tone did recover a while ago, other tones have fluctuated since then and I've had over 1 hour and 47 minutes of uptime and I've so far had 31,388 FEC errors with 77 FEC seconds on the downstream, all going fine and no continuous FEC by the thousands every second so far. The bitloading isn't having the previous behaviour I described in an earlier post where it seemed to be one step behind in its actions against tones, which I think I may have found the culpret for (and may well have been why errors happened more seriously). If you think about it, having a delayed action of one step behind meant that a further decrease in the bitloading effectively wasn't possible until more SNRM was lost or if SNRM on the effected tone increased (like I was seeing happen, if a tone recovered SNRM then the tone would lose one more bit).
Default bs_param:
My bs_param:
Notice 'bs wait_num', was 1 and is now 0. I believe this is responsible for the delayed action it is currently taking. If I'm right then setting this to 0 means it will not be delayed one step behind in the actions that bitswapping should be taking. Will need more time, I've been fooled a few times by this device (into thinking I've found a solution then later on I find out I haven't).
Early days but might've found a temporary solution, will update later but I expect it'll go wrong sooner or later .
EDIT 1:
The initial effected tone did recover a while ago, other tones have fluctuated since then and I've had over 1 hour and 47 minutes of uptime and I've so far had 31,388 FEC errors with 77 FEC seconds on the downstream, all going fine and no continuous FEC by the thousands every second so far. The bitloading isn't having the previous behaviour I described in an earlier post where it seemed to be one step behind in its actions against tones, which I think I may have found the culpret for (and may well have been why errors happened more seriously). If you think about it, having a delayed action of one step behind meant that a further decrease in the bitloading effectively wasn't possible until more SNRM was lost or if SNRM on the effected tone increased (like I was seeing happen, if a tone recovered SNRM then the tone would lose one more bit).
Default bs_param:
Code:
cur bs trigger snrm diff = 3. 0(dB)
cur bs snr_record_tone_num = 128 bs wait_num = 1
cur bs scan_start_tblidx = 1 bs scan_end_tblidx = 256
My bs_param:
Code:
cur bs trigger snrm diff = 3. 0(dB)
cur bs snr_record_tone_num = 128 bs wait_num = 0
cur bs scan_start_tblidx = 1 bs scan_end_tblidx = 256
Notice 'bs wait_num', was 1 and is now 0. I believe this is responsible for the delayed action it is currently taking. If I'm right then setting this to 0 means it will not be delayed one step behind in the actions that bitswapping should be taking. Will need more time, I've been fooled a few times by this device (into thinking I've found a solution then later on I find out I haven't).
Last edited: