A DigiSnap Pro system that is not charging the batteries can be characterized by "0.0W" in the app and status emails and an ever-declining battery voltage level.
The DigiSnap Pro requires 17-30VDC on its charger input or passive power over Ethernet pairs 4,5 and 7,8 to charge the batteries. Any less than 17 volts will not charge the batteries, and more than 30 volts will damage the charger. Here are some examples of compatible chargers:
There are many things that could cause images not to transfer. For most situations, there is an error message that directly relates to the problem. Watch the app log for error messages and then look up the specific message in the error message list.
If you are using a Canon EOS 6D, no images are transferring, and there are no error messages, check that the wifi is disabled. Canon support indicates that the USB and wifi connections will not work at the same time. Unfortunately the Canon USB interface does not indicate any specific error in this case, so the DigiSnap Pro is blind to the problem--to the DigiSnap, it simply appears like there are no images on the camera. The solution is to disable the camera's wifi feature.
The DigiSnap Pro has two different types of logs and they are available various places.
Once you've obtained a log, click here for tips on interpreting error messages. We're also glad to help.
Log messages generated anywhere in the system are broadcast to the following modules:
The other type of log is a detailed log of the network module's activity. This contains details not broadcast to the other modules and can be useful for troubleshooting networking issues. This log is a text file compressed in gzip format with the filename like
Name-YYYYMMDD_HHMMSS.log.gz. In older software versions, the filename is
debug.log.gz. It can be found in the following locations:
We can help you interpret this log.
Of course, if networking isn't working, you won't be able to transfer a log to your FTP server. Here is a procedure to force the DigiSnap Pro to save a log file to a USB drive:
.log.gzfile on the drive to [email protected] and we will help you interpret it.
If you have tried to look through your own log files you may have found that they can be hard to understand.
The first step to interpreting the log files is to unzip the container file. After extracting the .log file from the log.gz container you can open it with a text editor. It will be a large messy block of text.
We have made a tool which helps to make this text more readable. Drag and drop your .log file onto the AppDebugLog.exe program, and give Windows permission to run the application if prompted. This will create a new file in the same directory with a new name of decoded.log. This file can be opened in a text editor and is much more readable.