Sound Output Question On The Ez:1 Robot


I have a really weird thing with the EZ:1 robot and the v4

I have a large robot script doing lots of cool stuff, but recently I am seeing SayEZBwait phrases that randomly speak twice and sometimes more and Soundboard waves that repeat or stop halfway through the wave and start again?

Has anyone seen this, or have any ideas? I wondering if its the v4, but taking it out and now replacing it from the robot is a big job as you can see from the photo below - if there is an easy fix then I would prefer to try that before pulling the robot apart!

User-inserted image


EZBuilder version ?


I'm guessing...

if you are using a recent EZBuilder version, i would try an older version from last year 2015.

The EZBuilder code has been improved several times to support the new hardware (IoT Tiny), and a better scheduler task.

Sometimes new improvements introduces new bugs Smile


I'm guessing your code is being executed twice - which is why you're hearing stuff twice. This is because the Windows speech engine will not play something twice unless it's told to play something again.

To test it, add a variable that increments each time the phrase is spoken and see if the variable changes. For example ...


Sayezbwait("hello this is a number: " + $cnt)

Lastly, there's a chance the audio buffer is causing a repeat due to extremely high cpu usage on the ezbuilder PC. This is because the way audio is streamed has a start and stop command - if the stop command is sent late, then the audio buffer may have enough time to repeat.

The audio buffer is circular, so if there ever is a network congestion issue, the audio will repeat the rather than stop.


Toy maker mine does it all the time. I was showing some friends today and it kept repeating itself over and over. It is a somewhat long sentence so I thought it was my network.


It looks like it is the standard v4 that maybe is the problem. I now continually get fragmented/repeating on the Soundboard wave on the robot. For a test I set up my v4x/2 on the lab bench (with no I/O connections) and ran the same script many times and the problem never occurs, so it looks like the v4x/2 may solve the problem - I will not know for sure until I strip the robot down completely and swap over the v4. When the Soundboard is being used in this script no other robot actions are happening. I cannot see that anything on the robot could cause these multiple sound re triggering.

If this is a network problem, then maybe the improved v4x/2 is solving this particular issue?

Tony Ellis profile at:


How did you obtain one of the newer boards?


@kamaroman69, I obtained a board as I asked DJ if I could be a beta tester.

I must have a fault on the onboard standard v4 as it never carries out the speech/waves properly - it goes wrong every time? Going back to the v4x/2 (not on the robot) then the problem never happens so it cannot be on the PC, EZ-Builder side.

DJ, I tried your count increment idea but it did not work when the phrase was spoken 2 or more times the count stayed at one - I guessed we would need a multi-line command with the cnt++ on the start of the line followed by the Sayezbwait phrase to see if the variable would change, but as cnt++ is on the prior line then its never going to increment if the Sayezbwait line starts again.

I will get some time this week to strip the robot down and swap over the v4 controllers.

Tony Ellis profile at:


Update on the sound output problem.

I have extracted the v4 gear tray from the robot and it is now sitting on the bench not connected with anything I/O etc except for the external speakers. The problem is still there with speech/wave problems every time the script(s) are run. If I then run the same scripts on the v4x/2 it works fine every time.

I am sure that the original v4 just went faulty it has been in the robot for over a year with no problems whatsoever? So I do not think there is anything wrong with the original v4 controllers, I probably just had an unlucky fault appear on this original unit, not sure what else it can be?


@Toymaker, if you want to post your project, or enough of it that duplicates the issue, I would be happy to try with my V4's (all original shipment, although all upgraded to the latest available firmware) just to make sure it is an issue specific to your device.