Advanced Search

So to find rapid speed the trick is to set high initial rapid speed and watch ferror in halscope and at jog speed that ferror has huge increase minus for example 1% of that jog speed is the rapid speed?
Is there a way to force 7i33 to output 10V?

Also how can find max acceleration?

the FBUC is also ferrocontrol, its a fieldbus interface card with some I/O expansion cards connected to it,
couldnt find any sort of control in/encoder outputs on the drives, they just connect to the supply module that connects to the PC+fbuc, so looks like thats the only way to control/recieve feedback from them

I understand, as far as what I've seen from the manuals and such the fielbdus is proprietary and as per an elumatec engineer's review himself, the system wont even enable itself until all ferrocontrol only components are connected to each other, so theres no point in a half swap to third party, might as well just switch out the entire drive system, (though the only obvious issue is with the PC here, the guy from elumatec also said the same 28k USD for a new PC, so safe to say thats not an option)
Thanks for the advice, at the very least I did get a pretty decent bit of knowledge about linuxcnc which was quite interesting, and hopefully someone else with the same issue can use this information to save some time.
As for our next course of action, we'll start looking into retrofitting kits and other controllers like mach3, if anyone has any other suggestions or reviews on good companies with full retrofitting kits (drive system + controller etc) I'd appreciate that a lot.
Bit worried about the price for the spindle especially, but I've been told there are some pretty decent chinese companies with cheaper motors, and another option for the axes is just choosing a lower power drive and using a gearbox to match the necessary torque, so I'll keep looking.


edit: just went through the document and found this section, might be relevant:
Complex automation technology plants require an effective and radical possibility
of monitoring, i.e.
• insight into the system, in particular the retrieval of conditions
• influencing, intervening in the system
under various conditions:
• initial commissioning
• plant-specific basic parameterization
• subsequent altering or optimization of the settings
• service and regular maintenance
• malfunctions
For this purpose, two interfaces are available to the DARC system as a partial
component:
When it is integrated into a CAN or Profibus-DP-fieldbus system the DARC system
can be parameterized, tested and commissioned via the serial service interface RS-
232.
When it is integrated into the ferrocontrol CNC fieldbus system the DARC system
can be parameterized, tested and commissioned via the fieldbus.
The following chapters describe all the procedures and methods, depending on the
type of fieldbus used, necessary to operate the DARC system with the appropriate
service interface.

 

I have also speed mode servos tuned
with p and ff1 so cruise ferror is 0
but at the start - stop i have ferror spikes.
How to guess initial ff2 value?
What else can i do for start-stop ferror?

Problem: "looks 50% too large" seems to get bigger over time (with every project), but the rule still seems to hold water at the end.

I love the temp wiring stand. I will definitely use it going forward.

What io's do you think you are missing?

I notice that your digital in and digital out are empty. I had to use this to control my tool changer, pnumatic gripper, and to read spindle & tool changer sensors. It is how the O-code program can control the outputs and check the inputs.

I linked my door lock to some classic ladder pins.
Ex: "net door-open classicladder.0.in-01 => hm2_7i97.0.7i84.0.0.input-00"

The sserial seems like it might be right. Check to see if you can see the 7i84 pins in halshow. I had to expand pins > 7i97 > 0 > then I could seen the 7i84. If it doesn't work try replacing the XXXXX with zeros to become "sserial_port_0=00000000" It is what works for my 7i97T + 7i84 setup.

Thanks you All!!! I am not familiar with Python. I am starting to learn it.
In the meanwhile,
If I only want to add an image in the AXIS GUI, that will show a Camera view near the tool, and 3 label boxes.

What do you think it will be the easier way to have it done quickly?

Is this source code correct to add in the INI file to see the image

[DISPLAY]
PYVCP = image.xml

<?xml version="1.0" encoding="UTF-8"?>
<pyvcp>
<image name='fwd' file='fwd.gif'/>
</pyvcp>


This source code would be correct to add for the labels?

<pyvcp>
<label>
<text>"AXIS X"</text>
</label>
<label>
<text>"AXIS Y"</text>
</label>
<label>
<text>"AXIS Z"</text>
</label>
</pyvcp>

Or should I use something like:

Et1 = tk.Label(WINDOW, text="AXIS X", font=("Arial", 24), fg="blue", bg="yellow")
etiqueta.pack(padx=20, pady=20)
Et2 = tk.Label(WINDOW, text="AXIS Y", font=("Arial", 24), fg="blue", bg="yellow")
etiqueta.pack(padx=20, pady=20)
Et3 = tk.Label(WINDOW, text="AXIS Z", font=("Arial", 24), fg="blue", bg="yellow")
etiqueta.pack(padx=20, pady=20)




Thanks a lot.

There are some variables at the top of the shetcam post processor that allow you to prevent generation of the hole data if you don't want to use it.

Thank you very much! I will do that tomorrow (german time) and report the result!
Have a nice day!
Sincerely,
Hanno

Ok

issue of not being able to cut arcs due to radius error is sorted. User error as normal. For some reason I had it in my head that the statements in the gcode regarding the hole processing were commented out with a #. When I did actually comment them out with a ; the code loaded and ran with no issue.

the realtime error is possibly resolved but will know for sure when I do some more cutting tomorrow. I changed the Ethernet cable and also removed the WiFi nic. Will do more testing tomorrow and update the post if I can confirm which cured the issue, if it is cured that is.

Doesn't even look like the current hal file would run
as there are two different signals connected to
hm2_7i76e.0.7i76.0.0.spinout:

net pdnt.spindle-speed-abs => hm2_7i76e.0.7i76.0.0.spinout
#net spindle-vel-cmd-rps-abs => hm2_7i76e.0.7i76.0.0.spinout
net pdnt.spindle.is-on => hm2_7i76e.0.7i76.0.0.spinena
net spindle-cw => hm2_7i76e.0.7i76.0.0.spindir
net spindle-vel-cmd-rpm-abs <= spindle.0.speed-out-abs => hm2_7i76e.0.7i76.0.0.spinout

I would first get things running in the usual way by adding

net spindle.0.on => hm2_7i76e.0.7i76.0.0.spinena

commenting out

net pdnt.spindle.is-on => hm2_7i76e.0.7i76.0.0.spinena

and uncommenting:

#net spindle-enable             <=  spindle.0.on

When this is working I would look into the pendant spindle control options

thanks, yes i saw it, i will give it a try as soon as i learn this UI principles of linuxcnc..

as in everything the hard part is the beginning part i suppose..

this happens mostly because of i am new in linux environment and there is no step by step instructions for anything in linux.

i will write everything i learn step by step under this topic about the UI designing and editing for linuxcnc with qt designer so that newbies may save some time

Just a guess........
If your touch screen comes up as HID (assuming USB) you may be able to modify the mouse properties in "control center" . Sorry I can't be of more help, as I haven't got access to my setup.