Advanced Search

Does joint.N.amp-fault-in actually turn the machine off? I'm not sure it does. I know it stops motion. My thinking is that conce you have the machine dialed in you will never get this error.

Aahh shoot! I was hoping to avoid resoldering my DIY pullup resistor board. But thank you for the explanation.

Hello, I was trying to change the bitfile in my 7c81 so that there would be only one 7i78 on port P1. Port P2 would be freed up for separate MPGs for X and Z axes. So there would be no need for 7i33 (which would probably be another complication I wouldn't go through). But in the Mesa firmware there is no 7i78x2 configuration, nor 7i78 for Xilinx ISE (*.xise). Is it possible to download this configuration somewhere else?

Good morning, I have looked at the code now. Clear out the whole loop() function and insert just this line

That should do it. You never called ecat_slv() in cyclous mode.
The danger of using someone else's code.
It meant it never used spi to query lan9252 for changes and updates to register etc etc.

There were a lot of diagnozing and trouble-shooting with the I2C so I wanted an easy way
to run the board as a normal aurduino without the ethercat things. It was required to define ECAT
during compile for it to be an ecat device. Now that is gone, so remove all of that.

Fastfred wrote:

 I will try to figure this out my apologies That I haven't picked up on this yet.
 

No worries, you'll get through this even if you feel like you're lost now.

Takes a while for HAL to sink in - it did for me.

I was able to solve the error with maxvel too big by changing the steps per revolution to 2500 in the servo controller. Now I just have to solve the problem with the MVO.

No I did not copy the whole thing just the hal part for HLFB thats it.

Thanks

Why would graphics drivers help?

Does the screen look blurry?

Is your monitor connected via VGA?

I recommend DisplayPort, or basically anything that is not analog.

(As a general rule, digital video connections will reduce framerate if the resolution is too high for bandwidth, not reduce resolution)

Just so you know, the editor is kinda broken and if you make some text italic and then you edit your post, all text after the italicised text will become italicized for some reason, which is annoying.

 

You should not JUST copy the three files I posted; at best you could insert the snippets I posted first (there's a section in my custom.hal that matches it, you could cut-n-paste that). You *should* be able to use my HLFB logic as-is if you have wired each servo to its own enable/fault pins, and have a gantry-style (dual Y) system.

With a basic understanding of how HAL works, you should be able to figure out my hal setup. I'm not an expert at HAL so my logic is pretty basic. The bigcnc.* files are pretty much right out of pncconf (but tweaked) and the custom.hal file is all mine.

I really do appreciate the help I am getting I did say I don't understand this part yet and I am sure I was told to copy the file that was posted  djdelorie and just change the card pin naming to fit for my needs I will try to figure this out my apologies That I haven't picked up on this yet.

Ok ok. Spi was a pain for me until I got it sorted that's why I wanted to be really sure it works. Nothing works without spi.

There are a few hardware bootstrap jumpers on the Lan9252.
They are described in the schematics for lan9252 evaluation  board.
I have them marked on all board schematics. 
You can compare them with your board, perhaps there is something different?

I guess it wouldn't be too difficult to replicate your board and try to troubleshoot it.
Can you make sure to push relevant code to github and I can have a look at that.
I'm pretty sure I can puzzle together the hardware.

You are going to end up designing a board, just start haha.
You mention I2C. If you need it, yes. Otherwise no. I used it for 
plasma arch voltage. Worked great, but if you don't need it don't include I2C.



 

Fastfred wrote:

  Unless I still having a naming issue with the pins unfortunately I still don't understand this part yet. 


 

I think you don't understand HAL naming and so forth.

The HAL section you posted earlier has some issues:net hlfb_x => and2.0.in0
net enable-faults => and2.0.in1
net x-fault <= and2.0.out
What the above does is connect signal 'hlfb_x' to pin 'and2.0.in0'

And if the signal doesn't already exist when LCNC gets to that line in the file, it creates a signal with that name.

Problem is, nowhere in the section you posted is another pin connected to either signal 'hlfb_x' or signal 'x-fault'  So the 'and2.0.in0' and 'and2.0.out' pins are not connected to another pin.  The AND2 function isn't doing anything.

You need to link two (or more) pins that already exist for the logical function to work.  You create the signal names, but the pins must already exist in LCNC.

net SIGNAL PIN1 PIN2 is the format.  You can put the connections on different lines, and the "=>" symbol is helpful when reading the file, but not necessary.

All of which means your attempt (I think) to add a time delay in the amp-fault / amp-ok sequence isn't going to work.  Your physical inputs are connected directly to the amp-fault-in pins, and the time delay logic isn't in the equation.

Try this.  I've put each part on a separate line - make the file longer but can be easier to read for some people:

net  x-fault-in         hm2_7i96s.0.inm.00.input-10-not
net  x-fault-in         and2.0.in1
net  enable-faults  and2.0.in2
net  x-fault-delay   and2.0.out
net  x-fault-delay   joint.0.amp-fault-in

In order to limit costs and continue tests maybe I should try to build a lan9252 prototype board with eeprom spi and i2c.

Thanks will look at them soon and try.

Here are my full configs, since I didn't know which "part of the file" you meant.