Help with serial printer logger

[duats]

I am using the trial serial printer logger.
I am successfully logging printer data.
I am successfully displaying printer data.

I need to activate a sound on detection of various text strings in the printer data.
I have tried to set the filter for the events.dll to play sound on detection, but without success.
Can you give me the steps to configure this functionality?

Thanks for your help.

[Arthur Grasin]

I'm sorry, but serial printer logger can't notify on data detection. Please, try Advanced Serial Data Logger instead. You need to activate and configure the ASCII data parser (I suppose that you are capturing text data). In this case you can use events.dll as you want.

[duats]

Thanks,
I will install ASDL and see what I can do with that.

[duats]

OK, now I have installed ASDL.
I don't see any success in my objective, which is to play a particular sound when a particular text string is discovered in the received data.

I want to play different sound files on the occurrence of  "text type 1" or "text type 2" when the received data is in the form:
Date/Time dddddddddddddd  text type 1<CR><LF>
Date/Time dddddddddddddd  text type 2<CR><LF>


How is the query/parse filter used to identify the desired text?
I am not using any process to work with the parsed data; I just want the sound.

Once the data is isolated and the trigger is produced, how is the Events handling module used to execute the playing of the sound?  What is the form of the trigger for the Events handling module?

[Arthur Grasin]

1. You need to activate the ASCII parser in any case. The parser will split your data by rows (fig.1).
2. You need to activate the "Events handling" plug-in (fig.2)
3. Withing the the "Events handling" plug-in you should add a handler (fig.3)
4. Specify handler name and event type (fig.4).

[Arthur Grasin]

5. Configure the filter for this handler (fig.5) (small correction in the "Place" column select "Any event context item");
6. Specify your sound (fig.6);
7. Repeat steps 3-6 for second text entry.

[duats]

There is still no response. The test button on the sound file definition works, so the speaker, etc. is working.

What about the page "Query Parse Filter" ?
I set Data Query mode:  none
Parser module: ASCII data query & parser (default.dll)
Parse & Export for sent: no
Parse & Export for received: yes



Is there any way to see what the intermediate steps produce? How do you step-wise debug this thing?

[Arthur Grasin]

Additional screenshots are attached. I've tested this solution on my PC and it works well. Did you type your text instead of "type1" on fig.5?

How to debug:

Try to activate the DDE server data export plug-in. If you'll receive data and the "Active items" window will contain any items, then the parser works ok. Otherwise you should verify parser settings.

[duats]

Thanks,
 I did put my data strings in there.

I will return at 0630 GMT when my next shift starts and I will try the DDE.
I'll report the result. Hoping you are there that early.

[duats]

Thanks Arthur,

    Your reply #5 solved the problem. My misunderstanding was mainly in the parser. Now I see how that goes together.

    I had trouble after the changes because I did not restart the service. Evidently, the configuration changes stored in the registry are picked up on starting the ASDL service.

    We have success. I will expand on this myself and thanks again for your assistance.
    We have now purchased the pro version of ASDL.