t-oster / VisiCut

A userfriendly tool to prepare, save and send Jobs to Lasercutters
https://visicut.org
Other
235 stars 115 forks source link

all my squares come out like trapeziums and all text in italic. on a LS3020 Laos with visicut #148

Closed djuttien closed 11 years ago

djuttien commented 11 years ago

Haai,

I am using a LS3020 with a Laosboard and visicut, and somehow, while engraving, it is out of sync, all my squares come out like trapeziums and all text in italic..

there's nothing wrong when cutting... Is there a setting where I can change/modify/fix it?

cheers, Daan

peteruithoven commented 11 years ago

Hi djuttien,

I (@Fablab Amersfoort) also use a LS3020 (http://redmine.laoslaser.org/projects/laos/wiki/A_list_of_users_with_LAOS_converted_lasercutters). I don't have this problem. What are u using engrave or engrave 3d? The latter is not properly supported yet. Have you also tried to cut something very dense, big, complex to simulate the amount of movement the lasercutter does in the engrave modes?

You are using the latest firmware (https://github.com/LaosLaser/Firmware/tree/issue_73_75) and Visicut development version?

djuttien commented 11 years ago

Haai Peter,

Yes I will have to add the machine to the list (again) .. it's Bart Bakkers machine... 

I was hoping you were going to reply, 'cause I have seen on the forum you use the same setup...

I am using Engrave, after I did a cutting and made some test objects of 1 x 1 cm , and some of 2 x 5 cm, both just lines and filled letters and boxes in combination(s)

the 29-12 firmware has been installed and the latest 1.7 visicut  ( not the developmentversion? I don't know..)

thanx! Daan


From: Peter Uithoven notifications@github.com To: t-oster/VisiCut VisiCut@noreply.github.com Cc: djuttien djuttien@yahoo.com Sent: Friday, May 3, 2013 9:30 PM Subject: Re: [VisiCut] all my squares come out like trapeziums and all text in italic. on a LS3020 Laos with visicut (#148)

Hi djuttien, I (@Fablab Amersfoort) also use a LS3020 (http://redmine.laoslaser.org/projects/laos/wiki/A_list_of_users_with_LAOS_converted_lasercutters). I don't have this problem. What are u using engrave or engrave 3d? The latter is not properly supported yet. Have you also tried to cut something very dense, big, complex to simulate the amount of movement the lasercutter does in the engrave modes? You are using the latest firmware (https://github.com/LaosLaser/Firmware/tree/issue_73_75) and Visicut development version? — Reply to this email directly or view it on GitHub.

peteruithoven commented 11 years ago

Ah, I see Thomas released the development version as 1.7, nice milestone. So yeah the 1.7 should be right. I can see that there is a slightly newer version of the firmware (laoslaser-9-3-2013.bin).

Maybe try to lasercut the outlines of a big peace of text in the cut mode, so rule out any hardware issues.

At Fablab Amersfoort visitors recently did the following engraving, to my enjoyment. img_0168

djuttien commented 11 years ago

haai again,

can't seem to locate laoslaser-9-3-2013.bin at https://github.com/LaosLaser/Firmware , Am I blind or is it somewhere else?

cheers, Daan

peteruithoven commented 11 years ago

Weird, apologies, I can't find it either.

djuttien commented 11 years ago

hee Peter, can you mail it to info@sawugo.nl ?

cheers, Daan

peteruithoven commented 11 years ago

Nop, not sure what I was looking at, but I can't find laoslaser-9-3-2013.bin anymore.

t-oster commented 11 years ago

Hi @djuttien, please modify your laos-config and try half the speed. It seems as if some steps get lost. Since the vector-mode is not that move-intensive,it may be that you can not recognize it.

djuttien commented 11 years ago

It seems to be fixed with putting the config.txt file from the laos-laser site on my machine... allthough now I have to reconfigure the home position and everything, but at least it is working now with engraving!

anyway.. it was a problem with the speed somewhere motion.speed in the config.txt of my laosboard... now set to default.

thanx! Daan

djuttien commented 11 years ago

bummer.. it has not been fixed.. had some trouble handling my Mbed memory, and have now tried engraving with motion.speed set at 50 , 25 en 10 , and there is no difference.. I can change the motion.speed, but as soon as I change different speedsettings my steppermotor's are going crazy brrrrrooom ..

http://reprap.org/wiki/Pololu_stepper_driver_board#Tuning_motor_current http://reprap.org/wiki/File:Pololu_v-ref_checking.jpg

I am now measuring the Voltage on my Polulu's, and checking how much output they should give (on a similar machine (thanx in advance Peter~!)

so it may be a Laos problem, but still not sure about it...

cheers, Daan

t-oster commented 11 years ago

I still don't think, that it's a VisiCut issue.... my laos engraves perfectly. But you can enable the "debug File" option in the lasercutter settings, so you get the file, which is sent to the laos and you can check the coordinates.

djuttien commented 11 years ago

allright.. it is not the polulu intensity.. at least they are now set at optimum, we tried and no matter the settings it comes out bad.... I will now see what is in the debug file when I engrave...I hope I am able to "read" them...

peteruithoven commented 11 years ago

debug file should be simplecode: http://redmine.laoslaser.org/projects/laos/wiki/SimpleCode A friend of mine made the following Processing sketch to visualize simplecode: http://companje.nl/laos-laser-simplecode-preview-tool/

On Thu, May 23, 2013 at 11:24 PM, djuttien notifications@github.com wrote:

allright.. it is not the polulu intensity.. at least they are now set at optimum, we tried and no matter the settings it comes out bad.... I will now see what is in the debug file when I engrave...I hope I am able to "read" them...

— Reply to this email directly or view it on GitHubhttps://github.com/t-oster/VisiCut/issues/148#issuecomment-18372670 .

djuttien commented 11 years ago

mumblegrumble.. . I have now ordered a new T5 belt to replace my suddenly broken one.. I have now made the early conclusion (won't know for sure 'till my new belt has been installed) that it has been a mechanical error.... mumblegrumble.. not happy... : (but really happy with visicut...