Hello Guest it is April 23, 2024, 11:36:38 AM

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Olovsson

Pages: 1 2
1
I have been trying to change the polling frequency and the buffer level to all values I can imagine. However, I can’t get rid of the ___WARNING message. If I put the polling frequency to 80Hz, I get the “MainLoop Tick Interval Out of Range” error. The “tick error” disappears at 75 Hz polling frequency, but the “___WARNING” is still there.
 
The reason I’m doing this is that the old PC broke down and I had to fix a new one to the mill. This PC is equipped with an AMD 5800X (8 core, 3.7 – 4.8 MHz) processor and 32Gb of internal memory. I would guess that the horsepower of that one should be more than enough to keep the PC frequency on a high level (80Hz) without getting any error.

Any other ideas what to do to get rid of this or to be able to run with your suggested 80 HZ and 125 ms buffer?
The mill seams to be working ok with 75Hz or lower polling frequency, but it feels quite annoying and a bit unsafe when the log window is "spitting" out a lot of warnings the whole time.   

Best Regards,
Olovsson

2
Hi,
I get a lot of the “WARNING: Main Loop ..” from the 7766. It seams to depend on what polling frequency you have set, a lower frequency generates less warnings. I have been playing around with the polling frequency and the buffer size, but can get rid of it completely.
     
What does the warning mean? Will it affect the machine in some ways? Do I need to try to get rid of the warning? In that case any ideas what to do, to get rid of it?

The log is from when I run a probing sequence with a lot of slow moves and a lot of probe points.

Best Regards,
Olovsson

Polling Frequency 75 Hz
Mach4300-Integra-4.24_Plugin-2.03.41
Mach4: 4612

[07:17:34.845] Motors are now set still:
       
  • Pos=214157, Actual=214157.00, StepGen 214157, Plugin 214156
  • [1] Pos=194750, Actual=194750.00, StepGen 194750, Plugin 194750
            [2] Pos=-192082, Actual=-192082.00, StepGen -192082, Plugin -192082
            [3] Pos=-1, Actual=-1.00, StepGen -1, Plugin -1

[07:17:34.846] __________WARNING: Main Loop Process duration: 6.9378ms, Polling Interval 13ms
[07:17:35.188] New Start Position: 214157 | 194750 | -192082
[07:17:35.225] __________WARNING: Main Loop Process duration: 5.246ms, Polling Interval 13ms
[07:17:35.289] __________WARNING: Main Loop Process duration: 5.7556ms, Polling Interval 13ms

3
Thanks Craig,

I have check the variables and it seems to work fine. The 4016 Var will be set to 68 or 69. The 2135, 2136 and 2137 is holding the X, Y and rotation angle that is set with the G68.

Olovsson 

4
Hi,

I'm working on a wizard that should measure and handle the rotation of the coordinate system. However, when I start the wizard it would be good to read out if G68 is active or not and with which angle it is rotated. I'm not able to find anything like that in the API (LUA) manual. Anyone that knows if that's possible or not?

Olovsson   

5
Hi,

I'm getting this error from the plugin every time I change direction:

[20:27:08.424] Waiting for controller to consume buffered motion: Mtr: 0 SeqID: Ctrl 943999 Mach 944007
[20:27:08.434] *><><* Motor 0 is almost in position 339695.00 339694.98
[20:27:08.434] *><><* Motor 1 is almost in position 332600.00 332600.00
[20:27:08.435] *><><* Motor 2 is almost in position -330478.00 -330478.02
[20:27:08.464] ########### ERROR: Motor 0 Set Still without in position 339695 339694
[20:27:08.464] MotionSetStill for motor 0
[20:27:08.465] ########### ERROR: Motor 1 Set Still without in position 332600 332600
[20:27:08.465] MotionSetStill for motor 1
[20:27:08.465] ########### ERROR: Motor 2 Set Still without in position -330478 -330478
[20:27:08.466] MotionSetStill for motor 2
[20:27:08.466] Motors are now set still:
       
  • Pos=339695, Actual=339695.00, StepGen 339695, Plugin 339694
  • [1] Pos=332600, Actual=332600.00, StepGen 332600, Plugin 332600
            [2] Pos=-330478, Actual=-330478.00, StepGen -330478, Plugin -330478

    Anything to worry about?

    Mach4 4.2.0.4300
    Mach4300-Integra-4.18_Plugin-2.03.33
    7766 FPGA: A2B2

    /Olovsson



6
HiCON Motion Controller / Re: 7766 and Gecko GR214V Feedback?
« on: January 02, 2019, 06:09:14 PM »
Thanks for the reply.

But I would still need to level shift the 5V TTL from the 214 to 3.3V to the J10? Right?

Regards,
Kjell

7
HiCON Motion Controller / Re: 7766 and Gecko GR214V Feedback?
« on: January 02, 2019, 04:08:37 PM »
Understand that the 7766 has 24V input. Is there any commercial board available that can be used? Or do I need to design one myself?

Regards,
Kjell

8
HiCON Motion Controller / 7766 and Gecko GR214V Feedback?
« on: December 28, 2018, 06:01:20 AM »
Hi,

I recently bought a 7766 and a couple of Gecko GR214V. On the 214 there is two outputs Error and Full Step feedback, 5V TTL signals. Is there any way I can get them into the 7766 and use them in Mach4? Well the Full Step feedback is really not an encoder, but it would be nice to have that as a feedback for step count.

Regards,
Kjell   

9
Mach4 General Discussion / Re: LUA problem when exit a Wizard
« on: July 17, 2018, 01:21:02 AM »
Thanks for pointing me in the right direction. I was doing some more testing and found that the only way I could get it to work was a “clean”:
Code: [Select]
UI.MainWindow:Connect( wx.wxEVT_CLOSE_WINDOW, function(event)
--implements MainFrameClose



event:Skip()
end )


I have an “Exit” button in the wizard and I changed so that one call Close() instead of Destroy():

Code: [Select]
function ExitWizard()

UI.MainWindow:Close()

end

After some reading, my understanding is that Close() should generate a wxEVT_CLOSE_WINDOW event, which should trigger the close of the window. Problem is that when you have more than one instance of the wizard running, which have the same code, it will not work. It works on the first window you try to close but then on the second the LUA runtime addresses the same “UI.MainWindow” as in the first one and you get the error say trying to address something that doesn’t exist anymore.
So right now it seems to be impossible to have two or more wizards that have the same name on the wxFrame object to run at the same time. This is of course not a big problem, normally you don’t run two of the same wizards at the same time. But at least I can close them now if starting more by mistake

10
Mach4 General Discussion / Re: LUA problem when exit a Wizard
« on: July 16, 2018, 09:01:49 AM »
Right, I was thinking around the same lines. But that doesn’t help if you start two of the same wizard (which has happened to me a number of times

Pages: 1 2