#flex-dev Logs
Nov 03 2025
#flex-dev Calendar
04:04 AM Tom_L: morning
04:04 AM JT-Chicken: morning
04:05 AM Tom_L: i pushed some metric probe stuff
04:10 AM Tom_L: i need to figure out a metric config to test the ops though
05:17 AM JT-Chicken: got that pulled
05:19 AM JT-Chicken: all you gotta do is change linear units to mm
05:46 AM lcnc-relay: <allaboutjake@> Tom_L: Honestly I don’t know how it should work, just that I didn’t expect a 2.5” move toward the bed after the probe. This is the first time I have a probe to play with so I don’t have a good understanding of typical workflows
05:56 AM JT-Cave: how probing should work depends on what you want
05:56 AM JT-Cave: want/need
06:04 AM lcnc-relay: <allaboutjake@> Yeah. Get that. I think setting #2036 to zero or a slight positive number is probably a more sensible default but as I said I’m new to this
06:05 AM lcnc-relay: <allaboutjake@> I have to check to see if it’s a relative or absolute move to #2046 actually. I’m assuming it’s relative
06:44 AM JT-Cave: never assume...
06:53 AM Tom_L: JT-Cave, to test mm all the velocities etc will be ok?
06:55 AM Tom_L: allaboutjake, this is my first stab at it too so i'm open to suggestions
06:57 AM JT-Cave: the velocities will be in mm/minute so no
06:58 AM JT-Cave: or yes but quite slow
06:59 AM Tom_L: i suppose if it moves i can at least test the routines
06:59 AM JT-Cave: yup
06:59 AM Tom_L: i suspect they're ok but 'ass u me' nothing
07:00 AM JT-Cave: yup
07:00 AM JT-Cave: just multiply the velocities by 25.4
07:00 AM Tom_L: instead of combining inch with metric in the same folder i put some entries in the ini to change to subroutines_metric
07:01 AM Tom_L: i'll copy a config over and see what i get
07:02 AM Tom_L: there were 2 i had to switch direction on on one move
07:16 AM Tom_L: if you're done for this morning i'll build
07:21 AM JT-Cave: wait till later or tomorrow
07:21 AM JT-Cave: working on hal led buttons
07:22 AM Tom_L: ok
07:23 AM JT-Cave: almost got it working except for the led part... at least the hal is working now
07:23 AM * JT-Cave starts his chicken day
07:49 AM Tom_L: JT-Cave, would i divide my joint scale or multiply it?
07:50 AM * Tom_L thinks divide
07:50 AM * Tom_L also thinks he opened a can-o-worms
07:58 AM Tom_L: then there's the per joint PID
08:30 AM JT-Cave: got hal led buttons working now to clean up the mess
08:32 AM Tom_L: nice
08:34 AM Tom_L: 200 cpr, 5mm screw, 10microstep
08:34 AM Tom_L: is metric count per mm?
08:35 AM JT-Shop: yup
08:35 AM Tom_L: would that put scale around 400?
08:36 AM rdtsc-w: 200 * 10 = 2k for one revolution
08:36 AM Tom_L: don't try doing 2 things at once...
08:36 AM JT-Shop: that's what I get
08:36 AM Tom_L: trying to catch up on paperwerk too :)
08:37 AM Tom_L: ok so 2k
08:37 AM Tom_L: then z is reduced by 3 with a pulley
08:37 AM Tom_L: so 6k on it?
08:38 AM Tom_L: wait... one rev is 5mm though
08:38 AM Tom_L: so it's closer to 400?
08:39 AM rdtsc-w: that sounds like a fairly coarse thread; I got imperial screws so am unsure
08:40 AM Tom_L: 5mm pitch screw
08:41 AM rdtsc-w: my scale is 10,000 with 10x microstepping and 200cpr, direct
08:41 AM Tom_L: 10160 for inch here
08:42 AM Tom_L: sounds about right
08:42 AM rdtsc-w: screw is 5 somethings - 200 * 10 * 5 = 10k
08:42 AM Tom_L: 5.08
08:43 AM Tom_L: gotta run
08:43 AM rdtsc-w: have fun
09:03 AM JT-Shop: geeze having fun trying to get a person directions to my house
09:29 AM rdtsc-w: an out-of-town-er?
10:38 AM lcnc-relay: <roguish> good morning.
10:44 AM JT-Shop: yup
10:47 AM rdtsc-w: Wonder if Waze will accept GPS coordinates :)
10:47 AM rdtsc-w: morning roguish
10:48 AM rdtsc-w: "Yes, Waze does accept GPS coordinates, but you need to enter them in the correct format, which is longitude first, followed by latitude, separated by a semicolon (e.g., 101.679442;3.071063). Make sure to check the syntax to ensure accurate navigation."
10:52 AM JT-Cave: the problem is the road I live off of connects to the hwy in two places so if you enter from the north end the directions are reversed
10:57 AM rdtsc-w: if it were me, I'd try "use Waze, type in LONG;LAT" - most ppl have Waze and that'll get 'em there even if they go the wrong way (provided your street is on the map.)
11:12 AM lcnc-relay: <roguish> frack..... been on the phone for over an hour..... several calls.
11:13 AM lcnc-relay: <roguish> talked to my congressman's office...
11:23 AM JT-Shop: most people out here have no clue what a waze is
11:23 AM JT-Shop: I don't even know anyone that uses waze
11:25 AM rdtsc-w: grew up with road atlases; haven't touched one in many years, all do-able from phone now
11:29 AM JT-Shop: if you know how...
11:29 AM * JT-Shop flew from New Orleans to Winter Haven Fl using Texaco road maps
11:29 AM JT-Shop: but that was a long time ago
11:31 AM rdtsc-w: Drove from Ohio to Texas and back using Waze, piece of cake
11:31 AM rdtsc-w: arduous drive however
11:33 AM JT-Shop: Texas is a big state
11:33 AM rdtsc-w: lots of locked gates for acres and acres of land
11:33 AM JT-Shop: I was surprised at the speed limits for rural 2 lane roads in east tx
11:34 AM rdtsc-w: what was it, 50? 55?
11:34 AM rdtsc-w: forget
11:41 AM JT-Shop: 75
12:05 PM rdtsc-w: do seem to recall wondering how one was supposed to get on and off at those speeds :)
12:55 PM Tom_L: just go to swampeast Mo and follow the deadend road down the other deadend road and you can't miss it
12:58 PM Tom_L: and i thought Texas posted speed limit were the minimum
12:59 PM Tom_L: at least until you get to Houston, then you'd better have good brakes