LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

labview connection with STM32 via I2C.

its not using any FTDI chip.
so, now im trying python code to communicate with stm32 via waveshare usb to i2c converter to read and write data as we use minicom or putty to check the connection but its not getting connected.

0 Kudos
Message 11 of 21
(183 Views)

I want to ask how many approaches are available to do the connection between labview and stm32 via I2C?
HELP!

0 Kudos
Message 12 of 21
(179 Views)

Hi Anup,

 

please keep related discussion IN ONE THREAD!

Is there a specific reason you wanted to start a new thread despite you already got answers on your problem?

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
Message 13 of 21
(148 Views)

@AnupSW13 wrote:

I want to ask how many approaches are available to do the connection between labview and stm32 via I2C?
HELP!


Seriously? I would think there are as many as you can think of! That won’t really help you but is a factual answer to your totally open ended question!

Do you expect us to spend hours listing them all for you? We are not here to do your homework.

Rolf Kalbermatter
My Blog
Message 14 of 21
(139 Views)

Screenshot (20).png

Screenshot (21).png

 

the error im facing is that 
1. it reads the data but it still shows timeout exired.
2. timeout expired error and not reading the data.
3. A framing error ocurred during transfer
4. A overrunn error ocurred during trnasfer. A character was not read from hardware before the next character arrived.
help?

0 Kudos
Message 15 of 21
(148 Views)

I guess you don't send/use termination character correctly.

G# - Award winning reference based OOP for LV, for free! - Qestit VIPM GitHub

Qestit Systems
Certified-LabVIEW-Developer
Message 16 of 21
(141 Views)

Hi Anup,

 

is this still the same communication line as in all the questions before?

 


@AnupSW13 wrote:

help?


  • You didn't cleanup your block diagram so use AutoCleanup!
  • You forgot to implement complete error handling.
  • You seem to forget about appending LF or CR chars with the command message.
  • You don't need to call VISAOpen and ConfigureSerialPort both. Use only ConfigureSerialPort before the VISAClear function!
  • Hide the labels of the functions, we usually know them or use the context help window to read their names. (It just clutters the block diagram.)
Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
Message 17 of 21
(133 Views)

Screenshot (22).png

 

 

is it correct now?

 

0 Kudos
Message 18 of 21
(119 Views)

@AnupSW13 wrote:

 

is it correct now?


How can we know from a picture?

 

Read this answer and then come back again:

https://forums.ni.com/t5/LabVIEW/Delta-elektronika-VISA-read-in-error/m-p/4409726#M1299458

 

Rolf Kalbermatter
My Blog
Message 19 of 21
(115 Views)

Hi Anup,

 


@AnupSW13 wrote:

is it correct now?


You still forgot to use AutoCleanup…

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
Message 20 of 21
(106 Views)