LabVIEW
Getting Started with Modbus over RS485 (LabView)
@rolfk wrote:
@Michael_Smith wrote:
I mean what software programming scheme I should follow, If I implement this Hardware Hierarchy?
You really keep changing the specifications on a whim!
First you talk about controlling the Modbus directly from the FPGA on the myRIO because you are concerned about latency.
Suddenly you want to connect the Modbus to the PC instead. That is quite a fundamental change in specifications. And poses the additional question what you want to use the myRIO for.
Hello Rolf,
No no the plan had been this from start. I didn't know how to access it using LabVIEW but now what I've understand is that I can't access serial port in LabVIEW FPGA that way. I'm just looking for an efficient and can't figure out which way is best suited. I'm a beginner level developer. The block diagram is the hardware level interface which I've to follow.
@Michael_Smith wrote:
@rolfk wrote:
@Michael_Smith wrote:
I mean what software programming scheme I should follow, If I implement this Hardware Hierarchy?
You really keep changing the specifications on a whim!
First you talk about controlling the Modbus directly from the FPGA on the myRIO because you are concerned about latency.
Suddenly you want to connect the Modbus to the PC instead. That is quite a fundamental change in specifications. And poses the additional question what you want to use the myRIO for.
Hello Rolf,
No no the plan had been this from start. I didn't know how to access it using LabVIEW but now what I've understand is that I can't access serial port in LabVIEW FPGA that way. I'm just looking for an efficient and can't figure out which way is best suited. I'm a beginner level developer. The block diagram is the hardware level interface which I've to follow.
So please explain what you do hope to do with the FPGA on the myRIO, and in fact why you even would want to have the myRIO in the picture. To me, when looking at your schemata, it looks like it is just hanging on your PC for no good reason.
@rolfk wrote:
@Michael_Smith wrote:
@rolfk wrote:
@Michael_Smith wrote:
I mean what software programming scheme I should follow, If I implement this Hardware Hierarchy?
You really keep changing the specifications on a whim!
First you talk about controlling the Modbus directly from the FPGA on the myRIO because you are concerned about latency.
Suddenly you want to connect the Modbus to the PC instead. That is quite a fundamental change in specifications. And poses the additional question what you want to use the myRIO for.
Hello Rolf,
No no the plan had been this from start. I didn't know how to access it using LabVIEW but now what I've understand is that I can't access serial port in LabVIEW FPGA that way. I'm just looking for an efficient and can't figure out which way is best suited. I'm a beginner level developer. The block diagram is the hardware level interface which I've to follow.So please explain what you do hope to do with the FPGA on the myRIO, and in fact why you even would want to have the myRIO in the picture. To me, when looking at your schemata, it looks like it is just hanging on your PC for no good reason.
myRIO for the RT 😬
Hi Michael,
@Michael_Smith wrote:
@rolfk wrote:
So please explain what you do hope to do with the FPGA on the myRIO, and in fact why you even would want to have the myRIO in the picture. To me, when looking at your schemata, it looks like it is just hanging on your PC for no good reason.myRIO for the RT 😬
. It's good, right?
Modbus over RS485 is not RT.
The ServoDrive should be able to handle the "RT" stuff on its own. (Better ServoDrives definitely can do this.)
The PC can do all the stuff you need to do (AFAIK from your descriptions).
You forgot to explain why you need the myRIO to do non-RT stuff - especially with an additional communication line between PC and myRIO added to the communication with your ServoDrive…
