UPPAAL-5.0.0 vs. UPPAAL-4.1.20-stratego-11 handling of hybrid guards

[John Baugh]

In Uppaal 5.0.0, a simple bouncing ball model "ball-error.xml" produces an error:

> A general hybrid guard is enabled without urgent synchronisation

In Uppaal 4.1.20 Stratego 11, no error is produced.

Adding "urgent broadcast chan bounce;" to the transition causes the error in Uppaal 5.0.0 to go away, but it then adds a warning:

> Clock guards are not allowed on urgent edges;

This seems to run okay, but is there something fundamentally wrong about this approach? Or, maybe to put it another way, what is the simplest bouncing ball model in Uppaal 5.0.0 with a valid semantics?

Thank you for any help and insight you can provide.

Regards,

John

[John Baugh]

The same error is produced in Uppaal 5.0.0 (see attached) on the distributed "ball.xml" file included under the menu item "File -> Open Example -> smc -> ball" ... any guidance or suggestions would be appreciated.

Regards,

John