How to list ALL issues and solutions, including solved and dismissed

[james.edwa...@gmail.com]

I am trying to rework my axes but I can't figure out how to get there. Going to "Basics" level does not list those issues. I have checked "include solved" and "dismissed" but most issues don't show up. I looked at the online document but didn't see any info re this.  I would love to find a way to list ALL the issues. Thanks in advance!

--Jim

[mark maker]

Hi Jim,

For the most part, Issues & Solutions just looks at the configuration and finds stuff that it "thinks" is not OK. So if you don't have issues with your axes listed, chances are there simply are none 😎

Having said that, some Issues & Solutions items are related to things that are basically uninitialized or disabled when encountered. I&S then suggests initializing/enabling these settings, sometimes involving some suggested associated configuration and/or automatic or interactive calibration. For instance, if you want to revisit your axes Soft Limits, just disable the Enabled? checkboxes for the respecitive limit(s), press Apply, the press Find  Issues & Solutions again to get the interactive guidance.

These are just examples, other things can be brought back to the attention of Issues & Solution by zeroing coordinates from a location, emptying G-code from a command/regex, etc. Normally these should be "once" settings, i.e. I&S does not assume they need to be revisited.

Where things may make sense to revisit repeatedly, especially when involving calibrations, the items should be listed when you enable the Include Solved? checkbox. However, this feature was added later in the evolution of I&S so there might be solutions missing there. If you tell me exactly what you think should be revisitable, tell me.

It's hard work to make these revisitable solutions, though. It is difficult to make them "stateless" re other machine config that is normally done later, i.e. where the solution might be a prerequisite in turn (dependency chain). Therefore, they are implemented only where really necessary. 😅

_Mark

On 21.03.2023 19:16, james.edwa...@gmail.com wrote:

I am trying to rework my axes but I can't figure out how to get there. Going to "Basics" level does not list those issues. I have checked "include solved" and "dismissed" but most issues don't show up. I looked at the online document but didn't see any info re this.  I would love to find a way to list ALL the issues. Thanks in advance!

--Jim

--
You received this message because you are subscribed to the Google Groups "OpenPnP" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openpnp+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openpnp/9a02c1f8-f638-4a80-8f78-90fc8324ebe1n%40googlegroups.com.

[Jim Freeman]

Hi, Mark. Thanks. I was thinking about the the “dependencies” between early choices in the setup and later options/choices. I understand it could be quite difficult for the code to take care of all of this. My situation is that I am making an exact clone of a liteplacer I have  working nicely, so I thought the easiest way would be to copy the machine.xml and other xml files over to the new computer and it would just run. So far no good luck. I also tried to delete the xml files and start from scratch, but I got stuck in the virtual machine and couldn’t figure out how to start issues/solutions to define the new liteplacer.

Best, Jim

 

Sent from Mail for Windows

To view this discussion on the web visit https://groups.google.com/d/msgid/openpnp/8207130d-621c-2fb4-2950-04c29e05126c%40makr.zone.

 

[mark maker]

> My situation is that I am making an exact clone of a liteplacer I have  working nicely, so I thought the easiest way would be to copy the machine.xml and other xml files over to the new computer and it would just run.

Assuminh you use the same version of OpenPnP, and apart from reassigning serial ports and and camera devices, this should in-deed work.

In what way does it not?

_Mark

To view this discussion on the web visit https://groups.google.com/d/msgid/openpnp/8DB4A891-D104-4F2C-9D2C-B15F3C728996%40hxcore.ol.

[Jim Freeman]

It is a homing problem. All motors work OK. When I try to home, it homes Z ok, then immediately jogs Y and fails. Normally the second axis to home would be x. I’ll send you a log file as soon as I can.

To view this discussion on the web visit https://groups.google.com/d/msgid/openpnp/1afd9c6f-e398-ae8d-5756-ae363593deec%40makr.zone.

 

[Jim Freeman]

Here is the machine file and the log file of the failed homing on the new machine. It seems to me that the machine does not wait for the next move to complete. Best, Jim

To view this discussion on the web visit https://groups.google.com/d/msgid/openpnp/1afd9c6f-e398-ae8d-5756-ae363593deec%40makr.zone.

[tonyl...@gmail.com]

Have you verified all your TinyG settings? Looking at your log I see some warnings about non-standard microstep settings on your X and Y motors - I don't know what TinyG would do with those. See the LitePlacer page for a link to a complete set of TinyG settings that are known to work. Also, have you verified all your end-stop switch wiring - if that's wrong, homing won't work correctly.

Tony

[mark maker]

According to the log it says

2023-03-22 09:56:16.665 MessageBoxes DEBUG: Error: java.lang.Exception: FIDUCIAL-HOME no matches found.

Do you not see that message box?

I assume your "exact clone" does not have the Homing Fiducial mounted at all, or maybe not at the same spot, which in turn might be related to the typically dodgy Liteplacer endstop mounting not being exactly the same.

_Mark

To view this discussion on the web visit https://groups.google.com/d/msgid/openpnp/CABRkqyC9xOshxN_9K0wW%3D0b%2B8qtFn2O72WOY0RCDGkTOhKYWhA%40mail.gmail.com.

[tonyl...@gmail.com]

Mark,

It's his mechanical homing that is not working correctly - that's why I think it is either a TinyG config problem or a wiring problem.  He needs to get that working first before visual homing will work.

Tony

[Litterio Andrea Guainella]

Hi all,

@Jim check TinyG configuration about "xtm" and "ytm". If you have Liteplacer thiese values should be set to 600.000 mm.

Your issue It happened to me too and I realized that these parameters are the maximum travel that the x and y homing phase can do.

For check TinyG configuration put "$$" in command line and click "send" (for safe reason backup this configuration via copy/paste to a text file).

For editing value put "$xtm=600.000" in command line   and click "send".

For editing value put "$ytm=600.000" in command line  and click "send".

If useful check image below

LAG

[Jim Freeman]

Hi Tony and Mark.

Tony, in the page of the link you sent me there is a link to tinyg settings known to work, It doesn't seem to work for me. But I have a working system to compare to. A question, in the page you sent, the home command is 

<command type="HOME_COMMAND">
      <text><![CDATA[G28.2 X0 Y0 Z0 A0 ]]></text>
      <text><![CDATA[G92 X0 Y0 Z0]]></text>

while in my code it is 

G28.2 X0 Y0 Z0 A0
G28.3 X0 Y0 Z0 A0. 
Since my code works on the first machine I assume it will also work on the second.
The homing behavior on the new machine is: the Z goes in the negative for a little ( 1 cm or so) then goes in the positive until it hits the max Z limit switch. 
It does not back off from the limit switch, then immediately moves a little in -Y, then halts with the optical homing failure. 
But it never completes the mechanical homing first. It seems like the m400 immediately gets an acknowledgement, not waiting for the machine to move. (But I am not an expert!)  
Thanks for looking into this.
Best, Jim

To view this discussion on the web visit https://groups.google.com/d/msgid/openpnp/f2a81aa6-2c95-448a-8807-191081eef3dbn%40googlegroups.com.

[tonyl...@gmail.com]

I'd ignore any of the machine.xml stuff you see on that page. It's old and that's why I added the "The following information may be a bit outdated..." caveat to that part. What happens when you click the link to the TinyG settings on that page?

[Jim Freeman]

Thanks for the suggestion. My settings for those are OK. Yes I recall that originally they were too small, I think 150mm. But that is not my problem now. I get very strange behavior when I try to do mechanical homing, immediately failing.

Best, Jim

You received this message because you are subscribed to a topic in the Google Groups "OpenPnP" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/openpnp/LJc9gwBJMLY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to openpnp+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openpnp/d2288f75-a541-4554-a823-7e2fcffb8a70n%40googlegroups.com.

[Jim Freeman]

It takes me to :

https://github.com/openpnp/openpnp/files/11004279/TinyG_settings.txt

but it doesn't open.

To view this discussion on the web visit https://groups.google.com/d/msgid/openpnp/febe2e89-70a8-48ec-a67d-9a2b2247518cn%40googlegroups.com.

[tonyl...@gmail.com]

It should download a text file to your PC - check you downloads folder. I'm currently adding a new wiki page that has the settings explicitly listed. It should be available in a few minutes.

[tonyl...@gmail.com]

The new wiki page should be available now at TinyG Configuration Settings. That page is now also linked from the LitePlacer page.  I also put a big banner on the LitePlacer page to indicate the stuff that is most likely outdated.

Tony