Luis Moreira wrote:
> A friend of mine as asked me to have a look at a couple of car seats he
> got for is "project car", which are all motorised and have a CAN Bus
> embedded for communications between the seat controller and the motor
> controllers. The seat's motor for movement forward and back is optional
> and he asked me if I could clone one of the existing motors and
> controller to use for that function. They were manufactured by Recaro
> the model is DSE and date of manufacture is 1997.
> I manage to interface into the CAN bus and I can read all the messages
> on the bus I even manage to send messages to some of the motors by
> mimicking the data sent by the controller. But without knowing the
> specifications of the messages being sent is very difficult to develop a
> clone that will do the job. I manage to figure out the message
> identifiers, and I even found which nodes are receiving and answering
> back, but without the message implementation structure, is getting
> difficult to work out how to control the motors properly.
> I was wandering if anyone would have or know where or how I could get
> this info. I am not looking for the CAN message specification, as I know
> that, but instead I am looking for info on how the data part of the
> message is structured.
>
> These motors have a built in controller with CAN interface and were
> built by Bosch, I wander if they are standard and used somewhere else...
>
> We already tried Recaro but, as not many of these seats were made do to
> complexity and cost, they claim not to have that information anymore.

Luis,

Reverse engineering the protocol shouldn't be too difficult. Can you post 
what you're seeing, in response to different actions (move seat forward @ 
max speed, move it back @ max speed, etc)?

Vitaliy 

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