Fix Linux GPIO logging

[costas-basdekis]

Description

When enabling GPIO_LOGGING, a code that uses a deprecated version of a macro (MAX3 vs _MAX) is used, that causes a compilation error.

Also updated .gitignore to ignore *_log.csv files in the top directory

Benefits

Fixes GPIO logging

Configurations

#define MOTHERBOARD BOARD_LINUX_RAMPS
#define GPIO_LOGGING

I haven't added a test case, to not increase the duration of tests, but could easily add one

[costas-basdekis]

Also a question: is there a way to visualise the output of IOLogger?

How do you usually use it?

[p3p]

I'm pretty sure no one other than me when I added this platform has ever used it, so there isn't really a response to usually ^^, but when I was using it I used KST2 (https://kst-plot.kde.org/) to visualise the position data in realtime from the csv file,

My intention was to replace this platform with the simulator I'm working on, and a separate cut down Linux realtime platform, what are you currently using it for?

[costas-basdekis]

@p3p I was playing running the Linux implementation on my machine, and I was wondering if there was a way to see what actually happens with the pins. I'd be interested to hear what else you've done on that front, I was thinking maybe a frontend that shows pin state & history, just for the fun of it.

Also, how do you set pins? I tried G28 but of course there's no actual end stops and it just emergency stops.