![]() ![]() The difficulty with this is that while a function may have been called in a way that it destroys memory, this does not always have to cause immediately an error or crash. While these two reasons should not be ignored and thoroughly investigated, you should also account for the possibility that any other function you call may be called in the wrong way and cause such issues. After the function returns control to LabVIEW, LabVIEW reserves the right to deallocate or reuse that buffer for anything it deems useful and when your function then attempts to write into that buffer asynchronously it may simply overwrite memory that is in the meantime used by LabVIEW for something else. The LabVIEW buffer passed into the function is only guaranteed to be valid during the function call itself. ![]() The documentation states something to that effect that this number will depend on the used CCD element.Ģ) The function is not filling in the data while the function executes but instead keeps the pointer in the background to be filled in asynchronously. ![]() When you look at the function I provided, there are really two possible reasons why they could cause this error:ġ) The CCD array has more than the 1024 pixels that I assumed from your documentation. Typically this happens because you do not allocate a buffer for the function to write into. This could be any of the functions you call through any Call Library Node. Error 1097 means that something has written to memory it should not have done. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |