2GIG GC2 panel firmware update failure

[nakapako (Dante)]

Attempting to update new GC2 panel (fw 1.19) to latest firmware but panel never connects. Followed video instructions to install FTDI drivers for the USB cable, specified correct COM port in the executable command line in the flash shortcut but flash panel just shows “pinging” and “no panel”. Tried on 2 different PCs (Windows 7 and Windows 10) but same issue. Possible that cable is bad?

Thanks,
db

[rreynolds (Roy)]

It’s possible but there are several other possible issues as well. First, I assume you’ve seen this video? If not, definitely check it out.

How to update the firmware on your 2GIG Go!Control Panel

Also, make sure to read the notes underneath the video on this page to get the right firmware files. That video is a bit old.

The problem is often that the cable is not reliably connecting to the panel, the cable is inserted backwards (if the tab is broken), or the panel isn’t being powered complete down before starting the process.

Unable to update Firmware

Followed the YouTube videos which show you how to find the USB port and correctly label the files, etc. A couple things to make sure: Be certain you are creating a shortcut and adjusting the target line of the shortcut, not the primary file location. Make sure that the panel is powered down completely. The panel must have no power, including battery. The software then finds the panel once you plug in the panel power supply.

2Gig Firmware Update Issues

It appears the issue was with a loose cable on the 2nd PC. Once the cable was taped in place, the updater was able to ping the control panel. I was then able to flash the firmware from version 1.10.1 to 1.12 successfully. Once that was complete the 1.13.1 update and then 1.19 update both worked.

If you can upload a photo of how you have the cable connected to the panel that may help. If we try everything else and the cable appears to be defective, we can always replace it with a new one to see if that helps.

[nakapako (Dante)]

Thanks for the response. My efforts are based on the video and webpage you referred to. I’ve tried again this morning and attached links to photos below:

https://photos.google.com/photo/AF1QipPND8NSUcxm2a89i8TV5A-YCSdbWajpqQ12sIYX
https://photos.google.com/photo/AF1QipPPkSjFPXMSUswUM_iN6V8fqjSsw5EBkZKOXs-1
https://photos.google.com/photo/AF1QipO-MLLa4HY04C2TNdHBZEvrBNBuvQgFFYVqLrp2

Thank you,

db

[nakapako (Dante)]

Here’s the rflashd_20.log if it helps:

12/08/19 10:27:36: RFLASHD v2.31 (cp1_arm7_PRODUCTION_17202_V1.19.3_en-US COM20) Nov 1 2018 08:02:38
12/08/19 10:27:36: VersionEx: (Ver 6 1) (SP 1 0 Service Pack 1) Suite 0100 ProdType 0001
12/08/19 10:27:36: COM port: 20
12/08/19 10:27:36: update_all_resources 1
12/08/19 10:27:36: Initializing for COM20
12/08/19 10:27:36: comm_prop.dwMaxTxQueue 0
12/08/19 10:27:36: comm_prop.dwMaxRxQueue 0
12/08/19 10:27:36: Rx Thread Created 0x00000140
12/08/19 10:27:36: A6A27737 Ver 01 Platform 01 Target 03 Tool 01 Resource Table Address 00008000
12/08/19 10:27:36: Task Count: 21
12/08/19 10:27:36: 000 0x0003 16257 ALARM 0x0025B000 0x00D013 05BF
12/08/19 10:27:36: 001 0x0004 16257 DIAG 0x00269000 0x03108B 21FB
12/08/19 10:27:36: 002 0x0005 16187 IOP 0x0029B000 0x006317 69EC
12/08/19 10:27:36: 003 0x0006 16187 LCD 0x002A2000 0x001910 78FE
12/08/19 10:27:36: 004 0x0007 16257 PANEL 0x002A4000 0x013F38 1C78
12/08/19 10:27:36: 005 0x0008 16187 RM_UART 0x002B8000 0x005FF7 E826
12/08/19 10:27:36: 006 0x0009 16187 REPORT 0x002BF000 0x011333 ECF6
12/08/19 10:27:36: 007 0x0010 16257 SENSORS 0x002D1000 0x00CB8B 4493
12/08/19 10:27:36: 008 0x000A 16187 XCVR 0x002DE000 0x00B7C0 5B20
12/08/19 10:27:36: 009 0x000B 16257 SOUNDER 0x002EB000 0x00A3A7 A56A
12/08/19 10:27:36: 010 0x000C 16187 UPDATE 0x002F6000 0x006639 C563
12/08/19 10:27:36: 011 0x000D 16187 ZWAVE 0x002FD000 0x0269BB C701
12/08/19 10:27:36: 012 0x000F 16257 SYNC 0x00325000 0x00D9CB BDBE
12/08/19 10:27:36: 013 0x0011 16187 EB 0x00334000 0x0021F9 CB96
12/08/19 10:27:36: 014 0x000E 16429 UI 0x00337000 0x124820 0E5F
12/08/19 10:27:36: 015 0x0013 16429 UI_EXTENSION 0x00467000 0x01F86C FA70
12/08/19 10:27:36: 016 0x7000 06189 RADIO_MODEM_0 0x0009B000 0x075AC6 020A
12/08/19 10:27:36: 017 0x7001 00100 STUB_RM_1 0x00113000 0x000619 E849
12/08/19 10:27:36: 018 0x7002 00100 STUB_RM_2 0x0015B000 0x000301 CB9D
12/08/19 10:27:36: 019 0x7003 00400 RM_SECURENET 0x0019B000 0x03CD22 1D0C
12/08/19 10:27:36: 020 0x7004 00100 STUB_RM_4 0x001DB000 0x000301 4111
12/08/19 10:27:36: Resource Count 685

[jwcsurety (Jason)]

On your 2GIG Panel, can you go to the Version page (Security > Menu > Toolbox > Master Code > Scroll Right > Version) and post a photo of what you see there?

Also note the exact firmware version if it is not visible in the image (it scrolls left due to its length)

[nakapako (Dante)]

I’ll do that when I’m home later today. My panel is now online with surety/alarm.com. Can the fw be upgraded OTA?

Thank you,

db

[jwcsurety (Jason)]

Ah, yes if you are already up and running, yes, firmware can be pushed OTA. I’l get that started for you now. It is a minor version update so it shouldn’t take as long as normal, but note that cellular updates often take 3-12 hours to complete depending on signal and size of the update.

Please remain out of programming and do not power down the panel until this is complete. You should see version 1.19.3 when done.

[nakapako (Dante)]

Appreciate that. Is there a notification on the panel when the upgrade is complete?

Thank you,

db

[jwcsurety (Jason)]

There is no dedicated notification from the panel no, though in most cases the panel will restart the security process and may reboot, which will result in announcing its arming state again.

I can tell you though that it shows in Alarm.com that it has finished already and the firmware is 1.19.3.1. You should be good to go!

[nakapako (Dante)]

Awesome! Thanks so much.

db