DIGICAM ERROR LIST:

• Error 11: (divide by zero)

• Timed out waiting.. then second popup:

• The Digicam connected is not Registered…

• Error # 8002 was generated by MSComm. invalid port number

• Error 6 (Overflow)

• no Digicam connected

• could not connect to the digicam

• cannot find dmc32.dll

• Error # 55

Error 11 : (divide by zero) :

no usb serial adaptor, or it is not on com1 (must set in Device manager)  Disconnect and reconnect USB if com 1 in use.  Forcing to be com1 if listed as in use, does not work.

fixed by setting adapter to com1 and 19200 baud 8n1, no flow control.  ( flow control does not matter, tried others and all work)

Then was able to click : “download a block of profiles”

It attempts to connect to machine and check serial number.

Then got     “Timed out waiting..   ”   then second popup

“The Digicam connected is not Registered…”

Change the serial number of the Digicam, or register with Burton’s help.

Fix: set serial number to known registered serial number :

Use serial number changer program OR:

used cutecom picocom /dev/ttyUSB0 --baud 19200

and linux. Galil Commands:

LV   (lists variables)

SN=0000001217.000

BV

(set serial number, burn variables. replies with : each time)

“Error # 8002 was generated by MSComm. invalid port number”

port needs to be set to com 1 in device manager.

Note: baud and flow control seems to be set by software.  Adapter just needs to be set to COM1.

Error 6 (Overflow):

Happens when serial db9 not connected to Galil board or has a null cable (needs null adapter as well), but com1 is OK.

time out: wrong cable, machine not on.

Timeout: then “ no Digicam connected ” message:

• No serial coms.
• Bad cable, connector, null modem (it should be straight),
• dip switches set to other than 19200 baud.
• USB is OK in this case.

“could not connect to the digicam”

the digicam, not just digicam, wording important to identify this error

This happens when the software gets stuck uploading.  Issue on newer Windows versions. The software will communicate enough to get to block upload, but won’t finish.

The serial comms works with a terminal/linux, but it (the software)is wanting specifically timed replies to commands ‘:’ usually, after a \r or ST  Prolific USB-ser adapters do this.  Try FTDI?

Digicam upload (click button) checks serial number then, lets you choose file,  then sends ST (stop) command. This is the timing critical part, where it gets stuck, especially with the USB-serial adapter. It will just stick here forever.  It also might stick on the next \r that it expects a : from, this will result in “could not connect to the digicam” error

in fakedigicammachine07.py : REPLY_DELAY_SEC = 0.012  # seconds per character  this is critical.  0.012 works for two hardware serial ports (one on virtual machine).  Prolific on V-box no work with this timing. Will try FTDI.  (all_files/Circuits2009/Wright_machine/DIGICAM/New_Software/Fake_DC_machine)

“cannot find dmc32.dll”

This happens when digicam is installed on Win10. Put DMC32.dll manually in folder with digicam.exe

Error # 55

file already open.  just restart software.

Checking the usb-ser adapter in Win 10:

1. Plug in the USB-serial adapter
2. Press Win + X → Device Manager
3. Expand Ports (COM & LPT)
4. Right-click the adapter (e.g. “USB Serial Port (COM3)” )
   → Properties
5. Go to the Details tab
6. From the dropdown, select Hardware Ids
7. You’ll see something like:

USB\VID_067B&PID_2303

or

USB\VID_0403&PID_6001

Common chipsets