Jump to content

jb011a9840

Dormant
  • Posts

    13
  • Joined

  • Last visited

Personal Information

  • Country
    GB
  • Industry
    Engineering

Recent Profile Visitors

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

jb011a9840's Achievements

3

Reputation

  1. Yes, if I start a print from the SD card then during the print I open the comm port to send a M27 command for example, the printer resets. I would like to open the comm port during a print to send commands without the printer resetting.
  2. Hi folks, I'm looking to disable the auto reset that happens when you open the serial port on my UM2+. On the other printers I've got it was a simple case of removing the capacitor on the DTR line of the FTDI chip and then I can send commands to the printer and read back the status while printing from an SD card. Is there a similar capacitor on the UM2+ that can be removed? Cheers Jamie
  3. I had the same problem, check out the link below
  4. Finally got the date and time to update correctly after a power cycle, used this tutorial on configuring the NPT client: http://frederic-wou.net/set-ntp-client-debian-8-x-jessie/
  5. The printer is on a wired connection with a reserved DHCP address, its been about 3hrs since it was last put through a power cycle and it still shown the 1970's. Does the printer use the network to pull the time and date from a NTP server?
  6. Something strange has now happened, the printer has been working fine with the updated time, however recently whenever the printer is powered down and back up the time resets to 01/01/1970? I've went through the process of resetting the time / date and it works until the machine is power cycled: https://www.garron.me/en/linux/set-time-date-timezone-ntp-linux-shell-gnome-command-line.html Is there a version of a "BIOS" battery in the UM3 that could be flat?
  7. Hi Folks, I've been thinking of adding an E-stop function to an app I put together to remotely monitor my UM3E. The "abort" option in the /print_job/stare seems like the best option, however when I try it in the Ultimaker 3 API screen I keep getting a "400: Bad Request" (see attached) The Id and Key being used are still valid Any help would be much appreciated Cheers Jamie
  8. Hi folks, This may seem like a stupid question, but how do you change the time on the UM3E? I've started pulling API data from the printer (http://xxx.xxx.xxx.xxx/api/v1/print_job) to monitor the status so I can plan when the next job can be put into the machine The "datetime_started" is 1 hour out against local time (Edinburgh) I'm not sure if it's not updated to British Summer Time (I use the word Summer loosely ) or it syncs with a time server in Europe. Any help would be great. Cheers Jamie
  9. Hi folks, I’ve been seeing some issues with my Ultimaker 3 ext when pausing a print. When pausing the print from the front control panel the print head parks at the front left with a crunching noise and when the print is resumed the X axis now appears to have an offset of about 5mm (see photo 1) The print was aborted and a new print started, this time everything looked OK but at some point, during the process the X axis decided to offset again be 5 mm (the printer was not paused during this print) (see photo 2) This time the printer was powered down and restarted, the 3rd attempt at printing the part was a success. The material being used is ABS with HIPS support, firmware 3.7.7.20170627 I have seen another random instance of this in the past (photo 3) Has anyone else experienced this issue?
  10. That is rather odd. WiFi was generally unstable in 3.4, as well for NFC. Which exact minor version of 3.4 did you save? Is Cura losing the printer WiFi connection or is the printer dropping of the network? (If you go to the printer to the network status menu, if it switches between connected and not connected, then it's the printer) 3.6 has NFC testing menus in the diagnostics. Do you want a copy of the 3.5 firmware as well to see how that behaves? That could help in diagnosing this problem. (We did test this firmware for 2 weeks on our testing fleet of 30 printers, with WiFi and NFC. I'm not saying your problem isn't real. Just want to figure out what is different in your setup then our testing setup, and why we didn't catch the problem you are having) I’m having similar issues, I bought the UM3 ext printer a couple of weeks ago. The initial setup completed correctly then connected and printed from Cura fine. I then upgraded the firmware to Stable 3.6.3.20170406, at this point Cura had problems connecting to the printer, it would initially connect then about 5 seconds later say the printer is disconnected and would not reconnect; this is the same for the Android Ultimaker 3 app on a tablet. Re-running the wifi setup, I was able to connect to the hotspot created to finish the setup but when opening the browser I was unable to see the page to complete the setup. At this point I also noticed the NFC was not working, when running the diagnostics the screen displays “NFC Hardware not found.” for both NFC tests. I installed the testing firmware 3.6.90.20170411 but the issues with the wifi and NFC still remain. When rolling back the firmware to 3.5.3.20161221 the wifi works correctly and doesn’t disconnect from Cura but the NFC is still not working. Any ideas??? Update: I’ve spent some time the evening playing around with the printer and identified the sample PVA reel that come with the printer as part of the issue! The following was carried out using Firmware Stable 3.6.3.20170406: With no reels fitted to the printer the NFC tests report “NFC hardware Detected” and “no tags detected” as you would expect. With the sample PLA Silver Metallic reel loaded the NFC tests report “NFC hardware Detected” and “ID: 0498147AF14A80, PLA Silver Metallic”. With the sample PLA Silver Metallic and sample PVA reel loaded the NFC tests report “NFC hardware not Detected” and “NFC hardware not Detected”. When the sample PVA reel is removed (PLA Silver Metallic still fitted) the NFC tests still report “NFC hardware not Detected” and “NFC hardware not Detected”. Switching the printed on and off clears the error and the NFC tests report “NFC hardware Detected” and “ID: 0498147AF14A80, PLA Silver Metallic”. I repeated this with the other 4 PLA reel I’ve got and the same issue occurred each time. The wifi connection to Cura is also stable without the sample PVA reel fitted. Does anyone know what the contact of the Sample PVA reel NFC should be? I’d like to read the content back to see if it has become corrupt.
  11. That is rather odd. WiFi was generally unstable in 3.4, as well for NFC. Which exact minor version of 3.4 did you save? Is Cura losing the printer WiFi connection or is the printer dropping of the network? (If you go to the printer to the network status menu, if it switches between connected and not connected, then it's the printer) 3.6 has NFC testing menus in the diagnostics. Do you want a copy of the 3.5 firmware as well to see how that behaves? That could help in diagnosing this problem. (We did test this firmware for 2 weeks on our testing fleet of 30 printers, with WiFi and NFC. I'm not saying your problem isn't real. Just want to figure out what is different in your setup then our testing setup, and why we didn't catch the problem you are having) I’m having similar issues, I bought the UM3 ext printer a couple of weeks ago. The initial setup completed correctly then connected and printed from Cura fine. I then upgraded the firmware to Stable 3.6.3.20170406, at this point Cura had problems connecting to the printer, it would initially connect then about 5 seconds later say the printer is disconnected and would not reconnect; this is the same for the Android Ultimaker 3 app on a tablet. Re-running the wifi setup, I was able to connect to the hotspot created to finish the setup but when opening the browser I was unable to see the page to complete the setup. At this point I also noticed the NFC was not working, when running the diagnostics the screen displays “NFC Hardware not found.” for both NFC tests. I installed the testing firmware 3.6.90.20170411 but the issues with the wifi and NFC still remain. When rolling back the firmware to 3.5.3.20161221 the wifi works correctly and doesn’t disconnect from Cura but the NFC is still not working. Any ideas???
×
×
  • Create New...