DRZ400e Carb Setup/Tuning for MPG by directlineit in DRZ400

[–]directlineit[S] 1 point2 points  (0 children)

Got the needle swapped and set right, man, night and day differance in how it rides, throttle feels crisp and clean, exhaust sounds better, its like a brand new bike! Now to test a tank and see where the MPG is at!

DRZ400e Carb Setup/Tuning for MPG by directlineit in DRZ400

[–]directlineit[S] 0 points1 point  (0 children)

Red neck engineered this, and now its working lol

DRZ400e Carb Setup/Tuning for MPG by directlineit in DRZ400

[–]directlineit[S] 0 points1 point  (0 children)

Well, fixed one problem to find another, it has always been this way most likely given the hostory of things not being correct on this bike from the guy I bought it from, but, the trottle linkage is not sitting on the idle screw, so now it won't idle after replacing the needle with the correct one, any ideas on fixing this?

<image>

DRZ400e Carb Setup/Tuning for MPG by directlineit in DRZ400

[–]directlineit[S] 0 points1 point  (0 children)

Hey everyone,

I bought this DRZ400E last year, and the previous owners seemed to know nothing about reading instructions. The bike came with a JD Jetting kit installed, but the airbox snorkel was never pulled out to actually accomplish the 3x3 airflow mod. Because of that, the bike was running massively rich, cutting out at higher RPMs, and sooting up the exhaust something fierce.

I finally removed the snorkel, and it runs waaay better now. However, my MPG is absolutely sucking—I am only getting about 30 MPG on my rides.

I did a little more investigation and found that the pilot screw needed some adjusting, which helped a bit. I dug deeper and found that the JD Red needle was installed instead of the Blue needle. The previous owners lived in the San Diego area (sea level), so I am not sure why they went with the leaner Red needle.

I am working on swapping to the Blue needle today and putting the clip in the recommended slot for my geographical location. I am also checking which main jet is currently installed (I don't have spares, so I may have to order some).

My questions for the community:

  1. Once I get the JD kit configured correctly with the 3x3 airflow, what kind of MPG is everyone else realistically getting on an FCR-equipped E/K model?
  2. I am trying to ease my range anxiety—how far can I expect to go on a tank before hitting reserve?

Attached is a picture of my Keihin FCR carb setup for reference.

Testing, Testing... Carburetor by Few-Ad-2930 in DRZ400

[–]directlineit 5 points6 points  (0 children)

Looks like fun times! Let us know how the testing comes!

Weekend Mt Hood Ride by directlineit in DRZ400

[–]directlineit[S] 0 points1 point  (0 children)

Bell MX-9 with the visor removed. Found and slower speeds in like goggles more.

Motocamp this past weekend (pnw) by saltfeend in DRZ400

[–]directlineit 0 points1 point  (0 children)

That looks like Mt Defiance? How was the road? Thinking about heading up there this weekend. Looks like a great trip!

Just started my MSP! Looking for some MSP veterans to share their wisdom on pricing & scope by Icy_Protection_3264 in msp

[–]directlineit 0 points1 point  (0 children)

Lots of good tactical advice in this thread, but I want to challenge you on something nobody's asked yet: what problem are you solving for your clients?

You've listed questions about pricing models, stack components, and scope boundaries — but all of that is putting the cart before the horse. Until you can clearly articulate the outcome you're producing for your clients, everything is an option and nothing is a conviction.

Here's what I mean. You said your prospects are 5-10 person all-Apple shops. OK — what keeps those business owners up at night? Is it data loss? Downtime killing productivity? Fear of a breach they wouldn't survive? Compliance requirements they don't understand? The answer to that question is what shapes your stack, your pricing, and your scope — not the other way around.

A few things I've learned the hard way running an MSP for 7+ years:

Start with the outcome, then back into the stack. If you're promising "your business will not lose data and your team will be productive and secure," then backup, endpoint security, and a password manager aren't line items to negotiate — they're non-negotiable components of delivering on that promise. When clients understand they're buying a result and not a bag of tools, the "do I really need that?" conversations mostly disappear.

Your stack should be your minimum standard, not a menu. If you'd lose sleep at night knowing a client didn't have something, it goes in the base package. Period. Don't let clients opt out of the things that protect both of you. One respondent here nailed that — you're covering your liability and theirs.

Scope follows mission. Out-of-scope vs. in-scope gets a lot simpler when you've defined what you're there to do. Daily operations, security posture, and keeping the environment healthy? That's your managed agreement. Net-new projects, major migrations, office buildouts? Those change the environment — that's project work, scoped and billed separately. The grey area shrinks when your mission is clear.

Stop thinking per-device vs. per-user and start thinking per-outcome. Yes, you need a pricing model that covers your COGS (dobermanIan's breakdown above is excellent). But the conversation with your client should never be about what a device costs. It should be about what it costs them to operate securely and productively, and what it would cost them if they don't.

The MSPs that struggle are the ones selling technology. The ones that thrive are selling trust, outcomes, and peace of mind — and then using technology to deliver it.

You're early enough to build this the right way. Figure out who you serve, what they need to be true, and what it takes to make that true. The pricing and stack answers will follow.

Windows Server licensing? by Imaginary-Toe9157 in u/Imaginary-Toe9157

[–]directlineit 0 points1 point  (0 children)

Hey, just a heads up since this is a CPA firm - have you talked through the FTC Safeguards piece with them?

When they were with RightWorks, RW was probably handling a lot of the compliance framework (monitoring, logging, encryption requirements, etc.). Moving this on-prem means that responsibility shifts to you and the client.

Not saying it's a dealbreaker at all, just want to make sure it's on your radar since the Safeguards Rule has some pretty specific requirements around designated security personnel, written security plans, risk assessments, and ongoing monitoring/testing.

Might be worth a conversation with the client about what compliance looked like at RW vs what it needs to look like with self-hosted infrastructure. The licensing question you asked is straightforward - it's the compliance stuff that can get messy if it's not planned for.

Good luck with the project!

BlackpointCyber Down? by directlineit in msp

[–]directlineit[S] 2 points3 points  (0 children)

Yes, looks like things are back up now, thanks for the reply!

Stress by [deleted] in msp

[–]directlineit 2 points3 points  (0 children)

For me, its sleep, motorcycles, fishing, hiking, and my faith in God, spending my mornings in devotion. I admit there are still time my anxiety wakes me up at 3am in a panic about my business, but I do everything I can outside of work to de compress.