LinuxCNC-RIO - RealtimeIO for LinuxCNC based on FPGA (ICE40 / ECP5)

Mecanix wrote:

Hi, I'm not to familiar with the background of your issues (from a quick glance there's a hundred posts to decipher, it's overwhelming), but have you posted a concise and consolidated schematic, wiring installation and pictures of your entire set-up here or anywhere else?

Without that I highly doubt anyone (here at least) will be able to remotely assist. Although the noise issue you seem to be having has nothing to do with RIO let alone Linux CNC.

Ruling out RIO and Lcnc is easy, outputs can easily be probed while running a simple gcode program.
 

Yeah, you are probably right. But I think even then remote troubleshooting is pretty difficult. I may open up another thread in the forum. But right now I need a break and look for something else. Still need to get Modbus working for my spindle. Will be starting with that soon.

I changed the Y Axis motors back to the Nema 23 with the DM332T driver. 3200 Microsteps/rpm and I can go up to 6000mm/min without an issue.
Handwheel xhc-whb04b-6 is working as well.

Now I am focusing on getting Modbus and the spindle to work. This is the last thing I need to run the mill with the Tang. Can someone confirm that this wiring is correct for the Max485?
 

StackExchange and EEVBlog are both fantastic venues for brainstorming and validating electrical/circuit ideas and designs, you'd find accurate answers to your questions in a finger snap and be done already. I highly doubt a Lcnc forum will be of any help. Great place for software, configs, dev, and industrial motion control hardware though, mostly.

[deleted] potentially misleading, no hands on exp. sorry ab that. 

digiex_chris wrote:

That reminds me, is there a way to configure minimum delay time between a DIR change and a movement command? some steppers are more picky about that. I also need to flip the action of the EN pin, my steppers are enable-low and it's currently outputting high when enabled.
 

you can config modifier's to each pin, there are functions like invert, debounce, ...

 

to add an delay between step and dir, you can add a debounce modifier to the step pin, than you have a delayed step signal


 

I need someone pointing me in the right direction to get my spindle running.

I can either try to get classic ladder to work. For whatever reason, it will not work with Rio.

This is the code rio creates in the rio.hal file.
If I start LinuxCNC, it is not in Modbus Master mode. So I changed the configuration. This is what works on the same machine.

When I start LinuxCNC I get the following 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.

---

I could also continue to work on the Modbus integration. I know which registers to read and write from my VFD, but need some starting help to translate this:

 

Into this:
 
 

I suspect you will likely get more helpful help in the classicladder section, I don't see this as an issue specifically with riocore, particularly with the error indicating memory issues in the classicladder components, rather than the riocore driver. At the very least, there likely is more classicladder experts watching that section than here.

www.forum.linuxcnc.org/25-classicladder

The only thing I can think of is the order the gui loads in vs the classicladder user mode stuff matters. I've seen some people use -w and -W to make the loading wait until things are complete as well. I needed to do that for one of my custom (non-classicladder) programs, needed to have it wait for the hal stuff to be complete before continuing to load the hal file.

linuxcnc.org/docs/stable/html/ladder/cla..._non_realtime_module

The example configs in the linux cnc repo have been quite helpful for me personally, there might be some hints in there for your use case as well
github.com/LinuxCNC/linuxcnc/blob/master...dder/demo_sim_cl.hal

I made a post in the Classicladder Subforum. I believe I am a step ahead. The problem seems to be the activated Twopass option in the Ini. Not really sure how to work around that, but it feels like the solution is close.

forum.linuxcnc.org/25-classicladder/5451...ng-with-linuxcnc-rio

 

I have built a new stepdir driver,
with adjustable 'delay after dir' and adjustable pulse length (also 50% duty possible).

first tests are still running, but if you want to have a look at the branch: new_stepdir_fix_pulse_len_dir_delay

EDIT (there is also a test-bench for this driver):
 # (cd riocore/plugins/stepdir ; make testb)

 

branch: using_os_path_join

 

the rio-setup gui is running directly on windows now