Hi Mike,

=A0=A0=A0=A0=A0=A0=A0=A0Thanks for checking things out. =A0Still a work in =
progress:)

=A0=A0=A0=A0=A0=A0=A0=A0The app does provide a way for me to have different=
 protocols 'plug =

in', but =

it has not been implemented yet. =A0I hard coded the Lego and Helix protoco=
ls =

for now to get going/debuging. =A0It's shoudl be fairly easy for me to add =

more 'hard coded' protocols in the meantime. =A0 There are a few protocols =
out =

there now and I am thinking of supporting many of them. =A0( providing a wa=
y to =

have Dahsboard Controls plug in as well ) =A0I was going to add MODBUS next=
, =

but am currently trying to figure out how to include USB driver based =

protocols like phidgets.com. =A0Once I have that type of protocol working =

within my app, I can continue working on the plug-in model for other. =A0( =

althought it may be more difficult when I implement it )

=A0=A0=A0=A0=A0=A0=A0=A0As you can see from the MPLAB C code, I can configu=
re the helix =

protocol's =

packet header. =A0Currently the header includes a slaveID byte, OpCode ( =

register number ) byte, and SizeOfPayload byte ( 2 in your case ) followed =
by =

the Data Payload bytes ( 2 bytes ) and a 2 CRC checksum bytes. =A0I can set=
 the =

order in which these bytes appear in code, and also optionally use an 8 bit =

CRC. =A0So out of the box, that is the closest I could come to your protoco=
l. =A0
Is the protocol you are using some type of standard or a custom setup? =A0I=
'm =

sure we can get it going.

=A0=A0=A0=A0=A0=A0=A0=A0Do you use slave IDs?

Cheers
Lou

On Thursday 04 January 2007 05:38, Michael Rigby-Jones wrote:
> >-----Original Message-----
> >From: piclist-bounces@mit.edu [mailto:piclist-bounces@mit.edu]
> >On Behalf Of Lou - roboDNA
> >Sent: 04 January 2007 00:44
> >To: piclist@mit.edu
> >Subject: [PIC] Beta Testers
> >
> >
> >Hi,
> >
> >I am looking for some PIC users to test out a PC based
> >application I am
> >writting.  It allows users to remotely operate PIC based
> >devices from a PC
> >over RS-232, TCP/IP, 802.11.
> >
> >If anyone has a robot/device which requires a visual PC
> >interface, check it
> >out and provide feedback if possible.
> >
> >Free Download at http://roboDNA.com
> >
> >Cheers,
> >Lou
>
> Lou,
>
> The GUI looks very nice indeed, I can see a lot of hard work went into it
> and I'm keen to try it.
>
> I have a question regarding the abilities of the GUI to use custom packet
> protocols.  I have looked through the "Dashboard Designer" PDF, and saw t=
he
> support for the roboDNA Helix protocol; would it be possible for users to
> add their own existing packet based protocol to the gui, either using bui=
lt
> in functions or via some kind of plugin?
>
> The packet structure I have in mind is quite simple, 4 byte outgoing pack=
et
> followed by 4 byte response.  Each packet contains 8 bit register number,
> 16 bit data, 4 bit checksum, read/write bit and a couple of status bits. =
 I
> can give you more details if needed.
>
> Best regards
>
> Mike
>
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> This e-mail is intended for the person it is addressed to only. The
> information contained in it may be confidential and/or protected by
> law. If you are not the intended recipient of this message, you must
> not make any use of this information, or copy or show it to any
> person. Please contact us immediately to tell us that you have
> received this e-mail, and return the original to us. Any use,
> forwarding, printing or copying of this message is strictly prohibited.
> No part of this message can be considered a request for goods or
> services.
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

-- =

w: roboDNA.com
e: lou@roboDNA.com
p: 613-832-4755

-- =

http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist