Advanced Search

I'm working on a low-cost retrofit for my Deckel FP4A and I really want to reuse the existing motors, but I'd like to replace the stock Industrial Drives drives with ones that operate on single phase 220VAC, so in order to do that in an affordable way I think I need to use a resolver to SSI converter to get absolute position data from the motors for commutation by the drives. I'm wondering if anyone has gone down this road before and had any insight to add.

Currently I think I want to use the Delta ASDA-A2 drive and a Vega 2796524 Resolver to SSI Converter, has anyone tried this before?

I'm still going through all the datasheets I can find, but based on what I've found so far, I think this should be a workable solution.

Ideally I would be using a drive that can natively handle resolver feedback, but I haven't had any luck finding such a drive for a reasonable price. Any info is greatly appreciated!

Luckly the company that built the machine vfd sent me the manual.

Just checked the price for an EL4102 costs more than a new recent VFD, are there other ways to control the spindle with ethercat?

The VFD allow to control rpm in many ways:

0/10v
-10/10v
0/20mA
4/20mA
By serial

Are you going with ColorCNC by romanetz or LiteX-CNC.

Either way the basic thing is, your create a config for the firmware using a json file, follow the instructions to build the firmware, upoad the bit file to the Colorlight board, then create a Linuxcnc config & ini files.

Litex-CNC (it's been awhile since I decided not to use this as I felt it was easier to go another route.)
So, no one does not upload a config to the board, a new bit file has to be built.

The way I tackle a new project.
Read the whole thread, take notes, follow the link on the github page to the docs, read the docs, have a browse around the github page. Take a bit of time to get the feel.
Setup a build environment, and attempt to build a config. Then I'd modify one of the supplied configs to get a hang of it.
Eventually I'll upload a bit file to the board, probably from one of the supplied json files. Reread the read or refer to any note regarding creating a hal file.
May take a couple of nights or weeks depending on a lot of things. You may find you'll have to read & reread & reread some more. I'm sure there's some examples scattered about in the thread.
Research is the key point. All the info is there.
If you don't fully understand how it works, you may have to find someone to do the hard work for you. Or have a look of one of the more active projects, maybe Linuxcnc-RIO, which uses a larger range of FPGA boards (even the mesa clone I designed works with Linuxcnc-RIO) and doesn't rely on the ever changing availability or certain Colorlight boards being available and actually being shipped to you.

I think there won't be any problems with this. The main thing is to understand what needs to be done with the control board, in particular with colorlight. As I understand it, the author of the topic dropped the firmware files from this board and not only the author. i.e. all the files for changing and assigning ports are there. In fact, you just need to upload the files changed to your parameters to the board. Is that correct?

Cant do this anymore bye all wrote:

I like the fact there’s no adds.

I agree with you!

Cant do this anymore bye all wrote:

It would nice to see a link of method to donate a few coins. If I’ve missed it if someone has a link it would be appreciated.

Du hast Recht, das habe ich auch noch nicht gesehen, aber das ändert nichts an der Grundproblematik.

Cant do this anymore bye all wrote:

Whilst the editor is a pain, switching to “source view” can make life easier for edits.

It's not just the editor.
The site and I believe the forum are no longer included in the updates (security update).
Many functions have been deactivated or are not working properly.

Hence the desire to update something here.
(I am ignorant though)
- User structure, who edits what.
- Who can put new versions of LinuxCNC online?
- Who edits the wiki?
- Forum administrators, ....
- ... etc.

There are so many different places in the background that I don't know, as I'm just a normal user, so I can't estimate all the consequences, hence my suggestion.

Guys need help new to linux cnc
just starting to build my 1st cnc
using linux cnc
any recommendations for my setting 
 

my solution is convert analog out of vfd ( config analog out is load ) to fequency + use mesa card counter function

Usually, an analog input is required. However, another option is to connect an RS232/RS485 interface to the spindle inverter. I chose the second option, and it works well. You can skip to the 1-minute mark in the video to see it in action. There's a small bug with the numbers, though

Is that just a y thing?

Is it possible to run all these things together: 

Mesa 7i76 E  ---- 7I84 (Isolated remote field I/O card). Will use it to output quadrature signals to the Ultra3000s, it will generate this quadrature output from the Fanuc encoders [is this possible?], remaining I/O used elsewhere. 
                               
                         ---- 7I85 (4 Channel encoder 5 channel Serial RS-422 interface). Will hook up the 4 Fanuc redcaps to 4 of these RS-422 ports. And the encoder inputs are good to have around incase I want to add linear scales (2 axis) and maybe two MPG wheels. 

Sure would be great if this system worked because it happens to be two fairly inexpensive boards. Canadian dollar isn't so great right now 
I would be pleased to have those encoder inlets, too. 

Progress pic from a little while ago: 
 

Licenses were reviewed in depth by Debian as part of getting into their distros. (There are many different licenses) I think you can say the differences in licenses is not a conflict or we would not be in Debian

If the axis do not move, I would check:

1. That you don't have a watchdog bite
(If you are running "Axis" it will report this if not,
you may need to check with halshow)


2. The physical wiring (remember I asked what were the
connections between TB2 pins and drive signals?)


3. The timing specifications of the drives (the current timings should work
with most drives but there are so oddball drives with really slow inputs)


 

Y cannot jog until it is homed.

andypugh wrote:

Is there any chance that this corresponds to something in the kinematics? Maybe an inflection point in one of the joints?

Its possible that at that point another joint starts contributing to the motion.
Think of 2D motion on X & Y at 45 deg at max velocity. Both axes will be moving at their max, but the total combined axis velocity  will be about 40% higher.

okay update. 

I reran the pncconf, reassigned the second y as a tandem and also corrected what turns out was mis-assignment by me initially. Everything should be good to go now in terms of what the board thinks is assigned and what is actually. Updated hal and ini attached. 

Still no movement from any axis:
X: Does nothing physically but machine thinks its jogging (DRO updating)
Y: Throws an error: "Cannot Jog Joint 1 because home_sequence is synchronized 
Z:Does nothing physically but machine thinks its jogging (DRO updating)
A: Does nothing physically but machine thinks its jogging (DRO updating)