Classic Ladder not working with LinuxCNC Rio

Hi Forum,

I am trying to get Classic Ladder working with ]LinuxCNC RIO.

I try to get my VFD working with Classic Ladder. This is what works on the same machine with soft stepping.

loadrt classicladder_rt numS32out=100
addf classicladder.0.refresh servo-thread
loadusr classicladder --modmaster vfd.clp

When I start LinuxCNC with the FPGA connected I get the following error:Shared memory conflict or RT component not loaded!

ERROR CLASSICLADDER-   Ladder memory allocation error

I tried to remove the numS32out=100, but no success. I can load the program manually with the ladder editor, but it is still not in modmaster mode and won't work.

Someone an idea what the cause would be and how to fix it?

Aciera wrote:

Not sure if this applies to your setup but classicladder does not seem to work with [HAL] TWOPASS = on

Classic ladder works on both my machines with TWOPASS = ON

2.9.3 on mill, and 2.10 on lathe.

Maybe the loadusr line needs to be in postgui.hal?

Indeed Twopass was on. I switched it off. This lead to the following behavior:

The machine started classic Ladder. CL worked as intended. The Axis Gui of the CNC did not load. When I closed CL, the axis gui loaded. I thought I could go into the Ladder Editor and simply start it again, but once I was in ladder editor, the Modbus Maser pages in the config where not there. Like it was just loading a blank program.

I have not tried to put the CL part in the postgui hal file. Will try that.

I tried putting the loadusr line in the posthui hal file. Did not work. I tried to put all 3 lines in the postgui hal file, did not work either.

The problem is, even in the postgui hal file, CL opens up, but the Axis GUI of the machine does not open up, until I quit the CL.

I feel like the solution is very close, I just don't know how to set up the starting sequence.

OP-

First thing to do is run LCNC from the command line, and turn on some level of debugging in the INI file.  That's helped me catch 'backstage' problems, or at least I can figure out where to start looking.

Then run LCNC - with and without twopass - and see what is happening in the terminal window.

I suggest changing the terminal preferences to 'unlimited scroll-back' before you start.

Once you capture a problem ion the terminal, take a screenshot and post it up here.

Will do that once back from Thanksgiving holidays.

I have some logs created. In the logs you find the different rio.hal and rio.ini configurations.
Twopass disabled
loadusr -w classicladder --modmaster vfd.clp in postgui_call_list.hal
pastebin.com/61urYP3n

Twopass enabled
loadusr -w classicladder --modmaster vfd.clp in postgui_call_list.hal
pastebin.com/bKd8N5Ex
 

Lcnc, Rio, Modbus all looking good. GTK not so much though (Failed to load module "atk-bridge").

Are you on a VM or accessing your linux session via VNC or XRDP by any chance? Additionally, it would be a proactive move to list/describe all the GTK debugging steps undertaken so far so that others seeing this can be updated on your progress. Bet it's an easy fix.