Is anyone experiencing a similar problem?
I began setting up a new ZHD520R-V2 using the application and the USB-C power cord. I started with the firmware download, and finished with a successfull sync with the ballistic data from the App. The batteries were on the charger at .5 amp and now indicate full charge. While unplugged from the USB power adapter with the batteries properly inserted, the unit will not power up. I tried both batteries with no success. With the battery in, and the unit plugged in with the USB connector, the unit will power up normally. Upon startup, I immediately unplug from the USB power and the unit will handoff to the battery successfully. The unit will even go into standby mode with a quick tap of the button and come out of standby mode back into full function while on the battery. It is only when I shut the unit down that it will not re-power up with the battery.
After the handoff the optic seems to function normally. It even indicates the batteries are fully charged as does the charger.
I am hoping this is a bug in the firmware.
I began setting up a new ZHD520R-V2 using the application and the USB-C power cord. I started with the firmware download, and finished with a successfull sync with the ballistic data from the App. The batteries were on the charger at .5 amp and now indicate full charge. While unplugged from the USB power adapter with the batteries properly inserted, the unit will not power up. I tried both batteries with no success. With the battery in, and the unit plugged in with the USB connector, the unit will power up normally. Upon startup, I immediately unplug from the USB power and the unit will handoff to the battery successfully. The unit will even go into standby mode with a quick tap of the button and come out of standby mode back into full function while on the battery. It is only when I shut the unit down that it will not re-power up with the battery.
After the handoff the optic seems to function normally. It even indicates the batteries are fully charged as does the charger.
I am hoping this is a bug in the firmware.