Doing some holiday shopping? Please check here for shipping deadlines to make sure your order arrives in time.


Member Since: August 13, 2010

Country: United States

  • What... No love for octal? ;-)

  • Interesting discussion. 2 comments:<br />
    <br />
    1) As Linux proves (and SCO never figured out) the value is in the service and support. With some specific exceptions, open source is the way of the future, and the best way to continue to make money in the future is to provide a better level of support for what you're selling than the next guy. If someone wants to copy you, let them. They'll always be at least one step behind you.<br />
    <br />
    2) Please tell me that people really aren't trying to spam them with repeated get requests. Unless they did something tragically stupid (like firing off a new session on every get request), or you can get a significant number of people doing it, you aren't going to take them to their knees. Also most ISPs don't look too kindly at DOS and DDOS attacks. I'd recommend following SFE's lead. Take the high road, innovate and improve.

  • Couldn't agree more. Especially with D. Defensive design is something that few engineers these days are doing, and at a time when it needs to be applied even more. (Think the Apple iPhone's antenna: "You're holding it wrong." Thanks, Steve.)<br />
    <br />
    I agree with buying the eval/dev kits, but at times when that's not an option, I always point people to the reference designs and application notes. They do help fill in the blanks in a datasheet. <br />
    <br />
    Congrats on the job offer :-)

  • Add an execution path: (in case you want to use the Arduino IDE's AVRDude install)<br />
    <br />
    Windows XP:<br />
    http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/path.mspx?mfr=true<br />
    <br />
    Vista/7:<br />
    Control Panel->System->Advanced System Settings->Environment Variables<br />

  • "15,000,000+ unicorns and rainbows provided"<br />
    <br />

  • I suggested SF just because I think more people have experience with it. Google code or GitHub are equally suited for the purpose. (That is-- good, but not quite a perfect fit.) We need somewhere to do it. As I said earlier, I'd personally be more than willing to donate my time, experience and money towards a better solution, but I'd need to make sure that there's enough of a community backing it to fill in the blanks, and to help carry the load.
    (I don't disagree that SF has gone down hill as of late. They really need a way to prune all those dead projects. Yes, there really are some very actively maintained projects there. There are just far more abandoned projects than live ones.)

  • Set up an email address if anyone's interested. If there's enough demand, I'll start working on it.
    Send Ideas/comments to:
    oshw at thebecwar.com

  • I realize it's not specific to hardware designs, but SourceForge seems to offer all the options that people want. Anyone can create a project, it has great visibility within the community, there's documentation-ability (a new word I just made up), and all the other things everyone seems to want.
    OTOH, I'd be willing to do the leg work to set up some kind of portal to list the projects, but I'm not sure how big the demand is, or if there's even enough people willing to contribute to such a project. With the cost of server space and datacenter hosting, is there enough community support to fund such a project?

  • The easiest way is to use the ELM327 chip. It handles low level protocols automatically, and converts the vehicle bus to a standard RS-232 format. Otherwise you need to obtain the standards document for the bus topology you want to access (SAE, CAN, ISO) and read out the timing diagrams.
    Each bus (SAE J1850 PWM/VPW, ISO 15765-4, SAE J2284, ISO 9141-2, ISO 14230-4) has a hardware layer header for messaging, and SAE J1979 also has additional packet framing data.
    I paid for the SAE's OBD-II (J1979) standards document, but for most of the more common PIDs you can find the information you want online. If you want manufacturer specific PIDs (like Ford's internal codes for the RAP module, etc.) be prepared to have some difficulties. The individual extentions to the standards are extremely proprietary and licensing them for use can cost as much as $10k-20k.

  • Holy crap... Holy crap... Holy crap...
    I just crapped myself. I just wish I was going to be back from Iraq in time.

No public wish lists :(