HODGDON Reloading data center is now free online

[40SW]

I read it in the American Rifleman. Sorry if this is redundant., but its too good not to share. Hodgdon reloading data is now free online. Great resource center and FREE!!!
Here is the link. http://data.hodgdon.com/main_menu.asp

 

[IDriveB5]

I believe theyve had this available for a few months. Its really well done and I like having all that data in one spot. Thumbs up for hodgdon.

 

[Walkalong]

I really do not like it all all, but beggers can't be choosers I guess. I liked the old setup much better.

 

[ArchAngelCD]

I like this setup and it's not really that new.

It's great having Hodgdon, Winchester and IMR powder data all in one spot. It makes things a lot easier since those are the powders I prefer to use.

 

[BeJaRa]

it is nice, but it can be a little slow retieving data on occasion.

 

[SASS#23149]

I don't like the new setup either.too slow for my taste.

give us back the old one,please.

 

[Walkalong]

I don't like the new setup either.too slow for my taste.

And heavon help you if you make an error! It won't let you start over and it won't let you use the back button on your browser to get out either! Oh well.

 

[Hawk]

I thought that had been there for some time.

I don't know about the old format but the current one can be pasted into Excel very cleanly. I've got spreadsheets for the cartridges I load. The "Data / Filter / Autofilter" functionality is slicker 'n snail snot.

For some reason, I have problems getting a similar "clean" import from Alliant's site.

 

[45ACPUSER]

Make sure you hit print data to see what primers and brass are being used to generate the data. Brings open another windown that is more detailed, and you do not have to print it.

 

[nitesite]

I use it frequently, and it performs fairly well especially for showing several different powders from three brand names.

But fer chrissake did they have to use a universal receiver .357 Magnum with a ten-inch barrel??????????????????????

 

[kellyj00]

read their mission statement.
Only would a company in Kansas say something like that as part of their business.

I shoot Hodgdon powders almost exclusively for that reason.

 

[USSR]

Not a well thought out reloading data site from a safety standpoint. For example, in .308 Winchester it lists maximum loads of 45.4gr of IMR4895 with a 168SMK and 45.0gr of IMR4895 with a 175SMK, WITHOUT SPECIFYING THE BRASS USED! If someone uses anywhere's near that much powder in LC or IMI brass, they are liable to be in a world of hurt. NEVER give out a load without specifying the brass that was used in load development.

Don

 

[Norton]

I like it because it has a ton of loads that they don't list in their print manual, specifically a 168gr BT for 30'06 and a 175gr BT for 30'06.

Maybe a little clunky, but it works for what I need it for.

 

[RPCVYemen]

And heavon help you if you make an error! It won't let you start over and it won't let you use the back button on your browser to get out either! Oh well.

This may be a reasonable design choice on their part. When you use the browser back button, you are relying on the browser having cached data correctly on your machine (not theirs).

Suppose the browser has a bug in its cache - it shows you the different data than it transmits to them, etc. Then the load they generate might not be from the data you think you have submitted, but from some stale data. Suppose you think you've requested a load for a 255 gr lead bullet, but the cgi script running on the Hodgdon site actually received a request for a 200 gr jacketed bullet?

There are "stale" data issues whenever you use the "back" and "forward" buttons on a browser. You will also notice that many financial sites don't permit you to use the "back" and "forward" buttons - for the same reason. One financial site I used regularly implements their own "back" and "forward" buttons on the web page - that way they can cache the data, and they can be more confident about its validity.

Let me make it clear that I am speculating here - it has been a long time since I wrote any HTML, and there are about a dozen new web site technologies introduced every month, so my notion of what happens on their web site may be all wrong.

But I have notice that many sites with "critical" data will not let you use your browser's "back" and "forward" buttons.

Mike

 

[Ol` Joe]

Not a well thought out reloading data site from a safety standpoint. For example, in .308 Winchester it lists maximum loads of 45.4gr of IMR4895 with a 168SMK and 45.0gr of IMR4895 with a 175SMK, WITHOUT SPECIFYING THE BRASS USED! If someone uses anywhere's near that much powder in LC or IMI brass, they are liable to be in a world of hurt. NEVER give out a load without specifying the brass that was used in load development.

The data is there, you have to hit the print icon as noted in another post to expose it. I don`t know why they don`t offer all the data on the first page but is there along with pressures and COL. They used Winchester cases in their data and Federal primers.

 

[Walkalong]

This may be a reasonable design choice on their part.

Perhaps, but annoying nonetheless.

 

[USSR]

Ah, Yes, there it is. As a computer programmer, all I can say is, what a piss poor design.

Don

 

[RPCVYemen]

Ah, Yes, there it is. As a computer programmer, all I can say is, what a piss poor design.

Do you know enough about HTML/Web design to know if my analysis is correct? Is the driving problem a browser related "stale data" issue?

I haven't worked up in user space for well over a decade - I've been in the kernel. I played with HTML a while back just to see how just to see how it worked. So my analysis may be incorrect.

Without understanding the issues, I agree or disagree with your evaluation of the design. If one of the restraints was: "This module must return valid loads, even when used with browsers that are know to corrupt caches.", then it's very hard to see another way out.

[If you are a commercial programmer, you probably understand that it's very difficult to evaluate a design without understanding the constraints. I have had to do some pretty hideous things for legacy compatibility. Sometimes you just gag and code it the way it needs to be coded.]

Mike

 

[nitesite]

I smell a thread drift coming on.....