Jump to content

Brooose

Members
  • Posts

    18
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Brooose's Achievements

Member

Member (2/4)

0

Reputation

  1. Is there information, basically a statement/letter of volatility, for a USB-2627? We'd need info such as, types and quantities of memory inside, whether or not it's user accessible, whether it's volatile or non-volatile memory, and what, if anything, needs to be done to erase any proprietary data from the non-volatile memory. Would a procedure in Dasylab, such as acquiring for 60 seconds with no inputs connected, be sufficient to clear any memory?
  2. The v15 driver solved the problem. Even though the display windows (Y/t chart, meters, and the relay icon changing) seems to lag sometimes, it appears to capture the correct data and lengths. What I wasn't able to find was a way to delay recording after a trigger condition is met. eg. I have 2 logic signals, one when the power starts and one when the test starts. The test start logic gets a glitch pulse when the power starts. I was trying to trigger on the power start, but only start recording 5 seconds later (2 seconds before the test starts), but I couldn't see how. I ended up putting an average block in the test start signal and use that as the start trigger, but putting in 2 seconds of pretrigger doesn't record 2 seconds. It's an odd amount, like 1.3 seconds or 2.3 seconds if I specify 3. Even specifying samples does the same thing. I suppose it's good enough, but it's a workaround.
  3. I tried installing the 16.0.0.501 and the 15.0.0.310 (from the downloads site) and both said (when trying to import them) they couldn't be used with this version of program. There was a 14.4.0.0 version also on the downloads website that successfully imported. When you open the analog input module, it says version 15.0.0 down in the corner. Is there any difference or release notes for the 14.3.0.0 dlp file and the 14.4.0.0 version? Is there a big difference in the 15.0.0.310 or 16.0.0.501 versus the 14.4?
  4. Is the V15 driver compatible with Datylab 2016? I can't upgrade from 2016 unless we buy all of the software all over again, so it looks we're stuck running with 2016.
  5. That is what I had tried before. The best that it did was to run for maybe 3 triggers and freeze up. You had to then stop it in Dasylab. is 14.3 the latest version of the Data Translation driver?
  6. Since Dasylab isn't working for two units, would QuickDAQ be a better option? At first glance, it seems to work with two units, but I need the two units to start acquiring on a pulse trigger with ~4 seconds of pretrigger, record for 15 seconds, save the data to a file with some sequence number, and rearm the trigger awaiting the next pulse. I haven't found the pretrigger or the rearm functionality; can it do it?
  7. I've tried the different settings in the alignment blocks. Most of them run for about 5 cycles or so and then it just freezes up; the relays stay latched, but it doesn't retrigger or continue to save data. This is really eating my lunch. I need to get a solution going and this $1500 software isn't cutting it. Is there some other straight forward way to use these two devices together?
  8. fastest data signal as in highest frequency content? (square wave having higher freq. content than a sine wave) Should both alignment blocks have the same method? Would 'synchronize with computer clock' be better? Should the slave be set to ignore real-time if it's being triggered by the master?
  9. I tried exactly that; the top device being the slave and the 2nd the master, per the manual. They're both set to 50000 sample rate with 5000 block size. The write file is set to write 100 blocks per file (option in multifile dialog box). That worked a little better. I have the trigger coming from a waveform generator that makes a pulse every 20 seconds (going into channel 0 of the master device) and the devices record for 10 seconds. The writes are using multi fille. using 'linear interpolation' in the alignment blocks and it runs for about 6 cycles before it gets the error "the data flow blocked by a subsequent module from one of the AIN devices (it varies which one gets the error first). When I changed the alignment to 'sync with computer clock' (tried that on a whim) it runs for 3 cycles and gets the error "data has different block or time information". I don't know why they run for a few cycles and then error out. Is there some other log file or error indicator for exactly what the problem is?
  10. example dasy 2 x DT9857E.DSB except for the modbus devices actually being DT9857E devices, this is the setup that sort of works (doesn't crash).
  11. Do you mean have all of the signals going into one relay? Those relays can only handle 15 signals and I need to record ~25. I'll make a duplicate setup using modbus AI so maybe you can look at that?
  12. We have the alignment block in between the relay and the write because we were told to a couple of years ago when we started using these. I want to trigger both devices from one TTL signal. So, what do I put into the slave's relay 'X' input so it doesn't complain about it being disconnected? I'll be using 15 channels from the master and 10 channels from the slave. Is there a generic device or simulation mode I can use so that you don't need the same hardware I have? I can make a setup to show you what I'm trying to do.
  13. When I try to load the .DSB file you included above, it says the stored time base is not available. Select another one; a module cannot be loaded. Then it starts to open and crashed Dasylab.
  14. That message came from a 2nd combi trigger (for the slave unit). I was splitting the signal coming out of one combi trigger into the relay 'X' input for each device. The question is, do I need a combi trigger for each device? Does the slave need a relay? Normally with one unit, I have the device with one of the channels going into a combi trigger. the signals go into a relay and the combi trigger output goes into the X input to the relay. The relay then goes into an alignment block and then the write. The trouble is getting the 2 devices to work together in the same concept.
  15. If you don't need more than 12 bit resolution or so, why not just use a good oscilloscope to capture the data? A halfway decent windows scope can acquire at like 10 GS/sec or so.
×
×
  • Create New...