Trivial consideration for this or other upgrades. When hitting the RUN the tool path file fades out. Before hitting Click ‘Continue’ when spindle is up to speed…I always want to double check myself to make sure I changed files before cutting…slightly challenging with 70+ eyes.
Thanks
Also the degree symbol (Alt 0176). Even though name shows up in Explorer view, the file name will not show up in the list on the BB.
Pony
1 Like
I am getting back into the shop after a long absence, is 1.5 almost ready or will there be a beta 4?
@OnefinityCNC any news?
I used it for another project this week. Probing and carving worked fine. I did test estop, but after homing the recalled position was not the previously used work origin. That feature still seems buggy, working sometimes.
1 Like
Is anybody else still testing 1.5 Beta 3, or is it just me? 
I’ve had a few instances where switching tool config between Huanyang spindle and PWM (laser) seems weird, the tool doesn’t spin up or fire until after I reboot. I was helping a friend on a project so I didn’t stop to debug. Just glad I caught it before it continued without a running tool! (other movements were working fine)
Yes I’m having some intermittent wierd things happen as well, like failure for spindle to spin up. Or getting locked in the jogging loop problem. Also my zero seems to change mid program… I’m about to call it with the BB controller honestly.
1 Like
Can you post up any videos of this issue?
Can you post up any videos of this issue?
I’ll try to capture it next time! I was scrambling since i had a guest in the shop with me.
1 Like
ill try but its so random.
1 Like
I used the machine for many hours this weekend with my laser. I didn’t encounter any failures to fire. So that makes me think it’s the changing tool settings between spindle and laser that results in the no-spin-up issues.
I did run into 6 or more times where after gcode finished running, somehow that file would disappear from the dropdown selector. hard refreshing the page wouldn’t help, i’d have to re-upload the file to run it again. My curiousity to investigate lead me to verify using SSH that even when the file was missing from the menu it actually still existed on the filesystem. I ended up deleting all the gcode files and after that it didn’t happen again. As a web dev i’m pretty aware of not using special chars in filenames, but maybe one stuck in, or maybe there’s a max filename length i’m surpassing?
I also get locked in jogging mode if I try to move too soon after a program completes or is paused/stopped. But i understand that’s not a new firmware thing. ( Controller unresponsive after using the pause or stop buttons ) For me when that happens, toggling e-stop on and off and re-homing is necessary to resume normal operation.
If it’s possible, I would reason that blocking jogging input would be beneficial while the yellow “busy” warning is displayed.
1 Like
I ran into a weird issue yesterday when using the touch probe worked fine a few times, then went silly and the probe-z function raised z instead of lowered it! it did it three times in a row, then i rebooted and it worked fine again. But, several carves and runs of the laser worked fine… I can’t explain the weirdness, or recreate it on demand… I’ll probably re-flash on a new sdcard in case mine is starting to flake, but it’s not that old…
1 Like
I assume that 1.5.x will move from beta to being the latest firmware. Will the new rotary require this version to work or will there be a newer version? I’m asking because I wanted to add a spare SD card to my rotary order but wanted it to have the firmware needed to run it. I sent a message to the info people at 1F but they just sent me a link to where I could order a card. Nothing about if the current 1.4.2 firmware is able to be configured for a rotary.
I just made a clean SD reflash of 1.4.2 then updated to 1.5 beta3. After adjusting all the settings and adding all my 12 macros, I don’t know how or what happened but all macros disappeared! Very frustrating!
once you updated and set config did you reboot? reboot before loading your settings back or loading your macros. same things happened to me.
I did restart a few times before loading the macros.
Also another issue I have, I can create a backup when there’s no macros, but if I have macros, I cannot download the file, I get an error message in Chrome saying “Blocked by your organization” although it’s a personal PC…
Not sure how/where to post firmware issues. I am using 1.4.0 but my issue has been in previous versions. (I’ll try 1.5 as soon as official release)
Problem 1: The controller will not load a file that has double parenthesis.
(Sample comment (2nd parenthesis))
Problem2: It seems to ignore G53 at the end of the program.
Here is the end of my file:
N6545 X12.5955 Z0.0691
N6550 X12.5976 Z0.0767
N6555 X12.5992 Z0.0844
N6560 X12.6001 Z0.0922
N6565 X12.6004 Z0.1
N6570 G0 Z0.6
N6575 M5
N6580 M9
N6585 G53 G0 Z0
N6590 G53 G0 X20 Y10 (the line of concern)
N6595 M30
%
Even though the command is absolute coordinates (G53),
while loading file, the simulation will try to go to the G54 origin plus the values given. And will indicate “Over”.
For example, If the offsets are something like X15 Y15 and the program is loaded, end of program will show X15 + X20 exceeds soft limit.
To Onefinity ,
Do you have a release date for this upgrade?
Regards