Search Results for 'notification'

[pelgrimParticipant]

sorry for the late answer, it really bugs me that I don’t get email notifications anymore.

I was talking ofcourse of “breaking a few laws by snuffing out their usb commands”
and use them for creating our own system.

All we really need are the complete set of usb commands and we can build our own software.

I really agree with the software remarks Ed has put in his article A horse talks

If CEL agrees or not, it’s a guess, there is simply not enough interaction between them and the forum to assume they saw what you are doing here.

java (EE), JavaFX, HTML, GIS) programmer, database wizard, framework inventor, looking for a job ! http://roboxing.com/wizards

[pelgrimParticipant]

Am I the only one without email notifications ?

java (EE), JavaFX, HTML, GIS) programmer, database wizard, framework inventor, looking for a job ! http://roboxing.com/wizards

since a few days all went quiet on the forum, or so it seemed.
Just noticed this morning things are buzy as usual, but I’m getting no more notifications from the forum.

Something has changed ?
Settings need to be changed somewhere ?

java (EE), JavaFX, HTML, GIS) programmer, database wizard, framework inventor, looking for a job ! http://roboxing.com/wizards

[pelgrimParticipant]

Don’t know about anyone else, but when I receive an email notification when a new message is posted, I check the new topics in the index on the right side to see what’s new,
not caring in which category a new topic is.
Of topic, but your problem seems to be solved anyway

java (EE), JavaFX, HTML, GIS) programmer, database wizard, framework inventor, looking for a job ! http://roboxing.com/wizards

[DavidParticipant]

Seems to be a HUGE number of errors in the AutoMaker.log file…

 

2014-11-08 10:13:18,085 [main] INFO libertysystems.stenographer.StenographerFactory.initLogger(StenographerFactory.java:161) - StenographerFactory initialised with logfile=/Users/dmuller/CEL Robox//AutoMaker.log loglevel=INFO logmode=LOCAL
2014-11-08 10:13:18,120 [main] INFO celtech.Lookup.<init>(Lookup.java:45) - Detected locale - en-US
2014-11-08 10:13:18,121 [main] INFO celtech.configuration.ApplicationConfiguration.getUserStorageDirectory(ApplicationConfiguration.java:593) - User storage directory = /Users/dmuller/CEL Robox/
2014-11-08 10:13:43,144 [JavaFX Application Thread] INFO libertysystems.stenographer.StenographerFactory.initLogger(StenographerFactory.java:161) - StenographerFactory initialised with logfile=/Users/dmuller/CEL Robox//AutoMaker.log loglevel=INFO logmode=LOCAL
2014-11-08 10:13:43,284 [JavaFX Application Thread] INFO celtech.Lookup.<init>(Lookup.java:45) - Detected locale - en-US
2014-11-08 10:13:43,305 [JavaFX Application Thread] INFO celtech.configuration.ApplicationConfiguration.getUserStorageDirectory(ApplicationConfiguration.java:593) - User storage directory = /Users/dmuller/CEL Robox/
2014-11-08 10:13:43,306 [JavaFX Application Thread] ERROR celtech.appManager.ProjectManager.loadState(ProjectManager.java:97) - Failed to load project manager
2014-11-08 10:13:47,804 [JavaFX Application Thread] INFO celtech.configuration.ApplicationConfiguration.getApplicationShortName(ApplicationConfiguration.java:467) - Application short name = AutoMaker
2014-11-08 10:13:47,805 [JavaFX Application Thread] INFO celtech.configuration.ApplicationConfiguration.getApplicationName(ApplicationConfiguration.java:436) - Application name = CEL AutoMaker
2014-11-08 10:13:48,515 [JavaFX Application Thread] ERROR libertysystems.stenographer.LoggingOutputStream.flush(LoggingOutputStream.java:188) - Exception in thread “JavaFX Application Thread”
2014-11-08 10:13:48,516 [JavaFX Application Thread] ERROR libertysystems.stenographer.LoggingOutputStream.flush(LoggingOutputStream.java:188) - java.lang.NullPointerException
2014-11-08 10:13:48,516 [JavaFX Application Thread] ERROR libertysystems.stenographer.LoggingOutputStream.flush(LoggingOutputStream.java:188) - at celtech.coreUI.DisplayManager.whenModelLoadSucceeded(DisplayManager.java:166)
2014-11-08 10:13:48,517 [JavaFX Application Thread] ERROR libertysystems.stenographer.LoggingOutputStream.flush(LoggingOutputStream.java:188) - at celtech.coreUI.DisplayManager.lambda$new$10(DisplayManager.java:149)
2014-11-08 10:13:48,517 [JavaFX Application Thread] ERROR libertysystems.stenographer.LoggingOutputStream.flush(LoggingOutputStream.java:188) - at celtech.coreUI.DisplayManager$$Lambda$1/962143767.handle(Unknown Source)
2014-11-08 10:13:48,517 [JavaFX Application Thread] ERROR libertysystems.stenographer.LoggingOutputStream.flush(LoggingOutputStream.java:188) - at com.sun.javafx.event.CompositeEventHandler.dispatchBubblingEvent(CompositeEventHandler.java:86)
2014-11-08 10:13:48,517 [JavaFX Application Thread] ERROR libertysystems.stenographer.LoggingOutputStream.flush(LoggingOutputStream.java:188) - at com.sun.javafx.event.EventHandlerManager.dispatchBubblingEvent(EventHandlerManager.java:238)
2014-11-08 10:13:48,517 [JavaFX Application Thread] ERROR libertysystems.stenographer.LoggingOutputStream.flush(LoggingOutputStream.java:188) - at com.sun.javafx.event.EventHandlerManager.dispatchBubblingEvent(EventHandlerManager.java:191)
2014-11-08 10:13:48,517 [JavaFX Application Thread] ERROR libertysystems.stenographer.LoggingOutputStream.flush(LoggingOutputStream.java:188) - at com.sun.javafx.event.BasicEventDispatcher.dispatchEvent(BasicEventDispatcher.java:58)
2014-11-08 10:13:48,517 [JavaFX Application Thread] ERROR libertysystems.stenographer.LoggingOutputStream.flush(LoggingOutputStream.java:188) - at com.sun.javafx.event.EventDispatchChainImpl.dispatchEvent(EventDispatchChainImpl.java:114)
2014-11-08 10:13:48,518 [JavaFX Application Thread] ERROR libertysystems.stenographer.LoggingOutputStream.flush(LoggingOutputStream.java:188) - at com.sun.javafx.event.EventUtil.fireEventImpl(EventUtil.java:74)
2014-11-08 10:13:48,519 [JavaFX Application Thread] ERROR libertysystems.stenographer.LoggingOutputStream.flush(LoggingOutputStream.java:188) - at com.sun.javafx.event.EventUtil.fireEvent(EventUtil.java:54)
2014-11-08 10:13:48,519 [JavaFX Application Thread] ERROR libertysystems.stenographer.LoggingOutputStream.flush(LoggingOutputStream.java:188) - at javafx.event.Event.fireEvent(Event.java:204)
2014-11-08 10:13:48,519 [JavaFX Application Thread] ERROR libertysystems.stenographer.LoggingOutputStream.flush(LoggingOutputStream.java:188) - at javafx.concurrent.EventHelper.fireEvent(EventHelper.java:219)
2014-11-08 10:13:48,520 [JavaFX Application Thread] ERROR libertysystems.stenographer.LoggingOutputStream.flush(LoggingOutputStream.java:188) - at javafx.concurrent.Service.fireEvent(Service.java:874)
2014-11-08 10:13:48,520 [JavaFX Application Thread] ERROR libertysystems.stenographer.LoggingOutputStream.flush(LoggingOutputStream.java:188) - at javafx.concurrent.Service$5.changed(Service.java:568)
2014-11-08 10:13:48,520 [JavaFX Application Thread] ERROR libertysystems.stenographer.LoggingOutputStream.flush(LoggingOutputStream.java:188) - at javafx.concurrent.Service$5.changed(Service.java:541)
2014-11-08 10:13:48,520 [JavaFX Application Thread] ERROR libertysystems.stenographer.LoggingOutputStream.flush(LoggingOutputStream.java:188) - at com.sun.javafx.binding.ExpressionHelper$SingleChange.fireValueChangedEvent(ExpressionHelper.java:176)
2014-11-08 10:13:48,520 [JavaFX Application Thread] ERROR libertysystems.stenographer.LoggingOutputStream.flush(LoggingOutputStream.java:188) - at com.sun.javafx.binding.ExpressionHelper.fireValueChangedEvent(ExpressionHelper.java:80)
2014-11-08 10:13:48,521 [JavaFX Application Thread] ERROR libertysystems.stenographer.LoggingOutputStream.flush(LoggingOutputStream.java:188) - at javafx.beans.property.ObjectPropertyBase.fireValueChangedEvent(ObjectPropertyBase.java:105)
2014-11-08 10:13:48,522 [JavaFX Application Thread] ERROR libertysystems.stenographer.LoggingOutputStream.flush(LoggingOutputStream.java:188) - at javafx.beans.property.ObjectPropertyBase.markInvalid(ObjectPropertyBase.java:112)
2014-11-08 10:13:48,522 [JavaFX Application Thread] ERROR libertysystems.stenographer.LoggingOutputStream.flush(LoggingOutputStream.java:188) - at javafx.beans.property.ObjectPropertyBase.access$000(ObjectPropertyBase.java:51)
2014-11-08 10:13:48,522 [JavaFX Application Thread] ERROR libertysystems.stenographer.LoggingOutputStream.flush(LoggingOutputStream.java:188) - at javafx.beans.property.ObjectPropertyBase$Listener.invalidated(ObjectPropertyBase.java:232)
2014-11-08 10:13:48,522 [JavaFX Application Thread] ERROR libertysystems.stenographer.LoggingOutputStream.flush(LoggingOutputStream.java:188) - at com.sun.javafx.binding.ExpressionHelper$SingleInvalidation.fireValueChangedEvent(ExpressionHelper.java:135)
2014-11-08 10:13:48,522 [JavaFX Application Thread] ERROR libertysystems.stenographer.LoggingOutputStream.flush(LoggingOutputStream.java:188) - at com.sun.javafx.binding.ExpressionHelper.fireValueChangedEvent(ExpressionHelper.java:80)
2014-11-08 10:13:48,523 [JavaFX Application Thread] ERROR libertysystems.stenographer.LoggingOutputStream.flush(LoggingOutputStream.java:188) - at javafx.beans.property.ObjectPropertyBase.fireValueChangedEvent(ObjectPropertyBase.java:105)
2014-11-08 10:13:48,524 [JavaFX Application Thread] ERROR libertysystems.stenographer.LoggingOutputStream.flush(LoggingOutputStream.java:188) - at javafx.beans.property.ObjectPropertyBase.markInvalid(ObjectPropertyBase.java:112)
2014-11-08 10:13:48,524 [JavaFX Application Thread] ERROR libertysystems.stenographer.LoggingOutputStream.flush(LoggingOutputStream.java:188) - at javafx.beans.property.ObjectPropertyBase.set(ObjectPropertyBase.java:145)
2014-11-08 10:13:48,524 [JavaFX Application Thread] ERROR libertysystems.stenographer.LoggingOutputStream.flush(LoggingOutputStream.java:188) - at javafx.concurrent.Task.setState(Task.java:693)
2014-11-08 10:13:48,524 [JavaFX Application Thread] ERROR libertysystems.stenographer.LoggingOutputStream.flush(LoggingOutputStream.java:188) - at javafx.concurrent.Task$TaskCallable$2.run(Task.java:1438)
2014-11-08 10:13:48,524 [JavaFX Application Thread] ERROR libertysystems.stenographer.LoggingOutputStream.flush(LoggingOutputStream.java:188) - at com.sun.javafx.application.PlatformImpl$6$1.run(PlatformImpl.java:301)
2014-11-08 10:13:48,527 [JavaFX Application Thread] ERROR libertysystems.stenographer.LoggingOutputStream.flush(LoggingOutputStream.java:188) - at com.sun.javafx.application.PlatformImpl$6$1.run(PlatformImpl.java:298)
2014-11-08 10:13:48,527 [JavaFX Application Thread] ERROR libertysystems.stenographer.LoggingOutputStream.flush(LoggingOutputStream.java:188) - at java.security.AccessController.doPrivileged(Native Method)
2014-11-08 10:13:48,527 [JavaFX Application Thread] ERROR libertysystems.stenographer.LoggingOutputStream.flush(LoggingOutputStream.java:188) - at com.sun.javafx.application.PlatformImpl$6.run(PlatformImpl.java:298)
2014-11-08 10:13:48,527 [JavaFX Application Thread] ERROR libertysystems.stenographer.LoggingOutputStream.flush(LoggingOutputStream.java:188) - at com.sun.glass.ui.InvokeLaterDispatcher$Future.run(InvokeLaterDispatcher.java:95)
2014-11-08 10:13:50,241 [JavaFX Application Thread] INFO celtech.appManager.Notifier.showInformationNotification(Notifier.java:40) - Info Notification: Application update : You are using the most up to date version of AutoMaker
2014-11-08 10:14:01,554 [JavaFX Application Thread] INFO celtech.coreUI.components.ProjectTab$2.handle(ProjectTab.java:219) - onDragEntered
2014-11-08 10:14:02,534 [JavaFX Application Thread] INFO celtech.coreUI.components.ProjectTab$4.handle(ProjectTab.java:276) - onDragDropped
2014-11-08 10:14:21,397 [JavaFX Application Thread] INFO celtech.configuration.ApplicationConfiguration.getApplicationStorageDirectory(ApplicationConfiguration.java:625) - Application storage directory = /Users/dmuller/CEL Robox/

[Ed_backer909Participant]

backorders of some filaments are on the way! I got a Shipment notification on two Reels of Black.

Chris said all the remaining colors are on the Boat to the UK and will be shipped out by next week once they arrive in port.

 

I still don’t see empty reels but I plan on stripping one reel of Black for some of my other makers Materials and make a new Profile for it etc.

 

Good Luck All!

 

E

[Ed_backer909Participant]

Well, we all bought into this “needle valve” design as a potential benefit. Many users seem to have no problems? Or do they just not post here? I heard some use ONE valve and ONE material. Never switching means less problems for them! This is what we paid for? My B-Axis Stuck error stops ALL Printing, purging or any head movement.

I’ve been very vocal on Support, KS and here so as to not let CEL make excuses and set expectations that we will just wait indefinitely, quietly and patiently for them to resolve their issues internally and our problems externally. We will not sit very casually and quietly so as not to get anyone upset or “flamed” in public. Waiting and waiting with no news, no plan and no support other than “were sorry”, “were understaffed”. “were waiting/working on that”… Do they want us to be good KS backers and wait while they do their own thing with our money and keep saying “Woo Backers thanks for your orders”! We’ll get back when we have a fix for you….later!

Yeah right.

This KS funding works BOTH ways. We have a vested interest in the success and problems with this Printer. B-Axis seems a MAJOR issue and case design problem? We did NOT buy a off the shelf product that was mature and solid. We did expect some return for our investments however. Perhaps a working printer with some ‘glitches”. We do need more News, updates, notifications and plans to address any widespread issues & problems with CEL Plans & Dates for fixes and re-engineering these is a must. The lack of parts and support staff is a big miss on CEL leadership. One guy leaving should not bring to halt any organization. One bowden tube or B-Axis issues should not bog down even a smally company.

I get reminded all the time that this is not a “finished” product as a KS backer. We should not expect a finished product, but then we see this Marketing? Here is the CEL Text of the ROBOX to their new buyers and us as KS Owners:

Construction Methodology
All of the motion axes are coupled to a single sheet metal part, reducing the need for factory calibration and ensuring that your Robox® is perfect for printing straight off the production line.

Want something that you can just plug and print? Well that’s just what we’ve done – install the AutoMaker™ software, connect the power and USB, load a reel and click print – it’s as easy as that. All printers have been assembled and thoroughly tested before leaving the production line, so it’s ready to use straight away.

Just don’t switch nozzles, materials or get to fancy. When it fails or breaks please wait until we get to it…don’t expect it’s perfect, or ready to use straight away!

I /we have been more then patient with a printer sitting in a box since September, disassembeled, sans covers waiting on you!

Jeez

Ed

Backer 909

• This reply was modified 1 month, 3 weeks ago by  Ed_backer909.
• This reply was modified 1 month, 3 weeks ago by  Ed_backer909.
• This reply was modified 1 month, 3 weeks ago by  Ed_backer909.

[Trekman42Participant]

Got the notification from DHL, mine was picked up today (along with the extra filaments I ordered).

Dear all,

I am new to 3D printing and today I got my shipping notification from CEL. Seems my Robox is on the way to me - great.

During the last months I was reading this community silently in the background.
Now that the Robox is on the way I decided to become a part of the Robox community.
In the beginning when I ordered the Robox machine I was very enthusiastic about the concept of the Robox.
But lots of post on this community later I don’t know if it was the right decision to decide for Robox and not for e.g. Ultimaker 2.
Lots of posts here deal with the bad quality of the printing results (far below competitors), stucking print head, blobby print results, layers do not precisely match previous layers, problems printing PLA, CEL team not very responsive in Robox forums, and so on:

- Reliable? (as CEL mentioned on their website’s title): is far away from now.

- Works out of the box? (as mentioned on the Kickstarter page): seems not due to too many problems

- High Resolution? - Theoretically yes - but no 0.02mm prints seen up to now

 

So who can tell me why to buy Robox was/is still the right decision?

• This topic was modified 2 months ago by  René.
• This topic was modified 2 months ago by  René.
• This topic was modified 2 months ago by  René.
• This topic was modified 2 months ago by  René.
• This topic was modified 2 months ago by  René.

[Ed_backer909Participant]

got my clogged head back in mail sans any notification or tracking as well…they left it in mailbox.

my unit may have been purged of the problem but the unit itself won’t print anything. I get one email a day with links to the support solutions to try the following…

I’ve read everything posted and tried them all. Seems this until will require updates to the bowden tube, manual head purges, perhaps leaving covers off forever so it can be fixed/maintained etc. Very tired of the hours and hours spent on these support solutions and casual responses from tickets to go do the fix (again), go do this process/solution, go do a manual purge… again and again. this is not support.

Also combining ALL my issues into one ticket is not Good ITIL processes, just to ease your replies it makes for Poor Incident Tracking, Problem Management and root cause analysis. Read the ISO9000 and ITIL process guides guys?

Let’s fix support issues and not push solutions on customers? Let’s fix and stock parts, test and validate issues not send and pray solutions will work?

Desperate in Dallas

Ed

Just got my notification…Robox is on its way..can’t wait to get going!!

[Dr. WooParticipant]

Smoke alarm for 3D printers: Not a bad idea, but some kind of notification system (a WiFi-based push notification would be state of the art) or at least an audible alarm is needed to make it complete. Because the fire doesn’t necessarily stop just from “pulling the plug”.