<sb0>
it turns out that the HK government has recently set up a fancy machine shop that local companies can use, so, this will go there soon
Ultrasauce has quit [Ping timeout: 264 seconds]
Ultrasauce has joined #m-labs
futarisIRCcloud has joined #m-labs
<whitequark>
sb0: I don't see any toolpath files and I don't think there would be any point in publishing them
<whitequark>
they are highly machine and shop specific
<whitequark>
IGES or STEP are the standard interchange formats for that
<mtrbot-ml_>
[mattermost] <sb10q> Yeah, thought so
<mtrbot-ml_>
[mattermost] <sb10q> IGS (not IGES) isn't a tool path format, right?
<mtrbot-ml_>
[mattermost] <sb10q> Because there are IGS files on that site
mauz555 has joined #m-labs
<sb0>
whitequark: ^
m4ssi has joined #m-labs
futarisIRCcloud has quit [Quit: Connection closed for inactivity]
ohsix has quit [Ping timeout: 246 seconds]
ohsix has joined #m-labs
<mtrbot-ml_>
[mattermost] <sb10q> @astro afaict manual fetchcargo isn't necessary for building STM32 firmware. buildRustPackage does it itself.
<mtrbot-ml_>
[mattermost] <sb10q> we use fetchcargo explicitly for building the ARTIQ firmware because the compilation is managed by the python script, which isn't compatible with buildRustPackage
<mtrbot-ml_>
[mattermost] <sb10q> hm, well, there's some issue with it, but I still don't see why manual fetchcargo is the right solution
sb0 has quit [Quit: Leaving]
proteusguy has quit [Ping timeout: 258 seconds]
proteusguy has joined #m-labs
<whitequark>
sb: those are not IGS files, they are IGES.
<whitequark>
IGS is just a file extension.
<mtrbot-ml_>
[mattermost] <astro> @sb10q it is possible that I added that for unstable dependencies
tpw_rules has quit [Ping timeout: 258 seconds]
forrestv has quit [Ping timeout: 258 seconds]
rqou has quit [Ping timeout: 252 seconds]
tpw_rules has joined #m-labs
gruetze_ has joined #m-labs
Ultrasauce has quit [Quit: No Ping reply in 180 seconds.]
gruetzkopf has quit [Ping timeout: 252 seconds]
Gurty has quit [Ping timeout: 252 seconds]
Gurty has joined #m-labs
Gurty has quit [Changing host]
Gurty has joined #m-labs
Ultrasauce has joined #m-labs
rqou has joined #m-labs
forrestv has joined #m-labs
m4ssi has quit [Ping timeout: 259 seconds]
kuldeep has quit [Quit: Its never too late!]
m4ssi has joined #m-labs
kuldeep has joined #m-labs
m4ssi has quit [Ping timeout: 244 seconds]
m4ssi has joined #m-labs
Gurty has quit [Ping timeout: 252 seconds]
m4ssi has quit [Ping timeout: 272 seconds]
m4ssi has joined #m-labs
mauz555 has quit [Remote host closed the connection]
mauz555 has joined #m-labs
mauz555 has quit [Remote host closed the connection]
mauz555 has joined #m-labs
mauz555 has quit [Read error: Connection reset by peer]
mauz555 has joined #m-labs
mauz555 has quit [Remote host closed the connection]
mauz555 has joined #m-labs
Gurty has joined #m-labs
cedric has quit [Ping timeout: 258 seconds]
cedric has joined #m-labs
cedric has quit [Changing host]
cedric has joined #m-labs
<mtrbot-ml_>
[mattermost] <sb10q> whitequark: so there *are* tool path files available.
<whitequark>
sb: where?
<whitequark>
oh, sorry, I was not clear earlier, now that I reread
<whitequark>
STEP and IGES are solid model interchange format
<whitequark>
like STL or OBJ but more flexible
<whitequark>
you should be able to open those in freecad
m4ssi has quit [Quit: Leaving]
mauz555 has quit []
_whitelogger has joined #m-labs
m4ssi has joined #m-labs
futarisIRCcloud has joined #m-labs
m4ssi has quit [Remote host closed the connection]
m4ssi has joined #m-labs
m4ssi has quit [Remote host closed the connection]
m4ssi has joined #m-labs
m4ssi has quit [Remote host closed the connection]
m4ssi has joined #m-labs
m4ssi has quit [Remote host closed the connection]
m4ssi has joined #m-labs
m4ssi has quit [Remote host closed the connection]