EZ-B is definitely 32-bit, so that could be an issue. Could also be your .NET version. I haven't done anything in LabVIEW in many many years, so can't provide much assistance there, but I do know their customer service is excellent, so you might want to also ask the question in their user forum or even call their tech support.

Alan

I see. While on the topic of compatibility, can you tell me what .NET version EZ-B uses? Since I'm running 64-bit systems, I'm guess I need to start running programs in 32-bit compatibility now. Also, if I may digress, can I access the DLL file in some way to make some sort of 64-bit wrapper DLL? As of now, whenever I open EZ_B.dll in VS2015, I only get a strange Icon and Version dropdown (See Image).

Hopefully DJ will jump in. I believe it is now .NET 4.5. That is certainly the framework he recommends users install or re-install when things go wonky, but I know it is backwards compatible, so the DLL may be compiled in something lower. I haven't read the SDK readme file in a while, it might be in there.

I can't answer the wrapper question. Still learning the basics of .NET myself. Not nearly ready to take on that complexity. I only answered at all because I have a passing familiarity with LabView, but really only from playing around with it when National Instruments was one of my customers and I spent some time in their customer service center in Japan. Had some time on my hands, so played with their toys...... (Did you know NI developed Mindstorms for Lego?).

Alan

Yes I do know! But thanks for answering the question, helps clarify a good deal.

Thanks!

Have you seen this? http://digital.ni.com/public.nsf/allkb/DCB90714981A1F148625731E00797C33

Also, @anas9011 you should not need a 64bit wrapper because all 32bit binaries are upwards compatible from 64bit runtimes. That being said, if labview (for some strange reason) doesn't like 32bit libraries, i can compile the sdk in 64bit for you

The reason the ez-b is 32 bit is because there is no 64 bit variables used - which would provide no performance improvements. There are execution optimizations with 32 bit executable on a 64 bit system, because the other bits (in some instances) can be used at the same time. So in some cases, a 32 bit runtime is faster (or more optimized) than a 64 bit

Yep, I saw that post, first one I went to Actually, I just opened up LabView 2015 32-bit and I keep getting this error (see image), same with 64-bit. I'm downloading LV2013 to see if its some version issue; since we have some LabView VI's written to work with the rover and they reference the EZ_B.dll properly, but they were written in LV2013. I've looked around and tried stuff like this: http://digital.ni.com/public.nsf/allkb/4742EB60B64BE22186257BCE0053B8FD

@DJSures if you could send me a 64-bit library that would be very, very much appreciated.

Mini-solution:

Alright, so I did two things to make this somewhat work:

1. I put the DLL folder in the same folder as the LabView VI
2. I installed and ran the 32-bit version for both LV2013 and 2015
3. I downloaded the latest SDK and ARC update. The above let me read in all the other DLL's except for EZ_B.dll... which is very strange. I'm still trying to reference the EZ_B.dll though, any recommendations? Note that the above did not work with the 64-bit version (as expected).