Jump to content

Sandy

Members
  • Content Count

    5
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Sandy

  • Rank
    Newbie
  1. Hi, Is it possible to do safe remove of aUSB Stick/DOK from the ladder or a UI element? I'm saving a data row to SD, then the copying it to a DOK, all of which can be done from the ladder, using the status codes to avoid timing issues. I'd like to avoid the "DOK Unsafe Remove" warning that appears. I always get the same warning after using the safe remove button on a File Browser UI element, so this isn't a suitable workaround. Sandy
  2. Hi, I'm trying to build a log for my system using the Store DTI to File function. This runs after the struct containing the date is inserted into row 0 of a table, which should be appended immediately to the log file. The writes are sufficiently spaced (~30 minutes) that the SD write interval isn't an issue. I've found that when using option 2 "Only CSV" for the "Create CSV" input (F), the file is simply overwritten, and only ever contains 1 row. Option 1 "Create CSV File (All - udtf,csv,csv.zip)" does append correctly. In both cases "Append to File" (E) is set to 1 "Data will be appended to the file". This looks like a bug to me, and combined with the missing documentation for those options, I've wasted a little more time than I'd like trying to figure that out. Option 1 is an acceptable workaround, so I don't need further support, but this should be fixed. Sandy
  3. Thanks for catching that, I should know better than that by now. I'm not sure how it worked before - I might have been doing enough processing to slow the scan time right down. I ended up measuring the pauses, ie. by looking at when the number of bytes waiting stops changing. a 50ms timer worked nicely for this system.
  4. Hi, I'm trying to build a snooper that works on a modbus RTU network, to test a controller built by a third party. In this situation the Unistream is neither a master or slave, so the built-in modbus RTU configuration isn't suitable. I'm struggling to to get messages recieved consistently using the COM Rx ladder block. (it doesn't help that this ladder function isn't documented in the help file, specifically how it determines message boundaries in the absense of STX/ETX characters). I'd like to know that each time the "Data Arrived Bit" goes high, the first "RxLength" bytes in the "Rx Buffer" are new bytes, but that doesn't appear to be the case. With the attached code, I get an entry in the 'Raw' Data table for almost every scan. With condition before the COM Rx removed, it works better - but not a lot - there are lots of duplicate message fragments, but occasionally I get an unbroken and unduplicated sequence of characters which can be reassembled into a valid message. Any recommendations on how best to use the COM Rx function for this?
×
×
  • Create New...