- Posts: 121
- Thank you received: 0
How to access RS485 on Mesa 7i96?
- MakingStuff
- Topic Author
- Offline
- Premium Member
-
Here is the code that was used to access the USB device. Is it even possible to do this with the Mesa 7i96? If so what would I change?
loadusr -Wn vfd hy_vfd -n vfd -d /dev/ttyUSB0 -p none -r 9600
net spindle-cmd-rpm-abs => vfd.speed-command
net spindle-cw motion.spindle-forward =. vfd.spindle-forward
net spindle-ccw motion.spindle-reverse => vfd.spindle-reverse
net on motion.spindle-on => vfd.spindle-on
Please Log in to join the conversation.
Please Log in to join the conversation.
PCW wrote: Unfortunately this is not doable yet
That depends on how you define "doable".
I think all that is missing is a modbus driver for the Mesa UART?
Please Log in to join the conversation.
the low level driver from the formatter component (modbus etc)
Please Log in to join the conversation.
- strahlensauger
- Offline
- Elite Member
-
- Posts: 195
- Thank you received: 0
Mesa cards via the rs422 to a vfd. Wouldn't it be possible to add a second rs 485 in future releases oft the cards?
Please Log in to join the conversation.
strahlensauger wrote: In several FAQ plenty oft people asking to connect
Mesa cards via the rs422 to a vfd. Wouldn't it be possible to add a second rs 485 in future releases oft the cards?
The physical connection is not really the problem, it is getting the right data to the the FPGA.
I wonder if there is a way to make the Mesa UART appear in /dev as a serial port?
Please Log in to join the conversation.
so this can all be done by a generic hal protocol component connected to the hal pins
exported by the UART TX and RX modules. This avoids losing real time if its desired
(and even if modbus for example is not real time, there's no reason to add userland
uncertainly to transactions)
Please Log in to join the conversation.
PCW wrote: Its probably possible but I think a cleaner way would be to support a hal string type
so this can all be done by a generic hal protocol component connected to the hal pins
exported by the UART TX and RX modules. This avoids losing real time if its desired
(and even if modbus for example is not real time, there's no reason to add userland
uncertainly to transactions)
Indeed. But that would require re-writing of all the existing VFD drivers, which currently hook in to /dev/ttyUSB0
Please Log in to join the conversation.
