Advanced Search

One step closer. mmmm. motors being so much smaller gives a lot more room in the enclosure too which is nice.
Z has no brake, but being shorted to the resistor in the drive lets the spindle drop very slowly now, so nothing bad will happen from a sudden power cut. now... to make it run!

 

I see the basic problem.
The original vismach updates every 100ms but only if something changes.
Qtvcp updates every 100 ms no matter what.

I'm looking into what library options there are to correct this.
In the mean time, you can increase the buffer in qt_vismach.py
look for:
self.plotlen = 16000

Not sure what all types of laser heads this will work with but I'm about to stick a diode laser on a PnP machine I built but shelved. I'll be doing that in the next few days, I could stick this thing on it while I'm converting it over if that's the type of testing you're looking for.

I use a custom carrier board for a Mesa 7i92. Not sure what other kind IO capabilities that thing has but I think the only suitable input I have is an "SmartSerial" port. That's a 2.5Mbaud RS422 port which is what people tend to use around here for stuff like this since Mesa cards are the king of the hill. I could also swap the RS422 transceiver for a dual RS422 receiver to make it a quadrature encoder input.

If you are using a custom .ui file then load it in designer and save it again.
If you are using a default .ui, then pull again, the fix has been pushed.

 

--- English ---

Got an idea to try it out, sent the question to the Alibre reseller in Sweden.

-Alibre Sweden email reply wrote: Hi,

I have tested both and they work well if you look at the cost.

eCAM is the original which has been translated and adapted by an Alibre dealer in Switzerland. There is no difference between them except the language and - I guess - that the Alibre script only works with SimpexCAM.

As far as I know, there is an Alibre customer who bought SimplexCAM but I haven't got any feedback on how it works for them.

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'