Advanced Search

.Hal file I am using 

Hi Hakan thanks for your help  to configure the drive. 
Unfortunately I am having no luck in getting it to work. 
I have attached my files below do you mind having a look to see if there is anything obvious I am missing?  
I am very new to linux so am struggling to work out when using the loadrt command in the .hal file  where the other  file is loading from? 

Thanks Will 


 

just for kicks, chat gpt has sent me down several roads that i know are wrong.

1st it tried to use motion component, but it has no spindle pins defined.(i expect these need to be set up in the main ini or hal but it couldnt tell me

so this in said i could use the spindle components... and then realised its read only.

then it took to just fabricating pins and functions that dont exist.

sigh. and this is what we have trying to run out law enforcement cameras? mmmmm good times.

Wouldn't surprise me if /etc/ethercat.conf got overwritten. Anyway, check syslog.

I guess onceloved has a solution and you don't need to disable eoe in the master after that.

On a more general note it seems EoE and linuxcnc will not work together.
EoE as such may work, if that helps with configuration of a drive for example.
Reference is this post. forum.linuxcnc.org/ethercat/53961-eoe-configuration#311275

Thank you for your help in advance, I have tried to reinstall ethercat master and trying to disable eoe, but its getting worse with the ethercat service can't start. I hope I can continue to update when it works with onceloved's help

ooh, thanks

ill look at this when i wake up. im burned out from trying to make chatgpt give me something useful haha

Hakan wrote:

Nothings makes me more curious than someone being secretive haha.
 

Probably invented hot water, again!

Hallo miteinander,ich konnte keine vernünftigen Datenblätter für diesen Antrieb irgendwo finden.Schade denn ich hätte diesen Antrieb gut gebrauchen können. Jetzt habe ich Plan B umgesetzt.Wenigstens konnte ich das Getriebe retten, ich habe ein Adapter gebaut und wie ihr seht ein JMC Servo verbaut.Im Anhang findet ihr ein Bild.Vielen Dank an alle die das gelesen haben.Viele Grüße.

Nothings makes me more curious than someone being secretive haha.

This is what Ethercat master documentation says
 

Two places to modify

Read out the sii info with "ethercat -p 0 sii_read"

1. Supported mailbox protocols.
Like it says in the figure, word 0x1C byte 0x38, bit 0x02 specifies EoE support.
Clear that bit for no support.
To orient yourself, you should find bit 3, 0x04, set for CoE support.

2. Enabled EoE mailboxes.

To find the byte that specifies drive EoE mailbox enabled:

In the read sii file, use some kind of hex editor.
Skip 0x80 bytes forward over the hardware config info
Byte 0x80-0x81 is 0x1a00 meaning strings section
Byte 0x82-0x83 is a word specifying the length of the string section.
  Example : 0xd100 = 209(dec) words.
  Add 1 to make it even: 210 words.
  Multiply by 2 to make number of bytes: 420.
  Add two for the size of the 0x1a00 identifier word: 422
  Sum up 128 + 422 = 550. Hex 0x226
At bytes 0x226-0x227 one finds 0x1e00 meaning general information section
0x228-0x229 is a word specifying the length of the general section
EoE mailbox specifier is now byte 9 in this section: 0x231 
To orient yourself, byte 8 (0x230) is FoE mailbox specifier, CoE details are in byte 7, (0x22f)

To disable EoE, first verify that the specified byte is 1. Then, write a zero in that position.


Upload the modified sii file to the drive again with "ethercat -p n sii_write mod_eeprom"

Personally, I wouldn't do this. I would use a Ethercat master with EoE disabled.

The above is only theoretical and may be wrong. Don't use it.


 

I haven't had a chance to really give it a good go lately, other things have got in the way.
But I've found your project to be solid and though it doesn't really relate to your project, but when I came across it I was in a bit of a dark place and it gave me the will and drive to get active again.

Here are the general signals that was generated for me by pncconf some years ago.You would need at least the enable and one of the vel-cmds.
Maybe forward/reverse and so on.
They all connect to the spindle pins (created by the motmod component).
Speed feedback is optional but nice to have, at-speed if your spindle can do that.
 

I'm civil/builder/construction labourer, using the page I linked to I was able to create Mesa bitfiles (then some custom ones for a clone board I made).

What it comes down to is being able to follow instructions.

A small request to everyone who uses Rio.

I hate telemetry in software, I don't want it in other software and I don't build it into mine either!

The downside, however, is that I never know if the stuff is any use at all.

I'm always happy when someone writes here that they've built a custom board, or when I happen to see pictures or videos online of boards I don't know yet.

An open source programmer usually only sees the problems and errors that users have, but very rarely reports of success.

So I would be very happy if you could give me a little feedback.

And even those who don't use it can say what they think is missing or what is stopping them from trying it out.

Best regards, Olli

@Dave3891, but you can send me the files (pinouts + board-image),
than i can create one for you

Thanks !

not really, in 'riocore/files/pin*.py' are some helper scripts for me (dev-branch),
but yes, most i do by hand.

@all
---- WARNING --- parts of the dev-branch is not usable at this time,
i do some bigger changes for the joint/axis configuration