- Posts: 2419
- Thank you received: 2349
Useful Plasma Thread
Russian Anonimouses. :woohoo: Are they into the bios ? They will eat your desktop pc in one day....I just tried to boot into Linux on my desk PC but it failed for some reason and left me at the command prompt.
Thanks for your post Rod. I will investegate your diagram carefully.
I have made a short example of code for logging the program for 5 seconds with 0.1 seconds interval time.
Here off we can make multiple calculations for making the best choice for the machine by itself. User's can select type of calculation.
@Tommy,
the 5 second's or longer can display your cutting charts. After cutting, the chart's can say if you was a good cutter or a bad cutter.
The ultimate line stay's stady. But fluctuence's have to be avoid. Kerf crossing and corner lock is one of them.
At the logging every 0.1 second. The machine can make a desicion on the past logging. Will i go this way, or wil i go for improvement? Users can select a cutting chart. I think there will be 3 charts. 3 types of calculating. I think logaritme i will also try to use for fun, if possible.
Please Log in or Create an account to join the conversation.
fperiod is not guaranteed to be exact if the thread is early or late so testing for equality is not going to work every time. you need to do a if... else if... else if ... and test for > T1, T2 etc. Steal The buffer approach using pointers I shared and see how you go. Just change the BUFFSIZE to 5000.
Please Log in or Create an account to join the conversation.
Was it a linux mint desktop environment? :whistle:
So yes, why not switch to debian? :side:
Still having russian anonimouses, switch to Kali and strike back. :woohoo:
I also think that the THC component should be kept totally separate from the touchoff component.
First i thought also to build in blocks, i agree.
But now i think, if the component stay's structurized, it's easy to implement. Some guy's have 1000 lines of C code. :woohoo:
From what i know now, the touch off procedure takes about a max of 20-25 line's of C code. This is easely to implement in the same component. When i got it finished, i will show it to you coming day's. It's hot on my to do llst.
I agree when it has no probe function included (touch off)I think he confirms my thinking about keeping the actual THC component on a seperate thread where it can be running at a slower time frame
Hmm 200 Mhz.. This diagram looks to fast to make a conclusion for me. I can't figur out what the scaling value's are, sorry.The attached chart shows what happens to torch voltage when crossing a kerf (data from a hal plot at 200 Mhz sample time:
If i can see a chart of a periode of time T versus volts V, i can imagine how the arc is responding.
Torchsample.3 is a nice piece of code. I must get a lession of c code to get as good as you !!
I will remind this, nice info. This week i will get some time to program and learn of your code examples, hopely i don't have to cook indonesian hot chicken. :laugh:Steal The buffer approach using pointers I shared and see how you go. Just change the BUFFSIZE to 5000.
Please Log in or Create an account to join the conversation.
And there is no need to buy a data logger. You can use the Halsampler and sample components and log data to a file every servo thread cycle for further analysis in a spreadsheet. I captured 16000 readings of torch voltage using this method.
So I want to recapture the dV/dT data using Halsampler.
An alternative to a seperate thread is to skip a number of servo thread cycles. This is easy to do using a counter and modulo division something like
Please Log in or Create an account to join the conversation.
This example helps me :
Then this one : return 1;
Sometimes is see return 0;
And when to use static variables.
Please Log in or Create an account to join the conversation.
By default variables defined in a procedure are thrown away and the memory released when you exit the function so the memory can be reused. The static modifier defines the variable in static memory so it is not thrown away and retains its value when the function is next called. You can use global variables but that is a bit messy if a procedure is the only one that needs the variable.
Procedures can optionally return a value and the type is defined in the prototype. heres a simple example that returns the sum of 2 values:
so you might write
Butt often the return value is used to denote an error occurred.. Generally 1 for an error or 0 for valid result
say it was an error if a or be was > 100, we might return the answer by reference like this
and you might call it like this:
Through the magic of pointers, if valid values are passed, answer will still have the correct answer!
Finally, often we don't bother with the intermediate value (retval in the example) and would often write it like this:
Its up to you to decide what the error numbers are. Sometimes -1 is used. Often there will be a whole host of equates defined so different errors can be identified.
Please Log in or Create an account to join the conversation.