zpayne01

Members
  • Content Count

    4
  • Joined

  • Last visited

Community Reputation

0 Neutral

About zpayne01

  • Rank
    Newbie
  1. zpayne01

    Daqfactory Time

    Interesting, so are you saying when I have events that occur every 60 seconds (time 60 within a script with goto 0 afterward), if the clock changes (due to daily syncs), then it will account for this change (hypothetically the clock adjusts by 4 seconds at midnight so 4 seconds are added within the script)? Also, since I record data every second and each data point has a string associated with the time of the recording, will the new data be written with the new time after a sync, or will it continue with the old time point (I assume the former)?
  2. zpayne01

    Daqfactory Time

    Hello, I run a fairly complicated setup that uses multiple computers and microprocessors to run a sampling protocol alongside an instrument that uses DAQfactory attached to a Labjack. I check to make sure times are synched between the different computers several times per day, however, once DAQfactory has started, it seems to run on its own internal clock separate from the windows clock. This causes it to start lagging (3-5 seconds a day) which eventually forces a restart of the program. I was wondering if there was a way to get DAQfactory to sync automatically to the outside computer without forcing a complete restart. Thank you, Zachary Payne
  3. zpayne01

    Daily Crashes

    Sounds good. I will try updating to the latest release and e-mail you the document. I am using the built-in performance monitor to log CPU and ram usage but I haven't seen any issues. I also tried running CPU and RAM intensive applications alongside to see if they would crash as well and they did not, so I would say the issue is related to DAQfactory (or my script) itself and not hardware limitations of the computer; as I say that though I did read a similar issue related to graphing and the GPU so I may test that. Thank you for responding.
  4. zpayne01

    Daily Crashes

    Hello all, I have been having near-daily crashes on my DAQfactory program that I use to run some pretty sensitive instrumentation. The problem started about 2-3 months ago after I hooked up the computer to the internet (it usually runs offline to prevent such conflicts). Since that moment, crashes have gone from bi-weekly, to weekly, to now daily. Restarting the computer may provide 2-3 days of reprieve but it is no guarantee. I have updated windows and updated DAQfactory but I am at a loss. Below is the event log. If anyone can help me figure this out you would be doing me, and my lab, a great favor. Thank you! Log Name: Application Source: Application Error Date: 1/20/2020 8:31:08 PM Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: WINDOWS-UGALCI7 Description: Faulting application name: DAQFactory.exe, version: 16.3.2297.0, time stamp: 0x57d108c3 Faulting module name: DAQFactory.exe, version: 16.3.2297.0, time stamp: 0x57d108c3 Exception code: 0xc0000005 Fault offset: 0x0027aaca Faulting process id: 0xcb4 Faulting application start time: 0x01d5cfb446ebc732 Faulting application path: C:\DAQFactory\DAQFactory.exe Faulting module path: C:\DAQFactory\DAQFactory.exe Report Id: b25e8b6d-3bed-11ea-8e9d-000bab95945c Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Level>2</Level> <Task>100</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2020-01-21T01:31:08.000000000Z" /> <EventRecordID>26589</EventRecordID> <Channel>Application</Channel> <Computer>WINDOWS-UGALCI7</Computer> <Security /> </System> <EventData> <Data>DAQFactory.exe</Data> <Data>16.3.2297.0</Data> <Data>57d108c3</Data> <Data>DAQFactory.exe</Data> <Data>16.3.2297.0</Data> <Data>57d108c3</Data> <Data>c0000005</Data> <Data>0027aaca</Data> <Data>cb4</Data> <Data>01d5cfb446ebc732</Data> <Data>C:\DAQFactory\DAQFactory.exe</Data> <Data>C:\DAQFactory\DAQFactory.exe</Data> <Data>b25e8b6d-3bed-11ea-8e9d-000bab95945c</Data> </EventData> </Event>