DI250 setting up a PI3500

[indigit4l]

Jumper... help!

I read about jumper placement and it resetting the device back to DHCP. First I read it was J2 so with the device off I moved it, powered it back up, let it run for a minute, then powered down, moved the jumper back, powered up...

Didn't seem to work, so I read on another board that it was the FACT jumper and did the same process as above. Now I can't seem to get it to print a config sheet to view the IP info. Before I hit, "print test page" and it's print 8 pages of info. Now nothing. Today I get to go back and try and get it better, any ideas?

Below is the Pi3500 pdf and I've searched all the info on jumpers I could find. Could anyone help me find out what is wrong?

[Hansoon]

Pi-3500 uses a dedicated NIC, have lots of them for free but I doubt its worth the postage Germany-USA.

Reset of Pi-3500

Put jumper OP2 on the NIC in FACT position.

-Power up Machine (Interface cable machine-controller should be in place)
-Wait 3 minutes
-Return jumper to its original position
-Switch on machine again and wait until config page comes out, this may take 3-5 minutes. Will show now 0.0.0.0 as new IP-Address.
-Use a crossover patch cable between computer and controller and execute Bootp (Free BOOTP Desktop Download) to set new IP adress by using the MAC address which is labeled on the NIC. Bootp gives usually an error after this but that can be ignored.
Every time you use Bootp you should do the FACT restore first. It will work only one time after reset.

This should do it to set a new IP-address which later on can be modified through the web interface.

Hans

[indigit4l]

ok... better

thanks... turns out i left one of the jumpers (J2) switched in the other position. Now the IP is still the same, 192.168.1.151 (needs to be on 192.168.0.x) but I assume I can still change it as you mentioned. I can get so far as to enter the password through telnet, but then it just kinda hangs and the cursor doesn't do a thing.

using bootp, how do i change the ip? I've entered the MAC address, and what "available options" must I add? Or whatever else? thanks!

[Hansoon]

Go to Admin > Configure and set similar as follows:



Nothing else to be set. Use : as a divider for the subnet mask. Don't try "verify" its not working.

Wait at least 3 minutes to restart machine/controller again and than wait again 2-3 minutes for the new config page to come out with the new IP-address.

Hans

[indigit4l]

almost there

I see what you mean, but I must have a different interface. See pics... this was from the link you put up but also the only one I seem to find available on google.. any other links? Thanks for the fast response

[indigit4l]

working!

Man I was showing somebody how the telnet wasn't letting me in and boom, it started working. I switched it through telnet... I'm still interested in the program though. As an IT guy, I like all the tools I can find. Thanks Hans

[Hansoon]

Perhaps a newer version.

Here's the one I use:

YouSendIt - Send large files - transfer delivery - FTP Replacement

Hans

[indigit4l]

So, I was able to configure everything and just needed it to print to a networked computer...

Pi3500 is the network controller on the Di250 Minolta copier.

Downloading an XP or older driver from their website, and manually selecting it at the "have disk" part of the install (I was sure it was going to reject it and it does), Vista reads it, and asks you to pick from the Di250 driver or the Di350 driver (then hitting Di250, confirm, and it rejects it).

On the other hand, when I pick from the drivers that were available - already from Vista - starting with the manufacturer, I get Minolta, then Pi3500 is the closest match in the right pane.

Surely they're both meant to be networking drivers, but why would one specify the networking controller, and the other the copier? It sort of makes me feel that the copier isn't supported or else Vista would have the Di250 driver. A bit of a leap, I know.

I think what it is is the driver. While Vista is said to be compatible, I don't know. I mean, the copier supports PS and PCL6 so a simple generic tcp/ip driver you think would work, configured as RAW with the same port the printer is set to. I just couldn't get the thing to test print. I deactivated the firewall on the PC... don't think I needed to mess with the airport router, switched around a lot of the options in the driver config settings and nada.

There was quite a bit of chatter I noticed while doing a continuous ping on the printer... it started off almost inaccessible and then after 20 minutes it sort of levelized. Often it would fail to ping, and http would work sporadically. When it did sort of level out, it would get a ping of 3, 5, 4 ms and then 54ms, and repeat, but wouldn't go above 60.

Any ideas? Vista? NIC? I talked to a guy from the environment it was pulled from recently and it worked with the XP computers... my XP laptop died while I was installing the driver... anyways. Any ideas?

[Hansoon]

There's no Vista for this old beast.

Support & Drivers Search Results | Product: Pi3500 / File Type: Drivers / Operating System: Windows 2000/XP

Use RAW with Port 10001

it started off almost inaccessible and then after 20 minutes it sort of levelized. Often it would fail to ping, and http would work sporadically. When it did sort of level out, it would get a ping of 3, 5, 4 ms and then 54ms, and repeat, but wouldn't go above 60.

If so than it looks bit like a NIC problem.

Hans

[indigit4l]

Thank you, I will take this under advisement and let them know that that's what it probably is. I appreciate the help, and I'll update if I get it owrking on my XP laptop