Introduction and new project

[jackwall]

Well JackPott, I think I'll be just one of many many people who will be keen to see your updates, learn from your experience and get help from your updates with our own plans.

Wishing you the best,

jack

[MrProach]

Hi JackPott, how is your CANbus project going? Have you had any network up and running yet?
Ironically, I have resurrected my CANbus design as well. The current project required connecting to 19 Boeing-style engine instruments and the only sensible interfacing option I could come up with was sticking a CAN module inside each of them and daisy-chaining them.

[JackPott]

I'm not quite at the network stage yet. I had some more fundamental problems with the PIC (too much faith in the internal pull up resistors it seems) which I overcame last night. I now have a box with a knob on it that counts up and down... Network is the next step. I've narrowed down my choice of dongle to either the Lawicel or Roalan. The Roalan is a bit cheaper, and actually looks like it has a more robust driver/DLL set.

What are you using on the PC end of your network?

[MrProach]

I use my own hardware on the PC end.
If you want to avoid writing CAN code on device side you can get hardware CAN I/O devices like MCP25020 etc.

[JackPott]

I certainly don't want to get stuck in with the nitty gritty of transmission so I was planning to use a MCP2551 which looks pretty similar. Then I'm calling my message functions from ECAN.h (C1.

Not sure I'll have the interface up before I go on holiday next week so might be Feb before I get organised now. Excited, as once that's done I'll have a blueprint for other peripherals.