Re: [Flashforth-devel] building larger program words -- arduino mega2560 FF5

[Mikael N. <mik...@fl...>]

The MS word behaves exactly the same interactively and when compiled. 

The extra delays in interactive mode are caused by the interpreter
parsing the input and finding the words in the dictionary. 

Mikael 

On 2021-04-06 15:39, craig bair via Flashforth-devel wrote:

> I got it to work well enough yesterday that I sent it to the Test Group to use. Thanks for jogging my mind out of the rut it was going around in. The problems were all timing related and come back to not observing the behavior of the "ms" word closely enough. It behaves VERY differently inside a program word than it does in interactive mode. The 27+ milliseconds that it takes interactively is moore than enough for the sensor to complete its highest resolution data conversion. The portion of a millisecond till a tick occurs inside a larger word is far too short. The sensor NACKs until data conversion completes and I'm now allowing 17 msec plus whatever portion comes through in the first one. Good data every time as long as I wait a bit before switching sensors. The rate of change in the environment chamber is relatively slow compared to sampling 4 sensors round-robin one per second.