jim940

The base bootloader on the Arduino is at least 2Kb. Still, 16kB is good for many projects, plus we always have GCC if we need to use something else. But maybe TI will keep seeing the light and make it a 32kB code limit for CCS at the minimum at least for the Value Line chips. Jim

MSP430G2755 would be a Atmega328 ender especially if they end up making it in a DIP package. Jim

I'm reminded of Torvalds qoute on C++. Jim

I was looking at the C2K Launchpad, and was sort of disappointed they didn't go with a board that uses CAN, so decided to possibly make my own. Any ways, I did not route the LIN ports yet, I should have, but as you can see, there is quite a bit of fudging along to make it all work. It is more or less pin compatible with the regular C2K LaunchPad, except I'm using the 2 NC pins on the lower right headers to break out the CAN pins. And using a JTAG port for programming and debugging. It won't let me upload .brd files so I attached them to my website: http://www.northernd.../fil

I have a library here too with this footprint if you want ... Including a few other footprints like Aranan's A110L like in the boosterpack, OLED, LCD's etc. http://www.northernd...les/1 - Jim.lbr Jim

It might not be, because the LCD wants 5V but the LaunchPad is only 3.6V barely enough to make a proper logical "1" signal. This will work with the LaunchPad http://www.ebay.com/itm/Character-LCD-M ... 4cf98350dd Jim

I'm pretty sure, the GNDs need to be connected so the LCD and LaunchPad agree what the voltage levels are. Jim

Might be a issue of using a 5V LCD with the 3.6V Launch Pad. Also ... check to make sure the GND of the LCD and the GND of the LaunchPad are connected together. Jim

Thanks RobG, will send in the order tonight then! Jim

But it should work with SeeedStudio none the less? Jim

Tom, Its not a linear regulator, its just in a package suitable for use in where a 78XX type linear regulator would fit. It has a efficiency level of 82% when you input only 9V on the 3.3V version, and goes up from there the higher the input voltage. Most of my Web Bench designs were not that much better, and tended to be more limited on input voltage options. Jim

Added a power supply 9 to 72V and it has a switch now to select whether the input is from the 2x5 header or the terminal connection. I hand routed it in this time oPossum Might be over kill and its a tad pricy but the 78XX compatible regulator I'm looking at is: V7803W-500R ( http://search.digikey.com/us/en/product ... ND/2757923 ) So you can put in from 9 to 72 V and its all self contained, just used the regular 78XX footprint from the library though so I'm thinking that hole really isn't needed but that is okay I think. The regulators data sheet says to place a diode abov

The MSP is low power, so might as well try and keep our boosters from being power hogs with LED's hence why I left LED's out in the first place. Anyways here is the Schematic. Also added a termination resistor in case this is the last node in a line and you wanted something more permanent then Jerry rigging the resistor on the outside of the open connector. Jim booster.sch booster.brd

On Second thought ... in case you don't want to be wasting power. Booster.brd

Something like this? Jim Booster.brd

Well this is the minimalist version, the LaunchCAN still needs to be finalized in my head. None the less this one is probably what would interest people the most. If you catch any errors let me know. Pins currently used: 1 - CAN Bus Interrupt Pin 7 - UCB0 CLK 14 - UCB0 SIMO 15 - UCB0 SOMI 16 - RESET 18 - STE for MCP2525 19 - AutoBaud feature of TI SN64HVD235 And the BOM of course: [*:3u4zlitu]Microchip MCP2515 CAN Controller (MCP2515-E/SO). [*:3u4zlitu]TI SN64HVD235 CAN Transceiver (SN65HVD235D). [*:3u4zlitu]16Mhz Crystal [*:3u4zlitu]2x 22pf Capacitors [*:3u4zlit

I think this is the first time I've ever been lucky in any kind of draw. Jim

I apparently got a $5 American bill behind the LCD screen. :!!!: Jim

Thanks for the screen shot. You are right about its length possibly causing it to tip over, I will add some screw holes to mount standoffs to if not used in a enclosure, otherwise, if you installed it in a Hammond 1455C case, you'd have to use ribbon cable and not fixed headers, but you'd be able to slide it into slots that will hold the PCBs both length wise completely, and still leave you with a 20x20x41mm space for a battery pack if required. Jim

Here is the board, with the top user interface completed somewhat as a sample layout. main.brd Will get the Power and CAN over the weekend. The oddball connector at the end is a Male M12 CAN/DeviceNet sealed "micro" connector in case anyone is wondering. Currently includes a 4x4 keypad, the OLED screen (as per Bluehash's booster), and indicator lights up top (top row for GRN, bottom for RED etc). All of the keys and LED's are going to be wired up through I2C chips as mentioned above once the top is completely done. Jim

Sorry I am pretty bad at coming up with catchy names. Anyways, my proposal at the moment involves a "double" booster size of 100x50mm. Which will allow it to sit nicely in a 1455C case from Hammond as well. It will have properly broken out headers for LaunchPad Booster packs. Anyways some of the initial specifications I want on the board: [*:vili5prf]TI MSP430G2553 TSSOP-28 (or using headers to a LP) (might need something "bigger"?) [*:vili5prf]Microchip MCP2515 CAN Bus Controller aka "SPI<->CAN Bridge" [*:vili5prf]TI SN65HVD235 CAN Transceiver w/Auto-Baud Loop Back check

Good catch Tom! Jim

Yes and no, its a lot like a UART with a buffer, typically your stuck with 2-4 messages in the buffer at most with the CAN controllers I've seen. But programming wise, you check the buffer using a interrupt routine when the buffer flags a message is incoming. Even the external MCP2515 SPI<->CAN Bus has a additional pin to be connected to what ever uC's interrupt pin to flag that there is a message. So, similar to a lot of the MSP430 projects I see around here implementing the power modes, a interrupt routine that wakes up due to the CAN Bus Interrupt, would allow relatively low power

I just realized I forgot the "u" in forums. :oops: Anyways, I know more about the CAN Bus now then any other network protocol, spent a entire semester at my college studying it (first Semester of Project Design) so that when I did my project the next semester (Semester 2 we are supposed to build and make work the project) I was decently well versed in it: http://www.northerndtool.com/bionx Its Arduino I know, (don't kill me), but that is what I was asked to work with, so that is what I did. :shh: One thing that confused me as I learned about it, knowing the OSI model, is th

You'll have to use something like a MCP2515, which will convert the SPI from the MSP430 to a hardware CAN enabled port. Level shifting alone will not actually cut it for the way the CAN Bus was designed, error detection, collision detection etc is hardware not software level on every CAN Bus implementation. CAN Bus network packets (which OBD-II is just one of many subsets of message structures with known variables), are nice to work with, only oddity compared to other addressable message systems is that your not supposed to assign devices "addresses" instead CAN protocols use message ID's