Posts made by ianlee74

@dc42:

See https://duet3d.com/wiki/Configuring_RepRapFirmware_for_a_Delta_printer#Homing_file, or read the comments in the sample homedelta.g file that I provide.

That F parameter is actually what I was thinking of when I said I didn't really want to increase the motor speed. However, its been many months since I last read that and had forgotten about the "300" values. I bet that's my issue. I'll double check that tonight. It's probably doing exactly what its been told to do. My Z height is somewhere around 335mm now…

@dc42:

Are you certain that it was reading config.g correctly? The only hardware fault I can think of that would change the behaviour in the ways you describe would be a failure to read and process config.g, perhaps because of a hardware fault in the SD card interface.

How can I know for sure? The controller board that I'm using now is running off the same SD card that I was using on the board that doesn't work. Because the new board hadn't been fired up in many months, all I did was upload all the latest .bin files and it works as expected. Is there some way I can test if the SD card interface is working as expected? FYI, my controller board is totally enclosed and the SD card wasn't touched at the time that it stopped working.

Nice job. How did you get the scan?

Where can I get those slim blower fans?

Thanks!
Ian

Is it possible to set a timeout for the G28 command? Since building my taller (1000mm) delta, in my bed.g file I now have to give it multiple G28 commands to ensure it makes it all the way to the top since if the hotend starts at bed level then it will usually timeout about 3/4 the way to the top. I know I can increase the default speed. However, I like the speed and I simply want to give G28 more time. If this isn't possible easily then perhaps a parameter could be added to G28 to specify a timeout in seconds?

Thanks!
Ian

@ianlee74:

Any ideas I can test from here? If we don't find anything, can I send it in for examination and possible RMA or repair?

@dc42 - any thoughts? I don't mind attempting a repair on my end if you have some ideas on where I should be lookinging. I'm not excited about purchasing a 4th Duet WiFi board this year, though, without first having some idea what went wrong with this one.

Thanks!
Ian

I thought you were going to say you had the same issue I observed last night after loading 1.17RC2. Everything is working fine but it seems like it takes my hotend forever to get up to temperature now. It seems like its using a very linear ramp. I'll try re-running the auto PID tuning later and see if that gives it a better curve. Didn't feel like messing with it last night.

Well, after swapping out the board, I'm back to printing. No idea what's up with the that board. I still need to try and get it working so I can put it back in my other printer. Any ideas I can test from here? If we don't find anything, can I send it in for examination and possible RMA or repair?

@DjDemonD:

My understanding is that it microsoft's clumsy attempt to muscle into the 3D arena. I am sure the format has much to commend it but for the time being its just an annoyance having to use microsoft's 3D object builder to convert these back to .stls.

I believe that's a highly inaccurate and unfair way to describe the situation. It's my understanding that 3MF was developed by a consortium of companies with an interest in evolving the current state of 3D printing file formats. Microsoft chose to include it in Windows 10. They didn't develop it. If you check the membership list of the consortium you'll see there are many big name players involved.

To answer the OP's initial question, you can find list of places where 3MF has been adopted here.

@T3P3Tony:

I have fixed the issue as far as I can test, took the opportunity to upgrade the forum software as well. please let me kow if its working for you.

Works for me now. Thanks!

I got SAM-BA 2.16 installed tonight then erased the firmware and re-flashed the board. That didn't change anything. So, next steps were to unplug everything from the board and see if thermistors would work by themselves. This revealed something interesting. If only one of the thermistors (hotend & bed) is connected then the Duet doesn't report any reading at all for either thermistors. However, when I connect the second thermistor then I start getting the erratic values for both thermistors. I've tested both thermistors with a meter and tried connecting new thermistors and the behavior is the same. I now think there's something wrong with this board.

You can see my tests in this video.

Any ideas? Next, I'm going to start ripping my other Duet WiFi board out of my other printer (that's not working because of other issues….) and swap it out. I'm really hesitant to do this w/o knowing why this board is not working, though. I've examined all the obvious locations where there could be wiring problems and so far have found nothing that looks like a problem. The only thing that happened between working & not working was a config change & restart. I'm puzzled...

Tried it using Edge and Internet Explorer on the same machine and get the same result.

@T3P3Tony:

can you give some more information about what browser and what error, what type of search (advanced, standard?)

Tony see this video capture. This is using the latest version of Chrome on Windows 10 x64.
https://youtu.be/gZc54Way4pE

@dc42:

It does sound like a problem with SD card corruption to me. Have you checked it in a PC for errors? Or try reformatting it and then copy the files back on. Or a new SD card.

The SD card checked out OK. I reformatted it and copied everything new to it. No change. Next I'm erasing the firmware manually and trying to re-apply but ran into problems acquiring SAM-BA last night. I've got a copy now and will try again tonight. Still open to other theories if anyone has any.

@dc42:

For the record, the list of processors supported by bossac doesn't include the SAM4E used on the Duet WiFi. That's why we use SAM-BA. But you should only need to use it if you press the Erase button, or if the in-application firmware update fails.

Understood. This is in relation to this thread. Formatting the SD card and updating the firmware using the web interface have so far had no effect. So, I pushed the erase button in an attempt to get everything as clean as possible.

@DjDemonD:

Ill host the file for the time being:
https://1drv.ms/u/s!Apv79JfGbPIwgulVoRt8eCOHA4rAVQ

Got it. THANKS!

I'm trying to follow the Duet WiFi instructions to update the firmware using SAM-BA. However, the Microchip/Atmel website seems to be having problem with its login mechanism and won't let me download it… Could someone put the Window bits somewhere I can get them or send them to me?

I've used bossac in the past to update the firmware on my Duet boards. However, it doesn't seem to recognize my Duet WiFi board despite that it appears in Device Manager as a Bossa Program Port. Is this expected?

Thanks!
Ian

@T3P3Tony:

Hi Ian

You can do what you describe using one more thermistor input.

As the DuetWifi reports the CPU temperature there is an aspiration to make this a temperature channel that can be used for fan control.

Ah… Ok. Makes sense.

When I try to search this website I'm getting a Luna error.

@dc42:

It does sound like a problem with SD card corruption to me. Have you checked it in a PC for errors? Or try reformatting it and then copy the files back on. Or a new SD card.

Funny you should suggest that… I was just talking to one my local printer building pals and he suggested the same. I'll be trying a new card tonight.

Thanks!
Ian