I'm aware of the "not" hal pins but I'm not really a huge fan of using them 
on the daughter card as it's not very intuitive. They're better for an end 
use case if there's an individual input that has an inverted logic. I was 
hoping this could be changed at the driver level.

On Sunday, May 12, 2019 at 8:13:19 AM UTC-4, Charles Steinkuehler wrote:
>
> hostmot2 has both in and in_not pins, just use the one appropriate for 
> your wiring.  There is also an invert_output parameter if you need to 
> invert the output signal: 
>
> http://www.machinekit.io/docs/man/man9/hostmot2/#general-purpose-i-o 
>
> On 5/12/2019 6:21 AM, justin White wrote: 
> > Got another silly question.... 
> > 
> > Is it possible to invert the default state of the GPIO pins? I've found 
> > that pulling them up will bring them true, Hardware wise the easiest way 
> > I've found to make the inputs capable of handling multiple input 
> voltages 
> > will require them to be pulled down when activated, so I'd have to pull 
> > them up to a "false" state. This would only be something I need to do 
> with 
> > the gpio inputs. 
> > 
> > On Friday, May 10, 2019 at 6:40:30 PM UTC-4, Michael Brown wrote: 
> >> 
> >> Ok 
> >> Great to hear you have progress. 
> >> 
> >> On a side note: 
> >> I managed to find the bug in the ADC system and the fix got out into 
> the 
> >> socfpga-rbf deb yesterday.... :-=)   
> >> 
> >> On Friday, 10 May 2019 22:26:13 UTC+2, justin White wrote: 
> >>> 
> >>> When you are laying out your own custom DExx interface board, you 
> don't 
> >>>> have to stay restricted to allready made pinouts. 
> >>> 
> >>> Yeah that I know,  Like I said, I was mostly trying to determine how 
> many 
> >>> pins each tag type used and it's actual usage. I was a bit hung up on 
> the 
> >>> ADC thing because it didn't directly correspond with the pin tags but 
> now I 
> >>> realize it's an SPI interface. 
> >>> 
> >>> I'll have to come back to all of the above info once I try to create 
> the 
> >>> new FPGA project files, for now I think I get the idea. 
> >>> 
> >>> Purging the installed Machinekit packages and installing the new ones 
> as 
> >>> you suggested got HALshow working right away. 
> >>> 
> >>> I've pretty much got my encoder interface and output hardware sorted, 
> I 
> >>> use 24v I/0 but it should handle multiple voltages. 
> >>> 
> >> 
> > 
>
>
> -- 
> Charles Steinkuehler 
> [email protected] <javascript:> 
>

-- 
website: http://www.machinekit.io blog: http://blog.machinekit.io github: 
https://github.com/machinekit
--- 
You received this message because you are subscribed to the Google Groups 
"Machinekit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
Visit this group at https://groups.google.com/group/machinekit.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/machinekit/5b3d2475-8bbd-4e4d-8c52-1e204f246173%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to