You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On 5/20/19 ~15:00 I started a new set replicates in the ODIn, under a new run.
Made sure ODIn was off, with water blank tubes in place
Started the new run in FileMaker
Turned the ODIn on to calibrate to blank tubes
Transferred cultures into replicates
Loaded tubes into ODIn
I first noticed that the file was not showing in filemaker. The file "OD1_100334.txt" was created on the server however, and data was going to this location.
Today 5/21 ~12:15 I added an additional rack (with 8 tubes) to the odin. I then noticed that the server had a new file - "OD1_100334.txt.bak". Instead of starting with my 5/20 data, it starts at 5/21 11:58. This is also where the data in "OD1_100334.txt" ends.
So I'm not sure why a new .bak file was started. I didn't restart the odin, and you can see in the first read of the .bak file that the ODIn hasn't lost track of time (value of 73332464 in the milliseconds column).
I also see 0 data in the filemaker entry. At this time, I can access both of the data files and bind them together, so I can still view the current data.
The text was updated successfully, but these errors were encountered:
I replicated this error again today, and I think it's related to the time delay of the servers/odin. I haven't timed it, but it seems like if I wait more than 10 minutes to turn the hardware on after starting the filemaker run it can be avoided.
On 5/20/19 ~15:00 I started a new set replicates in the ODIn, under a new run.
I first noticed that the file was not showing in filemaker. The file "OD1_100334.txt" was created on the server however, and data was going to this location.
Today 5/21 ~12:15 I added an additional rack (with 8 tubes) to the odin. I then noticed that the server had a new file - "OD1_100334.txt.bak". Instead of starting with my 5/20 data, it starts at 5/21 11:58. This is also where the data in "OD1_100334.txt" ends.
So I'm not sure why a new .bak file was started. I didn't restart the odin, and you can see in the first read of the .bak file that the ODIn hasn't lost track of time (value of 73332464 in the milliseconds column).
I also see 0 data in the filemaker entry. At this time, I can access both of the data files and bind them together, so I can still view the current data.
The text was updated successfully, but these errors were encountered: