7i92 and G540 combination?

Here you go.. Maybe you could tell me what your looking for...

 

Is this after you attempted to go into run mode and it failed?
because it looks like it has not been requested to release estop:

4 bit OUT FALSE iocontrol.0.user-enable-out ==> estop-out


Maybe related the charge pump frequency is incorrect (2500 Hz rather than 10 KHz)

Also the chargepump it will not run until you get out of estop the way the chargepump stepgen
is connected in hal.  It may be needed to permanently enabled.

Also is it possible you have the fault polarity inverted? ( so as soon as you enable the charge pump you get a fault? )

To test further I would disconnect the fault input pin in hal and manually test the other functions

 

I went ahead and disconnected the e-stop in the hal.
I could see the status light set to a solid green on the gmoccapy but no motor movement.
the halcmd shows:
 
it does seem as if the charge-pump is not set to the right frequency.
the way the fault light is semi lit seems to be an indication.
I have the ability to try and put the e-stop on pin 13 maybe that bypasses the latching circuit.
which works...

You should be able to set the chargepump frequency to 10KHz by setting
hm2_7i92.0.stepgen.04.velocity-cmd to 1.0

it comes back with command not found...
Am i meant to be in some sort of directory...?

Re-posting the current hal file that includes the charge pump setup
would help by showing the exact line that needs changing.

That is , there is likely a line in the hal file like:

setp hm2_7i92.0.stepgen.04.velocity-cmd .25

that needs to be changed to

setp hm2_7i96s.0.stepgen.04.velocity-cmd 1

Oh, Thanks for that, I had no idea you meant edit the hal...
the difference in frequency did nothing.
all i can do is show that i am on the right page...
 
 

When you said "did nothing" do you mean that the G540 fault light is still illuminated?
Do you have the  external Estop connected? (pin 10 grounded)
Have you tried disabling the G540s watchdog?
 

In summary I have the e-stop disconnected in software,
however it is still connected physically because the g540 wouldn't respond without it...
I have setup pin 13 as an e-stop using the NO of the switch(the g540 takes a NC), and this is working as it should.
So the fault light still functions when i latch the physical and software switch, it is just that the motors never get enabled...


I'd like to try disabling the watchdog if i could, that seems relevant...