VB.Net Component works during DEBUG (VS2015) but does nothing after compiling

Hi to all,

I have a problem with a VB.Net component (I just started with coding).

Basically the component is an interface between Grasshopper and the Theremino System and everything goes right during debugging phase (with Rhino64) but when I load the compiled application in GH nothing happens.

If I compile only for x86 CPU everything works in Rhino32 but not in Rhino64

The component basically read the number from a file and write the number on an external application using memory.mapped files.

Do you have an Idea of why this happens?

Replies to This Discussion

Permalink Reply by David Rutten on March 31, 2017 at 2:24am

What do you mean by "nothing happens"? The components load but they do anything? The components don't load?

Permalink Reply by Mauro Sogni on March 31, 2017 at 3:43am

The component is supposed to write some values in a memory mapped file which is shared with the HAL Apllication from Theremino System (basically it is something similar to Arduino).

I use a number slider to write the values and control the external App and in the Output I read the memory mapped file just to check.

Now, in 32bit version of Rhino everything works (I write the value and control for example a servo motor), duringo debugging in visual studio everything works in Rhino64, but when I compile everyting, in rhino 64 I move the slider but on the output I always have 0.0 (starting value of the variable) and the servo motor doesn't move.

I know I am not so clear, but really I'm just starting with coding.

Permalink Reply by David Rutten on March 31, 2017 at 8:24am

Ok I understand now. I've never used MemoryMappedFiles before (didn't even know they existed until 10 minutes ago). There do seem to be some known issues with 32/64 bit access of the same file, depending on how the file is created.

Visual Studio is a 32-bit application, so that may explain why it works in the debugger. Are you getting any exceptions when you try to access the file in 64-bit release builds?

You may have to ask the Theremino developers whether their MappedMemoryFiles are accessible from 64-bit applications.

Permalink Reply by Mauro Sogni on March 31, 2017 at 8:27am

at the moment we solve the issue by creating an external app that basically connect GH and HAL by using the clipboard (Copy/Paste).

we are trying to do the same with memory mapped files and the external app.

we'll see

Permalink Reply by Mauro Sogni on April 3, 2017 at 9:50am

Just in case someone needs this:

The problem is in the class Theremino uses for exchange slots value inside a memory mapped file.

You need to build yourself a brand new function for read and write data.

bye bye

RSS