[Dsctl-devel] SF.net SVN: dsctl: [135] docs/Commands.txt

[<rog...@us...>]

Revision: 135
          http://dsctl.svn.sourceforge.net/dsctl/?rev=135&view=rev
Author:   roger-linux
Date:     2007-07-28 22:14:27 -0700 (Sat, 28 Jul 2007)

Log Message:
-----------

Commands.txt: Provide documentation on some undocumented BCD996T commands. (Trivial)

Signed-off-by: Roger <ro...@es...>
Acked-by: Roger <ro...@es...>

Added Paths:
-----------
    docs/Commands.txt

Added: docs/Commands.txt
===================================================================
--- docs/Commands.txt	                        (rev 0)
+++ docs/Commands.txt	2007-07-29 05:14:27 UTC (rev 135)
@@ -0,0 +1,123 @@
+Documented commands can be found on Uniden's Website or else where on the web.
+For licensing purposes, I have not included either the BCD396T_Protocol.pdf
+or BCD996T_Protocol.pdf within Dsctl.  It's possible something within the
+first two pages might conflict with GNU Licensing.  Too add, I'm not a lawyer
+to I don't think I'd do a good job interpreting it! ;-)
+
+Here are some undocumented commands for the BCD996T (also used for BC246).
+
+So far, I have commands only used for uploading firmware used within
+BC_VUP.exe. These can easily be found using a hexeditor.
+
+The reason I ventured here, I was having severe problems uploading firmware to
+my BCD996T unit.  It seems BC_VUP.exe will upload too fast probably
+overloading the scanner input bandwidth or overloadin the scanner's cpu
+resources.  The reason I guess this, sending @115200bps with a "sleep .01"
+after each line of text within a *.scn firmware file will give me a successsful
+upgrade every time, versus using BC_VUP.exe will seemingly fail everytime with
+a checksum error.  The first time I upgraded the firmware with BC_VUP.exe, it
+took approx. ten tries.  Each try with BC_VUP.exe would seem to get better.
+
+It would be great if somebody could provide further info for the following
+commands.  However, it's no problem for me to integrate firmware uploading
+within Dsctl at the time being.  I can only provide support for other units if
+I have volunteers to test code.
+
+
+1) Commands used within BC_VUP.exe
+2) This is what is returned after firmware has been uploaded
+3) Interpretting Firmware Upgrade Process.
+
+
+1) Commands used within BC_VUP.exe
+
+	MOT - Some models might take this command?
+	
+	*OFF - Power Cycles the scanner after a firmware upgrade.
+	
+	*PGL - Clear memory???
+		10000000000?
+		11000000000 (bcd996t)
+	
+	*SCB 1 - Unknown
+
+	*SPD - Sets the baud rate 1-5
+		4 = 57600
+		5 = 115200 (bcd996t)
+	
+	*SUM - Enable Internal Checksum Calculator???
+
+	*PRG - Set the scanner in a mode to accept stdin? (ie. Accepts *.scn as input)
+		After firmware upload (S8040... line within *.scn file triggers end of
+		file?...
+	
+	*ULE - Unknown
+
+
+2) This is what is returned after firmware has been uploaded
+	
+	Returns "PROGRAM END" on completion
+
+		Returns "CHECKSUM ERROR" on fail.
+		Returns "CHECKSUM= 3A73H" on successful upload
+
+	How do we calculate checksums??
+
+	Approx upload time using a "sleep .01" per each line of text @115200bps
+	real    14m27.138s
+	user    1m14.043s
+	sys     2m15.521s
+
+
+3) Interpretting Firmware Upgrade Process.
+
+	First, check the model of the scanner as the firmware upgrade process is
+	slightly different with individual models.  (Size of Memory, ...)
+
+	Next, set/increase the speed as the default baud rate is 9600bps.  This
+	requires us to disconnect and reset to the increase baud rate.
+
+	From here, I can only guess the memory is cleared.  For some models, *SUM
+	seems to be used to activate a checksum calculator function.  It could be
+	for the bcd996t one of the *ULE, SCB 1 commands might do something
+	similar.
+
+	Send the Program command which seems to simiple let the scanner know not
+	to send a return error code on lines >87 characters and/or signal the
+	large *.scn firmware code is coming.
+
+	The last line of the *.scn firmware file seems to signal the scanner EOF.
+	
+	At this point, a checksum value is returned.
+	
+--- Begin of Snip ---
+.\xFE
+`\xF9
+\xD7y\xEB
+
+UNKNOWN COMMAND
+*MDL
+BCD996T
+*SPD 5
+SPEED 115200 bps
+*PGL 1000000000000000000
+OK
+*ULE
+OK
+*SCB 1
+SCB 1
+*PRG
+OK
+S00C0000006E480003C4003A73C9
+S214000000545555D5C555C555C555C555C555C5557C
+S21400001054557551C555C555C555C555C555C555D0
+S2140000205455754EC555C555C555C555C555C555C3
+	---omitted redundant data---
+S2140CFFC06E6E6E6E6E6E6E6E6E6E6E6E6E6E6E6E40
+S2140CFFD06E6E6E6E6E6E6E6E6E6E6E6E6E6E6E6E30
+S2140CFFE06E6E6E6E6E6E6E6E6E6E6E6E6E6E6E6E20
+S2140CFFF06E6E6E6E6E6E6E6E6E6E6E6E6E6E6E6E10
+S804000000FB
+PROGRAM END
+CHECKSUM= EC8BH
+--- End of Snip ---


Property changes on: docs/Commands.txt
___________________________________________________________________
Name: svn:executable
   + *


This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.