Project

General

Profile

receive file

Added by leenvw over 12 years ago

after sending a file from VisiCut, the time of sending takes appr. 15 seconds and the display says "receive file" and stuck.

The laser is not easily reset, in fact almost impossible. Tried everything. After different attempts, sometimes the sending is just a few seconds (whats normal). The cutting is good than.

Has anyone seen that before?


Replies (14)

RE: receive file - Added by pieterb over 12 years ago

yes i have had that to, mostly when changing the config.txt
sometimes it helps to send the file again.
this is probably a bug but where i do not know (visicut,mbed networking lib, firmware ?)

RE: receive file - Added by jaap over 12 years ago

I've seen it too, and I'm not using Visicut. So it's most likely a network/tftp-bug in the firmware.

RE: receive file - Added by leenvw over 12 years ago

I canget away with it by repeating the execute in VisiCut. Mostly after the second time, the sending of the file wents fast and the file appears on the I2C.

Is not very charming, but not high priority, I would say.

RE: receive file - Added by Martine over 12 years ago

same problem here.
restarted laser + visicut. does work most of the time...

RE: receive file - Added by jegb almost 9 years ago

I have to check my settings in Visicut, when I execute a job, Laos does not receive anything.
is there anyway to generate gcode file from inkscape and place it on the card, without going via Visicut? I found other inkscape extension for lasercut but have not tried it yet.

RE: receive file - Added by peteruithoven almost 9 years ago

Probably not, I don't think there are other programs that speak SimpleCode, see:
http://redmine.laoslaser.org/projects/laos/wiki/SimpleCode
(The lasercutter doesn't understand gcode)

RE: receive file - Added by jaap almost 9 years ago

If there's no reception (and no sign of receiving at all) you should check the Visicut settings. Maybe the IP or port is wrong. See if you can ping the laser from your computer and test if you can upload a SimpleCode file directly via tftp to the laser.

Visicut can also export simplecode to file, but you can also just make a test file with a text editor. The convention is to use .lgc as the filename ending.
This simplecode file should cut a square:

square.lgc

201 0
202 120819
203 252078
204 300000
7 100 10000
7 101 800
0 100000 100000
1 120000 100000
1 120000 120000
1 100000 120000
1 100000 100000

RE: receive file - Added by jegb almost 9 years ago

Thanks for the support.

The issue seems to be on the dhcp which if I set 1, the ip adress is 0.0.0.0. Is there any way to get MAC address from terminal?
That way I could force filter on the router AP and give it a fixed IP.

RE: receive file - Added by jegb almost 9 years ago

I get this randomly working, with small files seems to go fast, but when I send a large file seems to get stuck.
-is there anything different on the TFTP vs TCP setting in Visicut?
-is there any way to add a reset via 2 keys combination to avoid a power cycle ? Soft boot-reset would be a desirable feature, wouldnt it?

RE: receive file - Added by peteruithoven almost 9 years ago

You could press the button on the MBed?

RE: receive file - Added by jegb almost 9 years ago

not very convenient, board is next to the HV PSU.

Wouldn't be possible to use the Analog input (was it used for cover open/closed?) to trigger the reset?

RE: receive file - Added by peteruithoven almost 9 years ago

There is probably a reset pin on the MBED that you can plug a button into, just like with the Arduino.

RE: receive file - Added by jegb almost 9 years ago

Good idea, I will try this one out, according to this is Pin4

RE: receive file - Added by jegb almost 9 years ago

did not work, testing the header pin #4 with the reset pin on the push button is not connected.

According to this schematic, pins 45 and 46 are Target RST REQ1 and Target RST REQ2, IF_NRESET and IF_NRESET_EXT.

Pin 4 is the IF_NRESET_EXT, but to reset would need to expose IF_NRESET pin.

anybody has an idea what is the problem?

    (1-14/14)