Jump to content
Ultimaker Community of 3D Printing Experts


  • Content Count

  • Joined

  • Last visited

Community Reputation

3 Neutral

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Alright, it's been a while. Thinking about it, i understand that we are not being offered this option as it would put some liability on UM and potentially cause issues with machine safety guidlines. At least that is my interpretation of the silence. I have taken it upon myself to patch the "safe cooldown" value from 60 to 100. If you want to do that, knowing that it's in the Qt UI (Okuda) not in the printer controller (griffin) might safe you some time (certainly took me longer than it should have digging through griffin to figure out that it's not there.) D
  2. Applying the hotfix has solved the issue. Thanks everyone.
  3. I just had time for a quick check, in my case the issue is that dropbear can not start because no host keys are present. I'll try your hotfix tomorrow.
  4. Allwinner A20 is a common ARM SoC. The board mentioned in that post has USB and HDMI, so I don't know why they are using a TTL / RS232 adapter but either way getting a console on such devices is trivial unless the device has been intentionally locked down, as is not the case here. Once on the console, it should be quick to find the cause why ssh is not running or filtered. Should be a one time thing.
  5. Glad to hear you take this so seriously, I am sure i will post more a detailed follow-up come the new year. As noted it's mostly about the forced bed cooldown cycle where the fw forces one to wait for the bed to go below 60°C before it starts the next print cycle (for safety reasons?) which i have taken physical measures to speed up, using the fan from a nearby soldering station, which is a little ludicrous. It would be good if there was a user friendly manual override or a configurable cooldown end temperature. When I have safely and cleanly removed a print I would want to st
  6. Yea, it does show the address. According to nmap -A -p 1-65535 only ports 80 and 8080 are open. I will try the connect reset after the current print job is done.
  7. Hello, as much as i enjoy working with your quite robust machine - two mysterious nozzle clogs aside -, as i am sure you are aware there are always issues that require manual fiddling with FDM printers. Especially with the SSH bug i am experiencing making it impossible to direct control via G-Code, the quite ridig workflow with the machine's menu is testing my patience more often than not. Please please please allow us to: - First and foremost: Make the "Skip cooldown" option actually skip the bed cooldown cycle! If I have removed a failed print from a
  8. No mysterious change, problem persists. As far as i know the UM uses a Raspberry Pi oder similiar quite open SBC. I will find the time to get a console in January and keep this thread updated with my findings. Meanwhile i would encourage you to do the same, if you don't want to wait. It should be easy enough.
  9. Hey, I was wondering if there are any known issues or any other users are experiencing this issue. First observed with putty on LAN (no filters) and then verified with a direct crossover connection from a linux laptop running dnsmasq. Port 22 is closed (connection refused.) Dev mode is activated, verified on S3 Display, numerous restarts. Tried re-enabling etc. etc. Now I don't want to say that I might not still be overlooking something silly but it seems exceedingly unlikely. Anyone got something? Thanks, sono
  • Create New...