Mark Rivers

I don't think I will have a chance to complete that document before the release. I added a note at the end of the file saying it still needs to...

> where do I update the documentation? I noticed that you just added a whole new subdirectory. The documentation is now in docs/source/*.rst. I have deleted all of the old...

For this PR I think it would be good to create an Issue that contains the following: - The "problems" that this PR is intended to address. For example: -...

> And I was just wondering if you want a separate issue for some functional reasons, or if it was just aesthetics. Aesthetics, along the lines of what @prjemian said.

@anjohnson, @mdavidsaver, and @ralphlange could you please look at this? I would like to merge into the next asyn release if you are good with it. Thanks.

sCalcoutRecord.h is in the “calc” module. It will not try to use that file if you comment out this line in asyn/configure/RELEASE CALC=$(SUPPORT)/calc-3-7-4

The problem is probably because you are modifying CONFIG_SITE to set TIRPC=YES. If you do that, then you need to have a CONFIG_SITE.Common.windows-x64 that sets TIRPC=NO. Preferably, don't change CONFIG_SITE....

The comment in line 217 is the key to the problem. The asynOctet drivers get data from the device in "chunks". The problem arises when a potential terminator begins on...

> To provide more info, it can also be reproduced on asyn-R4-43 and asyn-R4-42. I believe I have identified the issue. The problem is that devAsynXXXArray::interruptCallback should be returning immediately...

I have fixed the problem. interruptCallback() now returns immediately if interruptAccept is 0. I have pushed the fix to the master branch.