- Posts: 143
- Thank you received: 0
Please recommend PCI-E Parallel Port card
Please Log in to join the conversation.
PCW wrote: Can you post your hal file? is it possible you are loading some other driver in addition to hal_parport?
If hal_parport works with the card, it should not complain (and if it does, I think thats a bug)
(the 0,1,2 address shortcut will only work if Linux detects the card but this should not matter to hal_parport if the actual parallel port base address is provided)
here is my hal file. this is copied directly from my working box, with the address appended. i dont think the problem is actually in linuxcnc, but in the os itself. it is really weird lspci shows that it is there, but dmsg shows nothing of it being recognized as a parport.
basically, if i give it the address directly, i get an error message on startup that parport not found at [some number which is not the address], but machine responds. if i use the shortcut, then i get similar error, but nothing else...
Attachment not found
Please Log in to join the conversation.
PCW wrote: Plus if you are technically knowledgeable enough to care about distributions its not that difficult to install LinuxCNC on your distribution of choice.
my main issue is always *TIME*
it doesnt really matter tho, because i love linuxcnc and would install it on a turd if that meant not having to use windows!
Please Log in to join the conversation.
- Richard J Kinch
- Offline
- Senior Member
-
- Posts: 61
- Thank you received: 0
jmelson wrote: The ones I sell are marked Syba SD-PEX10005.
Jon's advice is expert, and I and others have confirmed this PCIe parallel port card as a "warrant" (something you can readily buy new at retail today, that is known to work with current LinuxCNC). It is also a well-made board but very low priced.
But please see the qualifications I reported on this expansion card in this thread . One precaution is that "Syba" is not the "make", just an U.S. importer/labeler/marketer of mystery China boards, and part number "Syba SD-PEX10005" does not definitely identify the product "model", because Syba has delivered a variety of at least two physically different boards bearing stickers with this same part number (and this number is just on a sticker, not the board itself, the actual board bears no indication of identity in brand or part number). So "Syba SD-PEX10005" is not a concrete "make and model" specification in the engineering sense (which is the only sense that matters), just a silk-market moniker for what Syba is selling lately. This sloppy Syba version identity is a potential problem, certainly in the past, and who knows if they won't confuse things worse in the future. Being a legacy-support product, with little market, made by careless engineering mimics in developing places, and imported carpet-bazaar style, this is all to be expected.
The factors of the Linux version, LinuxCNC version, and motherboard BIOS are also involved in getting parallel port expansion to work. Also as Jon mentions, the chip has an EEPROM configuration that is invisible to you but has to be set properly at the factory, so you can't know if some "China quality control" mistake was made until you test the board, but you can't do that isolated test if you don't have a known-working reference system already using the board. You can't perform multi-factor diagnosis without isolation and known-good reference capabilities. But this "Syba SD-PEX10005" (with a confirmed version identity) is as safe a "warrant" against surprises and mystery as you can get these days, especially if you source it from Jon and his beneficial specimen-qualifying and testing.
Please Log in to join the conversation.
Please Log in to join the conversation.
hal_parport is a very low level driver, AFAICT it does not need Linux driver
support at all (the port address = 0,1,2 shortcut would but that's about it)
edit: Also, what is the exact warning message?
Please Log in to join the conversation.
andypugh wrote: The attached HAL file says
Is your actual HAL file corrupted like that?Code:loadrt hal_parport cfg="0xe010 outâ€
no, i double checked and it must have gotten corrupted when i uploaded it or transferred it. i double checked on the box to make sure. it is a copy of the original hal file from my working box. the only thing that has been changed is the new address added. right now i have the startech port in it, but here in a few im going back to the shop and going to a complete listing of the error messages and all the exact details complete with pics.
Please Log in to join the conversation.
so here are the files and pics of the cards. the configuration is copied directly from a running machine, the differences are hardware and the old box is running wheezy and the new box is running stretch. it is a fresh install from the live cd, the only change is that it is upgraded to the 2.8 master.
old hardware:
core 2 duo, 2gb ram, onboard parport and pic parport, wheezy
new hardware:
ryzen 5, 8gb ram, syba and startech parports, stretch
originally, on the old box i was using 2.8.0-pre1-4572-g677d7b5 and after i tried the startech card i had unusual behavior (more on that later) so i updated to 2.8.0-pre1-4655-g39977ac31 this morning to eliminate variables. ran as expected.
output from original box:
output from new box with syba card:
PCW wrote: Also, what is the exact warning message?
the error i get when i run linuxcnc:
when i use address "0 out", it crashes on startup with:
i guess my understanding is that even tho the os doesnt recognize it as a true parallel port, linuxcnc can still address it directly? pretty spiffy.
so after i put in the startech card, this is the output:
so now it shows that i have a parallel port, and i can address it either by address or by shortcut, but now i have odd (REALLY BAD) behavior... for the homing sequence (XYZ on a XYYZ gantry), x homes normally, and only y1 homes while y0 is stationary (you can see how that doesnt end well...). luckily y axis was already homed and so only just past switches so no permanent damage done, but linuxcnc was stalled waiting for the homing sequence for y to complete.
while i dont have much knowledge in low level hardware, i was lead to believe that the os handled port to hardware address translation, so regardless of whether the parport is pci or pcie, the os should still see it as a parport and the addresses should still be the same? or am i going to have to redo the config files for the machine?
sorry for the long post, but had a lot of details to get out and thanks for all the replies! just in case, i am including my config directory.
Attachment not found
Attachment not found
Attachment not found
Attachment not found
Attachment not found
Please Log in to join the conversation.
the syba card-
Attachment not found
Attachment not found
Attachment not found
Attachment not found
the startech card-
Attachment not found
Attachment not found
Attachment not found
Please Log in to join the conversation.
it complains, but ultimately it works. dont really trust it tho
when i use address "0 out", it crashes on startup with:
hal_parport makes _no_ use of the linux parallel port driver so as long as the card operates,
it should be fine
( heck, you might be better off if Linux doesn't know about the card )
If the Linux OS did not find the card its expected that the port 0,1,2 shortcut cannot work so
its not a crash, just inability to find the parallel port base address from the OS index
The only case where its necessary for Linux's driver to initialize the card is
with broken parallel port hardware that requires non-standard initialization to work
Please Log in to join the conversation.
