ERROR Import Failed, Unsupported file type

[Bob T]

Hi All, this is the message I am receiving when I try to open a program that I made on the same computer just a few weeks ago with, I think, the same software (no upgrade inbetween times)

Am I saving something incorrectly?

[Bob T]

I have versions that are .LOG and .sbp, both get same response. My Shopbot software, also installed on this computer, will open it and give me a demo cut, but I can't edit

[Brady Watson]

Where does the file exist on the computer? Is it on a thumbdrive by any chance?

-B

[Bob T]

Yes, on a thumbdrive

[Brady Watson]

You never want to run a file off of a thumbdrive or network folder. It needs to be somewhere on the C drive. ShopBot has created the C:\SBParts folder for you to place your SBPs, although you can place them anywhere you want.

If you do CAD/CAM work in the house, then bring the TD with you to the shop, you have to copy the files to the hard drive before you run the SBP.

-B

[Bob T]

Thanks Brady. Yes, I do my design inside, and probably often save my toolpaths and split.I will look for the sbparts folder, thanks. I assume that the former work is not recoverable?

[Bob T]

and no, I hadn't seen that folder before. Thanks for the help.

[ckurak]

You never want to run a file off of a thumbdrive or network folder. It needs to be somewhere on the C drive.

-B

Not to be contrary...

Not using network drives makes sense to me. If the net goes down, things will probably go wrong very quickly.

But, why not thumbdrives? I have been running SBP files from thumbdrives for years. No problems experienced.

[bleeth]

I have been running 100 percent of my job files from my design computer in my office networked to the SB computer since I first set up my mill.
If SB opens it in preview, then how are you trying to open it to edit? If you were just double clicking the file you may need to "teach" that computer by right clicking, selecting "open with" and then navigate to notepad. You can open it with the SB software by entering FE in the command window.

[Brady Watson]

Chuck - Many people over the years have experienced ongoing problems from using a TD while running the tool. I've gone out to more than one shop that drained tech support enough to warrant an in person visit...only to find a TD being used to run files on their control computer. Once that was removed, all problems (machine jerkiness, loss of COM) went away.

Most consumer grade computers have cheap/inferior USB hardware that cannot handle pulling data off of a USB TD, process it in SB3 and spit it back out at near real time to the SB onboard controller, and then motors.

Data space is cheap...copy your files over to the hard drive and run them from there. YOU WILL NEVER FILL UP A HARD DRIVE IN YOUR LIFETIME WITH SBP FILES!!!

-B

[ckurak]

Chuck - Many people over the years have experienced ongoing problems from using a TD while running the tool. I've gone out to more than one shop that drained tech support enough to warrant an in person visit...only to find a TD being used to run files on their control computer. Once that was removed, all problems (machine jerkiness, loss of COM) went away.

Most consumer grade computers have cheap/inferior USB hardware that cannot handle pulling data off of a USB TD, process it in SB3 and spit it back out at near real time to the SB onboard controller, and then motors.

Data space is cheap...copy your files over to the hard drive and run them from there. YOU WILL NEVER FILL UP A HARD DRIVE IN YOUR LIFETIME WITH SBP FILES!!!

-B

OK. Fair enough. Thanks for the explanation. Evidently my newer laptop with my older PRT w/4G can handle everything just fine. But, as you stated, other combinations don't work well. So, the advice to avoid running files direct from a TD is valid. I learned something.

BTW, nothing here is named "Chuck" except for the beef at the food store. :)

Thanks!

[bleeth]

Good Morning Brady.
I thought that the SB software brings the file into local RAM or something like that first from wherever it is and runs it from there. Hence the hesitation before it starts the file on larger files and the pause(s) on really big files to "reload".
Not too long ago I was running a very large 3-d file and after it started running I decided to let it go through on the first piece but make some toolpathing changes for the next one. Made the changes in Artcam and then saved the file over the original while it was still running in the shop. When I realized what I had done, I totally freaked, but there was no issue as the control software had already copied the file to it's own temp location for processing.
As I recall, my original PRT controller and software would handle 50k lines of code at once, Gecko upgrade handled around 150k and the Alpha rig now handles several hundred thou.

[Brady Watson]

Dave,
Imagine paying $$$$ for a tech to fly cross country to diagnose your machine because it is stuttering, running unreliably or erratic...and he pulls out the thumb drive you had stuck in the control computer or runs your networked files locally to find that it cured the issue. What a colossal waste of time, money and energy for all involved!

So, I stand by my words: It is poor practice to run SBPs over the network or off of a thumb drive, regardless of machine vintage.

I prefer recommending what is the most reliable for everyone under the heading of 'Best known practices'.

As I have said before, it's your tool...do what you want.

-B

[bleeth]

I don't doubt your experience or general conclusions. I wonder on the thumb drive issues if the particular drives and/or the ports had some kind of secondary software operating due to their use (like a virus checker). Same thing on network files not running right. It could be that I have never had those issues due to having stripped the operating computer of all services not required for operation (Black Vipered)? Something I recommend for all users along with spending the few overall bucks it takes to have a dedicated computer running the mill.

If I had spent the bucks to have a tech fly across the country to check out that problem without trying some obvious solutions first, or if tech had not suggested them before offering on-site analysis, I would in the first case, kick myself soundly and in the second want to know why not? We should all know that since the computer is such a large variable in the overall package, that not only how much power, speed, and ram it has is important, so is how it is configured.

In the case of someone having run their tool for quite some time and then "all of a sudden" having an issue, the first step of analysis has to be: What, if anything, was done different. If they have been using a TD with no issue for some time and now have one, did they change to a different TD? Use a different port? New user? tougher to diagnose without a history, but I would go with you 100% and make sure they tried the files by running them locally before saying I thought they needed a tech site visit, as well as get all the specs of whatever computer and/or hub they were using to drive it. (Do I recall correctly that the newer rigs don't need the powered hub as previously since it no longer needs a serial/USB adapter? I don't know if it helps me or not, but I still use one.)

[Ajcoholic]

Ive always done my my designing at home, and brought my files on the USB drive to the shop. It takes seconds to transfer it to the proper folder in my documents. Then run it. Ive never tried running it directly from the USB drive. But for the time it takes to transfer it to the hard drive, why?

Also, I rely on having the files on two separate computers by backup. Chances of both failing at the same time are slim to none. Especially when one isnt ever hooked up to the internet.