From owner-freebsd-questions@FreeBSD.ORG Mon Sep 5 09:18:46 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A5E8916A41F for ; Mon, 5 Sep 2005 09:18:46 +0000 (GMT) (envelope-from glenn@antimatter.net) Received: from cobalt.antimatter.net (cobalt.antimatter.net [69.55.224.239]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5B57D43D4C for ; Mon, 5 Sep 2005 09:18:46 +0000 (GMT) (envelope-from glenn@antimatter.net) Received: from glenn-mobile.antimatter.net (cpe-66-27-86-22.san.res.rr.com [66.27.86.22]) (authenticated bits=0) by cobalt.antimatter.net (8.13.4/8.13.4) with ESMTP id j859IfUK023947 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 5 Sep 2005 02:18:42 -0700 X-MailKey: purple frogs are falling from the sky Message-Id: <6.2.3.4.2.20050905014920.06c83620@cobalt.antimatter.net> X-Mailer: QUALCOMM Windows Eudora Version 6.2.3.4 Date: Mon, 05 Sep 2005 02:18:30 -0700 To: "Paul Hamilton" , From: Glenn Dawson In-Reply-To: <043801c5b1f1$0d0281f0$6600a8c0@w2k2> References: <043801c5b1f1$0d0281f0$6600a8c0@w2k2> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Cc: Subject: Re: Serial Port data dumping program X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Sep 2005 09:18:46 -0000 At 01:08 AM 9/5/2005, Paul Hamilton wrote: >Hi, > >I am trying to debug a Mini SSC FreeBSD program that I am trying to write. >It would be nice to be able to be able to see what is being transmitted. It >would help in the debugging of my program. > >Here is a link to a Windows based Mini SSC program: >http://www.rentron.com/Mini-ssc.htm Using this, I can control the servo, so >I know the hardware and cables work etc. > >I have been using the 'minicom' port to dump the received data. However, it >doesn't seem to collect the data properly. Data coming in should be in >accordance with the SSC protocol, ie: > >byte 1: 0xFF // sync byte > >byte 2: 0x01 - 0x25f //servo address How do you fit 0x25f into a single byte? (I count 10 bits required) >byte 3: 0x00 - 0x255 // servo position Same question as above. >Here is a dump of the collected data (via minicom): > >#hexdump minicom.cap >0000000 45ff 49ff 4cff 50ff 53ff 57ff 5aff 57ff >0000010 53ff 50ff 4cff 49ff 45ff 45ff 01ff ff82 >0000020 8101 01ff ff80 8202 02ff ff81 8002 03ff >0000030 ff83 8203 03ff ff81 8003 7fff 7fff 7eff >0000040 01ff ff7f 7f02 03ff ff7f ff7f 8001 02ff >0000050 ff80 8003 04ff ff80 ff80 8006 07ff 0080 > >Looking at the first row of data, it is only showing two bytes, sync and >servo position. Rows 020 and 030, shows some servo addresses, but >sometimes, together! Both the mini-ssc.exe and minicom program are using >9600 8n1, so why is it showing this? Is there something I have missed in >the setup of minicom? Looks like this is a serial buffer problem. You probably have byte ordering issues. Does something like this look more reasonable? 0000000 ff45 ff49 ff4c ff50 ff53 ff57 ff5a ff57 0000010 ff53 ff50 ff4c ff49 ff45 ff45 ff01 82ff 0000020 0181 ff01 80ff 0282 ff02 81ff 0280 ff03 0000030 83ff 0382 ff03 81ff 0380 ff7f ff7f ff7e 0000040 ff01 7fff 027f ff03 7fff 7fff 0180 ff02 0000050 80ff 0380 ff04 80ff 80ff 0680 ff07 8000 -Glenn >Is there a better program I could use to display the incoming serial data in >hex? > >NOTE: I only use two wires, signal ground and Tx Data (connected to the Rx >Data). The servo does respond correctly, so I know the serial data must be >in the correct 3 byte format. > >Looking fwd to your thoughts. > >Cheers, > >Paul Hamilton > >_______________________________________________ >freebsd-questions@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-questions >To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"