Advanced Search

109jb wrote:

I got my touchscreen monitor delivered yesterday and just wanted to confirm that the issue I was having with touchscreen button not working right was a consequence of using Flex GUI in a virtual machine on windows. The Flex GUI that I made works perfectly on a real machine with touchscreen. For the real machine I am using a RPi 4b and a generic 10" touchscreen monitor.

For anyone else designing their GUI this way, I am using VirtualBox on a Windows 10 machine. The virtual Machine has LinuxCNC 2.9.4 installed from the live iso download. Here are the couple quirks I have found running it in the virtual machine. I want to stress that these issues don't exist once the .ui file is put on my RPi machine.

1. touchscreen buttons don't respond as expected in virtual machine
2. The machine will unexpectedly go to "Power Off" as soon as a motion command (Jog, MDI, or in a program) completes. Doesn't do it every time, but pretty often. Again, only in the virtual machine.
   
   I also want to again give thanks for this wonderful tool and to give a peek at what I am working on. I have a 3 axis benchtop mill (RF-45 size) that I converted to CNC a few years ago. I did this as a hobby and use the machine for my hobbies. It has been run with many things including LinuxCNC on an old tower PC with ancient monitor, keyboard and mouse, with GRBL on an Arduino hooked to a Netbook with my own Visual Basic interface, and I tried one of those standalone controllers, but sent it back because it was junk. I finally decided to just do it better and got a RPi 4b, installed LinuxCNC and have been working on an interface that for most of the way I use the mill can be done without ever touching a keyboard. I'll still have a small wireless keyboard with trackpad available if needed though. This is the interface I'm working on and I think it will suit me. I have the UI sized to perfectly fit the display that I bought to use as much space as possible. Thanks again for the very useful tool.
   
   John B

I've been doing mine in a Virtualbox Debian VM but the host is Manjaro Linux.  It sounds like you are just catching realtime or feedback errors. I pulled some of the sim stuff from prebuilt configurations so I could run mine without being attached to hardware, I don't have any errors that put it into E-stop condition. The touchscreen works exactly as it would running Debian itself so I think that issue is more about the host you're running the VM on.

I discovered the same thing in 2023-06-22 22:31:56 in this forum:
elektronikforumet.com/forum/viewtopic.php?t=108054&hilit=CAM
Don't know if the thread is readable for outsiders and it is in Swedish.

-- Swedish --
Fick en idé att prova, drog iväg frågan till återförsäljaren av Alibre i Sverige.

-Alibre Sveriges epost svar- skrev: Hej,

jag har testat båda och de fungerar bra om man ser till kostnaden.

eCAM är originalet som sedan översatts och anpassats av en Alibreåterförsäljare i Schweiz. Det är ingen skillnad på dem förutom just språket och - gissar jag - att skriptet till Alibre endast fungerar med SimpexCAM.

Vad jag vet är det en Alibrekund som köpt SimplexCAM men jag har inte återkopplat hur det fungerar för dem.

 

prokopcio wrote:

I suggest 20-70kHz (0-10mm) and 10kHz(or 0Hz) = collision

This is linuxcnc. We will not have collisions!
Maybe  collisions are 5 kHz and our rule is: if < 10 kHz, report a collision

Thanks! I just want to prevent current through the spindle coils. I found parameters in the VFD to suppress low frequencies, so I think its solved. Thanks for your hints!
Hanno

From code just released today:   AttributeError: 'MachineLog' object has no attribute 'setFrameShape'

Hi Chris

Have you looked at the problem I wrote about earlier?

I got an R5 340X off of ebay, and I tried it out.  It didn't seem to make any difference in the RTAI or PREEMPT_RT kernels.
 

I feel like I'm missing some option.

I can't figure out why nosmt isn't working for the rtai kernel.

The only interrupts that are firing are RES, LOC and 24 which is the new graphics card.

Hopefully this helps with the settings.
If you use 0-10 volt input then you can only have positive voltage output.

using +5 and -5 volt input:
output scale defines what value will give full voltage output (+-2000 RPM = full voltage +-5 volts)
output min limit defines lowest value allowed (-2000 or negative full voltage)
output max limit defines highest value allowed (2000 or positive full voltage)
The spindle speed command range would be -2000 to 2000 RPM with output swing from -5 to 5 volts

using +5 and -5 volt input:
output scale defines what value will give full voltage output (+-4000 RPM = lets say 5 volts)
output min limit defines lowest value allowed (-2000 or -2.5 volts )
output max limit defines highest value allowed (2000 or 2.5 volts)
The spindle speed command range would be -2000 to 2000 RPM with output swing from -2.5 to 2.5 volts

output scale defines what value will give full voltage output (+-2000 RPM = full voltage +-5 volts)
output min limit defines lowest value allowed (-2000 or negative full voltage)
output max limit defines highest value allowed (2000 or positive full voltage)
The spindle speed command range would be -2000 to 2000 RPM with output swing from -5 to 5 volts

With 0 to 10 volt input
output scale defines what value will give full voltage output (+4000 RPM = 10 volts)
output min limit defines lowest value allowed (0 or 0 volts can't supply negative voltage)
output max limit defines highest value allowed (4000 or 10 volts)
The spindle speed command range would be 0 to 4000 RPM with output swing from 0 to 10 volts
You would need a reversing relay to run in reverse.


There can be other reasons the spindle does not run at low speeds such as VFD settings of minimium rpm etc.

Thanks Peter for your opinion.
You strongly confirmed my analyses.
because some cards have a limit of 100kHz ( ETHERCAT EL5151for example )
I suggest 20-70kHz (0-10mm) and 10kHz(or 0Hz) = collision

I know of no talk about releasing 2.10 anytime soon.

Option JP2 on the label, set it to always on for now.

Ich habe es schon befürchtet. Dann muss ich nun doch den Weg über die Kinematik Berechnung gehen, leider.
David, hab lieben Dank für die für mich wertvollen Hinweise. Ich möchte eigentlich sehr ungern aufgeben. Alternativ müsste ich meine Achse komplett  umbauen. Dafür hätte ich da noch ein wuchtiges Schneckengetriebe. Das ist dann aber ein großer Aufriss und wirklich das letzte Gefecht.
Liebe Grüße
Peter

 

I would say a couple hundred KHz so pretty much any encoder interface could work.
Also better if its a square wave so it asks the least of the frequency/period counter.
An offset frequency is good also so you don't lose bandwidth near 0 frequency.

That fixed the message popping up, thanks!

SimplexCAM and eCam look quite the same. Couldn't find any differences so far except the price. Could you?