My understanding is that the dynamic status fields were introduced for 1.0 or 1.1 so you should be good in terms of version.
Try $10=3 or $10=255 to see if that makes a difference.
No differenceā¦
$10=31
ok
?
<Idle|MPos:0.000,0.000,-67.500|Bf:15,127|FS:0,0>
ok
$10=255
ok
?
<Idle|MPos:0.000,0.000,-67.500|Bf:15,127|FS:0,0>
ok
$10=3
ok
?
<Idle|MPos:0.000,0.000,-67.500|Bf:15,127|FS:0,0>
ok
Bummerā¦
Hello to all.
Here are the results of the commands you wrote above:
$I
[ORIGIN: China]
[PRODUCER: ORTUR]
[AUTHOR: ORTUR]
[MODEL: Ortur Laser Master 2 Pro S2]
[OLF: 187]
[OLH: OLM_ESP_PRO_V1.2]
[SN: 8C58C60322A40FAC8E48A369AFXXXXXXXXXX]
[OLM:GENERAL]
[DATE:17:26:04 - Dec 15 2021]
[VER:1.1f(ESP32).20210403:]
[OPT:VNMZHSL,35,7680,3]
Target buffer size found
ok
$$
$0=5.0
$1=100
$2=0
$3=6
$4=7
$5=7
$6=1
$10=2047
$11=0.050
$12=0.002
$13=0
$14=6
$15=0
$16=1
$17=4
$18=0
$19=0
$20=1
$21=1
$22=1
$23=7
$24=600.000
$25=3000.000
$26=100
$27=3.000
$28=0.100
$29=0.0
$30=1000.
$31=0.
$32=1
$33=1000.000
$34=0.000
$35=0.000
$36=100.000
$37=0
$39=1
$40=1
$41=0
$42=1
$43=1
$44=3
$45=0
$46=0
$56=1.000
$57=1800.000
$58=395.000
$59=6000.000
$60=0
$61=0
$62=0
$63=3
$64=1
$65=0
$100=80.000
$101=80.000
$102=2124.000
$110=10200.000
$111=10200.000
$112=600.000
$120=2200.000
$121=1800.000
$122=200.000
$130=400.000
$131=400.000
$132=100.000
$259=0
$260=70
$261=0
$262=400
$263=30
$264=0
$265=50
$266=100
$267=0
$268=0
$269=0
$270=5120
ok
$#
[G54:0.000,0.000,0.000]
[G55:0.000,0.000,0.000]
[G56:0.000,0.000,0.000]
[G57:0.000,0.000,0.000]
[G58:0.000,0.000,0.000]
[G59:0.000,0.000,0.000]
[G59.1:0.000,0.000,0.000]
[G59.2:0.000,0.000,0.000]
[G59.3:0.000,0.000,0.000]
[G28:0.000,0.000,0.000]
[G30:0.000,0.000,0.000]
[G59.6:0.000,0.000,0.000]
[G92:0.000,0.000,0.000]
[HOME:0.000,0.000,0.000:0]
[TLO:0.000]
[PRB:0.000,0.000,0.000:0]
ok
?
<Idle|MPos:0.000,0.000,0.000|Bf:35,7679|FS:0,0|Pn:PXY|CL:0,100|PS:2,1|ER:0,0|WCO:0.000,0.000,0.000|VA:24064,0|Ov:100,100,100|A:S>
[GC:G1 G54 G17 G21 G90 G94 G49 G98 G50 M5 M9 T0 F6000 S0.]
ok
Any ideas?
Markus
This shows that both limit switches are triggered. Can you disconnect the limit switches and rerun ?? Hopefully that goes to āPn:Pā without the XY.
I canāt seem to get that output with my grbl machine.
Any ideas?
I suspect your firmware was compiled with this off. See notes from GRBL config.h. āREPORT_FIELD_PIN_STATEā is the field in question:
// The status report change for Grbl v1.1 and after also removed the ability to disable/enable most data
// fields from the report. This caused issues for GUI developers, whoāve had to manage several scenarios
// and configurations. The increased efficiency of the new reporting style allows for all data fields to
// be sent without potential performance issues.
// NOTE: The options below are here only provide a way to disable certain data fields if a unique
// situation demands it, but be aware GUIs may depend on this data. If disabled, it may not be compatible.
#define REPORT_FIELD_BUFFER_STATE // Default enabled. Comment to disable.
#define REPORT_FIELD_PIN_STATE // Default enabled. Comment to disable.
#define REPORT_FIELD_CURRENT_FEED_SPEED // Default enabled. Comment to disable.
#define REPORT_FIELD_WORK_COORD_OFFSET // Default enabled. Comment to disable.
#define REPORT_FIELD_OVERRIDES // Default enabled. Comment to disable.
#define REPORT_FIELD_LINE_NUMBERS // Default enabled. Comment to disable.
You could try flashing an alternative firmware for your controller. I suspect the stock GRBL build would work fine on your Woodpecker. Youād want to backup your settings in case they get clobbered.
Easily done from LaserGRBL. Slightly less easily with xloader. Slightly less easily yet with Arduino IDE.
Now IĀ“ve unplugged both limit switches and if i send the command ? in console, I will get the following message:
?
<Idle|MPos:3.000,3.000,0.000|Bf:35,7679|FS:0,0|Pn:PXY|CL:0,100|PS:2,1|ER:0,0>
ok
This means that i always have a signal from the limit switches, even though they are not connected at all.
I did another test now:
I reconnected the limit switches and measured at the connector to the mainboard whether the signals were arriving correctly or whether there was a short circuit in the wiring harness.
Result: The limit switches switch correctly and the signal arrives correctly at the connector to the mainboard.
However, if I measure the switch inputs directly on the mainboard pins, I always have continuity for a short time. Iām now betting strongly that my motherboard is broken. Or what do you think?
Thank you again for your efforts.
Thatās what Iām leaning towards as well. Iāve never heard of this failure mode before, though, so it would be fairly rare I think.
Try one thing. Try reflashing the firmware again. I know you already upgraded the firmware once but good to do a sanity test before throwing in the towel.
Are you still under warranty? If so, you should open a ticket with Ortur team.
I think i have the reason for that error message:
The Y-limit switch canĀ“t be deleted on the input.
I alternately pressed the limit switches and over ? read the signal in the console.
The X signal disappears when the X limit switch is no longer pressed and the Y signal no longer disappears. No chance to erase it. Not even if I remove the Y-limit switch cable from the connector to the mainboard. This confirms again that the mainboard must be defective, right?
I want to make sure I get what youāre saying.
If you run ? when X switch not active the status report does not show X. When triggered X shows?
However, for Y, youāre saying Y is always showing in the status report whether or not the switch is triggered?
Then yes, same conclusion as before. But just limited to Y side.
Do one thingā¦ can you look very carefully at the connector on the controller side as well as the board and make sure thereās nothing potentially shorting the Y pins? Iām wondering if thereās something going on thatās potentially keeping it permanently shorted.
Iāll look into that. I hate to brick it for something I donāt really use. Itās actually a āVevorā cnc3018 with supplied limit switches. But still an Arduinoā¦ Donāt know who makes the board.
Iāll check it on the one of the other machines. Never tried it on the 3d printerā¦
Iād suggest updating only if you have a copy of your current firmware available to reflash if needed.
Assuming the 3d printer runs a Marlin firmware not likely to work. I canāt recall offhand what the command is in Marlin to get limit switch status.
I donāt have a copy of it. I wonder if I can read it from the Arduino controller with āavrdudeā.?
Iāve never used avrdude but Iāve seen that it can be used for this. Iād give it a shot in either case. Always good to have a backup of your firmware.
I reflashed the firmware and IĀ“ve tested it with all 3 versions from ortur website (1.83 / 1.85 / 1.87).
But unfortunately it didnāt work either.
Because IĀ“m still under warranty, I opened a ticket with ortur team and asked for a new motherboard.
Here are the results of the limit switch tests:
Case 1: No limit switch is actuated:
<Idle|MPos:3.000,3.000,0.000|Bf:35,7680|FS:0,0|Pn:PY|CL:0,100|PS:2,1|ER:1888,1893>
Case 2: Limit switch X is actuated, Y is unactuated:
<Idle|MPos:3.000,3.000,0.000|Bf:35,7680|FS:0,0|Pn:PXY|CL:0,100|PS:2,1|ER:1925,1932>
Case 3: Limit switches X and Y are actuated:
<Idle|MPos:3.000,3.000,0.000|Bf:35,7680|FS:0,0|Pn:PXY|CL:0,100|PS:2,1|ER:1944,1941>
I think here we can see, that the X-Limit switch is ok and the y-limit switch is bad. But if i test the signal on the plug to motherboard, the y limit switch works.
I opened the housing and took a look at the motherboard, but i canĀ“t see anything which is shorting the y-signal.
If i make a test with unplugged motherboard-plug, the y-signal is still there:
<Idle|MPos:3.000,3.000,0.000|Bf:35,7680|FS:0,0|Pn:PY|CL:0,100|PS:2,1|ER:0,360|VA:122,0|Ov:100,100,100|A:S>
Now iĀ“m waiting for my new motherboard and cables from ortur. The support there was really very good and very uncomplicated.
I will inform you when i do test with my new parts.
Thank you all!
Markus
Awesome. Thanks for the follow-up.
Can you further explain what you mean by this point? I understood earlier that signal at board was always showing actuated for Y? Is this something different?
On this test i had unplugged the big white plug from motherboard and had tested the signal at the pins from x and y limit switches with my multimeter when i pushed the limit switches with my fingers.
Hello again.
Today I changed the motherboard and now everything is working fine.
Iām really happy now 
1 Like