News:

Welcome on our forum!

Main Menu
Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - Deiseyer

#1
Data loggers and plug-ins / Data base acces violation
September 11, 2013, 09:24:19 PM
Hi,

I've had a problem with advanced serial datalogger v.4.2, suddenly it stop to send data to SQL data base, and shows the message: Error when access to database [Access violation at address 7C81A1C1 in module 'ntdll.dll'. Write of adress 00000008].

Data was sored in .log files, I could recovered data for SQL through them, what could be the cause of this issue?
#2
Hi Arthur,

I've been trying starting datalogger as second instance, but each time it opens normally, it doesn't ask about the console mode, can I open it by other way?,

I add a picture


Thanks

#3
Hi Arthur,

I'm trying to monitoring data logger service, but when I open a second instance, it can't get information from port, it is already open by another device. It is another way to see what data logger is doing?


Thanks
#4
Hi,

If I configure Data logger as a service, how can I monitor or audit it?


Thanks
#5
Hi,

I'm working with advanced serial data logger, this is installed in a server, but sometimes when another user opens session, datalogger do too, it causes the first one opened gets blocked.

There is some way to configure datalogger that opens only once?

Thanks
#6
Hi,

I'm working with advanced serial datalogger 3.7.2, I configured datalogger as serial machine configuration
checkweigher coms settings:
code: ascii
stop bits: 1
parity check: off
baud rate: 9600

settings in software:
code:ascii
data bits: 8
parity: none
stop bits:1

datalogger is working well, but suddenly it stoped an closed. When it was opened again, datalogger was clean while checkweigher was sending data.
Then I paused receiving data, then I play it again, it appeared the UART receiver framming error on buttom area.
When I changed configuration to stop bits=2, I got code 96# and noise data, so I got back to original configuration stop bits = 1, since data are getting well.
This has been happened frequently, about 3 or 4 times on last 5 days, I haven't found cause yet