jkrom

MrPLC Member
  • Content count

    5
  • Joined

  • Last visited

Community Reputation

0 Neutral

About jkrom

  • Rank
    Newbie

Contact Methods

  • ICQ 0
  1. Data Storage?

    Someone on another forum told me about the DataBridge from Acumen Products which sounds like exactly what I'm looking for. I'll let you guys know how it works once I try it.
  2. fuel injection

    I had remembered hearing something about Johny Miller's Trans-Am car using Automation Direct equipment for some data acquisistion, interesting article. The processor speed required to control fuel injection, however, is way beyond what we're talking about here, though.
  3. Data Storage?

    Sorry if I was a little too vague before, but this project is just in the design phase and most of the specifics are not yet known. I wanted to know, now, whether I would need to add a PC to the system (and add to the quoted budget accordingly - but I really want to avoid if possible). Anyway, here is what I can tell you. This will be an end-of-line full function tester for automotive seats. It will test various aspects of the completely built seat just before it is bagged and sent to the OEM (GM). Data that would need to be saved may include; BSN (String - usually around 12 characters) Component Serial # (String - usually less than 20 characters) Max current draw from each motor (Integer) Heater pad resistance (integer) Thermistor resistance (integer) Seat belt buckle mA (integer) Side Air Bag resistance (integer) plus a few other pass/fail indicators Normally, all of this data would be sent to the plant's host network at the end of each cycle and they would store it, so that it can be retrieved later in the event of a seat related end-customer complaint or safety law suit. This particular tester, however, is for a pre-production model and was originally supposed to be a complete stand-alone unit that would just print a pass/fail label from a Zebra printer. Last week, after design was well underway, they changed their mind and wanted to be able to log data in the tester itself for a short period of time - until they copy it into a laptop. I would envision needing to store 200 - 300 records for a week's worth of testing. I mentioned strings specifically in my original question only because I think that it would be easier to put all of the data together in one string and use an AWT to send it through the serial port (or possibly use a print only tag to send it from the PView). I came across some info on the "DLG" command in the MicroLogix 1500 last night, but I'm a little fuzzy on how it actually works - does anyone have any experience?
  4. fuel injection

    I've thought of this as well, but have come to the conclusion that a PLC would not be up to speed. Your best bet is to check out the "MegaSquirt" build it yourself EFI http://www.msefi.com/
  5. I am working on a new project (MicroLogix 1500 w/ Net-ENI and PView 600) in which I would like to store test data without (hopefully) having a PC permanently attached. The only way I can think to do this within the PLC is to create a seperate string address for each test and having a ton of ladder logic to move from the latest to the oldest - doesn't sound like fun. I am envisioning a seperate device that would just hold strings of data until such a time (weekly? monthly?) that a laptop can be plugged in to extract it. Does such a device exist? Hope the question is clear enough (this is my first post) - please ask if you're unclear. __________________