Remora - ethernet NVEM / EC300 / EC500 cnc board

The Remora hardware abstraction makes this possible.

I've just added the software encoder module from the 3D printer version of Remora. I tested it on the MPG encoder inputs and it's working. I don't have a 24v encoder to test on the normal inputs. 

Version 1.1.0 is in the repo for testing.

github.com/scottalford75/Remora-RT1052-c...ora-rt1052-1.1.0.bin

In the config.txt file add the following:

BTW, the encoder module also supports an index input as well. The counting speed is limited to the base thread frequency.

scotta wrote:

In the config.txt file add the following:

    {
    "Thread": "Base",
    "Type": "Encoder",
        "Comment": "Encoder",
        "PV[i]":             0,
        "ChA Pin":            "P3_16",
        "ChB Pin":            "P3_17"
    }[/i]

 

scotta post=275098 userid=24854
BTW, the encoder module also supports an index input as well. The counting speed is limited to the base thread frequency.

Can you do something from start to end?
In this case, write working and tested config file?
How many time you must spend for it?
Few minutes?
You wrote "In the config.txt file add the following:", but there are "P3_16" and "P3_17" pins assigned already.
Should I remove these blocks?
What is index name? "ChZ Pin" or else? And where can I assign it?
Where from I can know it?
I understand you work very hard for free, have a job, a home, maybe children and dog, and other duties, but I have only one life too, and don't want to lose it for guessed what you done and how it works.
What is a few seconds for you may be an hours for me, and not for me only, for others too...

BTW. How to configure PWM pin?

I've been trying to avoid your comments, but I'll ask you now to read the docs!

Myself and others that support the Remora project have been working on this in our own time for the good of the LinuxCNC community. I'm happy to support others but I'll ask you to request it in nice way.

remora-docs.readthedocs.io/en/latest/fir...ig-File.html#encoder

remora-docs.readthedocs.io/en/latest/sof...indle-control-simple

You will see in the provided configuration files the following section:

So point the LinuxCNC HAL configuration to SP 0.

scotta wrote:

I'll ask you now to read the docs!
 

You don't understand me.
Did you test the encoder?
If you did tests, you must have the config.
Why don't you share the config instead "read the docs" advice?
For example the docs says "loadrt PRUencoder names=encoder.0", but I have no PRUencoder.so file, I don't know where from can I get the PRUencoder.so file, so this is useless for me.
Second example is PWM. There is wrote in the header of spindlePwm.cpp file "Module for NVMEM spindle RPM on pin PA_0", but I don't know where is the PA_0 pin in my EC500, so I don't know where I should connect the spindle driver...
I suspect you know, but you don't share this knowledge...

You don't understand !

Community project does not mean that one person does everything and everyone else uses it.
it means that everyone contributes and tries to improve the project. and by that i don't mean nagging. but being active yourself, fixing bugs, writing documentation, helping other users.

someone gives you a car for free and you complain that it doesn't come with a manual and you can't get the boot open. find out for yourself and share your knowledge.

Yes tux, you make a valid point. It would be a lot easier for new users if that were provided, and some things documented more. That being said, this is a project in development, and not exactly new-user friendly at the moment. Not everything is up to date, and there is a lot of nuance to the project. Reading through the entire documents is probably a good starting point. From there, there are a lot of users that can assist you if you are having problems that are not yet covered in the documents.

Im sure everyone would be willing to help you if you were less abrasive and confrontational in your posts. You dont need to kiss anyones ass, but try to be a bit more polite when asking questions instead of demanding help.

meister wrote:

You don't understand !

Community project does not mean that one person does everything and everyone else uses it.
it means that everyone contributes and tries to improve the project. and by that i don't mean nagging. but being active yourself, fixing bugs, writing documentation, helping other users.
 

No, you don't understand.
The community project is when many volunteers work together.
It means that no one has to do anything, but if he has already done something, HE MUST says how he did it and how it works, because IT IS NECESSARY to others for testing or improving.

I give you an example too:

---

This: www.aliexpress.com/item/1005003056314140.html
this: www.aliexpress.com/item/1005005471801078.html
and this: www.aliexpress.com/item/32673801669.html
can program EC500 with command pyocd flash remora-rt1052-1.1.0.bin --target mimxrt1050_quadspi

---

Did you know how much time took me to wrote information above?
Exactly four minutes.
And now everybody knows, not me only.
WHAT AND HOW,  no  "It works for me, guess how".

Ok tux, to your point, I dont think there is any mention of installing the encoder component in the documents and its unlikely in the RT1052/NVEM repo.
github.com/scottalford75/Remora/tree/mai...omponents/PRUencoder
Here is a link to the encoder comp. Install this like the other one.

PA_0 is likely referring to the STM pin number. I dont know what board you have but if you have a RT1052 board the pin numbers/names will be different.

 

 Did you know how much time took me to wrote information above?
Exactly four minutes.
And now everybody knows, not me only.
WHAT AND HOW,  no  "It works for me, guess how".
 

ok, how many boards and MCUs are supported in Remora ? how many features are supported ?
how many machine types ? that takes hours to document, he is a good programmer, I think it is better if he spends his time programming cool new features or fixing bugs and when he thinks he is done, maybe he will write a cool documentation.

if you want to help, write a documentation, it only takes you 5 minutes. start a wiki page or open a pull-request in github. or post each update here.
no matter, just make yourself useful