Advanced Search

I don't see a .qss file in there so can't tell what's wrong. Oh I see you used the mainwindow stylesheet which I never do. It's probably a typo somewhere in your stylesheet.

I se a .qss file and add it to the ini file as per the manual. Take a look at some of the example stylesheets. I use the Flex QSS program to generate stylesheets.

For some reason unknown to me I can't view your files.

JT

I will have a look whenever i get the chance, i need to use another PC or laptop to download the files, this PC if for the forum and youtbe only.

jyeomans wrote:

  
now the estop on the screen only reflects the physical button.    may be this is the way it is ment to work and i just had somthing different. 
 

That should be the proper way, it should not be possible to enable the machine on screen while any of the e-stop buttons are pressed.

Dang, those are some nice cuts!
-
Should we move this to "show your stuff"?

phillc54 gave some good advice to display stuff in axis, some i have still in use.
This entry in the usercommand file
linuxcnc.org/docs/stable/html/gui/axis.html#_user_command_file
could be used to display the the state of the lock. Just replace  'spindle.0.inhibit' by the switch input.
To prevent run a program, i can only imagine, press F2 button.

 

 

You can solve that this way:

i am not sure whether this is a hal issue or an issue with qtdragon_hd.  
i have just installed 2.9 the newest build,
and rebuilt my machine.  on my old machine the esop on the screen and the physical estop worked independantly.  
now the estop on the screen only reflects the physical button.    may be this is the way it is ment to work and i just had somthing different. 
i liked it as i get the button on the oppiset side form the screen and i had an estop on both sides of the machine.
 

@Hi

There are now different solvers in the codebase, in c and c++.

Performance:
 
Test object:
 

Hallo Gemeinde,
ich bin dabei einen der 2 Sensoren für den Werkzeugrevolver zu definieren bzw. was zu tun ist, wenn der Sensor nicht ausgelöst wird.
Der Revolver wird von einem Pneumatikzylinder aus seiner Verzahnung gedrückt, dabei wird der Sensor unlocked ausgelöst, wenn die Position erreicht ist, darf der Motor den Revolver drehen. Danach wird der Revolver wieder nach hinten gezogen und ein 2. Sensor wird geschaltet, es sind also Positionsschalter. Mein Problem ist der 2. Schalter, wenn der Revolver zurückgezogen ist, wenn diese Position nicht erreicht wird und eine Fehlstellung vorliegt (zB Stepper Schrittverlust oder sonstige Störung) dann soll die Maschine ja nicht weiterfahren.
Das habe ich mit einem digitalen Input und M66 im M6-Macro versucht, was so weit auch zu funktionieren scheint:

M66 P0 L3 Q5

Jetzt ist es aber so, dass nach dem Timeout die Maschine trotzdem weitermacht.
Ich vermute da müsste eine Bedingung rein, aber ich weiß nicht, wie ich das am besten umsetze.
Mein M6 Macro:
[/code]

This is cool, I have Mesa CT making a working configuration for the 7i76EU now. Just need to add the spindle types.



Thanks PCW
JT

Yaroslav wrote:

I solved the issue by moving the files to the root of the machine configuration folder.
 

All of the files or macros only?

From what I have seen during the tests the torch voltage is below 200V. During start and piercing it easily goes up to 180V but not above that.
It cuts around 100V. Thin material in the 80s-90s, thick in the 110s.
The arc is also DCEN, DC electrode negative, I have been told. The work piece ground is not connected to mains ground.

200V isn't uncommon to have on a PCB, mains 230V AC is common here. My understanding is that with enough isolation distance it is fine. And the whole ADC side is isolated.

I think an ADS1115 can be used just as well, ebay aliX amazon are full of them at super low cost. To go with the 11-bit version meant that I get 3.3 kHz sample time. The ADS1115 is only 860 Hz max. That was the main factor. For the ADS1xxx ADCs one need to put them in continuous conversion  mode or the time to get a value is terrible, several milliseconds. In continuous mode its 150 microseconds. I know now how to read the ADS1014 which is actually two channels A0 A1, and I think it would be possible to use the ADS1115 with 15-bit resolution in continuous mode reading one differential channel (between A0 and A1). How important is updating exactly every 1 ms with a new value? It can't be that important, there is a bit of noise in the voltage and to read the same value every 7th time can't be that bad, can it? Anyway, that was the decision point and I choose 11-bit resolution, one differential channel and 3.3 kHz updating rate. The footprint is the same for those ADS1xxx so one can easily solder in another one, and reprogram. It is actually only something like 10 lines of code for the ADC.

The BAT54S is there to protect the input of the op-amp. Don't know much about that, it is something I found. The lmv321 was also not actively chosen but was known to work. I do see non-linearity at the very bottom of the range, so it isn't fully rail-to-rail. They aren't as I understood it, and it isn't important, it isn't working close to the rail voltages. But it means the display says 2V when it is 0V, but it should be linear above say 5V (in the 0-200V range).

Do you have an ohmic sensing solution when the plasma nozzle is the same polarity as the work piece?
I can see no change in voltage when the torch touches the work piece. I was hoping for that, but no.
I am very interested to include that.

I solved the issue by moving the files to the root of the machine configuration folder.

Hello.
On linuxcnc 2.10, 2.9. (axis, gmoccapy)
I try enter in MDI  " #<_varzag>=55 "
after i try load ngc file when using that variable " #100=#<_varzag>.
I got error "Named parameter #<_varzag> not defined" , programm working fine - why showed that error ?
 

Hi John! Need your help! I ran into a problem: in the style sheet I made a style for buttons, I showed it in the video. That is, in the style there are different settings, but the main one is using an image as a button background! So I do absolutely the same thing for other buttons, that is, I apply the same style to other buttons and it does not work, or rather it works, but not quite correctly: in the video you can see that the button is not displayed. And when you hover over it, it applies the :hover and :pressed style, but the button inactivity style is not applied)))) what could be wrong? I attached the archive!