.NET Core programs (realtime) feasible?

Topics about the Software of Revolution Pi
Post Reply
DDD
Posts: 1
Joined: 05 Jun 2019, 13:01
Answers: 0

.NET Core programs (realtime) feasible?

Post by DDD »

Hi there,

has anyone tried to program the device with .NET Core? We want to do realtime digital IO and talk to other devices over Ethernet.

Can you please tell if it's a good idea to use .NET Core here? Are there any show-stopper we should know about?

Timing is key in our project and we need to react to inputs in a timely manner.

Any input hightly appreciated!

DDD
User avatar
dirk
KUNBUS
Posts: 1926
Joined: 15 Dec 2016, 13:19
Answers: 4

Re: .NET Core programs (realtime) feasible?

Post by dirk »

Dear DDD, here is an answer in our forum - unfortunately in German but jut translate it i.e. with https://www.deepl.com/translator
https://revolution.kunbus.de/forum/view ... 390&p=1463
User avatar
fpf_baden
Posts: 19
Joined: 08 Jun 2017, 08:31
Answers: 0
Location: Karlsruhe
Contact:

Re: .NET Core programs (realtime) feasible?

Post by fpf_baden »

Hi,
.NET Core is no problem.

But you have to poll digital inputs - there is no interrupt-service or so.
What exactly are you meaning with "realtime" ?

1µs, 1ms, 10ms, 100ms ?
fgaultier
Posts: 3
Joined: 21 Apr 2020, 10:57
Answers: 0

Re: .NET Core programs (realtime) feasible?

Post by fgaultier »

I tested checking inputs with .NET Core on REVPI Core 3, few months ago. It works fine, but I did not make any measurement for latencies, but should be faster than Python.

By the way, what is the usual latency you can expect before a change in one the DIO module input is reflected in "/dev/piControl0" ?
User avatar
dirk
KUNBUS
Posts: 1926
Joined: 15 Dec 2016, 13:19
Answers: 4

Re: .NET Core programs (realtime) feasible?

Post by dirk »

Hi please regarding the latency of the system there is the variable called "RevPiIOCycle". I have found this tutorial page "PiCtory neues RevPi Core V1.2".
Maybe we have missed to translate this in English - I'll check this.
This value depends on the hardware and the the PiCtory configuration of your system. You may read out this value in not rounded miliseconds with the command

Code: Select all

piTest -r RevPiIOCycle
Post Reply