New experimental firmware 1.09c July 09, 2015 07:15AM |
Registered: 10 years ago Posts: 665 |
Quote
Gratefully merged in dc42's new move code, but with some changes:
- Speed and extrusion multipliers are applied in the Move code
- Raw extruder totals have been implemented the same way as in my original Move code
- Move:ausePrint has been altered so that theoretical E distances are not reported, instead the number of skipped moves is returned (for the code queue)
- Interfaces for the code queue (MoveQueued, MoveCompleted) have been added again
- Bug fix: Dwell in simulation mode might cause moves not to be picked up by the Move module any more
The following changes were also made:
- GCodeBuffer doesn't have Pause/Resume interfaces any more
- Message indent increased again from 1 to 2 space chars
- Implemented M84 'S' parameter (set idle timeout in seconds)
M574 X0 Y2 Z0 S1
Re: New experimental firmware 1.09c July 09, 2015 07:46AM |
Registered: 12 years ago Posts: 1,611 |
Re: New experimental firmware 1.09c July 09, 2015 02:12PM |
Registered: 9 years ago Posts: 1,699 |
Re: New experimental firmware 1.09c July 10, 2015 12:21PM |
Registered: 10 years ago Posts: 665 |
Re: New experimental firmware 1.09c July 10, 2015 12:24PM |
Registered: 9 years ago Posts: 1,699 |
Re: New experimental firmware 1.09c July 10, 2015 01:21PM |
Registered: 9 years ago Posts: 1,699 |
Quote
zombiepantslol
Simultaneous XY homing should be supported (the corresponding G1 X.. Y.. S1 code works), but I haven't merged in dc42's homing files yet. If you want to try it, just grab a copy of dc42's homeall.g from his repository and replace the current one in your /sys directory.
Re: New experimental firmware 1.09c July 16, 2015 11:54AM |
Registered: 10 years ago Posts: 780 |
Re: New experimental firmware 1.09c July 16, 2015 02:00PM |
Registered: 9 years ago Posts: 1,699 |
Re: New experimental firmware 1.09c July 17, 2015 03:41AM |
Registered: 10 years ago Posts: 780 |
Re: New experimental firmware 1.09c July 17, 2015 06:24AM |
Registered: 10 years ago Posts: 780 |
Re: New experimental firmware 1.09c July 17, 2015 09:06AM |
Registered: 10 years ago Posts: 665 |
M111 P1 S1 M111 P2 S13) Make a Wireshark dump
Re: New experimental firmware 1.09c July 17, 2015 09:33AM |
Registered: 9 years ago Posts: 1,699 |
Quote
appjaws1
Well this is a continuing mystery
It works in linux, no problems but in windows chrome,firefox or IE the web interface will not load and just sits there waiting.
I have noticed that when chrome first starts, the web interface is displayed but after a few seconds the screen flashes and a small square box is visible to the left of the word Connect on the connect button, the screen then just sits there as if waiting for something.
So I can not try out zpl's firmware so will revert back to dc42's.
Re: New experimental firmware 1.09c July 17, 2015 12:14PM |
Registered: 10 years ago Posts: 780 |
Quote
zombiepantslol
If you want to help me resolve this, there are a couple of things you could do:
1) Try to connect to the Duet in a private window and check if it makes a difference
2) Enable debugging for the network and webserver modules, and check the serial log for any unusal messages:
M111 P1 S1 M111 P2 S13) Make a Wireshark dump
I'm not sure what could be causing this as everything is working well on my setup. Also make sure you don't install hardware updates via Windows Update, from my experience this causes more problems and occasionally messes up working network configurations.
Re: New experimental firmware 1.09c July 17, 2015 12:30PM |
Registered: 10 years ago Posts: 275 |
Re: New experimental firmware 1.09c July 17, 2015 01:03PM |
Registered: 9 years ago Posts: 1,699 |
Re: New experimental firmware 1.09c July 18, 2015 08:32AM |
Registered: 10 years ago Posts: 665 |
Quote
appjaws1
I have loaded 109d and still the web interface will not start, on all 3 browsers I am getting "The server at 192.168.1.14 is taking too long to respond."
Connecting in a private window made no difference whatsoever.
How do I enable debugging for the network and webserver modules when the interface will not even start?
wireshark dump [attachment 58279 wireshark-from-appjaws.pcapng] hope that helps.
I am really baffled by this Why does dc42-1.09c work and your 109c or 109d does not???
Can I do anything else to help resolve this?
Re: New experimental firmware 1.09c July 18, 2015 08:59AM |
Registered: 10 years ago Posts: 780 |
Quote
zombiepantslol
Thanks Paul, I've just looked through your Wireshark dump and it seems like your printer doesn't properly set up the networking address (although I'm still baffled why it works under Linux?). The Duet just doesn't seem to be available from your PC. Can you ping 192.168.1.10 instead and does the firmware report the proper IP address like "Network up, IP=192.168.1.14" when you start the Duet with a serial logger attached? Also, would you mind sharing your config.g file? I'd then try to replace my current config.g with it and check if it makes any difference.
Re: New experimental firmware 1.09c July 18, 2015 09:07AM |
Registered: 9 years ago Posts: 1,699 |
Re: New experimental firmware 1.09c July 18, 2015 09:14AM |
Registered: 10 years ago Posts: 780 |
Quote
Treito
I am sorry to say that but it has to be something with your Ormerod or your setup because at all others it works. Maybe there is a bug in the firmware and for some circumstances it is only affecting you. I would think that you downloaded the fw-file wrong but you want to reload it and that is good so. Please look especially for some shell outputs. How is bossac behaving? Is your USB-cable alright? What about other devices like Android? Maybe it is an extension in FF or Chrome that blocks the Ormerod?
Re: New experimental firmware 1.09c July 18, 2015 09:30AM |
Registered: 10 years ago Posts: 275 |
Quote
appjaws1
Quote
Treito
I am sorry to say that but it has to be something with your Ormerod or your setup because at all others it works. Maybe there is a bug in the firmware and for some circumstances it is only affecting you. I would think that you downloaded the fw-file wrong but you want to reload it and that is good so. Please look especially for some shell outputs. How is bossac behaving? Is your USB-cable alright? What about other devices like Android? Maybe it is an extension in FF or Chrome that blocks the Ormerod?
Thank you for your interest but the ormerod works fine with everything the same on my computer, except the firmware. I have changed the firmware between zpl and dc42 many times whist trying to resolve this issue so I am convinced that it is a firmware issue but I agree it must be a bug that is only affecting me. Aren't I lucky????
Re: New experimental firmware 1.09c July 18, 2015 09:35AM |
Registered: 9 years ago Posts: 1,699 |
Quote
Ormerod187
if you try in a dos prompt "arp -a" 0xBE:0xEF:0xDE:0xAD:0xFE:0xED should be there
sudo arp -a root's password: fritz.box (192.168.178.1) auf c0:25:06:c8:d2:75 [ether] auf enp0s25 HDDRekorder.fritz.box (192.168.178.130) auf d0:50:99:64:69:9c [ether] auf enp0s25 Canon-MG5350.fritz.box (192.168.178.32) auf 18:0c:ac:c3:f0:15 [ether] auf enp0s25 ? (192.168.178.14) auf be:ef:de:ad:fe:ed [ether] auf enp0s25
Re: New experimental firmware 1.09c July 18, 2015 10:50AM |
Registered: 10 years ago Posts: 275 |
Quote
Treito
Quote
Ormerod187
if you try in a dos prompt "arp -a" 0xBE:0xEF:0xDE:0xAD:0xFE:0xED should be there
Works for me except for the DOS-Prompt.
sudo arp -a root's password: fritz.box (192.168.178.1) auf c0:25:06:c8:d2:75 [ether] auf enp0s25 HDDRekorder.fritz.box (192.168.178.130) auf d0:50:99:64:69:9c [ether] auf enp0s25 Canon-MG5350.fritz.box (192.168.178.32) auf 18:0c:ac:c3:f0:15 [ether] auf enp0s25 ? (192.168.178.14) auf be:ef:de:ad:fe:ed [ether] auf enp0s25
Re: New experimental firmware 1.09c July 18, 2015 10:53AM |
Registered: 9 years ago Posts: 1,699 |
Re: New experimental firmware 1.09c July 18, 2015 11:01AM |
Registered: 10 years ago Posts: 14,672 |
Re: New experimental firmware 1.09c July 18, 2015 11:19AM |
Registered: 10 years ago Posts: 780 |
Quote
dc42
The network code I use is almost identical to zpl's code, because I resynced to his code in one of my recent releases (1.09b AFAIR). However, because of differences in the way the Arduino core is implemented, there is some network initialisation code for the network that runs as a different point in my fork compared to zpl's. Also I use different code to wait for config.g code to finish executing, which might also affect the timing of network initialisation..
Re: New experimental firmware 1.09c July 18, 2015 11:19AM |
Registered: 10 years ago Posts: 275 |
Quote
Treito
Sorry, but I am not a fan of Apple, but this is more ,y personnel opinion and I prefer Linux over Windows as much a possible.
Re: New experimental firmware 1.09c July 18, 2015 12:44PM |
Registered: 10 years ago Posts: 780 |
Re: New experimental firmware 1.09c July 18, 2015 12:55PM |
Registered: 10 years ago Posts: 14,672 |
Quote
appjaws1
Just to let you know.
I have loaded dc42-1.09c firmware so that I can print. I noticed that in the pronterface log the following;-
Connecting...
Printer is now online.
Network: Connection error, code -11
Network: Connection error, code -11
Network: Connection error, code -11
Network: Connection error, code -11
Network: Connection error, code -11
Network: Connection error, code -11
Network: Connection error, code -11
Network: Connection error, code -11
Network: Connection error, code -11
but using the web interface the printer seems to be working ok. and pinging the ormerod works with no errors.
Re: New experimental firmware 1.09c July 18, 2015 01:48PM |
Registered: 10 years ago Posts: 780 |
Quote
dc42
Quote
appjaws1
Just to let you know.
I have loaded dc42-1.09c firmware so that I can print. I noticed that in the pronterface log the following;-
Connecting...
Printer is now online.
Network: Connection error, code -11
Network: Connection error, code -11
Network: Connection error, code -11
Network: Connection error, code -11
Network: Connection error, code -11
Network: Connection error, code -11
Network: Connection error, code -11
Network: Connection error, code -11
Network: Connection error, code -11
but using the web interface the printer seems to be working ok. and pinging the ormerod works with no errors.
Where does the "Network up, IP=..." message appear - after the connection errors?
Re: New experimental firmware 1.09c July 18, 2015 04:29PM |
Registered: 10 years ago Posts: 14,672 |