#3  0x002b6494 in ?? ()

    #3) With great power comes great responsibility.

cond=0xaef01288) at pthread_cond_wait.c:502 #3 __pthread_cond_wait (cond=0xaef01288, mutex=0xaef0126c) at pthread_cond_wait.c:655 #4 0x00570064 in Poco::EventImpl::waitImpl (this=this@entry=0xaef

#3  0x004f6cfc in Poco::BasicBufferedStreamBuf<char, std::char_traits<char>, Poco::BufferAllocator<char> >::underflow (this=0x723fe7a0)

#3  0x005db168 in Poco::Util::Application::run (this=0x7ef97bc0) at /home/pi/repetier-server/Repetier-Server/Poco/Util/src/Application.cpp:334

Print #1 finishes, drops print head back to bed, does a purge and wipe function and then starts print #2 at a different bed location, and so forth with #3 & #4.

I never got to #3 because I checked it and it started working agian. 

Therefore my setup which I mentioned in #3

#3

* Ah, I suppose I'm getting closer to a unified view with having 3 printers per tab vs 6 tabs open. If I can get #2 and #3 working I'm a happy camper.

Repetier-Server Pro (#300651007) 1 unité(s)

I have looked in the configuration.h file and the pins.h file, it appears that board #33 is being selected, and it appears that temp_3 is set to use pin 12.

Since the extruders start at #0, wouldn't Ext0 actually be #1, ext1 being #2 and ext2 be #3??

#3  0x000000000083bf65 in boost::asio::io_service::run() ()

#3  0x0000000000e70461 in thread_proxy ()

#3  0x00000000009f9448 in Poco::ThreadImpl::runnableEntry(void*) ()

#3  0x000000000083bf65 in boost::asio::io_service::run() ()

Arrgghh #3:

Now it seems to probe the entire bed with the probe on the bed (i still have the max x=150, would like to set it closer to the 200 so i don't loose the ability to print with ext #3 on the outer edge )

If I set the probe X,Y points so position #1 is 20,20 position #2 is 150, 20 and position #3 is 20,250