Skip to main content

Pascal Press initial impressions

My kick starter reward for the Pascal Press campaign, a travel mug that can brew it's own coffee.  Here are my initial observations after the 3rd cup.

  • The materials and construction seem to be good it's made of Polypropylene, stainless steel, and  silicone rubber.  Everything mostly fits together nicely.
  • The screen printing of the logo an max grounds fill line is already half worn off, and rubs off with just a finger wipe.  I've had to lightly etched the fill line in with a knife.
  • The silicone grip appears to be cylindrical, whereas the press body is slightly conical, so the fit is a bit loose towards the bottom of the grip.  A tighter and/or conical grip would fix that.
  • The screw top lid needs 2 hands to open and has no storage place when off.  some sort of keeper like whats on a standard nalgene bottle would be nice.
  • Heat retention is not good. it seems like it will stay hot for about an hour, this might be related to the next point.
  • The inner cup is held entirely in place entirely by the stiffness of the seals. Some sort of light detente to hold it in would be nice.  I've noticed it popping back up by about 2-3 mm.
  • Used grounds get stuck in the spokes of the filter holder, and that can make for messy cleanup.
  • A larger capacity used grounds cavity would be nice, as it stands the full cup I'm brewing seems a little weak, and the only option I have to change the ratio would be to use less water.
  • Produced coffee seems to be on par with the upside-down areopress method. again, maybe a little weak... I'll need to get some better beans.
  • The volume for the grounds doesn't seem to be stated anywhere. 
All in all I'm a bit iffy on whether or not I can make this work as a daily driver.  I might just be spoiled by the 20 oz Stainless mug I've been toting around for the past 3 years.  That being said, it may be just the thing for a backwoods backpacker brewer.  I'll keep at it for a week or so, then post again with some more details and observations.

Comments

Post a Comment

Popular posts from this blog

8Bitdo NES 30 Pro on linux

This post will go over the setup I had to do to get my   8Bitdo  NES30 Pro controller working on my Arch linux desktop with steam.  This results in the system loading the xboxdrv automatically when the controller is connected, and unloading once finished. Firmware Update The first thing to tackle was the firmware update on the controller,  This may not be needed, but I like to keep my devices up to date. After some googling, I was able to find a program called fwupd  that's able to update the controller via a USB connection.  It's available for Arch in the community repo. The basic syntax of the command is: fwupdmgr get-devices fwupdmgr refresh fwupdmgr get-updatessudo fwupdmgr update The controller will need to be put into 'Firmware update mode'.  Be aware that the final command will also update all eligible firmware on your system, so If you don't want that, please dig into the documentation Bluetooth Connection G...

Craftware 1.17 on Arch Linux -- notes

Craftware a slicer for 3d printers is available for linux here .  It looks pretty good, and is supposedly multi threaded with support for hardware acceleration. I can only find it  as a deb file, and there's nothing in the AUR for it. I tried a few of the common methods for installing debs: debtap While it was able to create a package, upon installing it I got this error loading packages... error: failed to prepare transaction (package architecture is not valid) :: package craftware-1.17.1-1-i686 does not have a valid architecture So.. No good. I tried just extracting the package content, and running the binary: ./craftware: error while loading shared libraries: libomp.so: cannot open shared object file: No such file or directory and yes, it is installed. $ ldconfig -v           libomptarget.so -> libomptarget.so          libomp.so -> libomp.so          libzit...

The Saga of EA Customer support part 5

Jan 5, 2017  (14 Days after the initial contact) At 2:24 AM I was sent the following in reply to my 3rd ticket where I stated that I was going to become a nuisance. Thank you for contacting Electronic Arts Customer Experience. I sincerely apologize for the delay caused in responding to your issue and appreciate your patience. This is ***** from the Game team following up your incident.  I would like to inform you that your case was escalated to the dedicated team. In this case I suggest you to wait for email from the specialist team.  Should you have any further questions regarding this or any other issues, please do not hesitate to let us know. You can also find answers to common questions on our Help Center at http://help.ea.com , or ask our community experts by visiting Answer HQ at http://answers.ea.co This reply also closed the ticket. At 5:26 PM I replied with the following: Hi, Thank you for taking the time to update me on this issue. However:...