This wiki is not maintained! Do not use this when setting up AuScope experiments!

Differences

This shows you the differences between two versions of the page.

--- hardware:dbbc.utils_sw [2012/03/29 02:18]
Stuart Weston
+++ hardware:dbbc.utils_sw [2012/04/05 00:54] (current)
Stuart Weston
@@ Line 1: / Line 1: @@
 ====== 3rd Part Utilities and Software ======
+The DBBC Control program now has the ability to communicate via a TCP Socket on Port 4000.
 == IVS DBBC Configuration ==
@@ Line 14: / Line 16: @@
+=== DBBC Client ===
+One thing I discovered by messing around with the DBBC client is that it sends a null terminated string (\0) with a fixed length of 80 characters. When I started using nc to talk to the DBBC control Program, some commands would fail (like "load=dbbc_control_file.txt" - it would say that it couldn't find the file). If I sent the command with a null character after txt (echo -e "load=dbbc_control_file.txt\0" | nc -w 1 131.217.63.164 4000), then it would be accepted and work. Anything after the null character is ignored, and I really don't know why the DBBC Client insists on sending a full 80 character string (all after the null is some an apparently random 8-bit character, repeated).
+Jamie email 29/3/2012
+I have tested it and yes use a "\0" at the end of the string to be sent.
+Client Software from Gino: {{:hardware:dbbc_client_software.zip|}}