Troubleshooting

Solutions for known issues concerning Docklight or Docklight Scripting.

Issue

• When monitoring a high speed communication link, Docklight consumes 100% CPU time and seems to freeze.
  Applies to: Docklight (all versions) , Article ID: dl_prb001
  --> Solution
  
  
• Docklight does not display any serial data in the communication window(s) or just displays strange characters and question marks.
  Applies to: Docklight (all versions) , Article ID: dl_prb002
  --> Solution
  
  
• I have problems using Docklight with my USB-to-Serial adapter (or: PC card, PCI board). The COM port does not work with Docklight (or: Docklight crashes / the PC reboots when trying to access a COM port).
  Applies to: Docklight (all versions) , Article ID: dl_prb009
  --> Solution
  
  
• I am using a USB-to-Serial converter for Docklight Monitoring Mode (passive RS232 monitoring). After an unspecified time, e.g. half an hour, the computer suddenly reboots / shows a bluescreen error. The USB device appears as "Prolific USB-to-Serial Comm Port" in the Windows Device manager.
  Applies to: Docklight V1.9 / Docklight Scripting V1.9 , Article ID: dl_prb025
  --> Solution
  
  
• When I try to to open a COM port in Docklight, I receive an error message "The communication port COMxxx could not be opened. Windows Error #5 - Access is denied" or simular. I carefully checked that no other application is using this COM port. I also noticed the error only appears sometimes, or using a certain Docklight version. The Windows Hyperterminal software seems to be fine, for example.
  Applies to: Docklight / Docklight Scripting (all versions) , Article ID: dl_prb028
  --> Solution
  
  
• My script stops with an error message that says "Not allowed inside the Sub DL_OnSend() or Sub DL_OnReceive() subroutine", even though the command in question is definitively not executed within a Sub DL_OnSend() or Sub DL_OnReceive() procedure. What is wrong here?
  Applies to: Docklight Scripting V1.9 (build V1.9.21) , Article ID: dl_prb027
  --> Solution
  
  
• When I am using the keyboard console function, Docklight adds a new date/time stamp before each character I type. This was different in V1.7, how can I make Docklight behave like in previous versions?
  Applies to: Docklight V1.8 / Docklight Scripting V1.8 , Article ID: dl_prb023
  --> Solution
  
  
• I use Docklight in the background. Every time new data is received, Docklight steals the focus from the current application I am using. This is really annoying - how can I fix it?
  Applies to: Docklight / Docklight Scripting (all versions) , Article ID: dl_prb024
  --> Solution
  
  
• I am using a Keyspan USA-19H USB-to-Serial adapter. When using low baud rates (e.g. 9600 baud), some of the [TX] data sequences displayed in the Docklight Communication Window are dropped and not transmitted over the serial line.
  Applies to: Docklight V1.7 / Docklight Scripting V1.7 , Article ID: dl_prb022
  --> Solution
  
  
• I cannot get Docklight to work with my EXSYS serial extension with Oxford UART.
  Applies to: Docklight / Docklight Scripting (all versions) , Article ID: dl_prb019
  --> Solution
  
  
• I am using the flow control setting "RS485 Transceiver Control - Set RTS high while sending". On the receive data stream, some characters (ASCII code 19 and ASCII code 17) are missing. What is wrong here?
  Applies to: Docklight V1.7-V1.8 / Docklight Scripting V1.7-V1.8 , Article ID: dl_prb026
  --> Solution
  
  
• I am using a COM port higher than COM16. When I save the Docklight Project File and re-open it, Docklight sets the port to COM16.
  Applies to: Docklight V1.7 (build V1.7.33) , Article ID: dl_prb021
  --> Solution
  
  
• I am using the flow control setting "RS485 Transceiver Control - Set RTS high while sending". While executing a script, Docklight Scripting forgets to reset the RTS signal to low after completing the transmission.
  Applies to: Docklight Scripting V1.6 (build V1.6.8) , Article ID: dl_prb016
  --> Solution
  
  
• When I am testing a protocol that uses only the LF character (ASCII code 10) for line break, Docklight adds a line break directly after the date/time stamp and prints the RX data in the following line. How can I change this behavior?
  Applies to: Docklight (all versions) , Article ID: dl_prb020
  --> Solution
  
  
• There is something wrong with the communication data display in Docklight Scripting V1.6.8. In HEX or Decimal representation, there are additional spaces between the HEX / Decimal numbers. When I use the (non-scripting) Docklight V1.6.8, there is no problem.
  Applies to: Docklight Scripting V1.6 (build V1.6.8) , Article ID: dl_prb014
  --> Solution
  
  
• I am trying to use the DL.UploadFile() method, but the script gets stuck at this point and no data is transmitted. Strangely enough, everything works for file smaller than 512 bytes.
  Applies to: Docklight Scripting V1.6 (build V1.6.8) , Article ID: dl_prb015
  --> Solution
  
  
• I am using the flow control setting "Manual". I am wondering... are you sure the DCD lamp is actually displaying the status correctly?
  Applies to: Docklight / Docklight Scripting V1.6 (build V1.6.8) , Article ID: dl_prb017
  --> Solution
  
  
• I am using the "Keyboard Console" and flow control setting "Manual". Even though the RTS lamp is off, the RTS line on my connector goes high after typing characters.
  Applies to: Docklight Scripting V1.6 (build V1.6.8) , Article ID: dl_prb018
  --> Solution
  
  
• I am using the DL_OnReceive() event procedure within my script. Docklight displays the following error message: "DOCKLIGHT reports: Receive sequence queue overflow. Cannot generate all DL_OnReceive() calls". What can I do to avoid this?
  Applies to: Docklight Scripting V1.5 (build V1.5.2) , Article ID: dl_prb012
  --> Solution
  
  
• I am using Docklight on a Windows version with non-latin character sets (e.g. Windows XP Chinese Edition). While editing a sequence in ASCII mode that contains character codes greater than 127, these characters are changed to NUL (ASCII code 0), or the sequence editor crashes.
  Applies to: Docklight V1.0 - V1.4 / Docklight Scripting V1.4 - V1.5 , Article ID: dl_prb004
  --> Solution
  
  
• I am using Docklight to monitor an ASCII based protocol. Each line is terminated by a single CR (Carriage return, ASCII code 13). Sometimes the ASCII display window fails to display the first character of a new line. The ASCII log files and all other representations (HEX, Decimal, Binary) are ok. How can I fix this?
  Applies to: Docklight V1.4 (build V1.4.14) / Docklight Scripting V1.5 (build V1.5.2) , Article ID: dl_prb010
  --> Solution
  
  

back to the Docklight support page

www.fuh-edv.de
Marco Flachmann und Oliver Heggelbacher - Ingenieurbuero fuer EDV-Loesungen
file: docklight/troubleshooting_en.htm
updated: 2010-03-11

Products that are referred to in this document may be either trademarks and/or registered trademarks of the respective owners. The publisher and the author make no claim to these trademarks.