On 16 November 2015 at 16:13, John Kasunich wrote:
>> hm2_7i80.0.read.time is running between .87ms-1.2ms.
>
> That's pretty horrible.
It sounds it, but I am not sure what is normal for an ethernet-connected board.
--
atp
If you can't fix it, you don't own it.
On Mon, Nov 16, 2015, at 09:17 AM, r...@superiorroll.com wrote:
> After continually entering the "halcmd show pin \*time" command, the
> hm2_7i80.0.read.time is running between .87ms-1.2ms.
That's pretty horrible. Hopefully someone more familiar with the Mesa
drivers can make a more
Isn't that in clock cycles? (not ns)
On 11/16/2015 10:18 AM, andy pugh wrote:
> On 16 November 2015 at 16:13, John Kasunich wrote:
>>> hm2_7i80.0.read.time is running between .87ms-1.2ms.
>> That's pretty horrible.
> It sounds it, but I am not sure what is normal for an
On 11/16/15 9:18 AM, andy pugh wrote:
> On 16 November 2015 at 16:13, John Kasunich wrote:
>>> hm2_7i80.0.read.time is running between .87ms-1.2ms.
>>
>> That's pretty horrible.
>
> It sounds it, but I am not sure what is normal for an ethernet-connected
> board.
A few
PCW did say that, " One thing to remember is that read-time is
in CPU clocks"
I just performed the sudo ethtool -C eth2 rx-usecs 0 command, and it
definitely helped, now it is down around .25ms so far as I can tell.
Rick
On 11/16/2015 11:22 AM, sam sokolik wrote:
> Isn't that in clock
Thank You,
On 11/16/2015 9:01 AM, Dewey Garrett wrote:
>> What would the halcmd command be to show the max time for each loaded
>> component?
> for current execution time:
> $ halcmd show pin \*time
>
> for max execution time:
> $ halcmd show param \*tmax
--
Thanks
Rick Lair
Superior Roll
On 16 November 2015 at 13:49, wrote:
> 28 s32 RW3785632 hm2_7i80.0.read.tmax
>
> Could this be an issue? It is running on the 2.5ms servo thread.
That could be the problem, but that might be the value from the very
first init.
--
atp
If you can't fix
On 16 November 2015 at 12:11, Rick Lair wrote:
> What I found is, is my servo_thread is set at 2,500,000 ns and my ladder
> is peaking at 3,400,000 to 3,500,000 ns.
Are you sure about those numbers?
1,000,000 bS (1mS) is a common servo thread rate. Sometimes there is
an
On 16 November 2015 at 13:03, wrote:
> Here is data from the terminal,
>
> Realtime Threads:
> Period FP Name ( Time, Max-Time )
> 250 YES servo-thread ( 1344688, 4938272 )
OK, that does look like 2.5mS.
I think that
What would the halcmd command be to show the max time for each loaded
component?
> Original Message
> Subject: Re: [Emc-users] Add another "servo_thread" to my config
> From: andy pugh <bodge...@gmail.com>
> Date: Mon, November 16, 2015 8:3
halcmd show
28 s32 RW3785632 hm2_7i80.0.read.tmax
Could this be an issue? It is running on the 2.5ms servo thread.
Rick
> Original Message
> Subject: Re: [Emc-users] Add another "servo_thread" to my config
> From: andy pugh <bodge...@
Good morning Guys,
Just polishing up my build, and noticed a problem late Friday, I was
randomly noticing some weird things happening in regards to my ladder
logic, and looked at every thing regarding the ladder logic, even
re-writing multiple rungs to see if maybe I had a programming error.
After continually entering the "halcmd show pin \*time" command, the
hm2_7i80.0.read.time is running between .87ms-1.2ms.
> Original Message
> Subject: Re: [Emc-users] Add another "servo_thread" to my config
> From: andy pugh <bodge...@gmail.com&g
When using the load rt threads component, I don't need to add anything
to my INI do I?
Rick
On 11/16/2015 7:26 AM, andy pugh wrote:
> On 16 November 2015 at 12:11, Rick Lair wrote:
>
>> What I found is, is my servo_thread is set at 2,500,000 ns and my ladder
>> is
0.0 0:00.00
bdi-default
My ladder has 81 inputs, 62 outputs, 50 bits, almost 60 iec timers,
multiple S32 inputs an outputs, 105 rungs, and 8 different sections.
> Original Message
> Subject: Re: [Emc-users] Add another "servo_thread&qu
>What would the halcmd command be to show the max time for each loaded
>component?
for current execution time:
$ halcmd show pin \*time
for max execution time:
$ halcmd show param \*tmax
--
Dewey Garrett
--
Presto, an
16 matches
Mail list logo