• Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Martin

  • Rank
  1. Sorry if this may seem obvious. I have a project that spans multiple pages. We developed the interfaces with a developer key and now want to run the project under a Run-time license. How can I allow the user to easily switch between the different pages without having to re-insert the hardware key? Are there any easily attainable sort-cut keys or will I need to have to go back to each page and create my own navigation system? Thanks... in anticipation. Martin
  2. The other thing to consider is if the USB port is USB-2 or USB-3. USB-3 being the later standard and of course faster.
  3. I had loads of timing problems due to a wireless network. You have not said how you are connected... Usb, ethernet, wireless? If you are using a wireless connection anywhere I'd also check that.
  4. Guru! Thanks very much for that. My main problem is not knowing DaqFactory well enough to quickly implement your advice but I'm learning with each step. That was quite an elegant solution with the minimal of scripting involved... thanks very much yet again. Regards Martin
  5. Now why couldn't I express my needs as clear and as concise as that! You have it in a nutshell. I was hoping that DaqFactory would be able to handle this without the need to delve into scripting. I'm no programmer (by a long way). Can anyone point me in the right direction?
  6. Hello Forum... We wish to be able to measure the time a current is flowing over each of 4 channels. It may be for a fraction of a second or several seconds (maybe up to a minute). We have two Labjack T7's and each currently monitors 4 experimental reactors Our logging frequency for our experimental workbench is currently by the second and is something we want to maintain. What we need to know is what is the duration of current "ON" for each second. The frequency of current pulse is random. A channel may pulse a fraction of a second or indeed may remain "ON" for a number of seconds, therefore no rising or falling edges, just a constant high for the duration of several logging cycles (see attached graph). I understand that if there are no rising (or falling edges) then the data will read as "0" which will be totally wrong for our purpose... or am I reading this wrong? Is "Duty Cycle" using a rising edge the thing I should be looking for or should I be looking to count the number of pulses a signal is "HIGH". The "HIGH" being provided by our Hall Effect current sensor? The current is a regulated 7.5 Amps... it does not vary except in terms of the time that is is on. I made up a simple Excel chart to illustrate what we are looking at. Any guidance would be appreciated. Regards, Martin
  7. To end this topic.... on a good note of course. We now have 5 geiger counters monitoring 4 experiments and 1 background reading working great with the Labjack T7 expansion board. Along with the geigers are 9 channels of temperature, four channels of current. So thanks again for the input and guidance. Your assistance has made all the difference. Regards - Martin
  8. Hi LabjackSupport... That bit about the 0.066V / Amp gradient was interesting. I took your hint and did my own calibration run stepping from 0 - 30 Amps. The hall effect sensor averaged out at 0.0622V / Amp. So of course the maximum swing actually works out to be 60 x 0.0622 = 3.72 volts not 3.96 volts as the specification sheet suggests. Once this was plugged into the calculation the actual current monitoring turned out to be pretty tight. Lesson learned... never trust a spec sheet. Thanks again. Regards - Martin
  9. Thanks for the guidance Guru. Increasing the threshold to 0.9 and then to 1 helped a bit. The data drop-out was reduced.... However what really made the biggest difference was taking the data acquisition off of WiFi and hard wiring the lot back to a hub with ethernet. Even though the WiFi path was a relatively short distance and only one wall from the wireless router it was enough, when loading all points, to create missed cells of data and the dreaded duplicate lines. So with all the guidance on tweaking from yourselves in Support and then hard wiring the system we now have really very clean data. I hope these couple of postings become useful to others as a possible cause of data error. Thanks again. Regards - Martin
  10. We need some help and/or advice. We have a Daqfactory Pro (Release 17.1 - 2309) with a Labjack T7 (Firmware: 1.0255) logging three experiments. We are running it on Windows 7 Pro. SP1. Intel I7 processor with 4 Gig Ram. It is fully patched with auto update and sleep disabled. The Labjacks are hard wired back to the PC via Ethernet. Each experiment consists of two analog ports: a thermocouple (K Type) and a current sensor (hall effect) and a one digital port counting a Geiger detector (counts / second). We have two additional channels monitoring background radiation counts and ambient temperature for all three experiments. We are using a one second time-base to log all three experiments at the same time. We have tried many configurations now. From logging at "Fixed Interval" to "All Data Points" with "Align Threshold" from 0.1, 0.7, and even 0.99 . Each time DaqFactory and our T7 will run well for maybe a few hours and then it will start duplicating lines, blank lines, lines with only one or two fields, fields randomly captured and missed. There is no real consistent pattern. Then for no reason it will start logging perfectly well again. One thing that strikes me as odd, is that despite defining the CSV file for current to 2 significant figures, when our current sensors detect a small negative signal DF insists in logging to 5 significant figures... Why is this? We need to log these over a 24 hour period. I have attached the latest CSV file from last night along with the CTL file. The logfile starts going strange at line 15719, 15731, 15738 - 18453, 41930, 41948 - 44665 and is then fine down to 60002. Master_180806_160103.CSV Ecalox_LJ_Live_06_08_2018_d_2_Added_Channel.ctl
  11. Martin

    Missing data from CSV file.

    We increased the number from 0.7 to 0.99 but we are still getting lots of errors after around 4500 seconds/lines of data. It goes from a nice even one second count up to around 4500 lines to doubling the second count with the second line blank with just the repeated timestamp.
  12. Martin

    Missing data from CSV file.

    Thanks for getting back to me. I adjusted the time-stamp / timing as you suggest above but all it did was produce a different pattern. All was well up to around 4500 rows of 1 second logging then it started logging twice for each second... one full row and then a blank row with just the time stamp. I'm really not trying to do anything complicated here. Just reading my sensors once per second. Windows 7 professional, I7 processor, nothing else running to take or intefer with the memory. Do you think it is a buffer problem because the fault repeats itself at around the same position each time we restart the logfile.
  13. Martin

    Missing data from CSV file.

    I am logging a number of hall-effect sensors over a 24 hour period. Everything seems to be going fine except that at seemingly random periods DF seems to miss recording date. The timing is the default 1 second and I am using ASC712 hall effect sensors monitoring four DC current streams on AIN0, AIN1, AIN2, AIN3 I really don't know why this is happening and I've looked at it several times now. Should I use averaging? I've done the same thing with an Arduino and everything works well enough but our T7 Pro and Daqfactory seems to be a problem. Any ideas?
  14. Oh wow... Thanks very much to both comments and posters above. I've just implemented the suggestions and apart from fiddling with the offset it worked spot-on. I played with setting the offset via Kipling and within the conversion as suggested. Both worked perfectly. Next in my list is to get the entire configuration into a start-up routine that is passed to the T7 rather than having dedicated local T7 settings. Another excellent lesson learned. Martin
  15. I have attached am ACS712 Hall Effect current sensor to my T7 via GND / AIN2 powered from the 5 volt VS supply on the T7. It is rated as a 30 Amp device (there are 5 Amp and 20 Amp) devices available. It can measure both DC and AC but I am only interested in the DC factor. It has an output of 2.5V with zero current flowing through the sensor. Its minimum voltage out will be 0 Volts at -30 Amps and its maximum voltage out at 30 Amp will be +5 volts. How do I map this so that I can read the full range of -30 Amps to +30 Amps into DF. Kipling can see the 2.5 Volt output from the sensor and I can use DF to pull that through to the screen in DF but I need DF to convert or map the 0 - 5 volt swing (maximum) through to -30 to +30 Amps. I should imagine that this would be a vary useful piece of information to many DF / T7 users.