Modbus TCP issue with pokeys57E

More
27 Oct 2020 16:52 #187443 by Varang1an
Hi
I have been trying to set up modbus TCP with pokeys57E on linuxcnc 2.8 RT on debian stretch. For some reason I get error which has caused me to pull out my hair:silly: I took an error report from the whole modbus listing in case if someone knows what could be going on. The file happens to be 1.7mb so it won't fit here as attachment so I had to compress it.

I also attached my modbus.ini file so if anyone kind enough can take a look and hint me what I have set wrong or if pokey57e has some issue with modbus let me know.

Thank you in advance
Attachments:

Please Log in or Create an account to join the conversation.

More
28 Oct 2020 00:49 #187486 by BeagleBrainz
Debug file information:
Note: Using POSIX realtime
./nyx.hal:125: Pin 'modbus.xplus' does not exist
4823
Stopping realtime threads
Unloading hal components
Note: Using POSIX realtime
is your error which is in your nyx.hal file @ or around line 125. After you clear this error you may have others pop up, so it's just a case of either closely reviewing your hal files or fixing one error at a time.

Please Log in or Create an account to join the conversation.

More
28 Oct 2020 05:24 #187511 by rootboy
You've got:

[modbus.xplus.num_errors]
[modbus.xplus.00]

created already.

Your error is:

"./nyx.hal:125: Pin 'modbus.xplus' does not exist"

Do you want to (or can you?) create a pin that is the root of existing ones?

Otherwise, I'm very familiar with this particular error message. Not all that proficient in fixing them yet however...

Can you post your nyx.hal file?

Please Log in or Create an account to join the conversation.

More
28 Oct 2020 07:12 #187519 by Varang1an
Ok got forward on this, I had to change "modbus.xplus" to "modbus.xplus.00" and it seems to not complain anymore modbus pins, now however it complains the pin which it is attached in hal "halui.jog.0.plus"

"net jog_x_plus <= modbus.xplus.00 => halui.jog.0.plus

dunno why it can't find the halui pin as I have also halui set in ini file

Please Log in or Create an account to join the conversation.

More
28 Oct 2020 07:18 #187521 by Aciera
Can you post your INI and HAL files?

Please Log in or Create an account to join the conversation.

More
28 Oct 2020 07:24 #187522 by Varang1an
Sorry, I found reason for this... I used hal documentation 2.8 : linuxcnc.org/docs/2.8/html/config/core-components.html

and when I tried instead commands from devel:
linuxcnc.org/docs/devel/html/man/man1/halui.1.html

it works. Dunno how it is possible as I have 2.8. It seems the documentation is not that great on linuxcnc at some parts. I used now "halui.axis.x.plus" and it was accepted

Please Log in or Create an account to join the conversation.

More
28 Oct 2020 08:00 #187524 by Aciera
Indeed, there is still a reference in the 2.8 docs to halui.jog:

linuxcnc.org/docs/2.8/pdf/LinuxCNC_Documentation.pdf



despite the fact that the halui.jog have been replaced in 2.8:

linuxcnc.org/docs/2.8/html/getting-start...dating-linuxcnc.html




Could somebody fix that?
Attachments:

Please Log in or Create an account to join the conversation.

More
More
28 Oct 2020 08:07 - 28 Oct 2020 08:13 #187526 by Aciera
@Beagle

It's fine there
linuxcnc.org/docs/2.8/html/man/man1/halui.1.html

but it's wrong here

linuxcnc.org/docs/2.8/pdf/LinuxCNC_Documentation.pdf

and here:

linuxcnc.org/docs/2.8/html/gui/halui.html

also here (as I presume this is the doc meant for the current stable release):

linuxcnc.org/docs/html/gui/halui.html
Last edit: 28 Oct 2020 08:13 by Aciera.

Please Log in or Create an account to join the conversation.

More
28 Oct 2020 08:25 #187527 by BeagleBrainz
Another I'd like to add, and this is a situation that has manifested itself a bit lately, is that we've had users having errors and contributing the errors to a part of Linuxcnc. Now if these user had of read the error file, which gives a very clear reason to what the error is, a lot of time could have been saved.
What has frustrated me more, to a point where I gave up offering help, is that some users wont even bother to look or start multiple threads. Even after they have had be shown how to find the error.

Ok rant over....and yes I understand the OP is new.

Ok now would it be easier if the Debug stanza was at the top of the error report ?

Please Log in or Create an account to join the conversation.

Time to create page: 0.108 seconds
Powered by Kunena Forum