Lightobject.com Support Forum

Hello Greolt:

I know you have been trying hard to explain the way how you the 'Z' to be. I'm sorry that due to my level of English, I must be misunderstood some key issue and couldn't find you a solution yet. Before I totally understand, I won't present to Li as he won't be understand either. Even though the current change I have spent so much time and effort to make him to re-work it. It's not saying that he was not willing to do so, it's the way of logic and didn't quite agreed or understood, like the way I misunderstood yours.

Thank you for being patience with me and shout out loud "Dump!" Allow me sometimes to think about it and work on a Z table when I in China. Oh yes, I'm telling you that I'll go to China on next Monday and will be back on April 29. I'll discuss more issue with Li. May be I can find you a good solution. So, keep posting if you have something in mind and I'll check the support site often

When I come back from China, there will be a big change on Lightobject. More items to sell and more work area -> 15,000sqf warehouse/office is pending


Marco

Marco

I hope you enjoy your trip to China.

Perhaps I could make a couple of other small suggestions for usability improvements that you might mention to Li during your discussions.

1. Allow three decimal places in "Scan Gap (mm)". See pic. Presently it restricts to two decimal places. This would be much more flexible with differing DPI pctures.

2. Allow a setting less than 1 in "Z axis Um/Pulse" See pic. Presently if I enter 0.375 (the correct pulse distance that my Z axis needs) it rejects that and defaults to 1.0 This would suit many motorised table users.

I am optimistic that Li might see these two suggestions as easy to implement.

Good travelling,

Greolt

Sorry I forgot to attach the pictures.

1.) I think it is possible feasible But 2) is impossible. Anything less than 2.5 would be unstable per Li. He suggested the range is between 4 <> 20. If the um must be less than 2, he suggest to change driver setting.

Marco

Tech_Marco wrote:1.) I think it is possible feasible

That is great news Marco. This would allow for almost any DPI photo.

Tech_Marco wrote: But 2) is impossible. Anything less than 2.5 would be unstable per Li. He suggested the range is between 4 <> 20. If the um must be less than 2, he suggest to change driver setting.

This news does not affect my use of the controller. As explained previously, I completely disregard the Z axis DRO. If DRO says table has moved 50mm, in fact it has only moved 5mm.
However I thought it might be good for other users.

Greolt

I briefly tried the experimental firmware on Friday. It flashed on first try. I was able to move the z axis up and down without hitting the soft limit!!! This is a huge improvement! I didn't have enough time to thoroughly examine all the changes but the z movement alone was such a nice addition.

Hey Greolt,
I think your going to have to change the microstepping amount on your driver. if it's at 8 then you could set it to 4 or 2. You loose resolution but with a um setting so low, I don't think it will hurt. If you are using servos, then you need a new encoder unless you have an encoder multiplier setting enabled.

Tech_Marco:
I forgot to say thank you for giving me this firmware to try out. It is a better solution to the soft limit problem. Enjoy your trip to China, and I'm looking forward to what you have to bring back.

Could you look for a heavier and much longer 4th axis used for CNC machines or ATC(automatic tool change) CNC spindles?

Thanks again,
Chris

Telrad, send me some picture and specification and I'll pay attention to it

Marco

For the atc spindle we were looking for something like this one:

http://www.automationtechnologiesinc.co ... -spindle-2

And the 4th axis like this:

http://www.automationtechnologiesinc.co ... e-4th-axis

Telrad wrote: Hey Greolt,
I think your going to have to change the microstepping amount on your driver. if it's at 8 then you could set it to 4 or 2. You loose resolution but with a um setting so low, I don't think it will hurt. If you are using servos, then you need a new encoder unless you have an encoder multiplier setting enabled.

I use drivers with a fixed ten microsteps. If I move the table 50mm by the DRO, it in fact only moves 5mm. Correct setting would be 0.375 Um but I use 3.75 Um instead. However because I disregard the Z axis DRO, it does not affect me.

Other users may find it a problem. The typical motorised table gearing reduction, is quite large (compared to a belt driven X or Y). A setting less than 1.0 Um is often appropriate.

I had hoped that it might be a comparatively easy fix, but alas it seems not. As I say, it does not bother me personally.

Greolt

Are you using a Gecko G540 as your driver for the table? If so, and you're not afraid of a soldering iron, you could change the microstepping. I know my z axis is incredibly fine pitched as well but I can configure microstepping on the driver.

No I am not afraid of a soldering iron.

I am using G251s

As I said this is not a problem for me.

Greolt

Im not sure yet %100 but I think the new OS for the DSP messes up the ethernet connection. I can upload files to the laser but when run they show "File Error!" on the LCD.

This update does in fact corrupt downloads from ethernet. I switched back to the previous version of the OS and all is better with ethernet. It stinks because it was nice not having to reset the z table to move it lower.

I haven't tried the Ethernet. I'll ask programmer Li to give a try while I'm still in China


Marco