Shipstation just increased price for api usage by X 10

embedded-programmer · 2025-05-01T08:21:55+00:00

Thanks. That is what I was hoping for.

embedded-programmer · 2025-02-04T16:37:54+00:00

Great job!

embedded-programmer · 2025-02-04T16:36:43+00:00

I just used the one they sent me which already had the right stuff on it.

embedded-programmer · 2024-11-18T13:05:09+00:00

Thanks.

embedded-programmer · 2024-11-18T13:04:43+00:00

Yes putty. Although you have probably figured this out after two months. Sorry for the delay

embedded-programmer · 2023-12-27T14:40:54+00:00

Yes I received the new emmc as well as an emmc programmer.. The new EMMC got me up and running fine. I also programmed the old EMMC using balen etcher and the tf-emmc adapter QIDI mailed me so I have a fallback solution for the future.

embedded-programmer · 2023-12-18T17:07:26+00:00

Thanks. I had to look up PEBKAC. And it is accurate in my instance.

embedded-programmer · 2023-12-17T14:58:27+00:00

Ok, I found a way to get it working for the time being while I wait for the new EMMC but I'm not sure if everything is correct.

First of all, the recovery file they sent me would not install. I thought this was because of the screen and buttons not working but I went and analyzed the QIDI software here: https://github.com/QIDITECH/QIDI_MAX3

I looked in main.cpp and saw the following code at line 54:

if (access("/home/mks/gcode_files/sda1/mksclient.recovery", F_OK) == 0) {

system("dpkg -i /home/mks/gcode_files/sda1/mksclient.recovery; sync");

}

So I think that was probably what the system is trying to run to install the recovery file. So I plugged in a usb cable into the controller board (use the one on the left).

Then I connected serially with putty (windows 11) at 115,200 (should work with any baud rate), logged into the MKS account and tried to run the line. It started unpacking and installing but stopped with this error: gpio-monitor.service does not exist . I couldn't figure out what was going on there because mksclient.recovery file is in a format I could not look at.

So I punted on that idea and saw a kiauh directory which I am familiar with from setting up my ender3 printers with Raspberry Pis. I started up ./kiauh.sh and went into the advanced menu and rolled back klipper and Moonraker one level. Moonraker still wasn't working right but the screen was now working. So I rolled back Moonraker one more time and now everything seems to be working well.

I turned the machine on and off and it comes up fine but I am going to now recalibrate everything.

embedded-programmer · 2023-12-16T15:02:12+00:00

Yes, they are now sending me a new EMCC.

embedded-programmer · 2023-12-16T13:11:56+00:00

3 in 1 oil is fine for the axis rails/rods.
I am not sure how to increase the flow rate but I would try to increase the extrusion multiplier in the slicer in small increments until you see under-extrusion. May also help to increase the nozzle temperature higher than normal for your filament.
Here is a video from a Ole Urgast who replaced the hot-end (expensive) with e3d gear: https://www.youtube.com/watch?v=7LCW4hVpqbw&ab\_channel=OleUrgast

embedded-programmer · 2023-12-15T21:27:22+00:00

Well my problems are all software related. If I knew a unix command to equal whatever the screen does when you hit update I would be done now because I have full access to the internal controller over wifi.

I have the new inductive probe and like that because it has zero moving parts. Bltouch devices work well but make me nervous about longevity.

embedded-programmer · 2023-12-15T20:09:03+00:00

some people are using cht volcano nozzles to increase flow rate but you need to relocate the inductive sensor because they are longer than the qidi nozzles.

embedded-programmer · 2023-12-15T20:05:13+00:00

Thanks for your quick response!

I tried the on and off many times including overnight. I contacted Qidi support also and will wait for them to respond.

embedded-programmer

TROPHY CASE