Gmoccapy - A new screen for linuxcnc

Hi Norbert,

I have changed some outputs using abs.

I now get positive in both forward and reverse on the readout SXXX.

The bar below still gives me a negitive in reverse and a positive in forward.

What parameter are you looking at for the bar?

This all worked prior to update to 1.x.x

I get at speed light in MDI mode in forward and reverse.

When I run aprogram I do not get spindle at speed anymore.
I also get no axis motion. Synced spindle motion.

Somthing has changed as of 1.x.x.


Jim

Halo Jim,

I do not understand that.

The bar should be connected to spindle-rpm as abs value.
The LED ist just a led, it has no connection to gmoccapy internals and should be connected to spindle-at-speed.

Yes, there has been some chsnges from 0.9.9 to 1.0, as that was the change for stand alone.
In MDI, do you enter s1000m3 and s1000m4, or do you use the buttom?

Could you post your complete config?

Norbert

Norbert,

From my perspective it seems there is some underlying
support code that is now missing.

In MDI I enter s1000m03 and s1000m04.






I know this is a pain and I Thank you for your help Norbert.

Jim

Halo Jim,

I only had a few time to look at you hal files. They are very complicated and no optimized for the use with gmoccapy. You do use a mux to select jog rates, but you can connect directly to the coresponding gmoccapy pin. You take halui pin to connect overrides and do not connect to the offered pins. You use hal manuell toolchange, but you shouldn't.

I strongly recommend to read the hal pin part of the Wiki and try to avoid halui pin, when there are corresponding gmoccapy pin, as then gmoccapy will take care not to excecute commands not allowed, like jogging in mdi mode. This way your config would be a lot simpler.

You spindle connection is so complicated, that i do not understand how it works.
Could you support a flow diagramm?

Within the next days i will disconnect the spindle Feedback bar from taking influence to the speed label.
As mentioned, the at speed led is only an indicator and gmoccapy has no influence to lit or not, only the hal pin is responsable for that.

Please take a look at the sim spindle connections and the postgui file. I am realy wondering why it does work in mdi and not in auto. Please test with a file just containing s1000m3 and a m1, so that the program does not end imidiately.

What gmoccapy Version do you use?

Norbert

Hi Norbert,

I have looked at this some more. It seem s that I am able to run a program with the spindle in forward. Threading.

I am unable to run any program with the spindle in reverse. IE backtool lathe. I hope this helps.

Here is the logic for my spindle control.
I made and tested it with my logic simulator.


Jim

OK Jim,

that part is clear, but I recommend to make it as simple as possible, until we solved the problem, so the spindle part should be something like:
I cut now all reactions from gmoccapy to the feedback bar and the at speed led, so both do just indicate values and do not have any influence to gmoccapy nor gmoccapy to its values. I just pushed 1.0.2.1 for that purpose.

As far as I see, you convert to abs to early, only the last value , witch will be the feedback to the spindle bar should be absolute, all before need to be also with negative values, as the values are needed for at speed detection.

I also do not understand, how you can connect thinks like:
gmoccapy.jog-inc-4 is an in pin and has to be connected to an out pin! So something like: would look fine.

I strongly recommend to split your hal files in several files, so they are easier to read, take a own hal file for the spindle stuff, and a other for jogging etc.

As I do not have the machine to test, I would recommend to reduce to the basics first according to: spindle feedback So all abs, ors and so on are gone. If that works, you can add again all your control structures.

Norbert

P.S: If someone can send me an encoder for my lathe, I would be able to test