03-21-2020
10:03 PM
- last edited on
03-21-2020
10:43 PM
by
RogersMoin
Isn't the Hitron CODA-4582U running Linux? Unless this is using the Intel Puma which is not very good.
It would be nice to give SSH to the modem so we can see what the kernel says on while on the beta program so technical people can see what the kernel is saying, don't need root but the ability to read syslog, kernel dmesg assuming these are running Linux, would be easier to give you more detailed info vs vague reports...
I am hoping the 7.1.x firmware has (again assuming Linux kernel) a newer kernel since 2.0.10.36T6 has packet loss for me with low latency, this is pinging the endpoint gateway on your end < 10ms on avg should not have packet loss, reboot modem and it is corrected until it starts happening again sometimes after a day or two.
Here's my modem levels, RX is ok, assuming same spec ranges, when I worked for Shaw RX should've been closer to 0 dBmV so -15 to +15 is within spec.
TX is a bit low
Only log concerned with is: No Ranging Response received - T3 time-out often...
Port ID | Frequency (MHz) | Modulation | Signal strength (dBmV) | Channel ID | Signal noise ratio (dB) |
1 | 597000000 | 256QAM | 8.400 | 8 | 38.983 |
2 | 849000000 | 256QAM | 12.200 | 2 | 38.983 |
3 | 855000000 | 256QAM | 12.200 | 3 | 38.605 |
4 | 861000000 | 256QAM | 12.300 | 4 | 40.366 |
5 | 579000000 | 256QAM | 8.000 | 5 | 38.605 |
6 | 585000000 | 256QAM | 8.300 | 6 | 38.983 |
7 | 591000000 | 256QAM | 8.200 | 7 | 38.983 |
8 | 279000000 | 256QAM | 4.600 | 1 | 38.983 |
9 | 603000000 | 256QAM | 8.800 | 9 | 38.605 |
10 | 609000000 | 256QAM | 9.500 | 10 | 38.983 |
11 | 615000000 | 256QAM | 9.700 | 11 | 38.983 |
12 | 621000000 | 256QAM | 9.700 | 12 | 38.983 |
13 | 633000000 | 256QAM | 9.800 | 13 | 38.983 |
14 | 639000000 | 256QAM | 10.000 | 14 | 38.983 |
15 | 645000000 | 256QAM | 9.900 | 15 | 38.983 |
16 | 651000000 | 256QAM | 9.900 | 16 | 38.983 |
17 | 657000000 | 256QAM | 9.900 | 17 | 38.983 |
18 | 663000000 | 256QAM | 9.900 | 18 | 38.983 |
19 | 669000000 | 256QAM | 10.300 | 19 | 38.983 |
20 | 675000000 | 256QAM | 10.100 | 20 | 38.605 |
21 | 681000000 | 256QAM | 10.400 | 21 | 38.983 |
22 | 687000000 | 256QAM | 10.600 | 22 | 38.983 |
23 | 693000000 | 256QAM | 10.300 | 23 | 38.605 |
24 | 699000000 | 256QAM | 9.800 | 24 | 38.983 |
25 | 705000000 | 256QAM | 9.700 | 25 | 38.983 |
26 | 711000000 | 256QAM | 9.500 | 26 | 38.605 |
27 | 717000000 | 256QAM | 10.200 | 27 | 38.983 |
28 | 723000000 | 256QAM | 10.300 | 28 | 38.983 |
29 | 825000000 | 256QAM | 12.000 | 29 | 38.605 |
30 | 831000000 | 256QAM | 11.600 | 30 | 38.983 |
31 | 837000000 | 256QAM | 11.500 | 31 | 38.605 |
32 | 843000000 | 256QAM | 11.100 | 32 | 38.983 |
Receiver | FFT type | Subcarr 0 Frequency(MHz) | PLC locked | NCP locked | MDC1 locked | PLC power(dBmv) |
0 | NA | NA | NO | NO | NO | NA |
1 | 4K | 275600000 | YES | YES | YES | 5.300003 |
Port ID | Frequency (MHz) | Modulation | Signal strength (dBmV) | Channel ID | Bandwidth |
1 | 30596000 | ATDMA - 64QAM | 34.000 | 3 | 6400000 |
2 | 36996000 | ATDMA - 64QAM | 34.000 | 4 | 6400000 |
3 | 22100000 | ATDMA - 64QAM | 35.500 | 1 | 3200000 |
4 | 25300000 | ATDMA - 64QAM | 36.250 | 2 | 3200000 |
Channel Index | State | lin Digital Att | Digital Att | BW (sc's*fft) | Report Power | Report Power1_6 | FFT Size |
0 | DISABLED | 0.5000 | 0.0000 | 0.0000 | -inf | -1.0000 | 4K |
1 | DISABLED | 0.5000 | 0.0000 | 0.0000 | -inf | -1.0000 | 4K |
03-22-2020 02:35 AM
03-22-2020 10:17 AM
03-22-2020 06:30 PM - edited 03-22-2020 06:30 PM
I'm hoping they will not roll this beta out if there's that many issues still. Put it on hold, iron out the issues currently reported.
Just joined the program but I'd rather not have a very buggy firmware/OS release if it's not 'beta' quality vs alpha.
Unless Rogers wants to send me another modem for testing 😄
03-23-2020 09:24 PM - edited 03-23-2020 09:25 PM
Is there any special trick to triggering the firmware update? I had asked to join the trial about 7 days ago now, gave my CODA modem serial number and MAC address but I haven't had the firmware pushed out as of yet. Thanks all for you help and suggestions in advance, stay safe out there.
03-29-2020 04:43 PM
03-29-2020 06:05 PM
03-29-2020 06:50 PM
03-29-2020 07:56 PM
03-29-2020 07:59 PM