Advanced Search

Thank you for the consultation. I came to the same opinion. If I could program a PIC, I would think about converting the 7i84 to a modbus slave.
I will probably buy:
www.turck.us/en/product/6827381
It is not cheap.

I'm sorry, looking at your initial post again I'm not sure where this comes from:

[RS274NGC]
SUBROUTINE_PATH = macros

[MACROS]
MACRO = touch_plate_z

I'm not aware of a '[MACROS]' entry in the ini file.
So try this:

save your subroutine code as 'touch_plate_z.ngc' in a folder named 'macros' in your machine config folder.

then add this to the [RS274] section of your ini file:

Short question, I updated all my machines now to 2.9.3 and moved my modifications to the user tabs.
I thought also adding the setup sheet to my lathe using probe_basic_lathe.
With the mill it is still working on the lathe i get following error:

You might be better off looking at modbus. From my point of view you're looking at making some wholesale changes.
As far as I'm aware SmartSerial seems to be designed as a single device per channel at full duplex.

I'm trying to do the same thing. But the program does not start automatically. Could the problem be that I have an automatic login?

I have the latest version of linuxcnc installed.

SmartSerial is going to need 2.5mbps serial interface to begin with.

I found in manual 7i84:
 

Tho you may want to look into learning at least C.

I like C. I dont like python.

also find ssremote7i90.zip

Thank you, I will study it.

In normal mode, SmartSerial is used so that one serial output serves one SmartSerial device.
Is it possible to use SmartSerial with a modified Master as a bus? I want to use several 7i84.

SmartSerial uses a Full Duplex bus, but I have a Half Duplex bus. Is this a problem?

SmartSerial is going to need 2.5mbps serial interface to begin with.
The smart serial protocol is layed out in most of the mesa manuals.

Looking into the slave (probably the easier way to see how things work)
One of the best places to start is to download one of the 7i90 zip files, this includes the bitstreams for the card and the hostmot sources, within that you'll also find ssremote7i90.zip which is the src for the ssremote portion if you want to use the 7i90 as a ssremote card.
The source is in assembly for one of the softcores on the fpga, it's pretty easy to work out, that's not that many instructions. Convert that to your mcu of choice and you should be good to go. Tho you may want to look into learning at least C.
It took me about 2 weeks to really get a good idea of what was going on, then modify that portion to get that running on a colorlight RV901T board that supports 4 MPGs. A couple of days of that was a silly mistake on my part. It was never my intention to get the code running on a MCU, so I never bothered looking into it.

Ok thats just for the slave portion.
If you want to have a non Mesa Master, you'll have to do all of the above but looking at the slave point of view. Then you would have to come up with a serial device that works at 2.5mbps, and then write a SmartSerial that talks to your setup. Or though you can use 115.2k but that's about 20 times slower.

On top of all that you'll have to design the hardware, PCB boards and buy parts. At the end of the day it will more likely end up not being cost effective.

There's also a couple of other zip files that may be worth looking at.

I think the path or I am doing something  wrong because I am getting this message when I issue the o<touch_plate_z> call
EOF in file :/usr/share/axis/images/axis.ngc
seeking o-word:o<touch_plate_z> from line:0

Awesome. I looked some more and found
net joint.0.output => hm2_[MESA](BOARD).0.pwmgen.00.enable
missing

and these were the same for both the x and the y, so I numbered appropriately.

setp hm2_[MESA](BOARD).0.pwmgen.01.scale [JOINT_​​​​​​​1]SCALE
setp hm2_[MESA](BOARD).0.encoder.01.scale  [JOINT_1]ENCODER_SCALE
setp hm2_[MESA](BOARD).0.pwmgen.01.output-type 1 #PWM pin0

And it seems to be working great now.

This velocity one was missing too, but I didn’t add it. Should I?

net joint-0-vel-fb <=  hm2_[MESA](BOARD).0.encoder.00.velocity

I can’t believe you got back to me and helped me out so quick on the weekend.
I really appreciate the time and the knowledge you guy’s are putting into helping whoever needs it.
Thanks

i have fixed the flash-command, thanks:
github.com/multigcs/riocore/commit/3c532...8bd8f24ff9f27349ae22

Hello,

I bought new toy:
spotpear.com/shop/ESP32-S3R8-4.3inch-LCD...ay-LVGL-800x480.html
 
It is a Develop board for Arduino ESP32 with Display + Half Duplex RS485.

I have a project:
- which is not demanding on speed
- very simple logic
- needs several inputs
- needs a lot of outputs (up to 100)
- I don't want to use a relay for outputs
- 24V

I plan to use some industrial I/O controlled by Modbus RTO for this device.

But quality I/O is very expensive. I would like to use a Mesa 7i84.
Is this even possible?

It would be ideal to use some firmware for the Mesa 7i84 to make it a Modbus slave.
Is this even possible?
The price/quality of the 7i84 is fantastic and the use of this card would expand drastically. However, there is a PIC processor on this card and I don't understand that at all. I can program only Arduino.

The second option is to use an Arduino processor as a SmartSerial Master.
Is this even possible?
There are projects where SmartSerial Slave is used. But I would need a Master.
Would it be possible to use more than one 7i84(with original firmware) on one Half duplex RS485 Master?

Thanks a lot I will first check what you modified in order to understand and confirm no other impact on my setup and then flash the firmware

Those words were said cos I couldn't understand the point you were trying to make.

I don't get what issue you're having with ise.

Are you sourcing /opt/Xilinx/14.7/ISE_DS/settings64.sh before doing anything.

Now what I'm going to say is coming from someone who has worked 95% of his life as either a builders' labourer or civil labourer (roadworks). I dropped out of school at 15 and the closest I've come to any trade qualifications is 3/4 of a carpentry apprenticeship.

I've installed ise 14.7 webpack on a fresh install of mint 21.3 a week or 2 ago on a laptop belonging to rthorntn.

Installed webpack and installed a licence on my bookworm Linuxcnc box this morning, and have been using it for an easy 12 months on my main machine, running Mint 21. This particular machine has been building the mesa firmware I run on my boards.
To say it's trash is utter BS, just cos you can't get it to work is not representative of the software. If you want help to get it setup convey your errors and I'll try to lend a hand, but it sounds like you just wanna put shit on it cos you can't get it working. That's a YOU issue not a ISE issue. I don't think you're a bad person, I just think you're wrong about the software.

openFPGALooader & Sprtan6 boards.
openFPGALoader works fine, tho you really need to read the docs to load the firmware into the SPI chip. It's a 2 stage process that loads a temp bitstream into sram then that config is used to write to the SPI chip (ollie's makefile doesnt address this and it wasn't what I'd call an issue ATM, I just modded the makefile). Ollie's makefile only loads into sram and you lose the config when you remove power.This needs to be done externally from the IDE.
I add this to the MakefileI wouldn't copy and paste that as make does like it's tabs in the right place. This is the bit,xc6slx9tqg144, that tells openfpgaloader to which temp bitstream to load.



For whatever reason openfpgaloader can be a bit flakey on reading the SPI id's and can be a PITA, I think the issue I was having in reading the SPI ID on a certain chip was that it may not have been either 100% error free or it was not genuine. Which kinda surprised me as I bought it from o Aussie guy off ebay. Another issue could be flakey du pont connections, yes we all know better.



I will admit getting the Xilinx DLC9LP USB programmer to work is a pain as is the parallel port programmer (which is a genuine Xilinx product).
The tools aren't rubbish, and just cos they are a few years old doesn't make them stop working.

I've also set rthorntn up with a Spartan6 dev board and a couple of daughter boards, but due to his choice of breakout board I had to design a buffer board as all the IO is via optos on his chosen breakout board.

In all honesty I think old mate is just spending a lot of money to he doesn't have to pay what it would cost to ship a Mesa board to Oz.
This is the second project I've given him assistance with.
Whilst I haven't tried the Gowin hardware route I've messed around with rio on a couple of ICE40 boards and several different Spartan6 boards.

In all honesty I think it would be a waste to give up on your design. I'm gunna guess you've put a good amount of hours routing the board. It would be silly to throw the towel in.

Try:

I came across subroutine example to set my Z probe. But first I wanted to simplify it in order to understand the subroutines.

I have added the following to the machine ini file

[RS274NGC]
SUBROUTINE_PATH = macros

[MACROS]
MACRO = touch_plate_z

and have made a file in the macros directory that have the following statement


o<touch_plate_z> sub
G54 G0 x0 y0
o<touch_plate_z>endsub
M2

what statement I need to enter in the MDI window to execute this subroutine

Good day

Philip