About stefanAT_ctrlX

stefanAT_ctrlX

Maybe the S-530 block torque value is not adjusted the rigth way. I mean it's maybe too small and the customer reached allready the block value when starting the reference moving ? Regards, Stefan

stefanAT_ctrlX

Yes, with the option "Control via DRIVElink" not the S-134 is used but the P-1872. For example I have a project where I intended to use the control via DRIVElink at the slave because I want just one slave device on the bus (I mean my customer just wants to see one slave on his sercos (or EtherCAT) bus (=DRIVElink-master). And the P-1872 in the DRIVElink slave is controlled by DRIVElink master.

stefanAT_ctrlX

Hello @Joonas , I just made a fast check with my XCD and integrated CORE. I have just no motors connected and therefore I use AxisSimulation. But I set AF with S-134 (directly here now from DataLayer /Fieldbus S-134 to 111.... and also before the slave S-134 to AF. The S-47 I have just for the masterdrive and the for the slave drive I cancelled the S-47 from the EtherCAT (IO-Engineering) (you need the Expertadjustments to change the process data) . The slave follows the master. That was just a fast test ! 😉

stefanAT_ctrlX

Thank you @Sgilk ok, I will check...

stefanAT_ctrlX

The can0 is now with a green check at the settings/interfaces after $ sudo ip link set can0 type can bitrate 125000 $ sudo ip link set up can0 I used bitrate 500000. How can I use the can0 interface then in node-red? I thought to install https://flows.nodered.org/node/node-red-contrib-socketcan but that doesn't work (some errors occur). But I can import other nodes, connection to internet is working.

About stefanAT_ctrlX

Betreff: Reference travel direction inverted when homing

Betreff: DRIVElink with integrated core

Betreff: DRIVElink with integrated core

Re: Reading CAN bus data into ctrlX CORE

Re: Reading CAN bus data into ctrlX CORE