New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Signs of recent fire on Gerald, but no one had reported it. #1157
Comments
"one belt one more time" I say let's buy more now :-)
… On 20 Jun 2019, at 15:47, Mike Gorman ***@***.***> wrote:
I was in DoES on Thursday when one of the people who had booked Gerald for the morning was having some issues.
It turned out that there had been a fire in Gerald which had damaged the X-axis belt.
Luckily we had some spare belt, so I could replace the damaged one, but the key issue was that it was not reported, so it was just a matter of time before the belt broke, putting Gerald out of action. The machine also had to be cleaned as there was a lot of debris, dust and melted acrylic on the bed (though some had been cleaned away) as a consequence of the fire.
If @DoESsean <https://github.com/DoESsean> can possibly send an email to people who have booked the laser in the last week, we can then ask people to report the issue should it happen in the future. This is not to point fingers, as fires are a common risk with laser cutters, just to report when it does happen again, so that we can keep Gerald working as best as possible.
We also still have sufficient belt in stock to replace any one belt one more time.
@DoESLiverpool/laser-maintenance <https://github.com/orgs/DoESLiverpool/teams/laser-maintenance>
I will leave this issue open for a short while, as the new belt will need to be re-tensioned in a few days.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub <#1157?email_source=notifications&email_token=AAAGU2Z4HW25YJFJGA4HXZDP3OKBLA5CNFSM4HZUGZ42YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4G2XIFYQ>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAAGU24AXPXRIBCP4ICNEN3P3OKBLANCNFSM4HZUGZ4Q>.
|
I brought up this issue in the community meeting on Thursday evening. We have now agreed that cleaning the laser bed after use should be part of the laser induction and that was brought into effect later the same evening. We also need to add some signage to advise people to please clean the laser bed after use. |
Is the laser bed the grating that the work piece rests upon or the area
underneath that grating?
…On Fri, 21 Jun 2019, 12:39 Mike Gorman, ***@***.***> wrote:
I brought up this issue in the community meeting on Thursday evening.
We have now agreed that cleaning the laser bed after use should be part of
the laser induction and that was brought into effect later the same evening.
We also need to add some signage to advise people to please clean the
laser bed after use.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#1157?email_source=notifications&email_token=ABCNHKISE2UKIA5MGEYPF43P3S4XDA5CNFSM4HZUGZ42YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYIHMPQ#issuecomment-504395326>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABCNHKJASP5MYM3GBXOIEDLP3S4XDANCNFSM4HZUGZ4Q>
.
|
The 'how' of getting to the bed wasn't covered in the induction I did about a month ago but it's in the Wiki. I suspect folk may be overly worried about disturbing calibrations or causing damage and that triggers the 'don't bother, someone else's problem' subroutine. If a more experienced laser user wants to demonstrate the process, I'll happily video it (quick & dirty phone filming :) ), fling it on YouTube and it can be linked from the Wiki? |
Hi Dunc
That's a good idea. Are you around on Makernight? That could be a good time.
Jackie
On 25 Jun 2019 07:49, Dunc Reid <notifications@github.com> wrote:
The 'how' of getting to the bed wasn't covered in the induction I did about a month ago but it's in the Wiki. I suspect folk may be overly worried about disturbing calibrations or causing damage and that triggers the 'don't bother, someone else's problem' subroutine.
If a more experienced laser user wants to demonstrate the process, I'll happily video it (quick & dirty phone filming :) ), fling it on YouTube and it can be linked from the Wiki?
—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub<#1157?email_source=notifications&email_token=ADBVRUFAHQ7WB3WRCRNWQMLP4G5W7A5CNFSM4HZUGZ42YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYPG4TA#issuecomment-505310796>, or mute the thread<https://github.com/notifications/unsubscribe-auth/ADBVRUF7CA46QFH4DAAV2CDP4G5W7ANCNFSM4HZUGZ4Q>.
|
Sadly not.
In today (if I can get parked.. grrr!!) and tomorrow am.
On 25 Jun 2019, at 08:37, Jackie Pease <notifications@github.com<mailto:notifications@github.com>> wrote:
Hi Dunc
That's a good idea. Are you around on Makernight? That could be a good time.
Jackie
On 25 Jun 2019 07:49, Dunc Reid <notifications@github.com<mailto:notifications@github.com>> wrote:
The 'how' of getting to the bed wasn't covered in the induction I did about a month ago but it's in the Wiki. I suspect folk may be overly worried about disturbing calibrations or causing damage and that triggers the 'don't bother, someone else's problem' subroutine.
If a more experienced laser user wants to demonstrate the process, I'll happily video it (quick & dirty phone filming :) ), fling it on YouTube and it can be linked from the Wiki?
—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub<#1157?email_source=notifications&email_token=ADBVRUFAHQ7WB3WRCRNWQMLP4G5W7A5CNFSM4HZUGZ42YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYPG4TA#issuecomment-505310796>, or mute the thread<https://github.com/notifications/unsubscribe-auth/ADBVRUF7CA46QFH4DAAV2CDP4G5W7ANCNFSM4HZUGZ4Q>.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<#1157?email_source=notifications&email_token=AMOGG2OYRLGZE3TLSGPGC43P4HDLTA5CNFSM4HZUGZ42YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYPKQIA#issuecomment-505325600>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AMOGG2KIQTXJPP775HWM6WLP4HDLTANCNFSM4HZUGZ4Q>.
|
Hope you got parked.
Probably best to just ask around then - I'm sure there'll be someone there today who can show you how to clear out Gerald.
From: Dunc Reid
Sent: Tuesday 25 June, 09:46
Subject: Re: [DoESLiverpool/somebody-should] Signs of recent fire on Gerald, but no one had reported it. (#1157)
To: DoESLiverpool/somebody-should
Cc: Jackie Pease, Team mention
Sadly not.
In today (if I can get parked.. grrr!!) and tomorrow am.
On 25 Jun 2019, at 08:37, Jackie Pease <notifications@github.com<mailto:notifications@github.com>> wrote:
Hi Dunc
That's a good idea. Are you around on Makernight? That could be a good time.
Jackie
On 25 Jun 2019 07:49, Dunc Reid <notifications@github.com<mailto:notifications@github.com>> wrote:
The 'how' of getting to the bed wasn't covered in the induction I did about a month ago but it's in the Wiki. I suspect folk may be overly worried about disturbing calibrations or causing damage and that triggers the 'don't bother, someone else's problem' subroutine.
If a more experienced laser user wants to demonstrate the process, I'll happily video it (quick & dirty phone filming :) ), fling it on YouTube and it can be linked from the Wiki?
—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub<#1157?email_source=notifications&email_token=ADBVRUFAHQ7WB3WRCRNWQMLP4G5W7A5CNFSM4HZUGZ42YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYPG4TA#issuecomment-505310796>, or mute the thread<https://github.com/notifications/unsubscribe-auth/ADBVRUF7CA46QFH4DAAV2CDP4G5W7ANCNFSM4HZUGZ4Q>.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<#1157?email_source=notifications&email_token=AMOGG2OYRLGZE3TLSGPGC43P4HDLTA5CNFSM4HZUGZ42YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYPKQIA#issuecomment-505325600>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AMOGG2KIQTXJPP775HWM6WLP4HDLTANCNFSM4HZUGZ4Q>.
—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub<#1157?email_source=notifications&email_token=ADBVRUB6BYEMPR6MKSTHV4DP4HLNNA5CNFSM4HZUGZ42YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYPQLMY#issuecomment-505349555>, or mute the thread<https://github.com/notifications/unsubscribe-auth/ADBVRUDAWZJ3NZ2W2FCWEK3P4HLNNANCNFSM4HZUGZ4Q>.
|
Closing this issue for now - as we don’t really need to keep this open. |
I was in DoES on Thursday when one of the people who had booked Gerald for the morning was having some issues.
It turned out that there had been a fire in Gerald which had damaged the X-axis belt.
Luckily we had some spare belt, so I could replace the damaged one, but the key issue was that it was not reported, so it was just a matter of time before the belt broke, putting Gerald out of action. The machine also had to be cleaned as there was a lot of debris, dust and melted acrylic on the bed (though some had been cleaned away) as a consequence of the fire.
If @DoESsean can possibly send an email to people who have booked the laser in the last week, we can then ask people to report the issue should it happen in the future. This is not to point fingers, as fires are a common risk with laser cutters, just to report when it does happen again, so that we can keep Gerald working as best as possible.
We also still have sufficient belt in stock to replace any one belt one more time.
@DoESLiverpool/laser-maintenance
I will leave this issue open for a short while, as the new belt will need to be re-tensioned in a few days.
The text was updated successfully, but these errors were encountered: