I redid my system

this is mx linux. https://mxlinux.org/

I ran the new webcontrol.

It no longer gives the missing conf error.

but when I click upgrade to holey- it says upgrade complete but gives same error that my firmware is newer than the firmware included with web control. And still shows ver 1.27 as firmware. And the holey calibration is still grayed out.

Maybe we could upload the holey via arduino ide?

Anyway so I cut the square again and still 6 tall and 5.5/8 wide.

I tried also in linux mint (an ubuntu system said to be most like windows) on a newer laptop system and linux mint blocks the arduino board. It could read the board- but not write to the board. I will have to research why and how to get around it Linux Mint blocking the port. I do know that Linux Mint is not as reliable as MX Linux

It seems Ubunti based distro’s have a tendency blocking the port to USB lots of posts asking for help - solution seems simple just a matter of adding the user to group that can read and write to the board.

https://www.arduino.cc/en/Guide/Linux/#toc5

But I am done for the day. I will mess with this more morrow.

I’ll try to do some testing tomorrow with the single file install. Maybe something is going wrong with it. I generally use the single directory install since I’m running an RPI and don’t want to wait forever for it to unpack the program.

Can you check the Actions tab and verify it looks like this:

image

yes it does look like that.

I can do single directory if you prefer.

Well, I’d prefer, if you don’t mind, we try to sort out what the problem is with the single file (if that’s the problem). I’m going to build a new release that will report additional information during the firmware check routine. I’m befuddled as to why it is saying your firmware version is newer than the one webcontrol supports.

Alright.

Give the new release a shot tomorrow and let me know what appears in the message box when it detects a mismatch.

1 Like

I downloaded the file.

Here are my results:

one. Same error about missing conf file when I try and run upgrade
two. Now I have no left motor.

I unplugged and replugged all cables and still fails.

attached are screen shots

Madgrizzle if it would be easier you can call me.

Apparently the version of avrdude I have on the linux vm is not the newest, so the avrdude.conf file (which apparently is for the newest) is causing issues. So I’ll look into it.

As for the holey calibration being greyed out, your controller is still running the stock firmware (or the ā€˜stock’ holey calibration firmware)… not the one that comes with webcontrol. If it was a webcontrol holey calibration firmware, it would report Controller: 51.27.

We are making progress… just need to figure out how to get the linux vm avrdude updated.

Version 0.910 is out…I feel good about this one… :crossed_fingers:

Well sir I shall try.

1 Like

Ok we were able to upload the holey firmware.

BUT all motors fail now.!

[Screenshot-8|690x387]

(upload://aubQ2v7XzDRV1SFZG9qRzL6c9St.png) Screenshot-10

I tried upgrade to 1.26 and the motors work but are out of wack still.

So I again went back to the holey and though it says it is moving motors it is not. And I did not see any error messages.

Does the sled position move on the screen but the motors do not?

Exactly. And no errors

Though it does fail the motor test. as I posted screenshot above.

It’s possible its in Fake Servo mode. Go to G-Code->Send Custom GCode, Type B99 OFF and click submit.

THAT WORKED. running holey calib now

Great! I went and looked at code while waiting on your response and saw where an issue could come up (eeprom value not being initialized) and went to the main firmware’s repo and saw that @blurfl had made an update to it to avoid that situation. So now I’m working on integrating his update into webcontrol’s holey firmware. But you should be fine without the firmware mod since you initialized the eeprom with the B99 command.

Whew.