Posts made by bcrazycramer

@chrishamm said in 3.2b1 Duet 3 (DCS is not started):

@bcrazycramer Please see my earlier post.

Which part?

I get the same after rebooting.

I'm not using the Raspberry Pi for anything else except the Duet 3. I do have VNC enabled and SSH.

Do you know why this isn't working?

pi@duet3:~$ sudo /opt/dsf/bin/DuetWebServer
crit: Microsoft.AspNetCore.Server.Kestrel[0]
Unable to start Kestrel.
System.IO.IOException: Failed to bind to address http://[::]:80: address already in use.
---> Microsoft.AspNetCore.Connections.AddressInUseException: Address already in use
---> System.Net.Sockets.SocketException (98): Address already in use
at System.Net.Sockets.Socket.UpdateStatusAfterSocketErrorAndThrowException(SocketError error, String callerName)
at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress socketAddress)
at System.Net.Sockets.Socket.Bind(EndPoint localEP)
at Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets.SocketConnectionListener.Bind()
--- End of inner exception stack trace ---
at Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets.SocketConnectionListener.Bind()
at Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets.SocketTransportFactory.BindAsync(EndPoint endpoint, CancellationToken cancellationToken)
at Microsoft.AspNetCore.Server.Kestrel.Core.KestrelServer.<>c__DisplayClass21_01.<<StartAsync>g__OnBind|0>d.MoveNext() --- End of stack trace from previous location where exception was thrown --- at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.AddressBinder.BindEndpointAsync(ListenOptions endpoint, AddressBindContext context) --- End of inner exception stack trace --- at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.AddressBinder.BindEndpointAsync(ListenOptions endpoint, AddressBindContext context) at Microsoft.AspNetCore.Server.Kestrel.Core.ListenOptions.BindAsync(AddressBindContext context) at Microsoft.AspNetCore.Server.Kestrel.Core.AnyIPListenOptions.BindAsync(AddressBindContext context) at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.AddressBinder.EndpointsStrategy.BindAsync(AddressBindContext context) at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.AddressBinder.BindAsync(IServerAddressesFeature addresses, KestrelServerOptions serverOptions, ILogger logger, Func2 createBinding)
at Microsoft.AspNetCore.Server.Kestrel.Core.KestrelServer.StartAsync[TContext](IHttpApplication1 application, CancellationToken cancellationToken) Unhandled exception. System.IO.IOException: Failed to bind to address http://[::]:80: address already in use. ---> Microsoft.AspNetCore.Connections.AddressInUseException: Address already in use ---> System.Net.Sockets.SocketException (98): Address already in use at System.Net.Sockets.Socket.UpdateStatusAfterSocketErrorAndThrowException(SocketError error, String callerName) at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress socketAddress) at System.Net.Sockets.Socket.Bind(EndPoint localEP) at Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets.SocketConnectionListener.Bind() --- End of inner exception stack trace --- at Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets.SocketConnectionListener.Bind() at Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets.SocketTransportFactory.BindAsync(EndPoint endpoint, CancellationToken cancellationToken) at Microsoft.AspNetCore.Server.Kestrel.Core.KestrelServer.<>c__DisplayClass21_01.<<StartAsync>g__OnBind|0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.AddressBinder.BindEndpointAsync(ListenOptions endpoint, AddressBindContext context)
--- End of inner exception stack trace ---
at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.AddressBinder.BindEndpointAsync(ListenOptions endpoint, AddressBindContext context)
at Microsoft.AspNetCore.Server.Kestrel.Core.ListenOptions.BindAsync(AddressBindContext context)
at Microsoft.AspNetCore.Server.Kestrel.Core.AnyIPListenOptions.BindAsync(AddressBindContext context)
at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.AddressBinder.EndpointsStrategy.BindAsync(AddressBindContext context)
at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.AddressBinder.BindAsync(IServerAddressesFeature addresses, KestrelServerOptions serverOptions, ILogger logger, Func2 createBinding) at Microsoft.AspNetCore.Server.Kestrel.Core.KestrelServer.StartAsync[TContext](IHttpApplication1 application, CancellationToken cancellationToken)
at Microsoft.AspNetCore.Hosting.GenericWebHostService.StartAsync(CancellationToken cancellationToken)
at Microsoft.Extensions.Hosting.Internal.Host.StartAsync(CancellationToken cancellationToken)
at Microsoft.Extensions.Hosting.HostingAbstractionsHostExtensions.RunAsync(IHost host, CancellationToken token)
at Microsoft.Extensions.Hosting.HostingAbstractionsHostExtensions.RunAsync(IHost host, CancellationToken token)
at Microsoft.Extensions.Hosting.HostingAbstractionsHostExtensions.Run(IHost host)
at DuetWebServer.Program.Main(String[] args) in /home/christian/Duet3D/DuetSoftwareFramework/src/DuetWebServer/Program.cs:line 24
Aborted
pi@duet3:~$

@chrishamm said in 3.2b1 Duet 3 (DCS is not started):

/usr/lib/systemd/system/duetcontrolserver.service

Thank you! That fixed it.

After updating to 3.2b1 when I try to connect to the web control page I get these errors:

I think I did try it while trouble shooting with the group over on the Jubilee Discord:

pi@duet3:~$ echo M122 | sudo /opt/dsf/bin/CodeConsole
Unhandled exception. System.Net.Internals.SocketExceptionFactory+ExtendedSocketException (99): Cannot assign requested address /var/run/dsf/dcs.sock
at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
at System.Net.Sockets.Socket.Connect(EndPoint remoteEP)
at DuetAPIClient.BaseConnection.Connect(ClientInitMessage initMessage, String socketPath, CancellationToken cancellationToken) in /home/christian/Duet3D/DuetSoftwareFramework/src/DuetAPIClient/BaseConnection.cs:line 98
at CodeConsole.Program.Main(String[] args) in /home/christian/Duet3D/DuetSoftwareFramework/src/CodeConsole/Program.cs:line 44
at CodeConsole.Program.<Main>(String[] args)
Aborted
pi@duet3:~$

@T3P3Tony said in DCS Not starting (Could not connect to Duet):

@bcrazycramer

When you connect using a terminal program and Send M122 what result do you get?

It looks like you have the right image on the Pi and the right firmware on the Duet so there is some form of comms issue between the two. Either the Pi GPIO header, the cable or the Duet SBC header and associated electronics.

I already have it packed up and ready to ship back to Filastruder for replacement.

@Phaedrux said in RMA Request Duet 6HC:

Yes, I've reviewed your other thread and authorize a warranty exchange. Please contact Filastruder and initiate an exchange. Provide a link to this thread as authorization.

Thank you!

Hello,

I'd like to request an RMA or replacement for my Duet 3 6HC board. Do I do that here or with Filastruder where I purchased the board?

Please see my thread here for some of the troubleshooting I have done:

https://forum.duet3d.com/topic/18236/dcs-not-starting-could-not-connect-to-duet/18

Thank you,
Brandon

I created a new SD card with a new image and still get the same error about not being able to contact the Duet.

Do I need to RMA this board?

New ribbon cable installed and I still can't connect to the Duet:

Aug 21 19:31:09 duet3 systemd[1]: Stopped Duet Control Server.
Aug 21 19:31:09 duet3 systemd[1]: Started Duet Control Server.
Aug 21 19:31:10 duet3 DuetControlServer[1868]: Duet Control Server v3.1.1
Aug 21 19:31:10 duet3 DuetControlServer[1868]: Written by Christian Hammacher for Duet3D
Aug 21 19:31:10 duet3 DuetControlServer[1868]: Licensed under the terms of the GNU Public License Version 3
Aug 21 19:31:10 duet3 DuetControlServer[1868]: [info] Settings loaded
Aug 21 19:31:10 duet3 DuetControlServer[1868]: [info] Environment initialized
Aug 21 19:31:10 duet3 DuetControlServer[1868]: [fatal] Could not connect to Duet (Board is not available (no header))
Aug 21 19:31:10 duet3 systemd[1]: duetcontrolserver.service: Succeeded.
Aug 21 19:31:16 duet3 systemd[1]: duetcontrolserver.service: Service RestartSec=5s expired, scheduling restart.
Aug 21 19:31:16 duet3 systemd[1]: duetcontrolserver.service: Scheduled restart job, restart counter is at 64.
Aug 21 19:31:16 duet3 systemd[1]: Stopped Duet Control Server.
Aug 21 19:31:16 duet3 systemd[1]: Started Duet Control Server.

Do we know which pins are being used between the two? My old cable it damaged on the raspberry pi side. The first 20 pins are still in the connector.

Duet 3 MB6HC Firmware Version 3.1.1 Electronics: Duet 3 MB6HC V1.01 or later

@bearer said in DCS Not starting (Could not connect to Duet):

The Pi seems to indicate the Duet is connected but not responding properly.

Are you able to connect to the usb serial console and execute M115 to show which version of the firmware is running on the Duet now?

So connect it up with Repetier host or something similar and issue M115?

Why do you say it won't help?

How can I get an original 26 pin to 40 pin ribbon cable for the Duet 3 to Raspberry Pi?

I wasn't clicking write and then verify. My bad.

Current status after the write and verify:

Aug 18 19:43:25 duet3 systemd[1]: Stopped Duet Control Server.
Aug 18 19:43:25 duet3 systemd[1]: Started Duet Control Server.
Aug 18 19:43:26 duet3 DuetControlServer[1654]: Duet Control Server v3.1.1
Aug 18 19:43:26 duet3 DuetControlServer[1654]: Written by Christian Hammacher for Duet3D
Aug 18 19:43:26 duet3 DuetControlServer[1654]: Licensed under the terms of the GNU Public License Version 3
Aug 18 19:43:26 duet3 DuetControlServer[1654]: [info] Settings loaded
Aug 18 19:43:26 duet3 DuetControlServer[1654]: [info] Environment initialized
Aug 18 19:43:26 duet3 DuetControlServer[1654]: [fatal] Could not connect to Duet (Board is not available (no header))
Aug 18 19:43:26 duet3 systemd[1]: duetcontrolserver.service: Succeeded.
Aug 18 19:43:32 duet3 systemd[1]: duetcontrolserver.service: Service RestartSec=5s expired, scheduling restart.
Aug 18 19:43:32 duet3 systemd[1]: duetcontrolserver.service: Scheduled restart job, restart counter is at 51.
Aug 18 19:43:32 duet3 systemd[1]: Stopped Duet Control Server.
Aug 18 19:43:32 duet3 systemd[1]: Started Duet Control Server.

With another USB cable when I Verify I get Verify failed with page errors and byte errors.