01-18-2016 07:59 AM
"I don't think it outputs an analogue value but if it did, that would be incredibly useful."
Well, if you read the specification sheet of the device, it is going to be clear (it was not clear to me what device you want to interface, since you mentioned two things, and did not link any manual...). Do you have a spec sheet (pdf file)? Can you share it with us?
01-18-2016 08:02 AM
01-18-2016 08:19 AM
I guess the manual lists all interface options which can be ordered. What interface of your actual model has? I do not really have any experience with these protocols/interfaces, I wonder whether the EtherNet-IP version can be simply connected to a normal Ethernet slot on a PC? Maybe someone familiar with these interfaces could give more explanation here?
01-18-2016 08:22 AM
I have the CANopen option so it doesn't have etherCAT capability unfortunately.
Its model 5P33
01-18-2016 08:28 AM
Is it a viable option to buy an encoder with analogue output? The same company offers absolute encoders with analogue outputs. If you have AI DAQ already, this could be an alternative option.
On their website they show many models with analogue outputs:
Maybe they could swap your model with an analogue one?
01-18-2016 08:30 AM
Unfortunately I am stuck with the particular encoder I already have so need to figure out a solution based on this model
01-18-2016 09:26 AM
01-18-2016 10:51 AM
Increasing the budget or replacing the sensor are not options unfortunately.
There must be anotehr way. Since it operates on the CAN bus anyway, I think I can use a USB CAN interface for layer 1 and 2 and use the manufacturer software for the CANopen comms. I dont know how I would port it into LabVIEW. The manufacturer does provide .EDS files so perhaps this is for use with CANopen comms?
01-18-2016
11:02 AM
- last edited on
12-09-2021
04:06 PM
by
NI_Community_Su
Hi David,
as long as your employer pays your working time everything is ok… 😄
You could buy some hardware for ~1000$ or you can work for some time to get the same result. It's a decision your employer has to make!
EDS files (electronic data sheets) describe the "objects" your CANopen device uses, it's just a list of "addresses" and their meaning. They will not help you to implement the CANopen protocol layers!
Just an idea (I don't recommend to go this way): On NIs website you will find CANopen "drivers" to be used with cRIO/FPGA targets. They will show you how to implement CANopen commands like Read/WritePDO or Read/WriteSDO based on basic CAN messages. See how far you get…
01-18-2016 11:04 AM