# Fast and easy way to a LPLC Ethernet Remote IO Rack

C

K

#### Ken E.

Curt, I just found a script on the Eagle website for reading orcad files into eagle. I am not sure if it works, but its worth a try. ftp://ftp.cadsoft.de/pub/userfiles/eagapp2.doc ~Ken _______________________________________________ LinuxPLC mailing list [email protected] http://linuxplc.org/mailman/listinfo/linuxplc

C

#### Curt Wuollet

Hi Ken Per another post, I didn't get Eagle as lite is too small for the project and standard and pro are too spendy for me to do out of pocket unless I do a lot more board work. pcb lacks an autorouter and schematic capture but the price is right. I'm sure someone on the list can try it and get back to us. Regards cww _______________________________________________ LinuxPLC mailing list [email protected] http://linuxplc.org/mailman/listinfo/linuxplc

W

#### Willy Smith

Curt, Doesn't this make the cost per point rather prohibitive for a small group of I/Os? I have downloaded the package, but the only file I can look at is the BOM. It's got hundreds of parts! I don't know how much the ZFLinux chip costs, but this board must cost over $200 to build. Maybe I'm out to lunch, but I was hoping for a <$50 BOM and much less complexity. Willy _______________________________________________ LinuxPLC mailing list [email protected] http://linuxplc.org/mailman/listinfo/linuxplc

K

C

#### Curt Wuollet

Hi Ken I haven't seen a Linux port yet. We have a problem developing stuff for our OSS PLC on a proprietary runtime. Of course, if it's cool, a Linux port should happen any day now :^). I'll take a look around for Linux on Rabbit. I too was excited when I saw it a while ago. I could be wrong, but I think we want Linux on both ends. The really cool thing about the Zflinux stuff is that so much is already done. Hacking internals to fit on a tiny micro is for younger guys who can hack till 3 AM and not crash in their cornflakes :^) Having something now doesn't mean we can't have something better. (cheaper) later. We aren't in it to corner the market or make a million. With all the embedded Linux development going on things will just get better and better. Regards cww _______________________________________________ LinuxPLC mailing list [email protected] http://linuxplc.org/mailman/listinfo/linuxplc

C

#### Campbell, David (Ex AS17)

> Curt Wuollet wrote: > Hi Willy > > It would be cost prohibitive for small point counts. *snip* > That's expensive and not very powerful. Most SBC's > are awful spendy or don't have networking or some other essential. > I hope you can find something at $50.00 too. Quoting one of the press releases on zflinux's web site: "The MachZ is priced from$60 in low volume to mid $30's in high volume quantities on an OEM basis." I have been working my way through NatSemi's chip data sheet pages and found that the minimum part count for a NIC is 1 x controller, 2 x SRAM, 1 x EEPROM + x passive components. (Add in the voltage convertor if you want BNC). SRAM for the packet buffers, EEPROM for the configuration (including MAC address). Passives for the signal issolation. You will break the$50 limit just attempting to add network support. If you are serious about Linux on an embedded system you might want to throw the kernel into EEPROM (that is going to cost a few dollars). > I said "Fast and Easy" I didn't say cheap :^). > Like all engineering.... cheaper, faster, or better....pick any two. Just about got the three corners of project management there. price, quality and time, it is always a tradeoff between those three. Does anyone know of an ethernet &lt;=> serial convertor that can be accessed from the ethernet (eg: a reverse RAS box?). David Campbell _______________________________________________ LinuxPLC mailing list [email protected] http://linuxplc.org/mailman/listinfo/linuxplc

K

#### Ken E.

Actually Curt, The Rabbit 2000 people seem to have put together a nice software/hardware package for TCP/IP development and provide schematics, debugger, etc. .. I don't think that it gets much easier. Lets face it, you just have a main loop copying IO information and the ethernet stuff would happen on an Interrupt routine and get buffered for the main loop to process. I did a similar thing for the CAN bus with a siemens Micro and it went rather nicely. I would be able to help here, but I don't yet understand TCP/IP and ethernet. I think running linux on the IO end *just* for remote IO is kind of like hitting the proverbial fly with the sledgehammer and a lot of people wont go for it. I think you will have just as much work trying to port it into a tiny micro (even the zflinux) and getting around the various issues that you would have been better off using an embedded micro with no OS on it. Having said that, it is kind of like all the topics on here ... ultimately it remains to be decided by the one doign the actual work. ) ~Ken _______________________________________________ LinuxPLC mailing list [email protected] http://linuxplc.org/mailman/listinfo/linuxplc

C

A