Hi! Here I left the last version of the v_repExtShareMemory plugin for Vrep. (UPDATED 13/09/2017)This Plugin allows fast inter process communication of V-REP. It's particularly useful to communicate V-REP with Matlab or Simulink. Here some information:

¿What is Share Memory?“In computer programming, shared memory is a method by which program processes can exchange data more quickly than by reading and writing using the regular operating system services”

¿Why use Share Memory instead V-REP communication Plugin?Share Memory plugin is the fastest and simplest interprocess communication method. It doesn’t make any synchronization; it has not transfer delay, death times or transfers buffers/queues.

¿It is secure? In order to ensure top speed communication this plugin don’t use any inter process synchronization method, so NO, IT’s NOT SECURE. Lossless communication is not ensured. If a single program writes the memory, in practice it will not crash. For for bilateral communication of two programs create two separate share memory’s!

¿For what it would be used? It allows communicating V-REP with external process (running in the same PC), so you could communicate with almost any program developed in any language that allows Share Memory communication. For example you could communicate V-REP with C/C++ custom program ,Matlab m-function , Simulink block, LabView scheme, and any other program/language that can access share memory. You could, for example , make bridge between your robots hardware and Vrep.Event functionality could be use for fast synchronization of V-REP with external program too.

Creates and open a new shared memory ID it’s the number assigned to the share memory, it is his main identification but not the only one.Name is the Share memory name, it must be unique in all system. All process that access to a share memory with this name could read and write it! Size is the size in bytes of the share memory, take care of the dimension assigned, if you try to read or write out of this area you will get an error.

Close specific share memory by its ID. If you let this empty, it will try to close any opened memory. Be aware: If you don’t close the memory at the end of the simulation, it will remain opened. If try to open it again, you will get an error. When the program is closed all instances of share memories are going to get closed. In fact all share memory’s remains opened until all programs close it. It’s a good practice to close the share memory in the same script that you create it.

Reads a share memory by its ID.charbuff data shoud has full size of the memory , so be aware to create a sufficient big variable to contain the hole memory. After you may format data with simUnpackFloats() /simUnpackInts() functions.