August 17, 20223 yr Alright I got my checklists going and can answer with specific words, BUT it does not work with multiple answers being acceptable. I tried to figure it out from the manual and that's what I got: [*on|off|engine anti ice on|engine anti ice and wing anti ice on|wing anti ice and engine anti ice on|engine and wing anti ice on|wing and engine anti ice onow|medium|off*](@COVOICE: anti ice!) [0] Explanation: co pilot says "anti ice" and I can advance the checklist by saying either "on", "off" or "engine and wing anti ice on" etc. This does not really seem to work every time (mostly it does not), although I think it does sometimes. When it doesn't work it seems to bug out completely (also for the rest of the checklist) and only accept my general checklist advance command ("set and checked"), which always works. Did I do something wrong? Or is that too many answer variants for the program to understand? If so, is there another way to script that so it doesn't bug out? EDIT: Also: Do I need that exclamation mark at all? And do I need the [0] at all? Edited August 17, 20223 yr by Fiorentoni For transparency: I'm a community mentor at the BATC discord. However, I do not get paid for it in any way.
August 18, 20223 yr Author UPDATE: Disregard my first post, the problem is not multiple confirm options but multiple checklists one after another. The second checklist does not seem to work correctly every time and will not recognize my confirm. However by saying "stop checklist" and restarting the second checklist it will resume working normally. So it seems like the program does not "end" the checklist correctly and voice recognition bugs out with the new checklist. Is this because I missed something in my script? How do you "end" the checklist in the RPN script correctly? Can I auto-stop-checklist silently after every checklist script? Edited August 18, 20223 yr by Fiorentoni For transparency: I'm a community mentor at the BATC discord. However, I do not get paid for it in any way.
August 18, 20223 yr Commercial Member 1 hour ago, Fiorentoni said: UPDATE: Disregard my first post, the problem is not multiple confirm options but multiple checklists one after another. The second checklist does not seem to work correctly every time and will not recognize my confirm. However by saying "stop checklist" and restarting the second checklist it will resume working normally. So it seems like the program does not "end" the checklist correctly and voice recognition bugs out with the new checklist. Is this because I missed something in my script? How do you "end" the checklist in the RPN script correctly? Can I auto-stop-checklist silently after every checklist script? OK, I will check it out. Sounds more like a bug - and there is more. The Items in those lists are not local to the command, they are all valid throughout the entire checklist all at the same time. What did you configure to the "stop checklist" term? The AAO event? You should be able to call those like any other K-Event, for example "1 (>K:AAO_CL_STOP)". Try putting that as the last item in your checklist file as a work-around. How this works: AAO doesn't have any voice recognition code. It relies on the Windows speech recognition subsystem (remember that you need to train that one so it understands your voice better). Your commands are compiled into a "grammar" that is sent to that subsystem with the request that AAO is to be notified if Windows recognizes one of those terms. Most likely, the previous grammar is not being cleaned out properly (although that shouldn't cause it to "bug out" - I will look into it). 14 hours ago, Fiorentoni said: EDIT: Also: Do I need that exclamation mark at all? And do I need the [0] at all? Text to speech is also just bound to the Windows TTS subsystem. The exclamation mark causes it to pronounce the text differently, that is all (but it depends on the voice if you notice it). Your choice if you want that or not. The [0] are no longer needed. That should have been corrected in the latest manual, they should be gone from the checklist examples (AAO version 2.32). Edited August 18, 20223 yr by Lorby_SI LORBY-SI
August 18, 20223 yr Author 1 hour ago, Lorby_SI said: OK, I will check it out. Sounds more like a bug - and there is more. The Items in those lists are not local to the command, they are all valid throughout the entire checklist all at the same time. What did you configure to the "stop checklist" term? The AAO event? You should be able to call those like any other K-Event, for example "1 (>K:AAO_CL_STOP)". Try putting that as the last item in your checklist file as a work-around. How this works: AAO doesn't have any voice recognition code. It relies on the Windows speech recognition subsystem (remember that you need to train that one so it understands your voice better). Your commands are compiled into a "grammar" that is sent to that subsystem with the request that AAO is to be notified if Windows recognizes one of those terms. Most likely, the previous grammar is not being cleaned out properly (although that shouldn't cause it to "bug out" - I will look into it). Text to speech is also just bound to the Windows TTS subsystem. The exclamation mark causes it to pronounce the text differently, that is all (but it depends on the voice if you notice it). Your choice if you want that or not. The [0] are no longer needed. That should have been corrected in the latest manual, they should be gone from the checklist examples (AAO version 2.32). Thank you for the explanations. Yes, I'm using the AAO event to stop the checklist. I will try to add it at the end of every checklist. Like this? ... [*off*](@COVOICE: battery!) (@COVOICE: secure checklist completed) 1 (>K:AAO_CL_STOP) For transparency: I'm a community mentor at the BATC discord. However, I do not get paid for it in any way.
August 18, 20223 yr Commercial Member 1 hour ago, Fiorentoni said: Like this? ... [*off*](@COVOICE: battery!) (@COVOICE: secure checklist completed) 1 (>K:AAO_CL_STOP) I think so - only one way to find out... Just (AAO_CL_STOP) may work as well, maybe followed by an (END) in the last line of the file. Problem I'm having is that there is no visible fault in the code. When a new checklist is started, the same things happen as with the CL_STOP event. How exactly are you calling the "next" checklist? Right from the previous one, with a separate script - ?? LORBY-SI
August 18, 20223 yr Author 16 minutes ago, Lorby_SI said: I think so - only one way to find out... Just (AAO_CL_STOP) may work as well, maybe followed by an (END) in the last line of the file. Problem I'm having is that there is no visible fault in the code. When a new checklist is started, the same things happen as with the CL_STOP event. How exactly are you calling the "next" checklist? Right from the previous one, with a separate script - ?? Yes exactly, with a separate script. It doesn't even have to be right after that. The new checklist 15 minutes later is still enough to make it bug out mostly (though not always). I tried to go through five checklists one after another just a moment ago with the 1 (>K:AAO_CL_STOP) added to the end of each, and it did work without bugging out. Will test more later with a complete flight and let you know. Here's one entire script just in case I'm missing something: Quote <Macro Name="COVOICE">VOICE:Microsoft Mark) (VOICERATE:1) (VOICEVOLUME:100) (SPEAK</Macro> (@COVOICE: after start checklist) (WAIT:1000) [*on|off|engine anti ice on|engine anti ice and wing anti ice on|wing anti ice and engine anti ice on|engine and wing anti ice on|wing and engine anti ice on*](@COVOICE: anti ice) [*checked*](@COVOICE: e cam status) [*percent|set*](@COVOICE: pitch trim) [*neutral*](@COVOICE: rudder trim) (@COVOICE: after start checklist completed) 1 (>K:AAO_CL_STOP) For transparency: I'm a community mentor at the BATC discord. However, I do not get paid for it in any way.
August 18, 20223 yr Commercial Member Can you please send me an email to the support address (last page of the manual) with your proof of purchase? I would like to fix/change the logic here, but I find it hard to test it. LORBY-SI
August 18, 20223 yr Author 45 minutes ago, Lorby_SI said: Can you please send me an email to the support address (last page of the manual) with your proof of purchase? I would like to fix/change the logic here, but I find it hard to test it. Done. For transparency: I'm a community mentor at the BATC discord. However, I do not get paid for it in any way.
August 18, 20223 yr Commercial Member 2 hours ago, Fiorentoni said: Done. Sorry, I am having trouble with the wts mailserver. That should sort itself out, but it may take a while. LORBY-SI
August 18, 20223 yr Author 2 hours ago, Lorby_SI said: Sorry, I am having trouble with the wts mailserver. That should sort itself out, but it may take a while. Alright, just to let you know, it happened again, it did bug out. I can easily reproduce it by using a long checklist first [like 30 items] and after that start another one: Always bugs out at the very first item. Can only continue with the general advance command ("set and checked" in my case). Scripts were set with 1 (>K:AAO_CL_STOP). So no solution yet. Edited August 18, 20223 yr by Fiorentoni For transparency: I'm a community mentor at the BATC discord. However, I do not get paid for it in any way.
Archived
This topic is now archived and is closed to further replies.