Motorola V3i Firmware

[Mara Ermogemous]

Ifu think throwing out a perfectly good piece of hardware because of 'communication' issue is a smart thing to do, who's to say that future new configuration changes won't be communicated clearly to your new modem vendor - Xfinity themselves included - also?

The free modem WOW provides with the 1.2gig service has been working great and I haven't had a disconnect since activating it. The new mb8611 will arrive on Tuesday and if I activate it, I'll report back with how well it works/doesn't work.

So far, no issues at all. Still using my same router and networking equipment.

I only plan to use the modem they gave me for a few weeks before I'm convinced this is being done on purpose. In the meantime, I plan to contact Motorola next week as well to see what they can do.

Please redact all of the CM MAC and the CMTS MAC addresses in your error log entries for your privacy. They are considered to be personal information. The posting of personally identifiable information is a violation of their forum guidelines. The forum bot will not allow your post to be seen publically. It flagged your post as "Private".

A non-technical reason: a person works from home or is just not interested in having their internet drop out every 5 minutes while we wait the weeks or months it takes Motorola and Xfinity to stop pointing fingers at each other and actually fix the problem.

Unfortunately, switching hardware or internet providers is the only solution available to users that they fully control. It would be great if there was a customer configurable way to install a firmware version and also prevent automatic updates, but there doesn't appear to be one. If Xfinity wants that ability to update, then they need to take responsibility for fixing issues when auto update creates widespread problems like this.

On February 1st, my modem rolled back to version 19.2.18 and stayed there. Didn't have any more drops except one, which seemed to be an actual outage. On February 16th, it upgraded to version 21.3.7 again and the drops came back. Motorola finally got me my replacement modem, which I've swapped out today. After activating, it's running version 19.2.18.

Mine was still rebooting with new firmware(or rolled back one). Bought an arris s33 so far no reboots. Looks like some of those are starting to have issues also. I think it depends where you live which modem works better. Motorla did ship a refurb unit(1st unit was only 40 days old) and it still had rebooting issues even on 19.2.18. Live in clinton township michigan. New modem and 2nd never made a full day on either modem being up. Longest i think i logged was like 18 hours. It was going on for over 2 months until i switched. It is something to do with comcast systems not playing good with motorolas and now some of the arris's.

Good to hear that the Arris has been stable for you. I went through lots of problems sorting out my internet on my own. Support wasn't much help except to blame Motorola and rebooting the modem. I got Motorola to send me a new modem, but that was even flakier than the one I already owned so I sent it back. I would always lose DS locks a few days after a reboot but I just lived with it. Then we had a pretty big outage last December of about 2.5 days. When internet was restored, I noticed that the signals were better than before and I had a new firmware (21.3.7). It was very stable until last week so I was happy with the last firmware. I think Xfinity took the opportunity to do some maintenance that improved the signals while they were down. Anyway, I'll see how this rollback holds up.

I'm in need of the latest firmware image and manufacturer CVC for the Motorola SB6120 series modems. We're an Arris shop with C4c CMTS's and we stock Arris 2.0 and 3.0 modems for our customers. However we recently turned on upstream channel-bonding and now there's a handful of customer-owned SB6120's with older firmware that won't sync up to the bonded upstreams. I know it's firmware because there are a bunch with a later version that are working fine and bonded 4x4.

I would try getting a login to the motorola firmware site digitalcm.com takes about a day and then you would have access to them for the future. If you still can't get them message me and I will download them for you.

I got things worked around now.. have to feed the non-functional 6120's a 1.0 config file with the appropriate upgrade filename and CVC. Then once they're upgraded they can be put back on a 1.1 config and can then do 4x4 bonding.

Hi,

can someone send me Motorola SB6120E ("E" may special for Turkey, could not find any where.) firmware and othere required files please.

mail: onlynewuser [at] gmail [dot] com

thanks.

Performed wireless survey of warehouse area. Freqency and power planned to minimize interference, so surveys look good. I'm not seeing much external 5GHz interference. Using 20Mhz channel widths. We were not noticing these issues a few months prior.

I have other deployments of similar scan guns running on Meraki with same firmware but model APs. Trying to isolate the issue between a wireless issue or a scan gun hardware/software issue. AP utilization looks to be good. From controller, ping response show similar results as reported above with 0% loss rate.

We went through and disabled all the power saving settings on the device. I can ping from the device and the pings aren't lost, just very high latency. I would think if it was going into power saving mode, then I would start to drop packets or see disassociation from the AP.

Your device is probably using "Wifi Power Saving Mode (PSM)". With this the device tells the AP it is going to sleep (for say 100ms). The AP then buffers all the packets. The device then says "I'm awake now", and sends those packets.

"The only time I have found that CAM mode helps is when the APs do not play well with the power saving schemes on the device. CAM mode is a good test if you are having network issues. If it fixes a problem, it's worth investigating to find out why. There may be some AP settings or firmware updates for the APs or the device that might make power saving mode work properly. I try not to use CAM mode in production unless it is the only way to make things work."

I don't agree with the post however. The client has to request the power saving mode. If the AP is capable it can agree, and then it needs to buffer the packets. The AP firmware should not have much impact on the client making the request, or the amount of time that the client is requesting the sleep period to be.

The fact that I have high latency just to the local gateway with the scan guns but no other devices indicates a wireless issue with the scan guns. We have another location using similar hardware connecting to the same server who are not experience issues. Since it is a remote site, its taking some time to get a user to run similar testing for me there as a comparison (pings to gateway for example).

We have some Intermec/Honeywell scanners + ARM based devices and an update to 26.6.1 appears to be causing a similar issue - loss of WiFi signal, RDP connections freezing and disconnecting, and high latency.

We switched two guns to CAM mode. The battery only lasted 2-3 hours each time, but we did not have the disconnects like we were having. Since I was not onsite, I was unable to test the latency from the gun like I did before which will have to wait until I'm back onsite in a couple weeks.

@Echopath the issue I was having it was seen by simply unplugging the power supply. This caused the Windows power profile to change and in the battery profile an element of power saving was enabled. Within 5 seconds the pings went up massively, no idle time!

You will want to connect it to your PC via ActiveSync (a charging station with a USB connection to your PC) and then just use Windows Explorer to copy over the .CAB file you received from Symbol/Motorola to your scanner. Once the file is on the scanner, just click on it and it should install. The hard part is navigating the Motorola/Symbol support website. It is very fragile at best and completely unresponsive or down most of the time.

Thanks everyone for the replies and suggestions. I was trying to find the firmware myself which was daunting enough. I have since found out that we have a service contract and was able to get one of those techs to send me a link to the firmware that I need. I plan on trying to get this done next Monday - fingers crossed!

The SD card slot should be underneath the keyboard. You have to take the two screws out near where the keyboard meets the screen and it should come off with a little effort. That is for MC9060,9090,and 9190 models.

Hi all,

I also had the same streaming issue with my Motorola Focus73 camera and followed the instructions above to downgrade the firmware from 03.10.18 to 03.10.11 which worked once I eventually realised I had to upload the .sig file before the .tar.gz file. As others found above, after a few minutes it upgraded the firmware back to 03.10.18.

My cameras keep saying Firmware upgrade failed after 100% upload. What am I missing? Am I doing something wrong. I have tried many times with a number of different firmwares and all have failed. Can somebody help! Motorola make me mad!

The new lens is larger than the original so I had to remove the ring around the lens opening in order to avoid a vignette effect, just pry up near the 3 pins to release this ring:

image19781522 665 KB

Since I (try to) keep my camera completely blocked from accessing the internet (who needs the Hubble app anyways), I created a sensor that becomes true if the camera manages to connect to the Hubble servers.

I took a look at my CPS cable at home and confirmed it is a PMKN4154A CPS cable, part of the HKKN4027A CPS cable kit. This confirmation is good news because it means no special cable is needed for firmware updates.

I successfully updated the firmware in my DTR700 fleet earlier this week and the channel/talkgroup scan feature works as advertised. The scan behavior appears to be identical to the talkgroup scan feature in the older DTRs.

3a8082e126