Modbus TCP issue with pokeys57E

Well in this case the user did read the docs but the problem is that the docs are wrong. At least some of them.
Don't really know where to report that though.


And yes having the Debug section at the beginning would probably be easier for that matter.

I've left a message on the dev mailing list re debug info.

The issue I was raising was the error report not being read, or not recognising what the debug info was trying to relay.

yes sorry for this confusion as documents made me mistake on pins and as a relatively new user of linuxcnc (have two machines previously built, but it was easier as I didn't need to play so much with modbus and halui pins). Also I been looking around for exact same issues and couldn't find those.

I will try now myself to solve the issues and not bother people anymore.

Thank you for your help

No no don't be like that. I'm just trying to help users become a little more independent.

Would this have made the initial error easier to find ?
This error is related to not having a Mesa card connected to my machine (it was the easiest way to force an error), but hopefully you get the idea.

What Beagle means is:
Would it have been easier to find the error if you had got this

at the beginning of the log rather than buried towards the end?

Actually, on advice from Andy, I just swapped two lines in show_errors.tcl and added a string.
That screen shot is the actual pop up window with the mods that Andy suggested.

yes, that would been easier. I noticed I had also debug level 3 on modbus... which is way too much info on error report, I swapped it to 2 and directly I noticed modbus ini was ok.

Yes it would been easier to notice if the exact error was in beginning of report Anyway now I know where to look and maybe I will start to understand the error log little better.

Hopefully we can get that into mainline Linuxcnc.

Finally today I managed to get everything working So I have now fully working control panel through pokeys57E using modbus as communication method I have to say the documentation of hal pins would need a lot of fixing. Now I just need to fix toolchanger logic and I could make first test cuts

I have to say the documentation of hal pins would need a lot of fixing.

First step to fixing something is to report what is wrong. References to halui.jog in the docs for 2.8 have been reported, if you found other issues please report those as well.

Glad you got things going.