02-27-2024 04:40 AM
Dear all,
I'm trying to read and write information from a acceleration sensor with TEDS (e.g. sensitivity, calibration date, serial no.) with LabVIEW without using the NI hardware. I'm using a serial interface with an USB to RS232 adapter and a RS232 to BNC adapter.
I'm able to read the basic TEDS values (manufacturer, serial no. ASO), but I can't read the further information in the EEPROM.
My problem seems to be, that I need the proper commands for the bus.
I hope someone out here can help me with my problem!
Regards
Franzi
02-27-2024 12:47 PM
02-28-2024 12:41 AM
Thanks for your answer, but that's not what I asked for.
I know which template I need and with the right bitstream the values are shown correct. But I don't know the commands to get the right bitstream.
I copied the bitstream from a TwinCAT project which can read TEDS and was programmed by a colleague of mine. With this bitstream I get the values displayed correct with the template for my sensor. But I want to get the bitstream directly from the sensor without using the Beckhoff PLC.
02-28-2024 12:58 AM - edited 02-28-2024 12:59 AM
Hi Franzi,
@FranziskaZapf wrote:
I copied the bitstream from a TwinCAT project which can read TEDS and was programmed by a colleague of mine. With this bitstream I get the values displayed correct with the template for my sensor. But I want to get the bitstream directly from the sensor without using the Beckhoff PLC.
Are you sure you can use a plain RS232 port to communicate with a TEDS sensor?
(How did you connect the RS232 to your BNC connector? How to you supply power to your sensor using the BNC connector?)
This article suggests something different when using a 1-wire communication bus…
02-28-2024 04:26 AM
Hi GerdW,
as I'm able to read the basic TEDS values (screenshot is attached to my original post), I think the connection with the RS232 should work properly.
Regards
Franzi
02-28-2024 06:01 AM - edited 02-28-2024 06:15 AM
What vis are you using ? Just curious
(Seems to bitbang with the rs232 driver and/or additional DLLs)
Seems that you need to read the docs of the vis and the used DLL.