Hi David,
Last year, I reported an issue I had with the latest release of HearSay (see my
posting below).
I just figured out what was going wrong, and thought I should share this.
The problem was that, with the latest release of HearSay (2012) and
blockdrivers installed (!SerialDev),
HearSay would always use 115200 baud, regardless what it says in the bottom
left corner of the main window.
I have just discovered that by default, HearSay selects the ‘Sportster’ modem,
for which speed control has not been implemented in the driver script.
Selecting ‘Hayes’ solves the problem completely, and allows the baudrate to be
selected as before.
Best regards,
Paul Reuvers
On 7 Jul 2016, at 12:57, David Pilling <david@xxxxxxxxxxxxxxxxxxx> wrote:
Hi,
On 07/07/2016 10:07, Paul Reuvers wrote:
As I am the author of the Internal32 blockdriver, I inserted some debugging
lines in that code, and noticed that after changing
the baudrate, the blockdriver is never called. It is only called once on
startup (it IS called when altering the word format and the handshake
though).
