Advanced Search

so #5223 is being used in my remap,is it something that I config wrong in the remap or down.ngc ?

Darrell wrote:

Or just delete it I suppose. Doesn't work anyway.

Oh, please don't delete it yet, this looks like it has a lot of potential.

 Ive been trying to figure this out on my own but I am not getting any luck, after using my 3d probe to find Z0 on work piece (down.ngc) then call for T5 M6 for example (tool_change.ngc) both move with no errors but the calculation is off at the moment after T5 touches off the tool setter tip of tool is below Z0 (123 block) but if i move past the 123 block the spindle nose will Z0 off the 123 block.When i calculated the 3dprobe length I touched off spindle nose off the block then used 3d probe to touch off the block to get it length, but the spindle nose distance is moving over to the tool length (I think) dont know what else to do.


 

 

rodw wrote:

This isn't really good enough and if you are like me trying to keep my own ISOs current,  this resulted in an enormous wasted effort.

However big that effort was/is, it is utterly dwarfed by the effort devs put into this project.

rodw wrote:

If I make a contribution, I have to submit a PR and its carefully vetted. Why are others exempt?

See above, and adding: They are the ones who made this project possible, kept it alive, and keep improving every day, you wrote two comps and a howto. Insisting you should be treated the same is absolutely baffling.

rodw wrote:

In summary, I think the days of letting people to do their own thing should be over.

Yet you keep doing your own thing...

Fixed the subject tittle as it kept changing.

You can try using a USB WiFi dongle, but that is also "hit or miss", so it might work fine or might not work at all or might work intermittently.
I've had very good luck with USB to LAN adapters, so far out of over 10, all have worked fine for connecting to Mesa boards.
This also gives you 2 options for Mesa so you can test what works better for you.

Thanks all. Ground the PSU but this wasn't the cause

I should have known this but turns out the pi cannot use Ethernet and wifi reliably at the same time

Peronally, I think the issue here  is there has been a number of bugs introduced by these isolated commits. Look at 2.9. We released  2.9.4, then we released 2.9.5 to fix a bug. But heck we broke something else and released 2.96 and 2.97 before it was resolved, then we did exactly the same thing. released 2.9.9 to fix a bug which introduced a bug which was fixed in 2.9.10. In amongst that, we lost the repo keys which took some time to resolve before a release could be made. So we have advanced 6 versions for just 2 bug fixes. Now that's in the release code, surely its a lot worse in the dev branch.

This isn't really good enough and if you are like me trying to keep my own ISOs current,  this resulted in an enormous wasted effort. I now build my 2.9 versions from source.

If I make a contribution, I have to submit a PR and its carefully vetted. Why are others exempt? Surely its not hard to keep a private repo, and create a new version branch before making a commit to the main code.

In summary, I think the days of letting people to do their own thing should be over. The code is too complex now and we really should be setting an agreed path forward and focussing efforts on an agreed list of enhancements.
 

I am pretty sure MesaCT does not overwrite them, but been quite some time since i used it.
-
In case you want to prevent overwriting config files that are good and done with editing, you can use the file explorer and set the permissions to read only.

flyingbrick wrote:

 The 7I97T is powered by a Mean Well 5V PSU with no earth connection.

Must have earth connection, on all power supplies.

In general I lack experience in this stuff, ground loops especially are confusing. I didn't want to ground the 5v negative and create some other issue. According to what I could find online, the floating 5v is fairly normal (switch mode power supply).

Yes the case etc is ground, just 5v is floating.

Thanks pcw, will ground.

If you have the mind of an engineer, why don't you test the software's functionality instead of complaining you don't like the colour?
Its very comprehensive and the probing is first class.

No, once you get a working config stop using pncconf and edit by hand.

possibly but if you follow the updated how to sticky thread (1st post) , we don't use the igh repo anymore.

Is there a way to prevent the .hal file from being overwritten? If you manually edit the .hal file, everything gets overwritten by pncconf. Is there a setting to ensure that only the parts that were actually modified get overwritten in the .hal file?
Thanks,
Hans