07-12-2010 09:27 AM
I do have those drivers but I've never been able to post them due to IP restrictions. This request has come up several times in the forum, so I'm going to see if the situation here has relaxed somewhat with respect to being able to distribute this specific set of drivers. Can't promise anything. If I do get permission to distribute them I'd likely submit them to as a developer zone article rathat than this post.
07-12-2010 02:31 PM
07-12-2010 10:29 PM
@Znatok wrote:
Hi, For the new projects I recommend you to use SUB-20 instead of U2C. U2C is discontinued as it is based on end of life Cypress CPU (http://www.xdimax.com/usb_i2c/u2c12.html) New SUB-20 here: http://www.xdimax.com/sub20/sub20.html Has native LAbView support via VI and .NET component. Besides it has a lot of new features like PWM, A/D, MDIO,. RS232. According to their forum many people are using this feature already.
I agree. If we needed to replace one of our Diolan boards I'd probably opt for one of those.
08-02-2010 12:48 AM
Hello,
I already am with Diolan U2C board and doing communication using the .DLL file in labview....i am getting problem in U2C_SCAN_DEVICES function in DLL, I am using the API documentation with from DIOLAN.
If u have any help document with drivers can you share thanks.
If you were able to release the LabVIEW drivers for same board. let me know thanks
Regards
Vish
08-02-2010 01:00 AM
HI,
No I do not work with U2C. I use SUB-20 http://www.xdimax.com/sub20/sub20.html
and so far no problems. Perhaps some info related to SUb-20 will also be helpfull in your case:
08-02-2010 08:37 AM
@vish.solanki wrote:
Hello,
I already am with Diolan U2C board and doing communication using the .DLL file in labview....i am getting problem in U2C_SCAN_DEVICES function in DLL, I am using the API documentation with from DIOLAN.
If u have any help document with drivers can you share thanks.
If you were able to release the LabVIEW drivers for same board. let me know thanks
Regards
Vish
Which function are you trying to use? How is the Call Library Function Node configured?
08-04-2010 05:12 AM - edited 08-04-2010 05:14 AM
I am unable to get data , when i read "U2C_Read" (DLL function from i2cbrdg.dll).....can you share some information on ...using functions "U2C_Read" and "U2C_Write" from DLL library
Thanks a lot in advance...:womanvery-happy:
vish
08-04-2010 09:06 AM
I don't actually use the U2C_Read or U2C_Write functions. For I2C communication I use the "GetByte" functions and the "PutByte" functions. There are several of these, depending on what kind of operation you need to do. For SPI I use the "U2C_Spi_Write" and "U2C_Spi_Read". The reason I didn't use the "U2C_Read" and the "U2C_Write" is because they want a pointer to a structure, and in the past I've almost always had to resort to using a wrapper DLL to deal with this kind of datatype with LabVIEW calling DLL functions that used it.
08-16-2010 07:27 AM
Hello Smerico,
regarding Diolan U2C board...and its communcation to .DLL file
Can you help me with "U2C_Read" function, to implement using Wrapper DLL, I tried but not getting. (If u can give a small example)
For this Function "U2C_Read", I tried to use Wrapper DLL, i give input "handle device" and other input is a pointer to a structure.
* This structure contains all required information to perform I2C transaction
*/
typedef struct _U2C_TRANSACTION
{
BYTE nSlaveDeviceAddress; /*!< I2C Slave device address in 7 bit format */
BYTE nMemoryAddressLength; /*!< Slave Device Internal address size */
DWORD nMemoryAddress; /*!< Slave Device Internal address (Memory address) */
WORD nBufferLength; /*!< Transaction buffer length. Can be from 1 up to 256 */
BYTE Buffer[256]; /*!< Transaction Buffer */
} __PACKED_ATTR U2C_TRANSACTION, *PU2C_TRANSACTION;
Can you tell me how to pass the pointer to this above structure to the .dll file of the DIOLAN board
Thanks lot in advance....:womanhappy:
08-16-2010 08:04 AM
Hello Smercurio,
I got it..
its fixed....i tried using "array data pointers" ...