Advanced Search

Hi All, 
At some point the S-code could be used to command the spindle speed. The control sends an analog voltage to the LARRIOZ speed control card. The card reads a sensor that counts spindle revolutions and compares it to the commanded speed. The card can then switch relays, that in turn switch the contactors driving the motorized CVT transmission between spindle and spindle motor to increase/ decrease the spindle speed as required.
 
This never worked since I got the mill. I did at the time try to get it to work, but due to lack of knowledge and/ or documentation, I could not get working. I would think that the lithium battery in the Dallas non-volatile SRAM would be long gone, but I am not sure what would be stored in SRAM. I assume (While I know not to assume anything) that the firmware would live on the EPROM and the SRAM might hold parameters relating to the specific installation. Other than JP 1(Jumper), and P1 (Potentiometer) there is no other configuration or programming port on the LARRIOZ HABIKON1 board.
Although slow, I prefer this system, as I would not sacrifice low speed torque, as would be the case with using only a VFD for speed control.
I suppose it would be fairly easy with modern microcontrollers to get the system going again, but I would be happy to hear from others as to their experience or suggestions as to how I should proceed.
Regards
P
 

langdons wrote:

Also, how can a person do roofing, plumbing, parquet flooring, and CNC?

Multi-talented! perhaps too multi-talented!

Stop offending people, i will not warn you again!
Instead, go read through this forum, watch pictures and videos, you might get some appreciation about what our members here are capable off.

It would probably be a good idea to add MaHa's G10 solution to your startup code..

endian wrote:

Did anybody get it to run with Rods guide??

E.

I don't think it works.  The master is meant to sense if of EoE is available but 2 things collide.
1. There is a bug affecting this drive in the ethercat master
2. the Linuxcnc  driver does not support EoE

I think without the bug it should fall back to supporting non-EoE mode but its a long time since I looked at this.

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.