internal error window.cpp (17347)

[ryan_333]

Snowman,

I have been able to successfully use the NI845x VIs directly from LV, but unfortunately this approach won't work for my application.

I'll explain:  I have a bunch of C code written for a microcontroller that I am porting over so that it can be run from LV.  The C code consists of a command interpreter and several bit-banging SPI drivers.  When the command interpreter receives a command (string), it parses the command and then initiates SPI reads and writes according to what the command is requesting.  Ex:  the command "wrdev1 08 1f" would write 0x1f to register 0x08  of device 1.  Bit banging is necessary because I'm communicating with custom ICs that have very unusual SPI interfaces.  To bit bang, I need to send several commands to the NI8451 while my function is running, so I can't use an external 845x VI because it will only run after my block is finished.  I also need to monitor external lines while my function is running.

So my plan was to basically replace my microcontroller specific low-level drivers with NI845x functions.

I hope this clears things up, but if it doesn't, I can try to be more specific.

Thanks,

Ryan

[ColeTrain]

Hello ryan_333,

It seems that all of these crashes can be traced back to the 8451 that you are using here.  Will you please try to run on of the LabVIEW example programs that come with the 845x driver?  I understand that you do not want to use the LabVIEW calls in your final application, but this will help us narrow down if the crash is the 845x function call collision with something else, or if it's faulty hardware.

If the example program is able to run just fine, then would you please give a list of all of the processes running on your computer?  If you don't have any program readily able to create this for you, you can use the simple process monitor in the LabVIEW Example Finder to return all of your processes which you can then write to a spreadsheet.  Let me know if you need any help with that and I can modify the example for you.  

[ColeTrain]

Hey Ryan,

You dll definitely crashed my LabVIEW. I still don't know why just looking at the code, but I will work on figuring out what would cause this. Out of curiousity, were you able to run the code posted by Burben? I was able to run his code and return the device handle properly as he said. I will go compare the code tomorrow, but wanted to let you know his at least returned a value. I will keep you posted with what I find.

[ryan_333]

ColeR,

Thanks for continuing to work with me on this.  I tried loading Burban's .dll into LV again and it crashed.  I might get a chance to play with it some more later today.

Thanks,

Ryan