Has anyone else received any communication from Rigol regarding these issues?
Yes, I have. But I said I was going to post if there was any progress to report. There hasn't been.
I've had a few exchanges with my assigned support person, but to make it short in the latest message he asked if I saw the problem on my scope specifically, and he said they've not been able to recreate the problem on their units. He suggested I let the scope warm up and do a self-cal and he included a copy of the user guide.
I replied with a screen capture of the issue on my scope, along with the scope settings and signal input as he requested. I also referenced the blog again and pointed out not all units have the problem. And I pointed him to Dave's message indicating that Rigol engineering had recreated the problem and was working on a fix.
That was yesterday (11/21) in the AM. No reply on that one yet. There was no suggestion that I send him my scope, but he did say that my eval period would be extended if needed while they continue to investigate.
To avoid confusion for everyone, my case is *only* about the 5us jitter issue.