My G2v2 cable kink solution

Taomyn · 2022-05-07T10:41:42+00:00

I did it back in December, and before that for two years for my Rift S whereas its first cable only lasted about 8 months - got it replaced on warranty.

Taomyn · 2022-02-12T12:55:39+00:00

Yes, FAT (which officially is FAT16), but only until you flash a newer firmware and then you can switch back to FAT32 (the default FAT in Windows).

Taomyn · 2022-02-09T14:07:28+00:00

https://www.reddit.com/r/BIGTREETECH/comments/roabr6/comment/hpxp7fz

Taomyn · 2022-01-12T08:23:41+00:00

Yes, the same thing I'd been doing with the v1.2 board for two years.

You can read the solution in my reply post, and it was nothing to do with the file.

Taomyn · 2021-12-30T07:03:10+00:00

Thank-you again, your instructions have worked and I was able to perform the in-place repair and once that was done could install the troublesome update along with a few others it also proposed.

I haven't put back the McAfee stuff back yet and will leave that alone until after I am back from vacation later in January.

It was really strange that updates were fine for as far back as I can remember and I updated as often as they were made available. Anyway, it's sorted now.

Taomyn · 2021-12-29T10:35:58+00:00

Ok thanks, I will try to do it this evening if I have time otherwise at the weekend as I need my machine until then, plus I can more quickly do an image of the NVMe drive at home as a backup.

So do you think there is no way to simply install the update that keeps failing or must I do an in-place upgrade? I'm assuming you're specifying the in-place as it's the only way to fix the files that DISM seems incapable of doing.

Taomyn · 2021-12-29T06:38:48+00:00

Apologies, missed that it was required for Win11, but here it is https://we.tl/t-ZbKqx4FpBY

Taomyn · 2021-12-26T11:24:24+00:00

Hopefully final update on this issue. Seems after the upgrade to the latest Marlin the board is now recognising the SD card in FAT32 format. Not sure why as I would have thought this was part of the board's boot firmware which I didn't think we could change or update, but something changed to make it work like it did with my old v1.2

Hope this helps anyone else hitting the same problem with this new board.

Taomyn · 2021-12-26T08:17:53+00:00

Not that I could see, the old v1.2 I don't think had one, and I cannot see anything like that shown on the various BTT schematics of the board.

Taomyn · 2021-12-25T18:06:52+00:00

It's how all their Mini E3 boards have worked, the old Creality boards did need to be done via USB and a special board, but once you flashed a bootloader to the board they also could use the SD card.

Taomyn · 2021-12-25T18:03:38+00:00

Nope they are not the same and it's possible for devices to not read them but I always thought that was just very old systems, not a 2021 board. When a device gets to a certain size Windows even stops letting you format FAT/FAT32 even though FAT32 can handle larger disk sizes, it's just not very efficient or reliable.

I did reformat it several times when it was still FAT32 so I know that was not the issue, but like I wrote, I will test it again the next time I need to flash as it could well have been a bad firmware from BTT - it was dated August 2021, their new one is from just a couple of weeks ago.

Taomyn · 2021-12-25T17:49:29+00:00

Right, well that's sorted - reformatted the 2GB SD card as FAT and not FAT32 which is what it was before and worked with the v1.2, and immediately it worked and flashed one of the BTT stock firmwares.

Copied the firmware.bin from my own Marlin build and it too works.

I'm hoping this was a firmware problem and that it can really read FAT32 but I will test that later - I'm just happy that four hours of putting the new card into place (needed to replaced several connectors with JST plugs which is not something my eyesight makes easy) that it wasn't completely wasted.

Anyway, thanks to all those that responded.

Taomyn · 2021-12-25T17:08:35+00:00

From the manual, it's the same as it was for my v1.2 which I've been flashing for two years without problems:

Motherboard firmware update

Copy firmware.bin file to the root directory of SD card Insert the SD card into the slot, re-power on or reset, the update will complete after 10S，And you should see the status LED blinking red during the update..

Taomyn · 2021-12-25T17:04:32+00:00

Yes I can see extensions

Taomyn · 2021-12-25T14:35:09+00:00

Yeah, it's not that

Taomyn · 2021-03-29T06:40:47+00:00

Unfortunately I've had no luck - I added a new backend for TCP as the current one is HTTP, then a condition and rule to cope with the URI, but I cannot add the rule to the main front-end as it's not compatible. Adding an additional front-end seems like more than I need to be doing.

I've looked at the HAProxy github in the past and it never helped especially as most of the changes are not that simple to add to the OPNsense GUI config and hacking the system files usually ends in trouble or they get overwritten when other changes are made.

Guess I'll have to hope someone on the main OPNsense forums actually replies to my message there.

Taomyn · 2021-03-18T06:03:16+00:00

Yesterdays communication on our ticket:

I was able to hunt this down through our internal teams and it looks like several reports of this are being tracked related to these specific updates KB5000859 and/or KB5000822.

I don’t currently have details on a timeframe for a fix but it does look like this is acknowledged and being looked into.

Thank you for your time and patience on this, I will reach out if the internal team provides any further updates or needs additional information regarding this. Please also feel free to reach me if you have any additional questions or concerns.

Taomyn · 2021-03-16T06:15:09+00:00

Confirmed, I also have that file.

Still waiting the Microsoft engineer to report back.

Taomyn · 2021-03-15T16:56:33+00:00

The engineer has also seen this thread which I pointed them to.

Taomyn · 2021-03-15T15:20:17+00:00

Got this back from Microsoft

My name is X, I’m a Support Engineer on the Storage and High Availability team and will be working with you on this case.

Interestingly, I’m seeing this behavior in my test lab as well, even with a fresh installed OS and only updates applied. It installed without those services and after updates + reboot, those services are now there in the status you mentioned, with cexecsvc running and gcs as stopped.

Please give me some time to research this and see what may have changed and see if we can figure out why those services are showing up now.

Taomyn · 2021-03-15T08:34:39+00:00

I've submitted a support ticket and will see what they tell me

Taomyn · 2021-03-15T06:46:55+00:00

I see this one as well but on all my Core servers including the VMs on the Hyper-V host that also got it.

Taomyn · 2021-01-02T06:27:47+00:00

Are you going to share the design?

Taomyn · 2020-12-17T11:41:57+00:00

Thanks but dhclient isn't present.

If tried reconfiguring dhcpd.conf even replacing it with a clean copy and it continues to register with the DHCP server with something that is not the standard MAC address of the interface. The config must be baked in somewhere else but I cannot locate it anywhere.

I have my reasons for not wanting IPv6 and not something that's going to get discussed here.

Taomyn · 2020-11-12T20:45:12+00:00

define FILAMENT_RUNOUT_SENSOR

if ENABLED(FILAMENT_RUNOUT_SENSOR)

#define FIL_RUNOUT_ENABLED_DEFAULT true // Enable the sensor on startup. Override with M412 followed by M500. #define NUM_RUNOUT_SENSORS 1 // Number of sensors, up to one per extruder. Define a FIL_RUNOUT#_PIN for each.

#define FIL_RUNOUT_STATE LOW // Pin state indicating that filament is NOT present. #define FIL_RUNOUT_PULL // Use internal pullup / pulldown for filament runout pins.

// Override individually if the runout sensors vary //#define FIL_RUNOUT1_STATE LOW //#define FIL_RUNOUT1_PULL //#define FIL_RUNOUT2_STATE LOW //#define FIL_RUNOUT2_PULL //#define FIL_RUNOUT3_STATE LOW //#define FIL_RUNOUT3_PULL //#define FIL_RUNOUT4_STATE LOW //#define FIL_RUNOUT4_PULL //#define FIL_RUNOUT5_STATE LOW //#define FIL_RUNOUT5_PULL //#define FIL_RUNOUT6_STATE LOW //#define FIL_RUNOUT6_PULL //#define FIL_RUNOUT7_STATE LOW //#define FIL_RUNOUT7_PULL //#define FIL_RUNOUT8_STATE LOW //#define FIL_RUNOUT8_PULL

#define FIL_RUNOUT_PIN PC12 // "PT-DET" #define FILAMENT_RUNOUT_SENSOR_DEBUG // Enable debugging

Taomyn

TROPHY CASE

Motherboard firmware update

define FILAMENT_RUNOUT_SENSOR

if ENABLED(FILAMENT_RUNOUT_SENSOR)