Scan Time issue

ADVANCED-Joe

Member
Join Date
Oct 2019
Location
Montreal
Posts
3
Hi all,

I've recently been trying to make home-made profiler with a transducer and a laser.

The setup is pretty simple, the laser slides on a rail which is attached to the magnet of the transducer. The transducer gives me the position (x) of the laser and the laser gives me the distance to an irregular surface (y).

Combined together, if i take the distance given by the laser at every 1mm, I can create the profile of the irregular surface.

My issue is the PLC scan time which is about 20ms to 50ms. Since the scan time too long, the system has time to go through multiple positions before the scan is done which makes it impossible to get a distance value at every 1mm.

Does anyone have experienced something like this before?
I'm looking into buying a data logging card, but i don't know is this is my best option.
 
Laser : Keyence IL-100

Transducer : MTS Temposonics R-Series, RP S 1200U D60 1 A01

Both sensor give 4-20ma signal

Both of them connected to Flex/IO 1794-AENT in an Isolated analog input 1794-1F41

PLC is an Allen-Bradley 1756

For now the laser is on a rail and is moved by hand. The transducer magnet is clamped with the laser so when I move the laser, the magnet follow. It’s a very primitive setup and will be upgrade later to automate the laser motion.
 
Beckhoff has some modules that will buffer the readings for you into your normal scantime. The ethercat network is good at synchronising time between modules should you want the exact same timestamp on your two inputs. Taking beckhoff part number EL3702 for example, the -10 to +10V version. This module can transmit 100 samples per scan, up to 100k samples per second. 1ms or smaller cycle times are typical for beckhoff and other Codesys controllers. There are many other Codesys controllers that can use these ethercat terminals as well, like Siemens IOT2000.
 
Looking at the data sheets, your fastest update rate of your two sensors is 1ms. Is that enough for you?

I can't think of an AB remote IO solution that will give you 1ms update, perhaps you will need to wire to local IO. Even then 1ms can be tough.
 
Don't forget about the latency of the analog input itself. You may be able to configure the input point or card for reduced latency, but don't forget that it will still likely be greater than the PLC scan time and a bigger influence on the success of your project.
 

Similar Topics

Good morning all. Quick background, I’ve had no real formal PLC training, pretty much self taught. I have 2 identical machines with a SLC 5/05...
Replies
3
Views
1,940
Good Day, I'm using Mod Scan 232 for testing a Modbus RTU network on RS 485. The modbus device is Accuload iii.net. The connection settings on...
Replies
1
Views
4,190
I have a 1336 drive running on scan port from a slc 5/04 with scan port adapter card. we are sending a value over scan port and linking it to...
Replies
7
Views
2,924
Hi, I was wondering if anyone has experiance with the Microscan MS-3 laser matchcode set-up. I'm reading a label with 2 barcodes on it. I've...
Replies
1
Views
2,044
Hi everyone, I'm trying to simulate any program in control expert and see a register in Modscan32 or any software to do that (Like ModbusPoll). I...
Replies
0
Views
107
Back
Top Bottom