Jump to content
OMRON Forums

Recommended Posts

  • Replies 4
  • Created
  • Last Reply

Top Posters In This Topic

  • 1 year later...
Posted

I am trying to set-up the 8ES accessory with the Power Clipper, but the IDE set-up does not work.

I upgraded the Power clipper with the latest firmware (in 2 steps) and the latest IDE.

For some reason the setup utility does not work, I get the following error messages.

Can you give me the settings for the DACstrobe and DACshift?

 

 

Outputs

system ethercat -m0 xml //11/17/2016 :12:53 PM - 192.168.0.200

system ethercat master // 11/17/2016 :12:53 PM - 192.168.0.200

Sys.MaxEcats = 1 // 11/17/2016 :12:53 PM - 192.168.0.200

Error messages

11/17/2016 :12:53 PM - 192.168.0.200, Module - Setup Motor : Global mask: 0xffffffff

11/17/2016 :12:53 PM - 192.168.0.200, Module - Setup Motor : CS mask: 0x201ffc

11/17/2016 :12:53 PM - 192.168.0.200, Module - Setup Motor : Motor mask: 0xc01ffd

11/17/2016 :12:53 PM - 192.168.0.200, Module - Setup Motor : Macro ring mask: 0x1e

11/17/2016 :12:53 PM - 192.168.0.200, Module - Setup Motor : Update period: 1.000000 Sec

11/17/2016 :12:53 PM - 192.168.0.200, Module - Setup Motor : Sys.Default=1 @ 17-11-2016 12:53:13

Debug messages

11/17/2016 :12:53 PM - 192.168.0.200, Module - Setup Motor Container : There was some error while executing database query. Details : Database Error:Table 'ppmac192_168_0_200.hardware_tbl1' doesn't exist.

11/17/2016 :12:53 PM - 192.168.0.200, Module - Setup Motor : There are no EtherCAT devices connect to Master[0].

11/17/2016 :12:53 PM - 192.168.0.200, Module - Setup Motor Container : There was some error while executing database query. Details : Database Error:Table 'ppmac192_168_0_200.hardware_tbl1' doesn't exist.

11/17/2016 :12:53 PM - 192.168.0.200, Module - Global Clock : Empty Servo hardware List

Posted

Dacstrobe =$7fffc000 works.

 

I already tried that value before, but it did not look correct since the command signal still changed after the out0 command, slowly climbing to 10V.

Looking a bit further I noticed this was cause by the fact the current loop enabled by default!

 

So the signal changed was probably caused by the offset on the analog input.

After setting motor[].pAdc =0 everything worked fine.

Guest
This topic is now closed to further replies.

×
×
  • Create New...