Forum Replies Created
-
AuthorPosts
-
Bill
MemberHi,
Thanks for your reply.
Regarding your remark:
“The X position of the machine just prior to the homing switch operation (pressed) will be a value that is relative to some arbitrary point where the machine was last homed or tinyG was reset, which says to me that would not be a useful value to you.”
In fact, This is very useful to us. Please let me to explain.
I understand that when a G28.2 command completes, the X axis will be at 0 and the switch location will be -$xzb. But because the TinyG runs in open loop, it doesn’t know for sure if the XY table move to the required position accurately or not, as the actual table movement will be affected by motor, pulley and belt, etc. Thus the switch may not be at -$xzb as what TinyG thinks to be. So to have an idea if the XY table maintains the sound accuracy, we are hoping to read the homing switch position at each homing event, either at the time of the switch being pressed or released. Because once we establish an accurate homing switch position, we can use is as a reference for each homing in a volume production condition. If the variation of the homing switch position against the reference is outside a predefined threshold, it will be an indication of some system errors that have caused this variation, such as a loose pulley, etc.
Is there any command that we could use to find the position (coordinates) of the switch at each homing event? As listed in my previous email, the TinyG does seem to feedback the switch positions, both pressed and released, which shows that the TinyG knows exactly those events. It will be great if you could tell me how to retrieve the homing switch coordinates at each homing event reported by TinyG.MemberThanks for your answer!
Yes, we use G28.2 command to initiate homing.
What we want to know is the coordinates for each axis at the exact instant when the homing switch is just being pressed. It appears that, the TinyG sends the coordinates for each axis periodically AND at the instant when the homing switch is being pressed and released. However, we are not sure how to tell which coordinates correspond to the instant at the time of the homing switch being pressed. If you could provide me the instruction to retrieve the coordinates at the instant of homing, we can then retrieve the correct coordinates to perform a check for the homing action.
It appears that TinyG sent back string “qr:31” right after it sent out the coordinate at the instant when the homing switch is pressed, and sent “qr:31” again right after the switch is released. Please confirm if this is the case, and if I could use this info to determine the coordinates for homing, either at the instant when the switch is being pressed or released.
Please also advise what “qr:32” means.
The following texts are an example of the texts that TinyG sent back during homing:
———————————————–
posx:-7.441
posx:-10.639,vel:799.96
posx:-11.497,vel:0.04
qr:31
posx:-11.268,feed:60.00,vel:60.00
posx:-11.028
posx:-10.784
posx:-10.539
posx:-10.294
posx:-10.054
posx:-10.000,vel:0.13
qr:31
posx:-7.618,feed:800.00,vel:800.00
posx:-4.370
posx:-1.122
posx:-120.000,vel:0.00
qr:32
tinyg [mm] ok>
posx:0.000,feed:0.00,vel:0.43,coor:1,dist:0,stat:5
qr:31
tinyg [mm] ok>
—————————————————————-MemberHow can I get the position of the homing switch pressed from the TinyG feedback?
Memberthe command $ej=0 need send to TinyG every time when TinyG powered on or only once?
MemberI am using Labview to design operating interface, I found TinyG sometimes return text report, sometimes return JSON report. I want to fix it in text mode, so it is convenient for me to programe.
Thanks for your answer!!
MemberHow to set TinyG always report text mode? Any commands?
MemberThanks a lot!!
MemberThanks, I have changed the motor, it looks like better, I will keep trying.
MemberThanks, I will try!
MemberThanks for your answer! I am going to use Labview to do this(lots of our factory tools are developed by this language). Thanks again!
MemberI see, thank you very much!
Member[fb] firmware build 440.14
[fv] firmware version 0.97
[hp] hardware platform 1.00
[hv] hardware version 8.00Thanks!!
MemberFW is 0.97;
it is NC
[st] switch type 1 [0=NO,1=NC]Thanks for your answer!
Memberwe adjusted the following parameters, still sometimes work, sometimes not work:
[aam] a axis mode 1 [standard]
[avm] a velocity maximum 24000 deg/min
[afr] a feedrate maximum 24000 deg/min
[atn] a travel minimum 0.000 deg
[atm] a travel maximum 100.000 deg
[ajm] a jerk maximum 1200 deg/min^3 * 1 million
[ajh] a jerk homing 1440 deg/min^3 * 1 million
[ajd] a junction deviation 0.0500 deg (larger is faster)
[ara] a radius value 0.1989 deg
[asn] a switch min 3 [0=off,1=homing,2=limit,3=limit+homing]
[asx] a switch max 2 [0=off,1=homing,2=limit,3=limit+homing]
[asv] a search velocity 1080 deg/min
[alv] a latch velocity 216 deg/min
[alb] a latch backoff 3.600 deg
[azb] a zero backoff 3.600 degcan any give me a suggestion?
Thanks!!
Bill
September 28, 2015 at 8:10 pm in reply to: Motion suspend or stop when the switch is on & TinyG communication programming #8790MemberWhy don’t you just use Serial Port JSON Server (SPJS), which is what ChiliPeppr uses, and then bind in direct to SPJS over a websocket from your favorite language like Java, Python, etc.
A: for one reason, this tool is for worker in factory, the same operation need repeat lots of time a day. So we need only one window and one button for this project. Another reason, the other tools the factory are using are also developed by LabView, we prefer the same language.open COM7 115200 tinyg
when the door is open, send pause
“send COM7 !”
when the door is closed again, send resume
“send COM7 ~”
A: is this is TinyG commands or JSON server commands?Thanks for your answer!!
-
AuthorPosts
