Advanced Search

Mach3 is absolutely not usable for this or anything complicated, and so are most of "turn key" solutions, even Siemens will cause much more problems for you than LinuxCNC.
In short, there is no other viable option, especially there is nothing usable under 15-30K$.

try opening Linuxcnc Status (settings tab right hand side 'status')
Look under G5x offset.
I bet that linuxcnc is using the right offset but qtdragon is reporting wrong on the offset page.
I assume you are referencing the offset page entries?

Yes, that is a good start.

It is under developed, but I will help as I can.

There are a few extra pins:
qtdragon.axis-x-load (float input range 0-1)
qtdragon.axis-z-load (float input range 0-1)
qtdragon.spindle-load (s32 in put range 0-100)

wear offsets are available when using remap - the wear will be shown in the tool offsets page regardless.
qtdragon.mpg-in (s32 input for scrolling things on screen)

Looks like the screen is reacting with key events like a keyboard.
Like a keyboard repeats the key every X millis and store the number of events.

like moving the machine with a encoder and a fixed step. If you turn the hand wheel, the controller will count the encoder counts and even if you stop turning the wheel, the machine goes on moving until the calculated distance is reached.

I can unfortunately not tell you how to change that behavior. I would search for something like key repeat time.

I do use an older model of a  Faytech Touch and I am not able to reproduce the bhavior.

Norbert

Unfortunately the tester simulation config is missing in 2.9, but you can try this one.
unzip it in your YOUR NAME/linuxcnc/configs folder.
Then add your Designer .ui file in there naming it tester.ui

Load linuxcnc and select tester.ini
It should then load your panel with linuxcnc.

If you are using master branch tester is in sim/qtvcp_screens/tester

some more information on the connections between supply module and drives, looks like the parallel bus is how drives get control from the fieldbus.
   

regarding the canbus and profibus, the sections are mentioned in the document but listed as "in preparation" and empty, so I'm guessing maybe they initially planned to add but later on never really followed through?

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.