Advanced Search

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!

Looks good. I dont think you have issues with the voltage levels. In another thread I said I would scope out the work to electrode voltage to show what those voltages are, but unfortunately I have not had the chance, maybe next week.
When you use the divided arc voltage, you could put this design in to your easercat pcb, as in you dont need it to be separate.
If you find a decent 16-bit one example ADS1114IDGST then it might be worth the money. The 16-bit one gives you more opportunities if you want to make some additional features in the future, its quite a bit more expensive I know.
For the OP-amp if you find something with more tolerance in the input, that would make it safer but may not be worth it.

If you can give me an email address where you can be reached, I can share you an ohmic sensing schematic if you want to try it out and then share to the community.

hi Scotta
I wanted to compliment you on the work you have done and made available
to the LinuxCNC community.
I am excited about it and I bought an NVEM V5 to try to install the Remora firmware,
but when I opened the case I noticed that the chip is not an STM32F207 but the one in the photo


 


is it still compatible or did I buy the wrong card?

Thanks if you can give me some advice

P.S. sorry Scotta
I went a bit back with the posts and at 191 there is the answer to my question, thanks,
I'll move on....

Hello,

Now with the Mesa 7i96 there are more inputs and outputs to play with, compared to the old controller.

The machine has a (diy) mechanical spindle lock. It just slides on the wrench flats of the spindle.
The limit swicht for lock was previously connected to the E-stop in series, which is not the best way.
Now I connected the switch for the spindle lock to an input. in the hal file I connected that input to a pin called drive inhibit.

I cannot start the spindle drive when the switch is actuated and the spindle is locked. So far so good.

Now I tired to find some info how to get the Axis GUI to "disable the spindle buttons", maybe even some indicator on the GUI "spindle is locked" would be nice. And in ideal conditions I would not be able to run an automatic program.

If the spindle brake checkbox would be used it would be O.K. as well, but then I need to disable the automatic unchecking of the spindle brake, because the lock is manually operated.



 

Actually it's my issue for not checking the boot logs, the scripts setup the zram.service. Whether Raspberry OS uses zram is not related to our images, as we use Debian.....as of course you know.
The zram.service is part of the image builder, I've modified the process so the service shouldn't be enabled and later on install systemd-zram-generator and create a config that will use 1GB on a 4GB system, this can be modified if required.
As you can see zram tools are installed, this is whether or not systemd-zram-tools are installed.
The issue is because Bookworm uses systemd the package systemd-zram-generator is required, this is the missing piece of the puzzle. During the build the a different script is used to zram0 which fails.

As you can see from below zram0 is used for swap.
Without the mods I've describe above there is no swap. Whether it's need or not, but on a typical debian x86_64 install usually a 1GB swap partition is created.

As you can see it really doesn't affect the total free memory when it's not in use.And BTW it not caching memory nor mamory glands, but is creating a swap partition that is compressed in memory.

The simplest option is just to mark zram.service as masked and have no swap.

So at the moment I'm building an image with the mods.....and make sure I've done it right.

Rob

I have been stalled on this for quite some time. It's difficult work. Keep routing me on from time to time.