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

@Oxbown fixed in dev branch

Hi,I am currently configuring a Modbus RTU I/O expansion board with RioCore / RioFlow, and I ran into two issues:1. Unable to read digital inputs (N4D3E16 board)

• Board model: N4D3E16 (16 Digital Inputs / 16 Digital Outputs over RS485 Modbus RTU).
• Current status: Controlling all 16 digital outputs works without any issues. However, I am unable to read the status of the 16 digital inputs.
• I am following the register addressing and function codes described in the board's documentation (which I have attached). Could you check if there is an issue with how RioCore handles the Modbus function code (e.g., FC02 vs FC03 / register offset) for this mapping?
  
  2. RioFlow device renaming bug in LinuxCNC
  • When I assign a custom name to the devices in the RioFlow interface, LinuxCNC throws an error on startup and fails to load.
  • If I leave the device names blank (default), LinuxCNC starts and runs properly.

I have attached the JSON configuration file and the board's documentation for reference.Thanks in advance for looking into this!

ok, i think i see the problem but have to check how i fix it, i never used function code 3 for bit's

When I use pncconf to configure the MESA7i92 card, I set the dirhold to 10us, but the actual measurement is about 1ms. It automatically increases the value when executing linuxcnc. This is why I previously mentioned it works correctly on the dm542 (dir use pc817).

mesa7i92 step/dir
 
 

The Hostmot2 Stepgen/LinuxCNC does not increase the time between steps. What you are seeing is that
the actual direction change may be some distance from the step pulse  time because
the actual step direction logic depends on the sign of the velocity command and at slow speeds
this velocity change may occur at a time determined by the _fractional_ position count. The hostmot2 stepgen
hardware position is a 16.16 bit number so has a resolution of 1/65536th of an external step.

The setup and hold timings set the minimum timings, but not the maximums.
 

@Oxbown please try dev branch, i hope it works now, have no hardware to test.
and please set the Register address to 192.