Error in PLW32.exe

Forum for discussing PicoLog
Post Reply
Alex
User
User
Posts: 5
Joined: Thu Mar 03, 2005 7:58 am

Error in PLW32.exe

Post by Alex »

Hi..

When im running Picolog and recording data on my laptop, i get this error message about 10h after the recording started..

" The instruction at 0x00434328 referenced at 0x00000003. The memory could not be written "

Is this a known error, or could it be something wrong in the physical memory in the laptop ?
(I use a USB TC-08 with type K thermocouples)

Best Regards / Alex

Sarah

Post by Sarah »

Hi Alex

Thank you for your post, I am sorry to hear you have been seeing problems.

What version of the software is this with? I would recommend using our latest version and seeing if this helps.

If it does not help then let us know and we can try to replicate the problem here.

Best Regards

Alex
User
User
Posts: 5
Joined: Thu Mar 03, 2005 7:58 am

Post by Alex »

Hi.. again

Well, i´m running your latest software.
I´got a new laptop now. But i still have a similar problem. :-(

My laptop is an IBM thinkpad . 256 mb memory,
Windows 2000. and i am logged in as a power user.

Picolog was set to stop after 60000 channels
I had set the filterfactor to 6
It stopped after 32760 readings.
i used 3 channels + cold junktion.

Best Regards / Alex

EDIT: I found a newer version of your software.. ( Ill be back with a response in 24 h )

Alex
User
User
Posts: 5
Joined: Thu Mar 03, 2005 7:58 am

Post by Alex »

:( Still the same problem.
It stopped after 32760 samples.
9 hours and 5 min ..

Best Regards / Alex

Sarah

Post by Sarah »

Hi

Thank you for your post and the extra information.

We believe this may be a software bug related to the bit resolution that is being used.

Therefore you might like to try reducing the bit resolution and seeing if this helps. The other option is to set the software to "Repeat Immediately" and then set the maximum number of samples to 30000. This way at 30000 samples it will then start a new file and you should not see this problem any longer.

We will investigate the bug here and see if we can find a solution.

Hope this helps

Best Regards

Post Reply