12-13-2016 11:54 AM - last edited on 12-14-2016 05:50 PM by RogersMaude
Announced 13-December-2016 by @RogersDave http://communityforums.rogers.com/t5/forums/forumtopicpage/board-id/Getting_connected/message-id/379...
Credit to @Hybrid_Noodle
Hitron website: http://www.hitron-americas.com/product/coda-4582/
Datasheet: http://www.hitron-americas.com/wp-content/uploads/2016/09/CODA-4582-Datasheet.pdf
60W Power Supply built into unit
Pictures of Hardware Version 1A:
***Added Labels***
01-20-2017 12:27 PM
My CODA white dot, no issues since day 1, no missing channel no problem with wifi, no issues with speed.
Latency is normal ( for a hiltron modem with rogers routing on D3.0)
So glad to hear I can keep it and keep receiving firmwares updates along with D3.1 eventually and it can only get better at this point.
01-20-2017 12:38 PM - edited 01-20-2017 12:40 PM
I got a cougarmountain device that is connected to my network running 4 services and got an IP out of dhcp range 192.168.0.254. I am not sure what device is this. Anyone know what is this? I got the CODA modem in gateway mode.
01-20-2017 12:58 PM - edited 01-20-2017 01:11 PM
@hptouchdroid13, Cougarmountain is the ARM processor in the chipset. Its interesting that you can actually see that. You could try a factory reset to see if that changes the end results.
01-20-2017 01:02 PM
@Datalink I see. So it is part of the CODA device? That is odd. I am currtenly connected to it thru telnet and it has a Poky linux distro in it. I will try to factory reset it then.
01-20-2017 01:03 PM
@RogersDave wrote:
@soundwave80 wrote:
Can anyone from Rogers chime in here and give us a update on what's going on with this second recall?Modems are not being recalled per say, we simply asked stores to return their current inventory so that we can perform additional testing on these modems.
We are replacing them with fully tested "black-dot" modems. Customers that already received their unit will not need to return them (unless they are experiencing an issue with the one they have).
Dave
So in other words, if a rogers store is issuing a black dot modem as of today - it's guaranteed to be from a new, properly tested/fixed stock?
01-20-2017 01:06 PM - edited 01-20-2017 01:09 PM
01-20-2017 01:16 PM
@Datalink Yes it is interesting. I am using an Android App to check connected devices in my network and reported it got 4 services runnning 23, 111, ,139 and 445 services. I will try to fatory reset it later.
01-20-2017 01:27 PM
01-20-2017 02:06 PM - edited 01-20-2017 02:30 PM
@Datalink Already factory reset the modem and the device still exist. First I am detecting it as a WPS service then I turned off the WPS and it changes to COUGARMOUNTAIN hostname. Telnet is still open. I am using Android Fing app to scan the network
@RogersDave Could you please check my modem and see if it is a possible to add it as an open issue of the hardware.
01-20-2017 02:53 PM
I see Cougarmountain in Fing as well on my Android phone, on 192,168,254
Netbios Domain Hiron, Netbios Name cougarmountain Netbios Role Fileserver
01-20-2017 03:54 PM - edited 01-20-2017 03:55 PM
I recall Dave saying that Cougarmountain is the arm cpu used in the modem and it's not an issue, however after the phantom wifi band on the previous ACR modems that has not been fixed yet and is seriously affecting the wifi performance according to some reports -- I would not be surprised to find out something other "phantom" on this new hitron.
01-20-2017 04:40 PM - edited 01-20-2017 04:44 PM
I see. I am not the only one having this issue. Now my modem keeps restarting and I don't know if someone from Rogers is checking it.
01-20-2017 05:01 PM
01-20-2017 05:08 PM - edited 01-20-2017 05:08 PM
01-20-2017 05:57 PM - edited 01-20-2017 05:58 PM
I have called several rogers stores in North York and employees are completely clueless about the recent recall, insisting the recall was 3 weeks ago and all the modems they have are with a black dot now and they are all equal. When mentioned rogers community forums, I was told "it's just a bunch of people that have no idea what they are talking about". I know, minimal wage people and stuff, but this is just wrong and insulting!
Therefore, how do I know the black dot modem they would give me is actually from the tested bunch? I don't trust them to be honest, and I want to make sure I have the latest hardware to rule out all the problems I'm having with this modem?
01-20-2017 06:26 PM - edited 01-20-2017 06:30 PM
So today, even with the black-dot, I've come to a low speed situation, and disabling 2.4Ghz does not help in this case. I'm currently getting 8 Mbps DL / 50 Mbps UL.
I know if I reboot my modem then it'll go back, for a few days.
@RogersDave When I got this modem (3rd modem) it was at .13. I wouldn't have this issue in .13, but once upgraded to .19, it will always be the DL that would go down as low as 5 Mbps.
I have a modem with the black dot.
What would be my next steps here? I'm told my downstream is looking pretty good:
Port ID | Frequency (MHz) | Modulation | Signal strength (dBmV) | Channel ID | Signal noise ratio (dB) |
1 | 591000000 | 256QAM | 2.800 | 7 | 40.946 |
2 | 567000000 | 256QAM | 2.600 | 3 | 40.366 |
3 | 573000000 | 256QAM | 2.400 | 4 | 40.366 |
4 | 579000000 | 256QAM | 3.000 | 5 | 40.946 |
5 | 585000000 | 256QAM | 2.700 | 6 | 40.366 |
6 | 561000000 | 256QAM | 2.300 | 2 | 40.366 |
7 | 597000000 | 256QAM | 2.600 | 8 | 40.946 |
8 | 603000000 | 256QAM | 2.400 | 9 | 40.946 |
9 | 609000000 | 256QAM | 2.300 | 10 | 40.366 |
10 | 615000000 | 256QAM | 2.300 | 11 | 40.946 |
11 | 621000000 | 256QAM | 2.500 | 12 | 40.946 |
12 | 633000000 | 256QAM | 3.500 | 13 | 40.366 |
13 | 639000000 | 256QAM | 3.500 | 14 | 40.366 |
14 | 645000000 | 256QAM | 3.800 | 15 | 40.946 |
15 | 651000000 | 256QAM | 3.600 | 16 | 40.366 |
16 | 657000000 | 256QAM | 3.600 | 17 | 40.946 |
17 | 663000000 | 256QAM | 3.300 | 18 | 40.366 |
18 | 669000000 | 256QAM | 3.500 | 19 | 40.366 |
19 | 675000000 | 256QAM | 3.300 | 20 | 40.946 |
20 | 681000000 | 256QAM | 3.500 | 21 | 40.366 |
21 | 687000000 | 256QAM | 3.200 | 22 | 40.946 |
22 | 693000000 | 256QAM | 3.000 | 23 | 40.366 |
23 | 699000000 | 256QAM | 2.900 | 24 | 40.366 |
24 | 705000000 | 256QAM | 2.900 | 25 | 40.946 |
25 | 711000000 | 256QAM | 2.500 | 26 | 40.366 |
26 | 717000000 | 256QAM | 3.000 | 27 | 40.946 |
27 | 723000000 | 256QAM | 2.800 | 28 | 40.946 |
28 | 825000000 | 256QAM | 1.000 | 29 | 40.366 |
29 | 831000000 | 256QAM | 0.900 | 30 | 40.366 |
30 | 837000000 | 256QAM | 0.500 | 31 | 40.946 |
31 | 843000000 | 256QAM | 0.500 | 32 | 40.366 |
32 | 555000000 | 256QAM | 2.400 | 1 | 40.946 |
Receiver | FFT type | Subcarr 0 Frequency(MHz) | PLC locked | NCP locked | MDC1 locked | PLC power(dBmv) |
0 | 4K | 275600000 | YES | YES | YES | 3.500000 |
1 | NA | NA | NO | NO | NO | NA |
Port ID | Frequency (MHz) | Modulation | Signal strength (dBmV) | Channel ID | Bandwidth |
1 | 38595824 | ATDMA - 64QAM | 37.500 | 3 | 3200000 |
2 | 30596000 | ATDMA - 64QAM | 34.000 | 1 | 6400000 |
3 | 23700000 | ATDMA - 64QAM | 32.250 | 2 | 6400000 |
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 |
Any help would be appreciated.
01-20-2017 06:57 PM
01-20-2017 10:16 PM - edited 01-20-2017 10:18 PM
Need help here please. I have a windows 10 laptop is using 2.4g wifi connection, since switched to this CODA modem it starts dorp the connection very often but since today it drops right after just connected, I tried everything with no luck, any help will be very appreciated.
I am using getway function.
01-21-2017 09:30 AM - edited 01-21-2017 09:31 AM
goodmorning @Datalink why do i keep on getting DHCP RENEW WARNING and No Ranging Response received under docs event i even seen these on the acsmr modem what do they mean
01-21-2017 10:17 AM - edited 01-21-2017 11:52 AM
After a couple of factory reset trying to fix the phantom Cougarmountain device, now my modem keeps restarting and dropping connection. And my downstream is missing some channels now.
Port ID | Frequency (MHz) | Modulation | Signal strength (dBmV) | Channel ID | Signal noise ratio (dB) |
1 | 591000000 | 256QAM | -1.700 | 31 | 38.605 |
2 | 363000000 | 256QAM | -2.400 | 10 | 36.610 |
3 | 369000000 | 256QAM | -2.400 | 11 | 36.610 |
4 | 375000000 | 256QAM | -2.800 | 12 | 36.610 |
5 | 381000000 | 256QAM | -2.100 | 13 | 37.356 |
6 | 387000000 | 256QAM | -2.500 | 14 | 37.356 |
7 | 393000000 | 256QAM | -2.500 | 15 | 37.636 |
8 | 399000000 | 256QAM | -2.200 | 16 | 37.356 |
9 | 405000000 | 256QAM | -2.400 | 17 | 37.356 |
10 | 411000000 | 256QAM | -2.500 | 18 | 37.636 |
11 | 417000000 | 256QAM | -2.300 | 19 | 37.636 |
12 | 423000000 | 256QAM | -2.300 | 20 | 37.636 |
13 | 429000000 | 256QAM | -2.100 | 21 | 37.636 |
14 | 435000000 | 256QAM | -2.500 | 22 | 37.636 |
15 | 441000000 | 256QAM | -2.400 | 23 | 37.636 |
16 | 447000000 | 256QAM | -2.400 | 24 | 37.356 |
20 | 573000000 | 256QAM | -2.800 | 28 | 37.636 |
21 | 579000000 | 256QAM | -2.600 | 29 | 37.636 |
26 | 609000000 | 256QAM | -1.900 | 34 | 38.983 |
27 | 615000000 | 256QAM | -2.200 | 35 | 38.605 |
28 | 621000000 | 256QAM | -2.100 | 36 | 38.983 |
29 | 633000000 | 256QAM | -2.900 | 37 | 37.636 |
30 | 639000000 | 256QAM | -3.000 | 38 | 37.636 |
31 | 645000000 | 256QAM | -3.300 | 39 | 37.356 |
32 | 651000000 | 256QAM | -3.300 | 40 | 37.356 |
Receiver | FFT type | Subcarr 0 Frequency(MHz) | PLC locked | NCP locked | MDC1 locked | PLC power(dBmv) |
0 | NA | NA | NO | NO | NO | NA |
1 | NA | NA | NO | NO | NO | NA |
Port ID | Frequency (MHz) | Modulation | Signal strength (dBmV) | Channel ID | Bandwidth |
1 | 38595687 | ATDMA - 64QAM | 43.500 | 6 | 3200000 |
2 | 30596000 | ATDMA - 64QAM | 41.500 | 4 | 6400000 |
3 | 23700000 | ATDMA - 64QAM | 39.750 | 5 | 6400000 |
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 |
Before it was working great, maybe the factory reset messes everything up. Off to get a new one.
01-21-2017 12:14 PM