Please explain what you mean by "timeout" - what message are you getting, where, and what do you do to provoke it? If the message is from Repetier host then you should adjust the communications protocol, in particular, turn off "ping pong".

There is no adjustment. If you have run the thermocouple wires all the way back to the daughter board, then the reading should be within 2C of the actual value.

You could always try using the other channel on the daughter board.

That's actually what I did, M116 P0 in my startup code. I make sure all my prints start with the primary extruder. At some point I'd like to experiment with varying the temps at filament swap, and I'll add a M116 to the tpostX.g if/when I do.

There is an issue with github, when downloading the firmware.

If you right click on the firmware file in the folder and select "save link as" you get an approx. 30kb file which is obviously not correct. I've done it foolishly 3 times, and flashed it and had to do the hard reset option.

Instead left click the file, github will then display a grey box saying "view raw", and a button on the right "download". A left click there will get you the full 260kb file.

Before the move to auto update from DWC (essentially OTA update) I think some sort of MD5 check or something like that would be a lifesaver and its quick enough to do, and common practice with things like smartphone Roms, where the consequences of flashing a corrupt file can be permanently bricking your device. I accept this is not a risk with a corrupt firmware on this device.

I checked the wiki and the instructions there are clear.

Might there also be an argument to host the firmware files on the duet3d.com site somewhere with slightly more conventional download behaviour, i.e. right click would work etc…

Sorry to revive a dead thread but did you get it all working nicely in the end @CoolM8. I am nearing the end of my build and am readying myself to start the firmware side of it.

@dc42:

Yes, I could leave the option for probing points and reporting the height errors in the firmware, but just remove the actual compensation.

That would be fine for me. Obviously other users may have different views.

Thanks a lot for your quick answer, now it works !

Hi all, i'm happy to find the thread about my ardwrare problem. My printer are under construction and i just begin wiring and connection. Wifi network only run when i put my finger on R103. I bought my T3P3 board at the end of january, a blue production one. Should i've it replaced? Is there another solution without soldering for fix it alone?

Sorry for my english, i'm new french user who use google translate.

Have you tried using configtool? If you need to go into more detail, see https://duet3d.com/wiki/Configuring_RepRapFirmware_for_a_Cartesian_printer.

I found the error, I used a USB extension, never do this.. It works now 🙂

@T3P3Tony:

Thanks for the feedback. I will consider how to restructure the documentation to make it easier to navigate - the Wiki has grown a lot over the last few months, maybe the frontpage/table of contents layout is not the best.. Any thoughts on alternative structures?

Also you mention it loads slowly - is that all ages or just the front page?

Hi Tony, the slow loading issue no longer exists today. I'm not sure if it could have been a result of your server load or simply my overloaded PC yesterday, with many tabs open in Chrome.

Regarding the wiki structure, hopefully there are some lurking web interface gurus who can share their expertise - burtoogle for one, perhaps, and at least another MS tech writer I've seen lurking here - whose handle I forget, sorry 🙂 In the meantime I found some good introductory guidance at Wikipedia:
https://en.wikipedia.org/wiki/Wikipedia:Summary_style

As a case in point, I like the fact I can read much more on that one page. I'm not suggesting that structure is appropriate for all the Duet Wiki pages, but an ideal in terms of making it quicker to skim read to ensure all pertinent information is obtained (in order to prevent or at least reduce possibility of equipment damage, or seemingly-going-round-in-circles type frustration).
The following section in that wikipedia page seems to provide a good overview on balancing page size and detail:
1 Rationale
1.1 Article size
1.2 Levels of detail

Youtube seems a little lacking on the subject, but I did find this informative though slightly slow-paced webinar: https://youtu.be/wwi8s5VdHH0

I only have a couple of thoughts from my experience of the Duet wiki that might be of interest:
If keeping the same contents system, navigation might be improved by adding contents navigation to each subsection - to remind the reader what else exists under that particular heading - and to avoid the round trip back to the contents (Home) page.

Where a subsection contains only a paragraph, for example: https://duet3d.com/wiki/Prerequisites_for_using_the_Duet_WiFi
It would ultimately be quicker - and just as manageable as far as assimilating info - to read that as part of a longer piece of text. I didn't check out the entirety of that section, but I wonder if it could be completely flattened into a single page?

Update: I'm still not 100% sure what could be causing this but I turned off my RaspberryPi on the other side of my house and I havn't gotten any connection errors today… That could be the interference source even if it feels very strange..

Thanks. I added the .md extension so that line wrap works, after I write that post. I've corrected the post.

@hum3:

Another in the heffalump trap!

I had loaded the Web Interface first. Fix was like procedure 1.

Power down and extracted the uSD card

Copy and rename the latest set of files

Reinserted card and powered on

Send the command on the web interface M997 S0 this upgraded the firmware

Then upgraded the WIFI server using the web server

Looking better - so back to rebuild the Ormerod 1. Such quiet motors - lovely.,

Nice, I guess i was the odd ball out, I updated the web controller and interface no problem but couldn't update the firmware-had to rename it, and now all set.
Now I just need to figure out how to enable the configurator file I made. Commence the forum search!

Edit:Nailed it! on to BLtouch

Sending M110 S0 from the Duet Web Control stops the messages in Repetier, until you send another command. E.g., after I saw that it stopped, I tried M114 and M115 from Repetier just to see if the log still worked, and then the messages start again.

Anyway, not worth taking up more of your time – it doesn't hurt anything except the ability to see the logs, and if I want to I can always disconnect the Duet Web Control temporarily while in Repetier.

Thanks,
James

Its Sorted 🙂

I really do appreciate your help and being in constant contact….thank you.

As it happens it turned out to be a bad Ethernet cable, I was using the wrong type of Ethernet cable, soon as I changed it, it loaded straight into the interface.

Thanks again, excited again 🙂
Rob

I'm sorry I haven't been able to respond earlier, but now I have some time again to investigate your problem.

Assuming you are using a Duet WiFi, can you confirm you are using my latest Duet WiFi Server version 1.03? There was an issue in prior versions that caused empty responses to be sent to the web interface and this issue looks exactly like it.

Although I doubt an older version will resolve this problem, you can actually get older versions from my GitHub repository by looking through the list of commits. Here a link to the 1.12 DWC files, but be aware that it may not work properly with the latest firmware version: https://github.com/chrishamm/DuetWebControl/commit/edf9c9ba3f1148d67fbafeae0d6b20042705cb2a

0 chrishamm committed to chrishamm/DuetWebControl Packages for first-gen Duets and Duet WiFi added

I had an issue after downloading the .bin file was only 43k, I was about to flash it when I noticed, so I downloaded it again and it was 260kb or so which is the right size. Until the webinterface can do an automatic update it's worth checking the file size is right. Any chance of some sort of md5 check or something similar?

No issues with 1.17d though working perfectly for me.

Might be wise to have some sort of confirmation/warning when trying to downgrade firmware.